[JDEV] XMPP implementation questions

[Robert Norris]

> From discussions so far, my sense is that SASL and TLS support will be 
> added once it's in the jabberd server, but that client developers are
> fairly resistant to adding support for the end-to-end encryption spec
> given the need to parse CPIM formats (no existing libraries as far as I
> know) and support S/MIME (for which there are libraries, although the
> use of S/MIME is not very "Jabberish").

jabberd2 currently supports SASL (PLAIN and DIGEST-MD5) and TLS. Its
worth noting that the DIGEST-MD5 implementation doesn't support security
layers, so TLS is required for encryption. I expect that this is the way
most people will choose to go for encryption anyway as it has all the
normal server identification stuff and whatnot.

E2E is out of scope for a server, a fact that I'm eternally grateful
for :)

Rob.

-- 
Robert Norris                                       GPG: 1024D/FC18E6C2
Email+Jabber: rob at cataclysm.cx                Web: http://cataclysm.cx/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20030729/c2210ed9/attachment-0002.pgp>