Opened 12 days ago

Last modified 6 days ago

#24851 new enhancement

create a script that generates the authority format from the authorities in the current consensus

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: 0.3.4.x-final
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: tor-dirauth
Cc: teor@… Actual Points:
Parent ID: #24818 Points: 0.5
Reviewer: Sponsor:

Description

We need to make sure we also:

  • apply address overrides
  • make sure the details match the current list
  • check that all supported Tor versions can parse the list (existing unit tests)

Child Tickets

Change History (2)

comment:1 in reply to:  description Changed 11 days ago by teor

Here is the specification for the authority list:
https://github.com/teor2345/torspec/blob/dir-list/dir-list-spec.txt#L254

The data should be the same as the data in this list:
https://gitweb.torproject.org/tor.git/tree/src/or/config.c#n1079

But it will end up looking a bit like this list:
https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc#n27

And we need to get the data from the current Tor consensus using stem, so it's easy to update when it changes:
https://stem.torproject.org/api/descriptor/remote.html#stem.descriptor.remote.get_consensus

It's ok to just get the fields right in a first draft, and then work out the exact order and formatting later.

Replying to teor:

We need to make sure we also:

  • apply address overrides
  • make sure the details match the current list

The address overrides will become obvious when we check against the current list.

  • check that all supported Tor versions can parse the list (existing unit tests)

We can do this by replacing src/or/auth_dirs.inc with the generated list, then running Tor's "make check".
This will only work once #24854 is completed.

comment:2 Changed 6 days 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

Note: See TracTickets for help on using tickets.