Add Fallback Directory Candidate Selection Script
"Tor has included a feature to fetch the initial consensus from nodes
other than the authorities for a while now. We just haven't shipped a
list of alternate locations for clients to go to yet.
Reasons why we might want to ship tor with a list of additional places
where clients can find the consensus is that it makes authority
reachability and BW less important.
We want them to have been around and using their current key, address,
and port for a while now (120 days), and have been running, a guard,
and a v2 directory mirror for most of that time."
Features:
* whitelist and blacklist for an opt-in/opt-out trial.
* excludes BadExits, tor versions that aren't recommended, and low
consensus weight directory mirrors.
* reduces the weighting of Exits to avoid overloading them.
* places limits on the weight of any one fallback.
* includes an IPv6 address and orport for each FallbackDir, as
implemented in #17327. (Tor won't bootstrap using IPv6 fallbacks
until #17840 is merged.)
* generated output includes timestamps & Onionoo URL for traceability.
* unit test ensures that we successfully load all included default
fallback directories.
Closes ticket #15775. Patch by "teor".
OnionOO script by "weasel", "teor", "gsathya", and "karsten".
2015-05-12 20:10:39 +02:00
|
|
|
# updateFallbackDirs.py directory mirror blacklist
|
|
|
|
#
|
|
|
|
# Format:
|
|
|
|
# [ IPv4[:DirPort] ] [ orport=<ORPort> ] [ id=<ID> ] ...
|
|
|
|
# [ ipv6=<IPv6>[:<IPv6 ORPort>] ]
|
|
|
|
#
|
|
|
|
# If a sufficiently specific group of attributes matches, the directory mirror
|
|
|
|
# will be excluded: (each group is listed on its own line)
|
|
|
|
# <IPv4>, <DirPort>
|
|
|
|
# <IPv4>, <ORPort>
|
|
|
|
# <ID>
|
|
|
|
# <IPv6>, <DirPort>
|
|
|
|
# <IPv6>, <IPv6 ORPort>
|
|
|
|
# If DirPort and ORPort are not present, the entire IP address is blacklisted.
|
|
|
|
# (The blacklist overrides the whitelist.)
|
|
|
|
|
|
|
|
# If a relay operator doesn't want their relay to be a FallbackDir,
|
|
|
|
# enter the following information here:
|
|
|
|
# <IPv4>:<DirPort> orport=<ORPort> id=<ID> ipv6=<IPv6>:<IPv6 ORPort>
|
2016-01-18 02:34:34 +01:00
|
|
|
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2015-December/008364.html
|
|
|
|
87.181.248.227:9030 orport=443 id=8827944C4BDCBDAC9079803F47823403C11A9B7A
|
|
|
|
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2015-December/008368.html
|
|
|
|
149.18.2.82:9030 orport=9001 id=953DB709F2A2DECC8D7560661F934E64411444F7
|
|
|
|
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2015-December/008384.html
|
|
|
|
80.82.215.199:80 orport=443 id=3BEFAB76461B6B99DCF34C285E933562F5712AE4 ipv6=[2001:4ba0:cafe:a18::1]:443
|
|
|
|
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2016-January/008515.html
|
|
|
|
# later opt-out in
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2016-January/008521.html
|
|
|
|
5.9.158.75:80 orport=443 id=F1BE15429B3CE696D6807F4D4A58B1BFEC45C822 ipv6=[2a01:4f8:190:514a::2]:443
|
|
|
|
|
|
|
|
# Email sent directly to teor, verified using relay contact info
|
|
|
|
5.34.183.168:80 orport=443 id=601C92108A568742A7A6D9473FE3A414F7149070
|
|
|
|
217.12.199.208:8080 orport=22 id=BCFB0933367D626715DA32A147F417194A5D48D6
|
|
|
|
|
|
|
|
# https://lists.torproject.org/pipermail/tor-relays/2016-January/008555.html
|
|
|
|
62.210.207.124:9030 orport=9001 id=58938B1A5C4029B4415D38A4F36B7724273F4755 ipv6=[2001:bc8:31eb:100::1]:9001
|
|
|
|
62.210.207.124:9130 orport=9101 id=338D0AB6DBAB7B529B9C91B2FD770658000693C4 ipv6=[2001:bc8:31eb:100::1]:9101
|