[tor-relays] Draft Fallback Directory List

teor teor2345 at gmail.com
Sun Dec 11 12:45:42 UTC 2016

(This is a copy of the email I BCC'd to each relay operator on the draft
fallback directory list. Please email me to add your relays.)

Hash: SHA512

Dear Tor Relay Operator,

One or more of your relays have been selected as fallback directory
mirrors[0] for the next tor release. Please keep the relay available on
the same addresses, ports, and identity key (fingerprint) for the next
2 years.

This is a draft list.[3] I can make changes for the next week. Next
weekend, I will send another email to those operators whose relays have
been added or removed. (Otherwise, you're on the list.)

We are taking 3 relays per operator, if you only have 1 or 2 on the list,
please email me to add more.

Wondering why your relay didn't make the list?
Search the selection log[4] for its fingerprint.

If the log says:
* in neither blacklist nor whitelist,
email me to add your relay.
(I run a script that checks relays, then outputs a list.)

If it says:
* not a candidate: version delivers stale consensuses,
* not a candidate: version not recommended,
* not a candidate: changed address/port recently
(on or earlier), or
* outdated consensus,
upgrade to or later, or or later.

If it says:
* bandwidth too low,
* download too slow,
* HTTP Error 503: Directory busy,
* or some sort of download connection error,
it might help to give your relay more memory or bandwidth.
(And please make sure it's still running!)

If it says:
* not a candidate: changed address/port recently,
* not a candidate: guard avg too low,
* not a candidate: running avg too low, or
* not a candidate: v2dir avg too low,
your relay needs to be consistently up with high bandwidth to help
clients. Try keeping it stable for 6-12 months, and it might be selected
next time.

But don't worry, your relay(s) are still helping the tor network, even
if they are not selected as a fallback.


[0]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors
[3]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/draft_fallback_dirs_20161210_1121_2594b7b
   (or [8] if you want to see what the git commit will look like)
[4]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/draft_fallback_dirs_20161210_1121_2594b7b.log
[8]: https://github.com/teor2345/tor/blob/new-fallbacks-028-v2/src/or/fallback_dirs.inc

From: teor <teor2345 at gmail.com>
Subject: Call for Tor Fallback Directories
Date: 4 December 2016 at 21:44:39 AEDT
To: tor-relays at lists.torproject.org

Dear Tor Relay Operator,

Your relay(s) can help tor clients find the tor network by becoming a
fallback directory mirror.[0]

These mirrors are hard-coded into tor's source code, like the directory
authorities. We have 80 fallbacks, but we want 200 for the next release.

Fallbacks need to have:
- - the same IP address(es) and ports for the next 2 years,
- - the same relay identity key for the next 2 years,
- - good uptime (at least 95%), and
- - good bandwidth and network connectivity
(we estimate an extra 25GB per month).

Please email me to add your relays that fit these criteria to the list.
If you are BCC'd on this email, it looks like you have at least one
relay that could become a fallback.
You can also email me if you know your relay will be changing address
or key, and I'll make sure we don't choose it.

We are keeping the fallback lists from the last release[1][2].

So if you have emailed me before about becoming a fallback, there is no
need to email again. But please let me know if your relay details have
changed.  (I did not BCC relay operators who are already on the fallback
lists, unless their relay details changed.)

In a week or two, I will run a script to select the hard-coded list for
the release.

If you're interested, here's some background to this request:

The latest list[3] and log[4] of candidates was generated using the
instructions in [5] from scripts/maint/updateFallbackDirs.py on my
GitHub branch[6]. (This branch has some bug fixes compared to what's in
master.) We're tracking this work in [7].

(links updated to the latest code and relay list)
[0]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors
[1]: https://github.com/teor2345/tor/blob/fallbacks-201612-v4/scripts/maint/fallback.whitelist
[2]: https://github.com/teor2345/tor/blob/fallbacks-201612-v4/scripts/maint/fallback.blacklist
[3]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/draft_fallback_dirs_20161210_1121_2594b7b
[4]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/draft_fallback_dirs_20161210_1121_2594b7b.log
[5]: https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors
[6]: https://github.com/teor2345/tor/blob/fallbacks-201612-v4/scripts/maint/updateFallbackDirs.py
[7]: https://trac.torproject.org/projects/tor/ticket/18828

Comment: GPGTools - https://gpgtools.org



Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
xmpp: teor at torproject dot org

More information about the tor-relays mailing list