security-and-privacy/gnupg
security-and-privacy
/
gnupg
mirror of git://git.gnupg.org/gnupg.git
1
0
Fork 0
Code Releases Activity

* 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:
----------------------------------------------------------------------
This commit is contained in:
David Shaw 2002-12-01 21:06:13 +00:00
parent 8dfe1d4348
commit d37aad469c
2 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/ChangeLog
View File

@ -1,3 +1,9 @@
2002-12-01 David Shaw <dshaw@jabberwocky.com>
* 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 <dshaw@jabberwocky.com>
* gpg.sgml: Document --primary-keyring. Clarify

9
doc/gpg.sgml
View File

@ -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.
</para>
<para>
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.
</para>
</refsect1>