Suggestion...

[L. Sassaman]

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

If I may make one.

I propose an option (that could be turned off by setting
- --no-compatability-warning as an argument/config file line) that would
warn the user when he or she was about to do something that would prohibit
communication with PGP.

Examples are: Generate an ElGamal Signing key, specify Blowfish as the
default symmetric cipher (only an issue if you want to use that private
key in PGP later), set a hash other than SHA-1 for use with DSS keys, etc.

It can only help the users if they are made aware of the possible
compatability problems such options might cause. If communication with PGP
users is not a concern, they can simply turn off such warnings. But this
idea might head off the recurring posts that read "GnuPG isn't compatable
with PGP, this sucks!"

Just a thought.


- --Len.

__

L. Sassaman

System Administrator                |  "All of the chaos
Technology Consultant               |   Makes perfect sense..."
icq.. 10735603                      |
pgp.. finger://ns.quickie.net/rabbi |              --Joe Diffie



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1d (GNU/Linux)
Comment: OpenPGP Encrypted Email Preferred.

iD8DBQE44FsWPYrxsgmsCmoRAgLcAKCQRxuJxqExs9LPXIZUVOsEGgX0HwCgkKsc
TlOr4c81MWw/qAanLUJbj5w=
=4jy4
-----END PGP SIGNATURE-----