<div>By secure connection I mean being able to send and receive xml packets that can't be intercepted and decoded by a third party. So anything that achieves that is good for me. </div> <div> </div> <div>I use the XIFF library for dealing with XMPP (<A href="http://www.jivesoftware.org/xiff">http://www.jivesoftware.org/xiff</A>) </div> <div>It's built for Flash Actionscript 2.0 and it's exactly what I need except it doesn't do TLS+SASL.</div> <div> </div> <div>So let me get this straight: </div> <div>In order to use TLS + SASL : </div> <div>I send out a command <starttls bla bla /></div> <div>Server sends <proceed > </div> <div>I then start a new stream, select a mechanism (digest md-5), </div> <div>server sends a challenge (base64 encoded) </div> <div> </div> <div>I decode that but I don't know what to send back. The specs say I shoud send this :</div> <div> </div>
<div>username="somenode",realm="somerealm",\<BR>nonce="OA6MG9tEQGm2hh",cnonce="OA6MHXh6VqTrRk",\<BR>nc=00000001,qop=auth,digest-uri="xmpp/example.com",\<BR>response=d388dad90d4bbd760a152321f2143af7,charset=utf-8<BR></div> <div>What are these : username, realm, nonce, cnonce, nc, qop, digest-uri, response ? </div> <div>Where do I get them from ? </div> <div> </div> <div>(Sorry to be dense) </div> <div> </div> <div> </div> <div> </div> <div><BR><BR><B><I>Peter Saint-Andre <stpeter@jabber.org></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-----BEGIN PGP SIGNED MESSAGE-----<BR>Hash: SHA1<BR><BR>Adrian Adrian wrote:<BR>> Hello,<BR>> I'm totally new with the xmpp protocol so this questions may seem too<BR>> easy if not plain stupid.<BR>> I want to comunicate with the the im (wildfire) server through TLS.So I<BR>> do what the docs tell me to do :<BR>> I
send this command :<BR>> <STARTTLS xmlns="urn:ietf:params:xml:ns:xmpp-tls" /><BR>> And server responds with :<BR>> <PROCEED xmlns="urn:ietf:params:xml:ns:xmpp-tls" /><BR>> Now, if I read the docs correctly, I have to start a new stream and<BR>> begin SASL negotiation. Is this correct ?<BR>> If so, more questions will follow :) The digest-md5 is really making my<BR>> head spin.<BR>> Isn't there an easier way to establish a secure connection ? (without<BR>> receiving challenges and stuff)<BR><BR>Depends on what you mean by secure. :-)<BR><BR>There is an older, nearly-deprecated method for authentication between<BR>clients and servers:<BR><BR>http://www.jabber.org/jeps/jep-0078.html<BR><BR>In the old days clients could connect on a separate SSL-enabled port<BR>(usually 5223, though that was never codified).<BR><BR>But with RFC 3920, it is preferred to upgrade to TLS on port 5222 and<BR>then use SASL for authentication.<BR><BR>Are you writing your own library?
Why not use one of the existing code<BR>libraries that already does TLS+SASL?<BR><BR>Peter<BR><BR>- --<BR>Peter Saint-Andre<BR>Jabber Software Foundation<BR>http://www.jabber.org/people/stpeter.shtml<BR><BR>-----BEGIN PGP SIGNATURE-----<BR>Version: GnuPG v1.4.1 (Darwin)<BR>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org<BR><BR>iD8DBQFEGyLANF1RSzyt3NURAh6NAKDL/MysQyIZMTzojaZQdBI1m3kL/ACgvRbz<BR>45Y3Jk8Co9PM7AJ5QfZEnF4=<BR>=Y+/I<BR>-----END PGP SIGNATURE-----<BR></BLOCKQUOTE><BR><p>
<hr size=1>Relax. Yahoo! Mail
<a href="http://us.rd.yahoo.com/mail_us/taglines/virusall/*http://communications.yahoo.com/features.php?page=221">virus scanning</a> helps detect nasty viruses!