[tor-bugs] #9652 [BridgeDB]: Treat Pluggable Transports as Individual Bridges

[Tor Bug Tracker & Wiki]

#9652: Treat Pluggable Transports as Individual Bridges
-----------------------------+-----------------
     Reporter:  sysrqb       |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  BridgeDB     |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by asn):

 Replying to [comment:4 sysrqb]:
 > Some thoughts so I can make progress on this.
 >
 > Make a bridge's location in the ring is dependent on:
 > 1) its fingerprint and port number (or ip addr and port)
 > 2) a salt and the fingerprint
 > 3) <a better idea>
 >
 > The ORPort bridge instance must still contain a list of all transports
 and we will need to ignore all transports when we iterate over the dict
 when we dump the assignments to file (but this will be easy).
 >
 > I'm heavily leaning towards 1) with regard to how we distinguish the
 Bridge instances, until someone tells me this is A Bad Idea. Also, these
 changes won't be localized, this will require touching many parts of the
 code but they won't be difficult modifications.

 Using the TCP port as a way to separate bridges from their PTs sounds like
 a fine idea to me. I'm not sure what else should be included in the hash
 calculation. Doesn't BridgeDB also include a salt of some kind? Maybe it's
 a good idea to keep it in.

 Also, let's keep in mind that we will "soon" want to stop passing out
 vanilla bridges through BridgeDB, so this change will be even more
 important then.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9652#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online