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

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

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

 Since you prefer to not do it the SOCKS way, and instead use the address
 of hexchat as Bridge, we might not even need the managed-proxy interface
 and pyptlib.

 Specifically, if hexchat is an application with the following CLI:
 {{{hexchat-client <listenaddr> <xmpp_server> <jid/password>}}}
 and
 {{{hexchat-server <pushaddr> <xmpp_server> <jid/password>}}}
 we might be able to deploy this without the managed-proxy interface.

 On the client-side, we do the dummy `Bridge`/`ClientTransportPlugin`
 trick. On the server-side, we just fire up hexchat-server and point it to
 the ORPort of our bridge without even informing Tor about it.

 In the future, if we want the managed-proxy interface, we can add pyptlib
 support.

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