please add my relays as fallback mirrors, thanks
On Dec 4, 2016 5:45 AM, "teor" teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
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].
[0]: https://trac.torproject.org/projects/tor/wiki/doc/ FallbackDirectoryMirrors [1]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.whitelist [2]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.blacklist [3]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04 [4]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04.log [5]: https://trac.torproject.org/projects/tor/wiki/doc/ UpdatingFallbackDirectoryMirrors [6]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/ updateFallbackDirs.py [7]: https://trac.torproject.org/projects/tor/ticket/18828
T
- -- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org - ------------------------------------------------------------------------
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 8 Jan 2017, at 17:00, l3thal l3thal@smashthestack.org wrote:
please add my relays as fallback mirrors, thanks
I can't find any candidate fallbacks with your email address in the contact info.
Are these relays the ones you are asking for?
UNKNOWN - 1F45542A24A61BF9408F1C05E0DCE4E29F2CBA11 TorWeatherHelper - 0F100F60C7A63BED90216052324D29B08CFCF797
Let me know, and I'll put them on the list. Then we run a script before every release to pick the best ones.
Tim
On Dec 4, 2016 5:45 AM, "teor" teor2345@gmail.com wrote:
Signed PGP part 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].
FallbackDirectoryMirrors [1]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.whitelist [2]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/ scripts/maint/fallback.blacklist [3]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04 [4]: https://trac.torproject.org/projects/tor/attachment/ ticket/18828/potential_extra_fallbacks_2016-12-04.log [5]: https://trac.torproject.org/projects/tor/wiki/doc/ UpdatingFallbackDirectoryMirrors [6]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/ updateFallbackDirs.py [7]: https://trac.torproject.org/projects/tor/ticket/18828
T
--
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
tor-relays@lists.torproject.org