-----BEGIN PGP SIGNED MESSAGE-----
In
<3(_dot_)0(_dot_)5(_dot_)32(_dot_)19980321103445(_dot_)008b4180(_at_)popd(_dot_)ix(_dot_)netcom(_dot_)com>,
on 03/21/98
at 10:34 AM, Bill Stewart <bill(_dot_)stewart(_at_)pobox(_dot_)com> said:
It is a matter of principle. If the recipient can't read it, sending it
has no value, so there should be a common algorithm available. If the
recipient doesn't trust anything but 3DES, why should you annoy him by
sending him messages he can't read?
If you don't trust RSA, and always want send out your messages using
ElGamal public keys, why should you be prevented from doing so? Don't
let the mere fact that the recipient doesn't have an ElGamal key bother
you :-)
If you're paranoid enough that you insist that your messages be encrypted
with CAST5, do that, add a note saying it's encrypted with CAST5, and
encrypt that with the 3DES the recipient wants.
You seem to be missing the point here. Why should the recipiant mandate
how I encrypt my messages? It is *my* message! These are *preferences* not
mandates. The owner of a key may chose not to put any algorithm
*preferences* in his key should all communications to this user then be
forced to use 3DES dispite the fact he is capable of decrypting other
algorithms??
This really seems like artifical restrictions in the spec that are not
needed.
- --
- ---------------------------------------------------------------
William H. Geiger III http://users.invweb.net/~whgiii
Geiger Consulting Cooking With Warp 4.0
Author of E-Secure - PGP Front End for MR/2 Ice
PGP & MR/2 the only way for secure e-mail.
OS/2 PGP 2.6.3a at: http://users.invweb.net/~whgiii/esecure.html
- ---------------------------------------------------------------
Tag-O-Matic: You're throwing it all out the Windows!
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a-sha1
Charset: cp850
Comment: Registered_User_E-Secure_v1.1b1_ES000000
iQCVAwUBNRP/ZY9Co1n+aLhhAQEEwwP+Oqz2YD7z5dpChzXnwV9Vu4K5ouHvMiR4
X2aaKj1y8FRYOKNFt28rgQjm9K6iV3rIkn7Ge0ZRJhDxKoRec1iRzAEgRo2184be
oZOjp87OtxrqT673JCqVU11jEEN25rMObLr7yvIYXEvzOVD23fhibUxnOkeqOUA6
LQcrlTGzrr0=
=5Ien
-----END PGP SIGNATURE-----