aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/FAQ7
-rw-r--r--doc/gpg.sgml9
2 files changed, 15 insertions, 1 deletions
diff --git a/doc/FAQ b/doc/FAQ
index a7ca82cc7..bbfb27df3 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -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
diff --git a/doc/gpg.sgml b/doc/gpg.sgml
index 3ff12a4c7..fc63bdcb5 100644
--- a/doc/gpg.sgml
+++ b/doc/gpg.sgml
@@ -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>