Implement SOCKS5 Bytestreams in XMPP (XEP-0065)

NEW
Unassigned

Status

Chat Core
XMPP
4 years ago
a year ago

People

(Reporter: sawrubh, Unassigned)

Tracking

(Blocks: 1 bug)

trunk
x86_64
Linux

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

4 years ago
This bug will track the implementation of SOCKS5 Bytestream in js-xmpp.
Why is this necessary? This seems out of the scope for what we hope to accomplish during GSoC.
(In reply to Patrick Cloke [:clokep] from comment #1)
> Why is this necessary?

Per http://xmpp.org/extensions/xep-0096.html#protocol-tech both SOCKS5 Bytestreams (XEP-0065) and In-Band Bytestreams (XEP-0047) are required to claim we support XMPP file transfer.
(In reply to Florian Quèze [:florian] [:flo] from comment #2)
> (In reply to Patrick Cloke [:clokep] from comment #1)
> > Why is this necessary?
> 
> Per http://xmpp.org/extensions/xep-0096.html#protocol-tech both SOCKS5
> Bytestreams (XEP-0065) and In-Band Bytestreams (XEP-0047) are required to
> claim we support XMPP file transfer.

OK, but we shouldn't be worrying about this until bug 1024023 is done AND we have worked out the UI a bit more.
You need to log in before you can comment on or make changes to this bug.