Re: [tor-bugs] #9022 [Pluggable transport]: Create an XMPP pluggable transport

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#9022: Create an XMPP pluggable transport
---------------------------------+------------------------------------------
 Reporter:  asn                  |          Owner:  feynman 
     Type:  task                 |         Status:  accepted
 Priority:  normal               |      Milestone:          
Component:  Pluggable transport  |        Version:          
 Keywords:                       |         Parent:          
   Points:                       |   Actualpoints:          
---------------------------------+------------------------------------------

Comment(by feynman):

 I want to thank everyone on the IRC that helped me test this program.

 At this point I was able to connect and use a bridge through hexchat after
 making some minor modifications to the code. It now acts completely (or so
 I hope) transparently as a means of forwarding data from one computer over
 a chatline to another computer.

 This allows you to tell tor to use your local computer as a bridge and
 have hexchat waiting to forward data byte for byte to another computer
 (which would be running its own instance of hexchat).

 There is a lot of room for flexibility here. For example, the computer
 with an uncensored internet connection could be behind a NAT and does not
 even have to be running tor. As long as the computer can:
 a) Connect to and use an XMPP chat server
 b) Connect to the requested bridge (or run a bridge itself)
 , the computer is a viable relay for hexchat.

 A further consideration is the distribution of JIDs (xmpp usernames of the
 form username@chatserver) of people running hexchat. Remember, you do not
 have to know the IP address of the bridge you are connecting to if the
 bridge itself is running hexchat (in which case you would tell your client
 hexchat to connect to a 127.0.0.1 address on the remote computer).

 Finally, I want to note that at this point, running hexchat would probably
 be a security risk. Someone could connect to a computer running hexchat,
 then connect from there to any IP, local or remote, and send arbitrary
 data from that computer. The good news is that this is quite easy to fix.
 I can throw in another command line arguement that gives the computer a
 list of ip:ports it is authorized to connect to.

 All in all, the program is near complete. It just needs some means to
 limit the ip:ports it can connect to, and a pyptlib interface.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9022#comment:16>
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