[tor-bugs] #9156 [BridgeDB]: BridgeDB: Users try to add obfsbridges to their normal TBB

[Tor Bug Tracker & Wiki]

#9156: BridgeDB: Users try to add obfsbridges to their normal TBB
----------------------------------------+-----------------------------------
 Reporter:  asn                         |          Owner:  isis    
     Type:  task                        |         Status:  accepted
 Priority:  normal                      |      Milestone:          
Component:  BridgeDB                    |        Version:          
 Keywords:  pt,usability,torlaucher,ui  |         Parent:          
   Points:                              |   Actualpoints:          
----------------------------------------+-----------------------------------

Comment(by asn):

 Replying to [comment:32 sysrqb]:
 > Replying to [comment:31 mikeperry]:
 > > mcs: Yeah, I think we should make Tor Launcher accept a direct cut and
 paste from bridges.tp.o and send it to Tor. See #9445. I think the only
 santization we should do there is to check for 'bridge ' in the beginning
 of the line, and if it's there, send it directly, and if it's not, add it
 in.
 >
 > I think this is a good idea. I
 [https://gitweb.torproject.org/user/sysrqb/bridgedb.git/blob/71af0935269ce2bc5410462ad8e0ebdbaeb7f5ed
 :/bridge-db-spec.txt#l318 added a section] to the updated BridgeDB spec
 for this. This is correct, for now, but I suspect this will change in the
 near future. 1) When Vidalia is deprecated, ideally Tor Launcher should
 accept/expect the "bridge" keyword again, thus bringing TBB's expectations
 in alignment with valid torrc syntax. 2) We will likely begin distributing
 the bridge fingerprint, again, when Vidalia is out of the picture (#9499).
 So it will look something like:
 > {{{
 > "bridge" SP <address:port> SP <fingerprint> NL
 > }}}
 >
 > I think we need to clarify how tor expects the fingerprint on PT lines
 [https://trac.torproject.org/projects/tor/ticket/9462#comment:3 [0]].

 Actually, a full-fledged bridge line would look like this:
 {{{
 Bridge method address:port [[keyid=]id-fingerprint] [k=v] [k=v] [k=v]
 }}}

 I'm fine with completely removing the optional `keyid`, since the
 fingerprint can be distinguished from `k=v` values by using its length or
 the fact that it shouldn't contain equal signs.

 So, a bridge line could look like this:
 {{{
 Bridge obfs666 7.145.2.41:1338 D586D18309DED4CD6D57C18FDB97EFA96D330566
 shared-secret=nosecrets texture-type=bamboo
 }}}

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