Policy-Discussion

[Peter Saint-Andre <stpeter AT jabber.org>]

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

Ian G wrote:
> Peter Saint-Andre wrote:
> 
>>> Today's musings (and trying to keep the mission threat
>>> alive!)
>>
>>
>> Hmm, yes, a mission can be seen as a threat, eh? ;-)
> 
> Ha!
> 
> In a military sense, one side is always threatened, yes :)

Exactly.

> How's tricks?  How's the IM world?  Did they ever get
> their crypto sorted out?

In the Jabber world we use TLS for channel encryption and have been
making good progress with Duane on including the right ASN.1 bits (see
Section 5.1.1 of RFC 3920) in domain certificates to use CAcert-issued
certificates for secure server-to-server federation. Then we do SASL
EXTERNAL for auth and Bob's your uncle.

Of course, if you don't trust the servers (and naturally you shouldn't)
then we need end-to-end encryption, but we still haven't worked out a
commonly-used system for that. :(  (Some clients do OpenPGP, none do the
S/MIME stuff in RFC 3923, and the OTR-like protocol in JEP-0116 is still
experimental.)

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

iD8DBQFD9KwNNF1RSzyt3NURAnA6AKDasz0jKzg4SkrALjeNKDjLu21P+ACgx80G
tiWTXg1Fe0ND9aOrub7J1Eg=
=1WO3
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature