<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SOCKS5 on nagg.eu</title><link>https://nagg.eu/tags/socks5/</link><description>Recent content in SOCKS5 on nagg.eu</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 03 Sep 2015 14:08:00 +0000</lastBuildDate><atom:link href="https://nagg.eu/tags/socks5/index.xml" rel="self" type="application/rss+xml"/><item><title>ejabberd SOCKS5 proxy – file transfer</title><link>https://nagg.eu/ejabberd-socks5-proxy-file-transfer/</link><pubDate>Thu, 03 Sep 2015 14:08:00 +0000</pubDate><guid>https://nagg.eu/ejabberd-socks5-proxy-file-transfer/</guid><description>&lt;p&gt;Ejabberd XMPP server includes a SOCKS5 proxy, setting it up correctly is what
makes the difference between fast or very slow file transfer operations.&lt;br&gt;
As per XEP-0065 file transfer is either peer-to-peer or mediated by a proxy
server.&lt;br&gt;
In Conversation peer-to-peer transfer is done by converting the file in base64,
split it in 4 kb chunks sent one at the time always awaiting first for the ACK
of the precedent one; this makes the whole process painfully slow and bandwidth
consuming.&lt;br&gt;
The other file transfer method supported by Conversation is defined by XEP-0234
(or Jingle file transfer) which relies on a SOCKS5 proxy and also allow to
negotiate parameters like encryption.&lt;br&gt;
Ejabberd configuration:&lt;/p&gt;</description></item></channel></rss>