--FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
> From discussions so far, my sense is that SASL and TLS support will be=20 > 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. --=20 Robert Norris GPG: 1024D/FC18E6C2 Email+Jabber: [EMAIL PROTECTED] Web: http://cataclysm.cx/ --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/JcnDWb13Z/wY5sIRAjlmAJ9X4IJJBhay+2Lr3pDdvl6abqpwMQCeMv5m Y0tpvWXFPq8seKNlTUOtMQQ= =N3i4 -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
