On 09/05/2016 01:19 PM, AKASH DAS wrote:
> If I have to make any patch in the code, do I have to submit it in this
> mailing list or https-everywhere's mailing list? Just a doubt
What are you trying to patch? If you are trying to add a URL to their
whitelist, you don't need to submit a patch as th
If I have to make any patch in the code, do I have to submit it in this
mailing list or https-everywhere's mailing list? Just a doubt
On Mon, Sep 5, 2016 at 10:35 PM, David Fifield
wrote:
> On Mon, Sep 05, 2016 at 10:28:26PM +0530, AKASH DAS wrote:
> > Can I know the issues that are currently in
On Mon, Sep 05, 2016 at 10:28:26PM +0530, AKASH DAS wrote:
> Can I know the issues that are currently in https everywhere.
I don't know if this is what you're looking for, but here are some open
bug tracker tickets.
https://trac.torproject.org/projects/tor/query?status=!closed&component=HTTPS+Eve
On 09/05/2016 12:58 PM, AKASH DAS wrote:
> Can I know the issues that are currently in https everywhere.
This is the mailing list for Tor development, so you may want to
redirect your question to the EFF or some different channel.
HTTPS Everywhere has been really smooth for me and I've actually n
Respected all,
Can I know the issues that are currently in https everywhere.
--
*Akash Das*
*Student Systems Admin*
*Indian Institute Of Information Technology*
*Sricity*
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torprojec
On Fri, Apr 24, 2015 at 08:05:43PM -0700, Mike Perry wrote:
> ** Sure, there could be a pile of new attribute flags that could be set
> on every HTML resource tag that says the resource must use a "secure
> http:" channel if the parent document happened to load over a secure
> channel, but the net
To be clear, Tim is talking about "HTTPS Everywhere" in general, not the
browser extension!
On 4/24/15 8:05 PM, Mike Perry wrote:
Maciej Soltysiak:
http://www.w3.org/DesignIssues/Security-NotTheS.html
The problem with his argument is that the web (and any protocol, really)
needs a way to dem
Maciej Soltysiak:
> http://www.w3.org/DesignIssues/Security-NotTheS.html
The problem with his argument is that the web (and any protocol, really)
needs a way to demand a hard guarantee that a request must proceed over
a secure transport layer. If that layer is not available, the request
must fail.
http://www.w3.org/DesignIssues/Security-NotTheS.html
Maciej
___
tor-dev mailing list
tor-dev@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
This might be a good use for the Alternate-Protocol header currently
used by Chrome to allow opportunistic upgrade from HTTP to SPDY.
See also the Alt-Svc header proposed by the HTTPbis WG earlier this year.
___
tor-dev mailing list
tor-dev@lists.torproj
Nov 2014, at 23:00, tor-dev-requ...@lists.torproject.org wrote:
> Date: Mon, 03 Nov 2014 00:12:53 -0600
> From: Jeremy Rand
> To: tor-dev@lists.torproject.org, https-everywhere
> , namec...@googlegroups.com
> Subject: Re: [tor-dev] [HTTPS-Everywhere] "darkweb everywhere"
&g
On Mon, Nov 03, 2014 at 05:48:03AM +, yan wrote:
> +tor-dev. tl;dr: Would be nice if there were an HTTP response header
> that allows HTTPS servers to indicate their .onion domain names so that
> HTTPS Everywhere can automatically redirect to the .onion version in the
> future if the user choos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Yan,
Namecoin would definitely be interested in something similar (we were
actually discussing the possibility of exactly this yesterday). Maybe
we could produce a list of relevant projects that would benefit from
this? (The three that come to mi
+tor-dev. tl;dr: Would be nice if there were an HTTP response header
that allows HTTPS servers to indicate their .onion domain names so that
HTTPS Everywhere can automatically redirect to the .onion version in the
future if the user chooses a "use THS when available" preference.
I imagine the head
On 2014-07-08 12:47, Yan Zhu wrote:
> (resending to tor-dev with tp.o email address)
>
> On 07/08/2014 03:42 AM, Yan Zhu wrote:
>> On 07/08/2014 12:07 AM, Jeroen Massar wrote:
>>> On 2014-07-07 20:40, Red wrote:
>>> [.. lots of cool work being worked on ..]
>>>
>>> Hi Zack,
>>>
>>> Seems you are d
org/show_bug.cgi?id=685852#c0
>
>
>> ___
>> tor-dev mailing list
>> tor-dev@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>>
>
>
>
>
>
t; you could disable ruleset updates and just wait for the next HTTPS
> Everywhere release.
>
> -Yan
>
>>
>> Greets,
>> Jeroen
>>
>> ___
>> tor-dev mailing list
>> tor-dev@lists.torproject.org
&
(Trying again with my tp.o email address)
On 06/15/2014 02:05 PM, Yan Zhu wrote:
> It's unclear whether this message went through to tor-dev (can't find it
> in the archives), but I've added this update to
> https://trac.torproject.org/projects/tor/wiki/doc/gsoc.
>
> On 06/13/2014 05:06 PM, Red w
18 matches
Mail list logo
