Opened 7 months ago

Closed 4 months ago

#20170 closed defect (implemented)

Backport latest fallback list to 0.2.8 and 0.2.9

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.2.8.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 028-backport, fallback, 029-backport
Cc: Actual Points: 0.2
Parent ID: #18828 Points: 0.1
Reviewer: Sponsor:

Description

I'm generating a new list of fallback directory mirrors for release 0.2.9 in #18828.

We have a few options for dealing with the 0.2.8 list:

  • comment-out any broken fallbacks,
  • backport the 0.2.9 list,
  • do nothing.

I would prefer to have the same src/or/fallback_dirs.inc in every (relevant) Tor release, assuming we do another 0.2.8 series release.
This is consistent with how we handle directory authorities and geoip.
Otherwise it becomes hard to check multiple fallback lists at once.

But I could be convinced to go with either of the other options.

Child Tickets

TicketSummaryOwner
#20243Update fallback directories for 0.2.8

Attachments (1)

draft_fallback_dirs_20161207.log (515.5 KB) - added by teor 5 months ago.
Fallback selection log for draft 029 fallbacks on 20161207

Download all attachments as: .zip

Change History (13)

comment:1 Changed 7 months ago by teor

  • Parent ID set to #20172

We should do the following things before backporting:

  • inform the relay operators their relays have been selected for 0.2.9, and
  • check the list before the 0.2.9 stable release to ensure the relays are still working.

comment:2 Changed 7 months ago by teor

I made a branch broken-028-fallbacks on my github.
It comments out the broken 0.2.8 fallbacks, leaving 81/100. Another 10 are somewhat suspect (old versions, lost flags).

If this trend keeps going, we could be down to 50/100 by the end of the 2-year 0.2.8 release lifetime. We wanted to refresh the list when it reached 75/100.

So let's refresh both the 0.2.9 list and the 0.2.8 list. I don't think we need to delay any backport, because the new list will be larger and more reliable than the old one.

comment:3 Changed 7 months ago by teor

  • Owner set to teor
  • Status changed from new to assigned

comment:4 follow-up: Changed 7 months ago by teor

In fact, let's do both:

  • merge broken-028-fallbacks before the next 0.2.8 release, and
  • update the list based on the 0.2.9 list when it's ready.

comment:5 in reply to: ↑ 4 Changed 7 months ago by teor

Replying to teor:

In fact, let's do both:

  • merge broken-028-fallbacks before the next 0.2.8 release, and

Split off into #20190.

  • update the list based on the 0.2.9 list when it's ready.

This ticket.

comment:6 Changed 5 months ago by teor

  • Keywords 029-backport added
  • Parent ID changed from #20172 to #18828
  • Status changed from assigned to needs_revision
  • Summary changed from Backport 0.2.9 fallback list to 0.2.8? to Backport latest fallback list to 0.2.8 and 0.2.9
  • Version changed from Tor: 0.2.8.7 to Tor: 0.2.8.10

This is the task for backporting the fallback list to 0.2.8 and 0.2.9.
The changes to the script, whitelist, and blacklist will be handled in #18828, and merged to master only.

There will soon be a draft list attached to #18828, I will revise it around the 17th of December, once relay operators have had a week and a half to send in updates and upgrade old versions.

comment:7 Changed 5 months ago by teor

  • Status changed from needs_revision to needs_review
  • Version Tor: 0.2.8.10 deleted

I've built a draft fallback list using the branch in #18828.
I'll attach the logs to this ticket.

The list was generated using the instructions in:
https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryMirrors#b.GeneratingtheList

Around 17 December, I will update the final list, and we can backport it to 0.2.8 and 0.2.9.

If someone wants to run a version of tor with the new fallback list, I'd love a review.

The current draft branch with the list is new-fallbacks-028 on my github:
https://github.com/teor2345/tor/blob/new-fallbacks-028/src/or/fallback_dirs.inc

Changed 5 months ago by teor

Fallback selection log for draft 029 fallbacks on 20161207

comment:8 Changed 5 months ago by teor

We could also switch to 3 fallbacks per operator to get ~173 fallbacks, see #20914

comment:9 Changed 5 months ago by teor

  • Status changed from needs_review to needs_revision

Latest branch is new-fallbacks-028-v2, I'll update it next weekend as well.

comment:10 Changed 4 months ago by teor

  • Actual Points set to 0.2
  • Status changed from needs_revision to merge_ready

The latest fallback list is in the branch new-fallbacks-028-20161219 on my github.
It is based on maint-0.2.8 (I think around 0.2.8.9, but it should still merge cleanly).

comment:12 Changed 4 months ago by nickm

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

Merged to 0.2.8 and forward!

Note: See TracTickets for help on using tickets.