[tor-consensus-health] Fallback Directory Update

[teor]

Hi all,

Fallback directory mirrors help clients reach the Tor network.

We need to rebuild the list every so often when their details change.
(We have an automated check for 25% failure, and it just triggered.)

Does anyone want to help me do this?
It would be nice to get it done this month - but it's not urgent.

Here's what needs to be done in detail:

1. Update the fallback whitelist with new and changed relay details
   Tickets: https://trac.torproject.org/projects/tor/ticket/22321
            https://trac.torproject.org/projects/tor/ticket/22527
   File:    tor/scripts/maint/fallback.whitelist

2. Update updateFallbackDirs.py to have a CONSENSUS_EXPIRY_TOLERANCE of 0.
   Ticket: https://trac.torproject.org/projects/tor/ticket/20942
   File:   tor/scripts/maint/updateFallbackDirs.py

3. Run updateFallbackDirs.py with the new whitelist and CONSENSUS_EXPIRY_TOLERANCE.
   You'll need a decent network connection for this.
   Please attach the script logs to the trac ticket.
   Command: tor/scripts/maint/updateFallbackDirs.py > src/or/fallback_dirs.inc

4. Write a changes file
   Ticket: https://trac.torproject.org/projects/tor/ticket/22271
   Draft:

  o Minor features (fallback directory list):
    - Replace the 151 fallbacks originally introduced in Tor 0.3.1.3-alpha in
      May 2017 (of which ~111 were still functional) with a list of
      NNN fallbacks (NNN new, NNN unchanged, NNN removed) generated in December
      2017. Resolves ticket 22271.

   There are some commands that count fallback changes here:
   https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors#FormattingChangesFiles

5. Announce the new list on tor-relays@

6. Tell the relay search maintainer that the list has changed


Next Time:

I'd like to make the process quicker and easier next time.
But I don't want to make any big changes to it at the moment.
(Like switching to opt-out, or changing how relay operators contact us.)
Let's do that when we have time to try different things.

T

> On 7 Dec 2017, at 11:57, atagar at torproject.org wrote:
> 
> 40/151 (26%) fallback directories have become slow or unresponsive...
> 
>  * AEA43CB1E47BE5F8051711B2BF01683DB1568E05 => ORPort is unreachable (37.187.7.74:443)
>  * 7187CED1A3871F837D0E60AC98F374AC541CB0DA => ORPort is unreachable (95.183.48.12:443)
>  * 5EB8D862E70981B8690DEDEF546789E26AB2BD24 => ORPort is unreachable (109.163.234.5:443)
>  * 8672E8A01B4D3FA4C0BBE21C740D4506302EA487 => IPv6 ORPort is unreachable (2a03:b0c0:2:d0::27b:7001:9050)
>  (snip)

--
Tim / teor

PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
------------------------------------------------------------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-consensus-health/attachments/20171207/f749d053/attachment.sig>