[jdev] Digest auth: <digest> or <hash> ?

Heiner Wolf wolf at bluehands.de
Tue Jun 22 06:04:12 CDT 2004


Hi,

comparing the protocol log of my client an Exodus I found a strange difference. Exodus uses a <hash>-tag in the digest auth iq-set-jabber:iq:auth stanza. I thought this should be <digest> instead. 

It seems to work with both tags. Which one is "more" correct? 

After the stream setup:
SENT: <iq id="jcl_86" type="get">
        <query xmlns="jabber:iq:auth"><username>Wolfspelz</username></query>
      </iq>

RECV: <iq id='jcl_86' type='result'>
        <query xmlns='jabber:iq:auth'>
           <username>Wolfspelz</username>
           <password/>
           <digest/>
           <sequence>486</sequence>
           <token>3D00BF88</token>
           <resource/>
        </query>
      </iq>


SENT: <iq id="jcl_87" type="set">
        <query xmlns="jabber:iq:auth">
          <username>Wolfspelz</username>
          <resource>Exodus</resource>
          <hash>d7d601bc0739917e73b2174a4b00ed295474e089</hash>   <---------- <digest> ?
        </query>
      </iq>

Versions:
  Client: Exodus 0.9.0.0
  Server: javverd 1.4CVS (jabber.org)

hw
--
Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
http://www.bluehands.de/people/hw
+49 (0721) 16108 75
--
LLuna: Jabber enabled virtual presence on the web / http://www.lluna.de/
Galactic developments: Open source future history / http://www.galactic-developments.com/



More information about the JDev mailing list