Opened 7 years ago

Closed 7 years ago

#5949 closed defect (fixed)

BridgeDB reachability/blocking should be per address:port

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

Description

As censors will block bridges by ip:port or ip, BridgeDB should support tracking reachability at this granularity. Presently it is per-bridge, but as bridges will now support multiple listening ports and addresses, so should reachability information.

Child Tickets

Change History (3)

comment:1 Changed 7 years ago by aagbsn

Note that the implementation will probably need to use a database. I'm wondering if BridgeDB should use an ORM that has some sort of caching layer... SQLAlchemy for mayor?

comment:2 Changed 7 years ago by aagbsn

Parent ID: #4297#5418

Switched parent to #5418; this does not block #4297 from being deployed.

comment:3 Changed 7 years ago by aagbsn

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.