Bug 30176

Summary: Update SOCKS5 bytestream to use relays with muc contacts
Product: Telepathy Reporter: Guillaume Desmottes <guillaume.desmottes>
Component: gabbleAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED MOVED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: enhancement    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
i915 platform: i915 features:

Description Guillaume Desmottes 2010-09-14 04:37:53 UTC
Currently the SOCKS5 bytestream doesn't use relays when trying to establish a bytestream with a muc contact (we check in gabble_bytestream_socks5_initiate if the contact is a muc one and then don't add proxies to the stanza).

In practice that means than sending a file to a muc contact or any muc stream tubes will fallback to IBB if direct connections are not possible with the peer. The tube case is the most annoying one as if more applications start using muc stream tube, the XMPP servers are going to hate us.

That's because  XEP-0065 used to have a bug making impossible to use a relay with a muc contact. See [1] if you are interested in the glorius XMPP details. But, as pointed on [2] that's not longer the case and an updated version of the spec now has a solution [3] for this problem.

We should update our implementation to make use of this updated protocol and re-enable relays with muc contacts.

[1] http://mail.jabber.org/pipermail/standards/2009-March/021229.html
[2] http://developer.pidgin.im/ticket/8524#comment:3
[3] http://xmpp.org/extensions/tmp/xep-0065-1.8.html#muc
Comment 1 GitLab Migration User 2019-12-03 19:48:48 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/97.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.