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

[Tor Bug Tracker & Wiki]

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

 Replying to [comment:44 feynman]:
 > JIDs are often given random strings for their so called "resources" (or
 if a resource is requested, a random string is often appended to it).

 (I just want to point out that this is pretty uncommon for XMPP servers
 except GTalk. Most normal XMPP servers just give you the resource you
 request.)

 > To send an IQ, one must know the recipient's resource. This is great for
 security, but bad for this particular application. To get around this, I
 use a message (which can be sent without a resource) to send a connection
 request to a JID with an unknown resource. When the recipient responds,
 thus disclosing their resource, their full JID (including the resource) is
 added to a table that keeps track of JIDs and resources.
 >
 > The problem is if one of the computers disconnects and reconnects, they
 acquire a new resource and their is no way (currently) for the other
 computer to update its table.
 >
 > Another problem is that messages that have no resource specified can
 only be sent to people on your contact list.

 This also sounds like a limitation set by GTalk.

 Why do you want to avoid needing to have someone on your contact list to
 use this? If you want to properly exchange messages/iqs with someone, it
 helps to be able to know on which resources they are online. This should
 also make it much easier to automatically handle the case where the other
 side disconnected and reconnected on a different resource.

 If you're worried about privacy... I don't really see why you would
 authorize someone to use your connection as a proxy to the internet when
 you don't want them to know when you're online. It sounds fair to inform
 them when you're available to proxy a connection for you.

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