[tor-dev] Design for onionsite certification and use with Let's Encrypt

Ben Laurie ben at links.org
Wed Aug 26 08:07:53 UTC 2015

On Mon, 24 Aug 2015 at 19:25 Paul Syverson <paul.syverson at nrl.navy.mil>

> If another browser it could be a setup config option whether clients
> can choose to be redirected via tor2web or simply always sent to a
> route-insecure address. I will assume for simplicity that all requests
> for route-insecure addresses by other browsers simply send to a
> route-insecure HTTPS address in the ruleset (if available). I'm going
> to also assume that requests for onion addresses for other browsers
> simply fail, although if the tor2web option was available and chosen
> at the time of setup, then there is another question how to offer this
> to the client, perhaps as an HTTPS Everywhere setting.  Comments on
> the feasibility, usefulness, design etc. of the tor2web option would
> be bonus, but of course I'm most wanting to know about the viability
> of the most basic version of things.

Reading this made me wonder if there's a local HTTP Tor proxy, but a quick
search didn't find one. Is there one? If not, why not?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20150826/83879e08/attachment.html>

More information about the tor-dev mailing list