From d37aad469c432a6a3d08b42baf222b74e5ac01d9 Mon Sep 17 00:00:00 2001 From: David Shaw Date: Sun, 1 Dec 2002 21:06:13 +0000 Subject: * gpg.sgml: Point out that if the user absolutely must, it's better to use --pgpX than forcing an algorithm manually. Better still not to use anything, of course. CVS: ---------------------------------------------------------------------- gpg.sgml CVS: ---------------------------------------------------------------------- --- doc/ChangeLog | 6 ++++++ doc/gpg.sgml | 9 +++++++++ 2 files changed, 15 insertions(+) diff --git a/doc/ChangeLog b/doc/ChangeLog index bf7baa5f1..c0c7cd32c 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,9 @@ +2002-12-01 David Shaw + + * gpg.sgml: Point out that if the user absolutely must, it's + better to use --pgpX than forcing an algorithm manually. Better + still not to use anything, of course. + 2002-11-25 David Shaw * gpg.sgml: Document --primary-keyring. Clarify diff --git a/doc/gpg.sgml b/doc/gpg.sgml index af06de9c6..b34468afe 100644 --- a/doc/gpg.sgml +++ b/doc/gpg.sgml @@ -2561,6 +2561,15 @@ compression algorithm. By default, GnuPG will do the right thing and create messages that are usable by any OpenPGP program. Only override this safe default if you know what you are doing. + + +If you absolutely must override the safe default, you are far better +off using the --pgp2, --pgp6, or --pgp7 options. These options are +safe as they do not force any particular algorithms in violation of +OpenPGP, but rather reduce the available algorithms to a "PGP-safe" +list. + + -- cgit v1.2.3