>> [1] is not maintained since a long time. >> I'm curious what the reason for assigning the badexit flag to [2] >> was. If you know anything about it and can share something, that would >> be great. >> >> [2] https://atlas.torproject.org/#search/flag:badexit >> >> 37.221.171.234 75FCEA0BE7A2A472669352A1F0F2E59F99C6A3AA >> 37.221.171.237 128814837EC27F20D76EBDDB2CB3AB70258F0BA8 > > It was badexited in October 2015, with the reason "rewrite HTTP requests > to port 8123". > > That's the polipo port, so I wonder if they were running some sort of > polipo + broken iptables setup. > > There were a pile of exit relays around that address, all messing with > exit traffic on that port, and most of them have disappeared since then. Thank you for that info. I see the majority of dirauths removed the badexit flag now for relay: 128814837EC27F20D76EBDDB2CB3AB70258F0BA8 Was that because it was a long time ago or because it is no longer an exit (reject *:* exit policy)? https://lists.torproject.org/pipermail/tor-consensus-health/2017-September/008151.html -- https://mastodon.social/@nusenu https://twitter.com/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