#25534 closed enhancement (duplicate)

Reachability of fallback directories

Reported by: anadahz Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: reachability, tcp connect, ooni
Cc: dcf Actual Points:
Parent ID: #24818 Points:
Reviewer: Sponsor:

Description (last modified by anadahz)

The OONI probe TCP connect test (run by default from many probes) currently tests the TCP connectivity (successful connection: true/false) of the directory authorities and brigdes.

This ticket is about adding the fallback directories (https://gitweb.torproject.org/tor.git/plain/src/or/fallback_dirs.inc)
to the TCP connect OONI probe test (https://github.com/TheTorProject/ooni-spec/blob/master/test-specs/ts-008-tcp-connect.md).

Ideally this list should be easily generated (with the help of a script) and be accurate (up to date). The list currently lives on the ooni-resource repository:
https://github.com/OpenObservatory/ooni-resources/blob/master/bridge_reachability/tor-bridges-ip-port.csv

Child Tickets

Change History (8)

comment:1 Changed 19 months ago by arma

Component: Core TorCore Tor/Tor

(Giving it some component, so it doesn't get lost)

Is the work here on the Tor side, or on the OONI side?

comment:2 in reply to:  1 Changed 19 months ago by anadahz

Replying to arma:

(Giving it some component, so it doesn't get lost)

Thanks.

Is the work here on the Tor side, or on the OONI side?

It's actually OONI's side, it will be good to find out if the list of fallback dir authorities can be exported in a CSV format as required by the OONI resources input test file: host,port,nickname,protocol

comment:3 Changed 19 months ago by nickm

Terminology note: these are "fallback directories", not "fallback directory authorities".

Should this be an Ooni ticket? It doesn't seem to be something we can address in Core Tor...

comment:4 Changed 19 months ago by anadahz

Description: modified (diff)
Summary: Reachability of fallback directory authoritiesReachability of fallback directories

comment:5 in reply to:  3 ; Changed 19 months ago by anadahz

Replying to nickm:

Terminology note: these are "fallback directories", not "fallback directory authorities".

Thanks for the terminology note, updated the ticket accordingly.

Should this be an Ooni ticket? It doesn't seem to be something we can address in Core Tor...

Perhaps the contents of fallback_dirs.inc should be populated in a format (ticket:25534#comment:2) that can be added directly to ooni-resources repository (reachability input list). Having such a format ensures that we are going to have the input list up to date. Ideally this should also happen to the bridges (at least the ones listed in Tor Browser), directory authorities are not changing that often.

The relevant OONI ticket: https://github.com/OpenObservatory/ooni-resources/issues/11

comment:6 in reply to:  5 Changed 19 months ago by teor

Parent ID: #24818
Resolution: implemented
Status: newclosed

Replying to anadahz:

Replying to nickm:

Terminology note: these are "fallback directories", not "fallback directory authorities".

Thanks for the terminology note, updated the ticket accordingly.

Should this be an Ooni ticket? It doesn't seem to be something we can address in Core Tor...

Perhaps the contents of fallback_dirs.inc should be populated in a format (ticket:25534#comment:2) that can be added directly to ooni-resources repository (reachability input list). Having such a format ensures that we are going to have the input list up to date. Ideally this should also happen to the bridges (at least the ones listed in Tor Browser), directory authorities are not changing that often.

No, we don't provide custom fallback formats for each downstream consumer.
Instead, we have a spec that can be used to parse the list:
https://gitweb.torproject.org/torspec.git/tree/dir-list-spec.txt

The fallback file is currently used by Stem and Metrics (Relay Search). OONI can use it as well.
It should be very easy to parse the IPv4 address, DirPort (HTTP/TCP), and ORPort (TLS/TCP), and the IPv6 address and ORPort (TLS/TCP).

I recommend you use the fingerprint as the "nickname", because fallback nicknames are not guaranteed to be unique.

In future, we will make the authorities file into a separate list (#24854), and change the format so it's easy to parse (#24818). We also want to change the fallback format so it matches the authority format (#24852).

The relevant OONI ticket: https://github.com/OpenObservatory/ooni-resources/issues/11

I don't think there is anything that core tor needs to do to make this happen, so I'm closing the ticket.
(Tor Browser's default bridges are maintained by the Tor Browser team. You should probably parse Tor Browser's bridges file as well.)

comment:7 Changed 19 months ago by teor

Resolution: implemented
Status: closedreopened

CHanging status

comment:8 Changed 19 months ago by teor

Resolution: duplicate
Status: reopenedclosed
Note: See TracTickets for help on using tickets.