Re: [tor-relays] fix this please (debian repo documentation 0.3.3 -> 0.3.4)
I: > nusenu wrote: >> https://lists.torproject.org/pipermail/tor-dev/2018-June/013244.html > >> > That may be so but the reason I brought this up was because the > downloading of 0.3.3 failed and someone might give up at that point. the referenced email just contains my reasoning for why this should be fixed and how I would like it to be fixed -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] fix this please (debian repo documentation 0.3.3 -> 0.3.4)
nusenu wrote: > https://lists.torproject.org/pipermail/tor-dev/2018-June/013244.html That may be so but the reason I brought this up was because the downloading of 0.3.3 failed and someone might give up at that point. Rob ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] fix this please (debian repo documentation 0.3.3 -> 0.3.4)
https://lists.torproject.org/pipermail/tor-dev/2018-June/013244.html -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] fix this please
Teor >> Tor configs haven't changed much since 2013.>And that's deliberate: every time we update the minimal torrc, package managers>ask operators if they want to overwrite their existing torrc, and some operators>say "yes". Then they wonder why their relays break. Thanks Teor,I only thought that was important because I believe I have read here that torrc should be the latter version.Rob ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] fix this please
> On 30 Jun 2018, at 09:27, I wrote: > > The installation guide https://www.torproject.org/docs/debian.html.en points > to a dead end if you choose the experimental version because it hasn't been > changed to 0.3.4.x. Here's the existing ticket: https://trac.torproject.org/projects/tor/ticket/26474 I've cc'd hiro, who merges website patches. > The torrc that comes with 0.3.4.x is from 2013. Tor configs haven't changed much since 2013. And that's deliberate: every time we update the minimal torrc, package managers ask operators if they want to overwrite their existing torrc, and some operators say "yes". Then they wonder why their relays break. Instead, we have: https://gitweb.torproject.org/tor.git/tree/src/config/torrc.minimal.in-staging And: https://gitweb.torproject.org/tor.git/tree/src/config/torrc.sample.in We'll push a torrc.minimal update when there are enough changes, or when there's a critical update. (We try to make the torrc code backwards compatible, so that doesn't happen very often.) T___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] fix this please
The installation guide https://www.torproject.org/docs/debian.html.en points to a dead end if you choose the experimental version because it hasn't been changed to 0.3.4.x.The torrc that comes with 0.3.4.x is from 2013. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
