[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-talk] TorBirdy doesn't work with Gmail?
-----BEGIN PGP SIGNED MESSAGE-----
> The issue is that we're scraping
> http://exitlist.torproject.org/exit-addresses and, for example,
> 184.108.40.206 does not appear in that list. However, it is listed on
> torstatus.blutmagie.de and apparently it is exiting traffic.
I suppose it is a timing/delay issue since 220.127.116.11 is included in
the current version of
> I am not sure how such confusion can arise. Doesn't Tor rely on
> centralised directory servers to find exit nodes? Why would a node
> appear in one list but not another? Is it expected that the
> official exit list is incomplete?
Generally speaking you can never say that a user that is coming from
an IP address that is *NOT* listed as an exit node is *NOT* coming
This is because Tor exit relays might use separate IP addresses on
inbound and outbound traffic.
The inbound address is announced and can be found in the consensus but
the outbound traffic (the one gmail.com will see) is not necessarily
the one that can be found in the consensus if a server is specifically
configured to do so or if he is behind a NAT.
So I would suggest to allow *ANY* IP address as soon as you know that
the actual user specifically opted-in to be a "Tor gmail user" (if the
user completed one of your two options described) - any other approach
will only mean trouble for Tor users on the long run.
thanks for bringing this up here!
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
tor-talk mailing list