Opened 7 months ago

Last modified 7 months ago

#21619 new enhancement

Flag fallback directory mirrors in Atlas

Reported by: teor Owned by: irl
Priority: Medium Milestone:
Component: Metrics/Atlas Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor keeps a list of fallback directory mirrors in its source code.

consensus-health flags these mirrors using the synthetic flag "FallbackDir".

Could Atlas do something like this, too?
(Like the Not Recommended flag?)

The list is updated every 2-6 months:
https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc

And then parsed and included in stem in a friendlier format:
https://gitweb.torproject.org/stem.git/tree/stem/descriptor/fallback_directories.cfg

Child Tickets

Change History (5)

comment:1 in reply to:  description ; Changed 7 months ago by cypherpunks

Replying to teor:

Could Atlas do something like this, too?
(Like the Not Recommended flag?)

To add "Not Recommended" Atlas simply made use of onionoo boolean recommended_version, but there is no fallback flag in onionoo, so this would probably require a onionoo change first unless atlas keeps this list out of band.

comment:2 Changed 7 months ago by atagar

For what it's worth if you want the current list of fallback directories in the tor source here's what you can call (it pulls the list from gitweb)...

https://stem.torproject.org/api/descriptor/remote.html#stem.descriptor.remote.FallbackDirectory.from_remote

comment:3 in reply to:  1 Changed 7 months ago by teor

Replying to cypherpunks:

Replying to teor:

Could Atlas do something like this, too?
(Like the Not Recommended flag?)

To add "Not Recommended" Atlas simply made use of onionoo boolean recommended_version, but there is no fallback flag in onionoo, so this would probably require a onionoo change first unless atlas keeps this list out of band.

Thanks, opened #21620 for this.

comment:4 Changed 7 months ago by irl

Also useful for this would probably be to add "last_changed_address_or_port" to the details pages for relays. Probably in the 3rd column.

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

Replying to irl:

Also useful for this would probably be to add "last_changed_address_or_port" to the details pages for relays. Probably in the 3rd column.

This should be a separate ticket although i can't see the usefulness of adding it to the details page. The field seems more suitable for the script that generates the fallback list.

Note: See TracTickets for help on using tickets.