Re: [tor-relays] why the network lost 350 relays and some, bridges
I was intrigued by the high number of consumer IP's that these relay are supposed to be running on while seemingly automated updating the relay version. The nickname made me look into Ubuntu Snaps as a possible tor distribution which led me to this snap: https://snapcraft.io/tor-middle-relay. It was last updated the 9th of January and when you download the stable snap it is actually named 'snap269'. So the maintainer in this case is the snap maintainer, but not necessarily the relay(s) operator. I have not looked into how these snaps actually work but it may be the case that they actually needed the PortForwaring functionality to get tor running inside a snap. Given that information it could very well be the case that these relays are not running behind a NAT and not run by the same operator but actually by a group of different people.
On 1/12/19 11:08 AM, Argo2 wrote:
It was last updated the 9th of January and when you download the stable snap it is actually named 'snap269'.
Just FWIW this is incremented to snap270: https://metrics.torproject.org/rs.html#details/93156A27C9B035C488678E98FE415... -- Toralf PGP C4EACDDE 0076E94E
Toralf Förster:
Just FWIW this is incremented to snap270:
the number in the relay nickname is just the $SNAP_REVISION https://bazaar.launchpad.net/~privacy-squad/+junk/tor-middle-relay-snap/revi... -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
Argo2:
we are well aware of the source of that package (see previous threads on this ML)
I was not trying to suggest that package maintainer and relays maintainer are the same entity (Chad, the snap maintainer is on this list)
I doubt that. the demonstrated effect of removing the portforwarding functionality temporarily and their reverse DNS names suggest that they are mostly behind consumer grade Internet uplinks. -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
participants (3)
-
Argo2 -
nusenu -
Toralf Förster