[tor-relays] Become a Fallback Directory Mirror

[Anders Burmeister]

Hi Tim, Be my guest
775B0FAFDE71AADC23FFC8782B7BEB1D5A92733E
EFEACD781604EB80FBC025EDEDEA2D523AEAAA2F
484A10BA2B8D48A5F0216674C8DD50EF27BC32F3
1938EBACBB1A7BFA888D9623C90061130E63BB3F
Best Regards
Anders Burmeister

Sent with [ProtonMail](https://protonmail.com) Secure Email.

> -------- Original Message --------
> Subject: [tor-relays] Become a Fallback Directory Mirror
> Local Time: 21 December 2017 12:50 AM
> UTC Time: 20 December 2017 23:50
> From: teor2345 at gmail.com
> To: tor-relays at lists.torproject.org
>
> Dear Relay Operators,
>
> Do you want your relay to be a Tor fallback directory mirror?
> Will it have the same address and port for the next 2 years?
> Just reply to this email with your relay's fingerprint.
>
> If your relay is on the current list, you don't need to do anything.
>
> If you're asking:
>
> Q: What's a fallback directory mirror?
>
> Fallback directory mirrors help Tor clients connect to the network.
> For more details, see [1].
>
> Q: Is my relay on the current list?
>
> Search [2] and [3] for your relay fingerprint or IP address and port.
> [2] is the current list of fallbacks in Tor.
> [3] is used to create the next list of fallbacks.
>
> Q: What do I need to do if my relay is on the list?
>
> Keep the same IP address, keys, and ports.
> Email tor-relays if the relay's details change.
>
> Q: Can my relay be on the list next time?
>
> We need fast relays that will be on the same IP address and port for 2
> years. Reply to this email to get on the list, or to update the details
> of your relay.
>
> Once or twice a year, we run a script to choose about 150-200 relays
> from the potential list [3] for the list in Tor [2].
>
> Q: Why didn't my relay get on the list last time?
>
> We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might
> be down when we check. That's ok, we will check it again next time.
>
> It's good to have some new relays on the list every release. That helps
> tor clients, because blocking a changing list is harder.
>
> Q: What about the current relay DDoS?
>
> We don't think the DDoS will have much impact on the fallback list.
>
> If your relay is affected, please:
>
> - make sure it has enough available file descriptors, and
> - set MaxMemInQueues to the amount of RAM you have available per tor
> instance (or maybe a few hundred MB less).
>
> We're also working on some code changes. See [5] for more details.
>
> [1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors
> [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc
> [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist
> [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log
> [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
>
> --
> Tim / teor
>
> PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
> ricochet:ekmygaiu4rzgsk6n
>
> ---------------------------------------------------------------
>
> ---------------------------------------------------------------
>
> tor-relays mailing list
> tor-relays at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20171221/99fa06e1/attachment.html>