[jdev] Understanding target SOCKS5 connection flow with streamhost/requester

[Dave Cridland]

On Tue Nov  9 21:22:59 2010, Abhinav Singh wrote:
> (01:56:47) jabber:Sending (1 at dev.jaxl.im/2557233831289334472350031):
> http://jabber.org/protocol/bytestreams'>

Note the target jid above.


sha1("purplee6c1c0cbjaxl at dev.jaxl.im/5859500411289328645518583jaxl at dev.jaxl.im/5859500411289328645518583")
>  which equates to 59aadec011bdb96cb0f2fea5e6f6596e5a0d6f93 and not
> 50c0abe90692f69b56e49a53334daf8c6ad26f9e as shown in the logs.

It's SHA1(SID + Requester JID + Target JID):

>>> import hashlib
>>> hash = hahslib.sha1()
>>> hash.update('purplee6c1c0cb')
>>> hash.update('jaxl at dev.jaxl.im/5859500411289328645518583')
>>> hash.update('1 at dev.jaxl.im/2557233831289334472350031')
>>> hash.hexdigest()
'50c0abe90692f69b56e49a53334daf8c6ad26f9e'

Dave.
-- 
Dave Cridland - mailto:dave at cridland.net - xmpp:dwd at dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade