[tor-bugs] #5935 [BridgeDB]: Determine how bridge-pool assignments should work with BridgeDB's IPv6 and pluggable-transport extensions

[Tor Bug Tracker & Wiki]

#5935: Determine how bridge-pool assignments should work with BridgeDB's IPv6 and
pluggable-transport extensions
----------------------+-----------------------------------------------------
 Reporter:  aagbsn    |          Owner:     
     Type:  defect    |         Status:  new
 Priority:  normal    |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:            |         Parent:     
   Points:            |   Actualpoints:     
----------------------+-----------------------------------------------------

Comment(by aagbsn):

 This gets hairy; for example, consider the case where a bridge has an ipv4
 address with port 443, and an ipv6 address without port 443.

 For now though, I updated dumpAssignments to behave like above:
 From assignments.log
 {{{
 b26bcd139792e2c08db80d9d937b368f5ba89ed1 https ip=6 flag=stable ring=0
 25a770276301a32489ba7ad7e7400956b77db317 https ip=4,6 flag=stable ring=1
 5261ba8ae02fcd2f7455658bd0585aead329fd7f https ip=6 flag=stable ring=1
 8beac99141afe84eb55b06bb668527ea9a491156 https ip=4,6 ring=3 flag=stable
 port=443
 255671bfa78405b25892759831e0fef709984b6e https ip=6 ring=3 flag=stable
 7f59cd75fd7bcf6e68aea17e5c6b284d83196c94 https ip=4,6 ring=3 flag=stable
 b2b9e6da6e2d5a342300e03342cc2aaa37d92075 https ip=6 ring=3 flag=stable
 port=443
 a9f19793c946426306bbfe9ee200234e735cba2c https ip=4,6 flag=stable ring=2
 }}}

 I'll add transport support shortly.

 The order of keys doesn't matter, right?

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