||2 days ago|
|.gitignore||3 weeks ago|
|README.md||2 days ago|
|exclude_badExits.bash||2 days ago|
|exclude_badExits.py||2 days ago|
|exclude_badExits.txt||2 days ago|
|support_onions.py||2 days ago|
|trustor_poc.py||4 days ago|
This extends nusenu's basic idea of using the stem library to dynamically exclude nodes that are likely to be bad by putting them on the ExcludeNodes or ExcludeExitNodes setting of a running Tor.
The basic idea is to exclude Exit nodes that do not have ContactInfo:
That can be extended to relays that do not have an email in the contact, or to relays that do not have ContactInfo that is verified to include them. But there's a problem, and your Tor notice.log will tell you about it: you could exclude the relays needed to access hidden services or mirror directories. So we need to add to the process the concept of a whitelist. In addition, we may have our own blacklist of nodes we want to exclude, or use these lists for other applications like selektor.
So we make two files that are structured in YAML:
/etc/tor/yaml/torrc-goodnodes.yaml --- GoodNodes: EntryNodes:  Relays: # ExitNodes will be overwritten by this program ExitNodes:  IntroductionPoints:  # use the Onions section to list onion services you want the # Introduction Points whitelisted - these points may change daily # Look in tor's notice.log for 'Every introduction point for service' Onions:  # use the Services list to list elays you want the whitelisted # Look in tor's notice.log for 'Wanted to contact directory mirror' Services:  By default all sections of the goodnodes.yaml are used as a whitelist. Use the GoodNodes/Onions list to list onion services you want the Introduction Points whitelisted - these points may change daily Look in tor's notice.log for warnings of 'Every introduction point for service' ```--hs_dir``` ```default='/var/lib/tor'``` will make the program parse the files named ```hostname``` below this dir to find Hidden Services to whitelist. The Introduction Points can change during the day, so you may want to rerun this program to freshen the list of Introduction Points. A full run that processes all the relays from stem can take 30 minutes, or run with: ```--saved_only``` will run the program with just cached information on the relats, but will update the Introduction Points from the Services. /etc/tor/yaml/torrc-badnodes.yaml BadNodes: # list the internet domains you know are bad so you don't # waste time trying to download contacts from them. ExcludeDomains:  ExcludeNodes: # BadExit will be overwritten by this program BadExit:  # list MyBadExit in --bad_sections if you want it used, to exclude nodes # or any others as a list separated by comma(,) MyBadExit: 
(You may have to run this as the Tor user to get RW access to /run/tor/control, in which case the directory for the YAML files must be group Tor writeable, and its parent's directories group Tor RX.)
Because you don't want to exclude the introduction points to any onion
you want to connect to,
--white_onions should whitelist the
introduction points to a comma sep list of onions; we fixed stem to do this:
Use the GoodNodes/Onions list in goodnodes.yaml to list onion services you want the Introduction Points whitelisted - these points may change daily. Look in tor's notice.log for 'Every introduction point for service'
notice_log will parse the notice log for warnings about relays and
services that will then be whitelisted.
--torrc_output will write the torrc ExcludeNodes configuration to a file.
--good_contacts will write the contact info as a ciiss dictionary
to a YAML file. If the proof is uri-rsa, the well-known file of fingerprints
is downloaded and the fingerprints are added on a 'fps' field we create
of that fingerprint's entry of the YAML dictionary. This file is read at the
beginning of the program to start with a trust database, and only new
contact info from new relays are added to the dictionary.
Now for the final part: we lookup the Contact info of every relay
that is currently in our Tor, and check it the existence of the
well-known file that lists the fingerprints of the relays it runs.
If it fails to provide the well-know url, we assume its a bad
relay and add it to a list of nodes that goes on
(not just ExcludeExitNodes
). If the Contact info is good, we add the list of fingerprints to ExitNodes```, a whitelist of relays to use as exits.
--bad_on We offer the users 3 levels of cleaning:
- clean relays that have no contact
- clean relays that don't have an email in the contact (implies 1)
- clean relays that don't have "good' contactinfo. (implies 1)
The default is
NoEmail is inherently imperfect
in that many of the contact-as-an-email are obfuscated, but we try anyway.
To be "good" the ContactInfo must:
- have a url for the well-defined-file to be gotten
- must have a file that can be gotten at the URL
- must support getting the file with a valid SSL cert from a recognized authority
- (not in the spec but added by Python) must use a TLS SSL > v1
- must have a fingerprint list in the file
- must have the FP that got us the contactinfo in the fingerprint list in the file.
--wait_boot is the number of seconds to wait for Tor to booststrap
--wellknown_output will make the program write the well-known files
/.well-known/tor-relay/rsa-fingerprint.txt) to a directory.
--torrc_output will write a file of the commands that it sends to
the Tor controller, so you can include it in a
are downloaded from https://onionoo.torproject.org/details For usage, do ```python3 exclude_badExits.py --help` See [exclude_badExits.txt](./exclude_badExits.txt)