Re: [tor-dev] Proposal 273: Exit relay pinning for web services

On Wed, Oct 5, 2016 at 4:09 PM, Philipp Winter wrote: > Also, Tor Browser MUST abort the ERP procedure if the HTTPS > certificate is not signed by a trusted authority. This is a problem for independant sites that choose not to pay the CA cabal, deal with what free CA will be

Re: [tor-dev] Proposal 273: Exit relay pinning for web services

I think directing users to an onion service would be significantly simpler and better in several regards. Aside from the 'onion severs can't get DV SSL certs' problem are there others Yawning or I have not mentioned? As far as the proposal goes itself, I agree with Roger that the problem of user

Re: [tor-dev] Proposal 273: Exit relay pinning for web services

Philipp Winter: > The proposal is in draft state. We have several open questions that we > are still wrestling with in Section 2.6. Any feedback is greatly > appreciated. You can track the evolution of our proposal online: > Hi Philipp, It

Re: [tor-dev] Proposal 273: Exit relay pinning for web services

Won't comment on the entire content because I have one big comment which refers to the entire proposal or better say the concept of the proposal. I would reject this proposal's concept, because we have o excuse to over-engineer and complicate things in this manner. This is just too complicated

[tor-dev] Tor Relays on Whonix Gateway

Should Whonix document/encourage end users to turn clients into relays on their machines? ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Re: [tor-dev] Proposal 273: Exit relay pinning for web services

On 05/10/16 21:09, Philipp Winter wrote: >Web servers support ERP by advertising it in the "Tor-Exit-Pins" HTTP >header. The header contains two directives, "url" and "max-age": > > Tor-Exit-Pins: url="https://example.com/pins.txt;; max-age=2678400 > >The "url" directive points