[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9445 [Tor Launcher]: Include support for Pluggable Transports

#9445: Include support for Pluggable Transports
--------------------------+-------------------------------------------------
 Reporter:  bastik        |          Owner:  brade
     Type:  task          |         Status:  new  
 Priority:  normal        |      Milestone:       
Component:  Tor Launcher  |        Version:       
 Keywords:                |         Parent:  #9444
   Points:                |   Actualpoints:       
--------------------------+-------------------------------------------------
Changes (by isis):

 * cc: isis@â (added)


Comment:

 This was discussed briefly in #tor-dev while I was testing bridge support
 in the alpha 3.x builds (specifically 3.0.3a):

 {{{
 13:45          isis ) if you tell TBB-3.0.3a on startup to "use a proxy"
 and set it to socks5://127.0.0.1:9050, and then tell it that you need to
 use bridges, it
                       doesn't configure the bridge lines in your torrc,
 instead it decides to try to connect to <bridge_ipaddr>:<orport> via the
 socks5 proxy, which
               makes tor complain if WarnSocks 1
 13:46          isis ) hmm. and then it just hangs out there, chilling out
 with the progress bar at like 10%, doing nothing.
 13:47          isis ) well, at least it's confirmed that
 TOR_CONTROL_PASSWD='"passwd"' with the weird quoting works, and having two
 controllers works okay
 13:51          isis ) ah, also, when i tried entering obfs2 and obfs3
 bridges into torbutton on startup, it barfed appropriately, though it also
 did (i think) some
                       amount of processing to the text inside the text box
 in the "Tor Status" window, because it was originally like
 "1.1.1.1:1111\nobfs2
               2.2.2.2:2222\nobfs3 3.3.3.3:3333\n" and then i ended up with
 "1.1.1.1:1111\nobfs2\n2.2.2.2:2222\nobfs3\n3.3.3.3:3333\n" ...
 13:51          isis ) ... with extra newlines
 13:52        sysrqb ) ah, new lines around the transport
 14:00          isis ) sysrqb: yeah, which could be pretty bad, because if
 a client is trying to connect and they see the barfing logs with some
 mumbling about "not
                       formatted correctly" plus the thing in the "Network
 Settings" window which says "in the form <IP>:<port>" they may just remove
 the transport
                       names, and not the corresponding IPs
 14:01          isis ) this would be particularly bad because it would 1)
 still not work, and 2) cause a normal outgoing tor conn to a PT bridge,
 giving away to
                       censors that there is a bridge on that IP:port pair
 14:04        sysrqb ) isis: oh, huh, that's strange
 14:06        sysrqb ) isis: i guess you can add your lack-of-transport-
 support to #9445
 14:08     mikeperry ) isis: yeah, that is a tor launcher bug I guess, not
 tobtton
 15:52          isis ) mikeperry: also, the problem with transport lines
 and newlines in torlauncher/torbutton that i mentioned earlier, see
 http://sprunge.us/CQfL .
                       it did manage to set the Bridge lines in
 Data/Tor/torrc eventually, but only after restarting TBB.
 }}}

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9445#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs