<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><br><div>On 15 Oct 2017, at 04:08, Alec Muffett <<a href="mailto:alec.muffett@gmail.com">alec.muffett@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div class="gmail_quote">On 14 October 2017 at 19:43, dawuud <span dir="ltr"><<a href="mailto:dawuud@riseup.net" target="_blank">dawuud@riseup.net</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" preoffsettop="39">
Plaintext communications intermediaries like tor2web violate the end<br>
to end principle and the principle of least authority. If we as the<br>
Tor community are committed to human rights then it follows we would<br>
abolish terrible things like tor2web or at least frown upon it's use.<br></blockquote></div><div><br></div><div><br></div><div>I would recommend continuing to enable/support Tor2Web, or at least not moving to make such a solution inoperable.</div></div></blockquote><br><div>v2 onion service Tor2web would be easy for HSDirs to block, due to an</div><div>implementation bug. We've chosen not to block it. But we haven't spent</div><div>much time on fixing its bugs, either.</div><div><br></div><div>As far as I am aware, no-one is writing Tor2web for v3 onion services.</div><div><br></div><div>We have open tickets for protecting relays that handle onion service traffic</div><div>from knowing both the client and service IP address.</div><div><br></div><div><span style="background-color: rgba(255, 255, 255, 0);">So if anyone does write v3 Tor2web, they will need to write it so it:</span></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">* uses a 3-hop path for all descriptors, because otherwise </span><span style="background-color: rgba(255, 255, 255, 0);">that can be used</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"> for a selective denial of service;</span></div></div><div><span style="background-color: rgba(255, 255, 255, 0);">* uses a 3-hop path to connect to intro and rend when a descriptor has the</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"> single onion service flag;</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">* retry using a 3-hop path on failure (internal reachability or actual connection</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"> failure)</span></div><div><br></div><div>And I'm not sure whether we would merge this feature into core tor, due to the</div><div>user security issues that David and others have mentioned.</div><div><br></div><div>T</div></body></html>