[tor-bugs] #9127 [BridgeDB]: Users can't ask for ipv6 bridges with the new bridgedb interface

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Jun 30 14:49:05 UTC 2013


#9127: Users can't ask for ipv6 bridges with the new bridgedb interface
----------------------+-----------------------------------------------------
 Reporter:  asn       |          Owner:     
     Type:  task      |         Status:  new
 Priority:  normal    |      Milestone:     
Component:  BridgeDB  |        Version:     
 Keywords:            |         Parent:     
   Points:            |   Actualpoints:     
----------------------+-----------------------------------------------------

Comment(by sysrqb):

 Replying to [comment:6 asn]:
 > Replying to [comment:5 sysrqb]:
 > > Replying to [comment:4 asn]:
 > > > a) This design should not leak too many bridges. A user should not
 be able to get too many bridge addresses just by clicking checkboxes and
 dropdown menus. For example, with the naive implementation of this design,
 a user would be able to get N normal bridges by default, and then he would
 be able to get some more IPv6 bridges when he clicks the IPv6 checkbox,
 and then some more when he plays with the drop down menu. How can we
 minimize the amount of bridges leaked with this system?
 > >
 > > Well currently we don't leak any additional bridges if you request
 bridges multiple times but with different GET values, so any addition to
 the UI should not affect bridge selection.
 > >
 >
 > Sorry if I'm misunderstanding you but are you implying that this ticket
 can be implemented with solely UI changes? How would that happen? Don't
 you also have to enable the `filterBridgesByIP6` filter etc. to get only
 IPv6 bridges from the backend?

 Nope you're correct, I need more sleep. From irc:
 {{{
 15:21 < sysrqb> asn: ok, so for #9127 what I said was correct but for the
 wrong reason. With aagbsn's hack which returns obfs2/3 and regular
 bridges, it includes the bridges returned by transport=obfs2 and
 transport=obfs3
 15:21 < sysrqb> so if you requery for these specific transports, it just
 gives you a subset of the bridges returned without any criteria
 15:22 < sysrqb> bridges.tpo doesn't return any ipv6 address by default, so
 you obviously get a new bridge if you request ipv6 specifically
 }}}

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


More information about the tor-bugs mailing list