<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:10pt;color:#000000;">Hi,<br><br>While going through XEP-0065 and related RFC's i decided to play around with the debug window of Pidgin. Here is what I found when a connected account tries to accept a file:<br><br><font color="#000000">(01:56:47) <b>jabber:</b><span> Recv (572): <iq from="jaxl@dev.jaxl.im/5859500411289328645518583" to="1@dev.jaxl.im/2557233831289334472350031" type="set" id="purplee6c1c0cc"><query xmlns="<a target=" _blank="" href="http://jabber.org/protocol/bytestreams">http://jabber.org/protocol/bytestreams' sid='purplee6c1c0cb'><streamhost jid="jaxl@dev.jaxl.im/5859500411289328645518583" host="192.168.2.103" port="58919"><streamhost jid="jaxl@dev.jaxl.im/5859500411289328645518583" host="192.168.150.1" port="58919"><streamhost jid="jaxl@dev.jaxl.im/5859500411289328645518583"
host="192.168.220.1" port="58919"><streamhost jid="proxy.dev.jaxl.im" host="127.0.1.1" port="7777"></streamhost></streamhost></streamhost></streamhost></query></iq></span><br>(01:56:47) <b>dnsquery:</b> Performing DNS lookup for 192.168.2.103<br>(01:56:47) <b>dnsquery:</b> IP resolved for 192.168.2.103<br>(01:56:47) <b>proxy:</b> Attempting connection to 192.168.2.103<br>(01:56:47) <b>proxy:</b> Connecting to <span style="font-weight: bold;">50c0abe90692f69b56e49a53334daf8c6ad26f9e:0</span> via 192.168.2.103:58919 using SOCKS5<br>(01:56:47) <b>socks5 proxy:</b> Connection in progress<br>(01:56:47) <b>jabber:</b> in jabber_si_xfer_bytestreams_send_connected_cb<br>(01:56:47) <b>socks5 proxy:</b> Connected.</font><br><font color="#000000">(01:56:47) <b>jabber:</b> in jabber_si_xfer_bytestreams_send_read_cb<br>(01:56:47) <b>jabber:</b> reading those first two bytes<br>(01:56:47) <b>jabber:</b> in jabber_si_xfer_bytestreams_send_read_cb<br>(01:56:47)
<b>jabber:</b> reading 1 bytes for auth methods (trying to read 1 now)<br>(01:56:47) <b>jabber:</b> checking to make sure we're socks FIVE<br>(01:56:47) <b>jabber:</b> going to test 1 different methods<br>(01:56:47) <b>jabber:</b> testing 0<br>(01:56:47) <b>socks5 proxy:</b> Able to read.<br>(01:56:47) <b>jabber:</b> in jabber_si_xfer_bytestreams_send_read_again_cb<br>(01:56:47) <b>jabber:</b> reading the first 5 bytes<br>(01:56:47) <b>jabber:</b> in jabber_si_xfer_bytestreams_send_read_again_cb<br>(01:56:47) <b>jabber:</b> reading 42 bytes for DST.ADDR + port num (trying to read 42 now)<br>(01:56:47) <b>stun:</b> using server <br>(01:56:47) <b>jabber:</b> SOCKS5 connection negotiation completed. Waiting for IQ result to start file transfer.<br>(01:56:47) <b>s5:</b> reallocing from 5 to 18<br>(01:56:47) <b>s5:</b> reallocing from 18 to 20<br>(01:56:47) <b>proxy:</b> Connected to 50c0abe90692f69b56e49a53334daf8c6ad26f9e:0.<br></font><font
color="#666666">(01:56:47) <b>jabber:</b><span> Sending (1@dev.jaxl.im/2557233831289334472350031): <iq type="result" to="jaxl@dev.jaxl.im/5859500411289328645518583" id="purplee6c1c0cc"><query xmlns="<a target=" _blank="" href="http://jabber.org/protocol/bytestreams">http://jabber.org/protocol/bytestreams'><streamhost-used jid="jaxl@dev.jaxl.im/5859500411289328645518583"></streamhost-used></query></iq></span></font><br><div> <br>Now as per section 5.3.2. of XEP-0065 here is how Pidgin should have calculated hash for DST.ADDR:<br><font color="#000000">sha1("</font><font color="#000000">purplee6c1c0cb</font><font color="#000000">jaxl@dev.jaxl.im/5859500411289328645518583</font><font color="#000000">jaxl@dev.jaxl.im/5859500411289328645518583"</font><font color="#000000">) which equates to 59aadec011bdb96cb0f2fea5e6f6596e5a0d6f93 and not 50c0abe90692f69b56e49a53334daf8c6ad26f9e</font> as shown in the logs.<br><br>Am i missing something from the
XEP doc?<br></div><br>--<br>Abhinav Singh,<br>Founder, Jaxl Inc.<br>Bangalore, India<br><span><a target="_blank" href="http://abhinavsingh.com/blog">http://abhinavsingh.com/blog</a></span><div><br></div>
</div><br>
</body></html>