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

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Jun 9 10:35:20 UTC 2013


#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 asn):

 Replying to [comment:12 feynman]:
 > Replying to [comment:11 asn]:
 > I updated the files with most of the changes you suggested. Here are the
 things I did not change:
 >
 > - More paranoid "(dis)connect" message: I left this the way it was so it
 would be easy to spot in a debug file. I do not think people should run
 hexchat using their usual XMPP chat server accounts anyway, so making
 messages distinguishable from normal chats should be unnecessary.
 >
 > - Split the code base to more files: Clients and servers are objects of
 the same class because the program does not really distinguish them the
 way TCP does. In fact, any client can also act as a server.
 >
 > - Write a SOCKS-server for the client side: I will do this if I must,
 but it seems like a hack around an unnecessary limitation tor places on
 pluggable transports. I would personally prefer that tor be configured to
 have hexchat listen on a local address and tor configured to use that
 local address as a bridge. Then hexchat would forward the connection to
 the actual bridge. This would leave hexchat in the most versatile form.
 Then tor, or any other program could still use it as something other than
 a SOCKS proxy.
 >
 > -pyptlib support: You said you could/would take care of this. If you do
 not have time tomorrow or want me to take care of this, let me know.
 Otherwise, I will leave it to you to finish this off with pyptlib.
 >
 > -SSL support: If you were referring to SSL support with the chat server,
 it already supports that (sleekxmpp does this transparently).

 Sounds good. Thanks for the fixes. I will also do some code cleaning of my
 own when I get the time.

 BTW, with regards to the SOCKS-server thing, have you tried using hexchat
 with tor? If you can manage to make hexchat work with `Bridge` lines and
 `ClientTransportPlugin` lines, then I guess we don't need to do the SOCKS-
 server thing. You might be able to do it with something like this:
 {{{
 Bridge 127.0.0.1:5555 # actual hexchat address
 Bridge hexchat 0.0.0.1:1233 # dummy bridge line just to spawn up 'hexchat'
 transport
 ClientTransportPlugin hexchat exec /usr/bin/hexchat --blabla --managed #
 this line will force tor to spawn hexchat
 }}}
 Although this is a hack, so I can't promise it's going to work. Check out
 how `ClientTransportPlugin` and the managed proxy interface works:
 https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180
 -pluggable-transport.txt

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


More information about the tor-bugs mailing list