From: Paschoud A. <mai...@we...> - 2003-07-29 07:10:41
|
Hi, I tested with Nitro. It works without any problem. The XML protocol used is the next : Out: <stream:streamxmlns=' jabber:client' xmlns:stream='http://etherx.jabber.org/streams' to='jabber.smartdata.ch'> In: <?xml version='1.0'?> <stream:stream xmlns:stream='http://etherx.jabber.org/streams' id='3F253ABB' xmlns='jabber:client' from='jabber.smartdata.ch'> Out: <iq xmlns='jabber:client' id='ACID_45' type='get' from='apa...@ja.../Nitro'> <query xmlns= 'jabber:iq:auth'><username>apaschou</username></query></iq> In: <iq xmlns='jabber:client' id='ACID_45' type='result'> <query xmlns='jabber:iq:auth'> <username>apaschou</username> <digest/><sequence>499</sequence> <token>3F24F165</token> <resource/></query></iq> Out: <iq xmlns='jabber:client' id='ACID_46' type='set' from='apa...@ja.../Nitro'> <query xmlns='jabber:iq:auth'> <username>apaschou</username> <resource>Nitro</resource> <digest>ebf1a81063e428828349b18009c 2bd48553317ee</digest> </query></iq> As you can see, Nitro first wait for the <stream:stream ...> tag from the server before to send its query, and then it send a "get" and not a "set" query with only username (no password). I am new to Fire, so I don't know if we should use the Acid Jabber library or if the current one should be corrected. Anyway, I will make a bug report for this problem. Best regards. >This is likely a newer feature of the Jabber protocol which our library does not have implemented. > >I think we should move to using the Acid Jabber library which is used by Nitro (an Objective C Jabber client for Mac OS X). As far as I know, JabberFox is defunct, and does not have a clear line of separation between the library and the client like Acid/Nitro. > >Acid supports the challenge/response authentication, as well as a keepalive timer, etc. It's also written in Objective C which makes it a natural to use in Fire. > http://nitro.jabberstudio.org/ >-Jason > >On Friday, July 25, 2003, at 10:24 AM, Paschoud Alain wrote: >>I downloaded Fire sources to have debugs (I didn't find a way to activate them without to recompile). I printed the XML packets sent and received. I did the same with Jabberfox. >> >>Here are the results (out = out for the client): >> >>--> Fire : >> >>OUT: >><?xml version='1.0'?> >> >>OUT: >><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' to='jabber.smartdata.ch'> >> >>OUT: >><iq type='set' id='1'> >><query xmlns='jabber:iq:auth'> >><username>apaschou</username> >><resource>everybuddy</resource> >><password>mypassword</password> >></query></iq> >> >>IN: >><?xml version='1.0'?> >><stream:stream xmlns:stream='http://etherx.jabber.org/streams' id='3F21608D' xmlns='jabber:client' from='jabber.smartdata.ch'> >><iq type='error' id='1'> >><query xmlns='jabber:iq:auth'> >><username>apaschou</username> >><resource>everybuddy</resource> >><password>mypassword</password> >></query><error code='401'>Unauthorized</error></iq> >> >> >>--> JabberFox (some incorrect spaces could remain) : >> >>OUT: >><?xml version="1.0" encoding="UTF-8" ?> >> >>OUT: >><stream:stream to='jabber.smartdata.ch' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'> >> >>IN: >><?xml version='1.0'?> >>< stream:stream xmlns:stream='http://etherx.jabber.org/streams' id ='3F200277' xmlns='jabber:client ' from='jabber.smartdata.ch'> >> >>OUT: >><iq to ="jabber.smartdata.ch" type="get" id="aad4"> >><query xmlns="jabber:iq:auth"> >><username>apaschou</username> >></query></iq> >> >>IN: >><iq type='result' id=' aad4'> >><query xmlns='jabber:iq:auth'> >><username>apaschou</username> >><digest/><sequence>296</sequenc e> >><token>3CB68B92</token> >><resource/></query></iq > >> >>OUT: >><iq to ="jabber.smartda ta.ch" type="set" id="aaf1"> >><query xmlns="jabber :iq:auth"> >><username>apaschou</username> >><resource>JabberFoX</resource> >><hash>1ca1f b58645a3e2f9ae4c0170bec148f28bd0 5a7</hash></query></iq> >> >> >>In this logs, I see two main differences : >> >>Jabber Fox sends a <id> with parameter type="get" >>Fire sends a <id> with parameter type="set" >> >>JabberFox only send the username in its <query> >>Fire sends username and password in its <query> >> >>Fire do something wrong. But I didn't find any easy way to correct that in the sources. I just get them and I didn't understand exactly how things are done. >> >>If someone has a patch to propose, let me know, I will test it. >> >>Best regards. >> >> >>------------------------------------------------------- >>This SF.Net email sponsored by: Free pre-built ASP.NET sites including >>Data Reports, E-commerce, Portals, and Forums are available now. >>Download today and enter to win an XBOX or Visual Studio .NET. >>http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >>_______________________________________________ >>Fire-talk mailing list >>Fir...@li... >>https://lists.sourceforge.net/lists/listinfo/fire-talk > > > >------------------------------------------------------- >This SF.Net email sponsored by: Free pre-built ASP.NET sites including >Data Reports, E-commerce, Portals, and Forums are available now. >Download today and enter to win an XBOX or Visual Studio .NET. >http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 >_______________________________________________ >Fire-talk mailing list >Fir...@li... >https://lists.sourceforge.net/lists/listinfo/fire-talk |