<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On 30 Jun 2018, at 09:27, I <<a href="mailto:beatthebastards@inbox.com">beatthebastards@inbox.com</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta content="INBOX.COM" name="GENERATOR">
<div>The installation guide <a href="https://www.torproject.org/docs/debian.html.en">https://www.torproject.org/docs/debian.html.en</a> points to a dead end if you choose the experimental version because it hasn't been changed to 0.3.4.x.</div></div></blockquote><div><br></div><div>Here's the existing ticket:</div><div><a href="https://trac.torproject.org/projects/tor/ticket/26474">https://trac.torproject.org/projects/tor/ticket/26474</a></div><div><br></div><div>I've cc'd hiro, who merges website patches.</div><br><blockquote type="cite"><div><div>The torrc that comes with 0.3.4.x is from 2013.</div></div></blockquote><div><br></div>Tor configs haven't changed much since 2013.<br><br><div>And that's deliberate: every time we update the minimal torrc, package managers</div><div>ask operators if they want to overwrite their existing torrc, and some operators</div><div>say "yes". Then they wonder why their relays break.</div><div><br></div><div>Instead, we have:</div><div><a href="https://gitweb.torproject.org/tor.git/tree/src/config/torrc.minimal.in-staging">https://gitweb.torproject.org/tor.git/tree/src/config/torrc.minimal.in-staging</a></div><div>And:</div><div><a href="https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in">https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in</a></div><div><br></div><div>We'll push a torrc.minimal update when there are enough changes, or when</div><div>there's a critical update. (We try to make the torrc code backwards compatible,</div><div>so that doesn't happen very often.)</div><div><br></div><div>T</div></body></html>