Opened 7 years ago

Closed 7 years ago

#5947 closed defect (fixed)

BridgeDB should parse "a lines" from networkstatus-bridges

Reported by: aagbsn Owned by: aagbsn
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Keywords:
Cc: ln5 Actual Points:
Parent ID: #4297 Points:
Reviewer: Sponsor:

Description

BridgeDB reads or-addresses from the bridge-descriptors, but should read them from the networkstatus-bridges instead.

The format of an "a" line in networkstatus-bridges is the same as the or-address line in bridge-descriptor, but has been verified as reachable by the bridge-authority.

I'm not sure what the status of ipv6 reachability testing is, or when "a" lines will appear in networkstatus-bridges.

Child Tickets

Attachments (1)

4297-a-line.patch (5.0 KB) - added by aagbsn 7 years ago.
BridgeDB reads or-addresses from status file instead of descriptor file.

Download all attachments as: .zip

Change History (3)

Changed 7 years ago by aagbsn

Attachment: 4297-a-line.patch added

BridgeDB reads or-addresses from status file instead of descriptor file.

comment:1 in reply to:  description Changed 7 years ago by ln5

Replying to aagbsn:

I'm not sure what the status of ipv6 reachability testing is, or when "a" lines will appear in networkstatus-bridges.

Branch ipv6-phase3 in my public repo does that. The branch waits for
a new tor config option before being ready for merging.

comment:2 Changed 7 years ago by aagbsn

Resolution: fixed
Status: newclosed

fixed in: aagbsn/5947-parse-networkstatus-a-line

Note: See TracTickets for help on using tickets.