Opened 4 months ago

Closed 6 weeks ago

#21564 closed defect (implemented)

Regenerate fallback list for 0.3.1 or 0.3.2

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.3.1.x-final
Component: Core Tor/Fallback Scripts Version: Tor:
Severity: Normal Keywords: fallback, 030-backport, 029-backport, 028-backport
Cc: Actual Points: 0.3
Parent ID: Points: 3
Reviewer: Sponsor:


This involves:

  • checking for new relays
  • contacting potential fallback operators
  • rebuilding the list
  • contacting all fallback operators

See detailed instructions here:

Child Tickets

#20913Increase fallback stability, flag percentage, and bandwidthteor
#21121Update fallback whitelistteor
#21283Remove broken fallback directory mirrors
#22268TROVE-2017-003: Impersonation of a single fallback directory mirror

Attachments (1)

fallbacks_2017-05-16-0815-09cd78886.log (6.9 KB) - added by teor 6 weeks ago.
Log of fallback rebuild 16 May 2017

Download all attachments as: .zip

Change History (4)

comment:1 Changed 2 months ago by teor

This isn't needed in 0.3.1, see #21283 for removing broken fallbacks, which we'll do first. But we don't need to do either yet.

Changed 6 weeks ago by teor

Log of fallback rebuild 16 May 2017

comment:2 Changed 6 weeks ago by teor

  • Actual Points set to 0.3
  • Keywords 030-backport 029-backport 028-backport added
  • Milestone changed from Tor: 0.3.2.x-final to Tor: 0.3.1.x-final
  • Version set to Tor:

I closed #21283, and did a quick rebuild to get 151 fallbacks instead, using my branch fallback-inputs (commit 09cd78886).

I didn't check for new potential fallbacks (I'll do that in #22271), but I will need to contact all the new operators.

I have attached the log from the fallback generation script.

This is in my branch fallbacks-201705-028.

comment:3 Changed 6 weeks ago by nickm

  • Resolution set to implemented
  • Status changed from new to closed

Merged to 0.2.8 and forward!

Note: See TracTickets for help on using tickets.