Skip to content

GitLab

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

Open
Opened by Roger Dingledine@armaReporter

excludeexitnodes by ip misleading when exit relay uses outboundbindaddress

In legacy/trac#3143 (moved) we have a user who tried to set ExcludeExitNodes with an IP address based on the address of his Tor traffic. It didn't work, because the exit relay in question exits from a different IP address than it advertises in its descriptor.

My first answer was "well, you should be excluding exit nodes by fingerprint". But that isn't a very satisfactory answer.

We could have the descriptors (and microdescriptors, ugh) or the consensus mention alternate IPs for this purpose.

It was easy for me to look up because moria1's cached-descriptor file says

@uploaded-at 2011-05-09 17:38:43
@source "66.249.9.107"
router ecksnet 66.249.9.183 80 0 0

but that isn't going to be so easy for others.

There's also the tor bulk exit lists: https://metrics.torproject.org/data.html#exitlist which have this clause for the relay in question:

ExitNode 07E9456ED300CABCE2549119FE5B3CC27DA55585
Published 2011-05-10 11:39:28
LastStatus 2011-05-11 06:04:20
ExitAddress 66.249.9.107 2011-05-10 12:33:34

but that's not exactly easier for users to know about or use either.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information