Opened 2 years ago

Last modified 8 days ago

#24853 new enhancement

backport the new authority and fallback file formats

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-auth, 034-triage-20180328, 034-removed-20180328, 031-unreached-backport, 032-unreached-backport, 033-unreached-backport, tor-spec
Cc: Actual Points:
Parent ID: #24818 Points: 0.5
Reviewer: Sponsor:

Description (last modified by teor)

After doing #24851 and #24852.

  • backport them to all supported tor releases:
    • authorities: 0.2.5 (EOL 1 May 2018), 0.2.9, 0.3.0 (EOL 1 Feb 2018), 0.3.1, 0.3.2, 0.3.3
    • fallbacks: 0.2.9, 0.3.0 (EOL 1 Feb 2018), 0.3.1, 0.3.2, 0.3.3
  • make sure all supported tor releases parse the files correctly (unit tests)

Child Tickets

Change History (17)

comment:1 Changed 2 years ago by nickm

I think that the fallback file is already backported?

comment:2 Changed 2 years ago by teor

Summary: backport the new authority and fallback filesbackport the new authority and fallback file formats

The new fallback file is backported, but I want to keep the same entries, and change the format (again, sorry).
Using a similar format for authority and fallback files should make it easier for the same tool to parse them.

Edit: spelling

Last edited 2 years ago by teor (previous) (diff)

comment:3 Changed 2 years ago by teor

Keywords: 025-backport-maybe removed

We won't backport this to 0.2.5, because the format is missing ipv6. Instead, we will manually backport any authority changes that happen before May 2018 when 0.2.5 is EOL.

comment:4 Changed 2 years ago by teor

Description: modified (diff)

comment:5 Changed 2 years ago by teor

Milestone: Tor: 0.3.3.x-finalTor: 0.3.4.x-final

We have time to do these, let's do them well in 0.3.4

comment:6 Changed 2 years ago by nickm

Remove 030-backport from all open tickets that have it: 0.3.0 is now deprecated.

comment:7 Changed 22 months ago by nickm

Keywords: 034-triage-20180328 added

comment:8 Changed 22 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:9 Changed 22 months ago by teor

Description: modified (diff)
Keywords: 033-backport added; 030-backport-maybe removed

This ticket depends on #24851 and #24852.

comment:10 Changed 22 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:11 Changed 19 months ago by teor

Keywords: 031-unreached-backport added; 031-backport removed

0.3.1 is end of life, there are no more backports.
Tagging with 031-unreached-backport instead.

comment:12 Changed 14 months ago by teor

Keywords: 032-unreached-backport added; 032-backport removed

0.3.2 is end of life, so 032-backport is now 032-unreached-backport.

comment:13 Changed 11 months ago by teor

Keywords: 033-backport removed

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

comment:14 Changed 11 months ago by teor

Keywords: 033-backport-unreached added

Hmm, I guess they should still get 033-backport-unreached

comment:15 Changed 6 months ago by teor

Keywords: 033-unreached-backport added; 033-backport-unreached removed

Fix 033-unreached-backport spelling.

comment:16 Changed 5 months ago by teor

Keywords: tor-spec added; torspec removed

Standardise keyword to tor-spec

comment:17 Changed 8 days ago by teor

Keywords: 029-backport removed

0.2.9 is no longer maintained as of 1 January 2020. Therefore, we won't be backporting anything to it.

(None of these tickets are merge_ready, so we can just delete the backport tag.)

Note: See TracTickets for help on using tickets.