[jdev] cert handling in xmpp *client* implementations

[Peter Saint-Andre]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Speaking of cert handling, how do jabber/xmpp clients currently handle
server certificates? One approach would be to use the existing Mozilla
NSS store, which is on Linux distros and even many Windows distros. But
it would be good for clients to "do the right thing" in handling the
certs for jabber/xmpp servers (I guess that would mean following best
practices derived from the browser and email client markets).

Perhaps it would be good to document such best practices? Section 14.2
of RFC 3920 talks about this, but the text there may be a bit opaque for
many client developers...

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEdNQ9NF1RSzyt3NURAi9xAJ42ecHCegfJppXmHg0KXzDspyvKQACeJTEm
FrC8c2IMiLCHHURxJza+zWw=
=MGg+
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20060524/1c430f02/attachment-0002.bin>