security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-10 13:04:23 +01:00
Code Activity

* gpg.sgml: Add an interoperability section.

Browse Source
This commit is contained in:
David Shaw 2002-11-22 03:53:53 +00:00
parent 1c6bcef3ce
commit 2bb29764af
2 changed files with 28 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ChangeLog
View File

@ -1,3 +1,7 @@
2002-11-21 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Add an interoperability section.
2002-11-17 David Shaw <dshaw@jabberwocky.com>
* gpg.sgml: Correct defaults for --s2k-mode and --s2k-digest-mode.

25
doc/gpg.sgml
View File

@ -2518,6 +2518,30 @@ command line or using <literal>-</literal> to specify stdin.
</para>
</refsect1>
<refsect1>
<title>INTEROPERABILITY WITH OTHER OPENPGP PROGRAMS</title>
<para>
GnuPG tries to be a very flexible implementation of the OpenPGP
standard. In particular, GnuPG implements many of the "optional"
parts of the standard, such as the RIPEMD/160 hash, and the ZLIB
compression algorithms. It is important to be aware that not all
OpenPGP programs implement these optional algorithms and that by
forcing their use via the --cipher-algo, --digest-algo,
--cert-digest-algo, or --compress-algo options in GnuPG, it is
possible to create a perfectly valid OpenPGP message, but one that
cannot be read by the intended recipient.
</para>
<para>
For example, as of this writing, no version of official PGP supports
the BLOWFISH cipher algorithm. If you use it, no PGP user will be
able to decrypt your message. The same thing applies to the ZLIB
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>
</refsect1>
<refsect1>
<title>BUGS</title>
@ -2532,4 +2556,3 @@ as locked memory is allocated.
</refsect1>
</refentry>