Re: [tor-relays] Exits lost their function

2018-02-11 Thread Roger Dingledine
On Sun, Feb 11, 2018 at 11:55:44AM +0100, Paul wrote: > > (A) Correct, we recently changed it so both 80 and 443 are required: > > https://bugs.torproject.org/23637 > > Thank you for that explanation - how long should it take to get the >exit flag back when opening port 80 ? How long *should* it

Re: [tor-relays] Exits lost their function

2018-02-11 Thread Paul
Am 09.02.2018 um 19:41 schrieb Roger Dingledine: > On Fri, Feb 09, 2018 at 07:37:09PM +0100, niftybunny wrote: >> Minimum is: >> >> accept *:53 >> accept *:80 >> accept *:443 > > (A) Correct, we recently changed it so both 80 and 443 are required: > https://bugs.torproject.org/23637 > > --Roge

Re: [tor-relays] Exits lost their function

2018-02-11 Thread nusenu
> It's a good mystery. :) Maybe we can find more recent situations where > directory authorities completely left out the Exit flags from their votes? thanks for your analysis. maybe we can DocTor checks for this and graphs on consensus-health https://lists.torproject.org/pipermail/tor-dev/2018-Fe

Re: [tor-relays] Exits lost their function

2018-02-10 Thread Roger Dingledine
On Sat, Feb 10, 2018 at 11:37:00PM +, nusenu wrote: > | 0.3.1.9 | Bifroest | > | 0.3.2.9 | bastet | bridge dirauth Careful, it's Bifroest that's the bridge auth. bastet is just a normal v3 auth. > I'm curious: > Why did this change come into effect after only 3/9 hav

Re: [tor-relays] Exits lost their function

2018-02-10 Thread nusenu
niftybunny: > The thing is, someone should scan all relays and inform them that their exit > flag is gone. We need every exit we can get. thank you for your input - I sent out that other email to address it (luckily we do not need to scan to gather that kind of data). So back to my question:

Re: [tor-relays] Exits lost their function

2018-02-10 Thread niftybunny
The thing is, someone should scan all relays and inform them that their exit flag is gone. We need every exit we can get. > On 11. Feb 2018, at 00:37, nusenu wrote: > > >> so on that day I guess dir auths updated to the version enforcing >> 80+443 for exit flag > > >

Re: [tor-relays] Exits lost their function

2018-02-10 Thread nusenu
> so on that day I guess dir auths updated to the version enforcing > 80+443 for exit flag to confirm this: Dir Auth Tor versions as of 2018-01-19 13:00 +---++ | tor_version | nickname | +---++ | 0.3.1.9 | dannenberg | | 0

Re: [tor-relays] Exits lost their function

2018-02-09 Thread Roger Dingledine
On Fri, Feb 09, 2018 at 07:37:09PM +0100, niftybunny wrote: > Minimum is: > > accept *:53 > accept *:80 > accept *:443 (A) Correct, we recently changed it so both 80 and 443 are required: https://bugs.torproject.org/23637 (B) Port 53 has nothing to do with the exit flag, and it goes mostly unuse

Re: [tor-relays] Exits lost their function

2018-02-09 Thread nusenu
niftybunny: > reject 80 > > Thats why. good catch :) yes, I can confirm that, but it was already there on 2018-01-19 13:00 so on that day I guess dir auths updated to the version enforcing 80+443 for exit flag -- https://mastodon.social/@nusenu twitter: @nusenu_ signature.asc Descriptio

Re: [tor-relays] Exits lost their function

2018-02-09 Thread niftybunny
Minimum is: accept *:53 accept *:80 accept *:443 > On 9. Feb 2018, at 19:35, Paul wrote: > > > > Am 09.02.2018 um 19:28 schrieb niftybunny: >> reject 80 >> >> Thats why. > > > Was there a change of rules on that day? > Reject 80 was always the case in those settings. > > >> >>> On 9. F

Re: [tor-relays] Exits lost their function

2018-02-09 Thread Paul
Am 09.02.2018 um 19:28 schrieb niftybunny: > reject 80 > > Thats why. Was there a change of rules on that day? Reject 80 was always the case in those settings. > >> On 9. Feb 2018, at 19:25, nusenu wrote: >> >> >> >> Paul: >>> What could bring several exits at different providers and diffe

Re: [tor-relays] Exits lost their function

2018-02-09 Thread niftybunny
reject 80 Thats why. > On 9. Feb 2018, at 19:25, nusenu wrote: > > > > Paul: >> What could bring several exits at different providers and different >> operating systems (Linux and FreeBSD) down on the same day, Jan 21st? >> >> Since, while they still run as relays, they don’t show as exits

Re: [tor-relays] Exits lost their function

2018-02-09 Thread nusenu
Paul: > What could bring several exits at different providers and different operating > systems (Linux and FreeBSD) down on the same day, Jan 21st? > > Since, while they still run as relays, they don’t show as exits any more > without any change from my side. > > They do run on Tor 0.3.1.9 or

Re: [tor-relays] Exits lost their function

2018-02-09 Thread David Goulet
On 09 Feb (19:06:23), Paul wrote: > What could bring several exits at different providers and different operating > systems (Linux and FreeBSD) down on the same day, Jan 21st? > > Since, while they still run as relays, they don’t show as exits any more > without any change from my side. > > The

[tor-relays] Exits lost their function

2018-02-09 Thread Paul
What could bring several exits at different providers and different operating systems (Linux and FreeBSD) down on the same day, Jan 21st? Since, while they still run as relays, they don’t show as exits any more without any change from my side. They do run on Tor 0.3.1.9 or 0.3.2.9 in the same F