> 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.3.1.9 | longclaw | | 0.3.1.9 | dizum | | 0.3.1.9 | gabelmoo | | 0.3.1.9 | Bifroest | | 0.3.1.9 | Faravahar | | 0.3.1.9 | maatuska | | 0.3.2.9 | tor26 | | 0.3.3.0-alpha-dev | moria1 | | 0.3.2.9 | bastet | bridge dirauth +-------------------+------------+ Dir Auth Tor versions as of 2018-01-20 12:00 An hour after you lost the exit flag: +-------------------+------------+ | tor_version | nickname | +-------------------+------------+ | 0.3.1.9 | dannenberg | | 0.3.1.9 | longclaw | | 0.3.1.9 | dizum | | 0.3.1.9 | Bifroest | | 0.3.1.9 | Faravahar | | 0.3.1.9 | maatuska | | 0.3.2.9 | gabelmoo | | 0.3.2.9 | tor26 | | 0.3.3.0-alpha-dev | moria1 | | 0.3.2.9 | bastet | bridge dirauth +-------------------+------------+ I'm curious: Why did this change come into effect after only 3/9 having the change deployed? Are only a subset of dir auths responsible for voting about the exit flag? thanks! the change was in 0.3.2.9: > Minor features (directory authority): > > Make the "Exit" flag assignment only depend on whether the exit > policy allows connections to ports 80 and 443. Previously relays > would get the Exit flag if they allowed connections to one of these > ports and also port 6667. Resolves ticket 23637. -- https://mastodon.social/@nusenu twitter: @nusenu_
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays