security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

See ChangeLog: Mon Jun 5 23:41:54 CEST 2000 Werner Koch

Browse source
This commit is contained in:
Werner Koch 2000-06-05 21:28:41 +00:00
parent b65f9a8b0d
commit 2f64c3538a
10 changed files with 57 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/FAQ
View file

@ -398,11 +398,16 @@
revoke all the subkeys installed on that machine and install new
subkeys.
Q: In the edit meu the trust values is not displayed correctly after
Q: In the edit menu the trust values is not displayed correctly after
signing uids - why?
A: This happens because the some informations are stored immediately
in the trustdb, but the actual trust calculation can be done after
the save command. This is a not easy to fix design bug which will be
addressed in GnuPG 1.1
Q: An Elgamal signature does not verify anymore since version 1.0.2
A: Use the option --emulate-md-encode-bug.
Q: Old versions of GnuPG can't verify ElGamal signatures
A: Update to GnuPG 1.0.2

9
doc/gpg.sgml
View file

@ -1312,6 +1312,15 @@ This is not for normal use. Use the source to see for what it might be useful.
This is not for normal use. Use the source to see for what it might be useful.
</para></listitem></varlistentry>
<varlistentry>
<term>--emulate-md-encode-bug</term>
<listitem><para>
GnuPG versions prior to 1.0.2 had a bug in the way a signature was encode.
This options enables a workaround by checking faulty signatures again with
the encoding used in old versions. This may only happen for ElGamal signatures
which are not widely used.
</para></listitem></varlistentry>
</variablelist>
</refsect1>