2

Does anyone know if it's possible to configure Tor Browser to exclude circuits with exit relays whose hostnames contain "tor"?

For example, these exit relays are unwanted:

Host Name: arachnidefr94.torproxy-readme-arachnide-fr-35.fr
Host Name: tor-exit.nabnut.net
Host Name: tor18.anonymizer.ccc.de

Exit relays such as these are desired:

Host Name: atlantic480.us.unmetered.com
Host Name: hosted-by.snelis.com
Improve this question
3
  • One could achieve this by hard coding exit relays with "tor" in their hostnames in "ExcludeExitNodes node,node,…". But that would be a long list, and would require getting the nickname for each offending hostname. Or does "ExcludeExitNodes" accept hostnames? Better yet, does it accept wildcards?
    – mirimir
    Commented Jun 21, 2014 at 7:36
  • Just out of curiosity: Why do you want to achieve this?
    – MacLemon
    Commented Jun 22, 2014 at 12:57
  • Maybe it's to avoid blocking. But I doubt that it would help, because some blacklists include all known Tor exit nodes.
    – mirimir
    Commented Jun 24, 2014 at 7:54

1 Answer 1

Reset to default
1

After looking through the Tor manual I've come to the conclusion that blocking exit relays using a wildcard such as *tor* isn't possible using only regular configuration options.

It is possible to exclude individually named exit relays, however, using the ExcludeNodes or ExcludeExitNodes configuration options. If you try to use a wildcard, however, it fails.

i.e., You can do:

ExcludeExitNodes tor-exit.nabnut.net

But you can't do [the Tor browser refuses to start]:

ExcludeExitNodes *tor*

You might want to request this feature on tor-dev.

Improve this answer
1
  • One could use a script that: 1) got a list of exit nodes; 2) grepped those containing tor; and 3) updated an ExcludeExitNodes line in torrc. But maybe there's a length limit to options specified in torrc?
    – mirimir
    Commented Aug 22, 2014 at 3:02

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .