aboutsummaryrefslogtreecommitdiffstats
path: root/doc/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ14
1 files changed, 11 insertions, 3 deletions
diff --git a/doc/FAQ b/doc/FAQ
index cffb265a3..8d84af480 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -346,10 +346,10 @@
material?
A: No. For example you can add or remove "Comment:" lines. They
have a purpose like the mail header lines. However a "Hash:"
- line is needed for modern signatures, to tell the parser which
+ line is needed for OpenPGG signatures to tell the parser which
hash algorithm to use.
- Q: Now can a get list of key IDs used to encrypt a message?
+ Q: How can a get list of key IDs used to encrypt a message?
A: gpg --batch --decrypt --status-fd 1 2>/dev/null \
| awk '/^\[GNUPG:\] ENC_TO / { print $3 }'
@@ -357,9 +357,17 @@
Q: PGP 5.x, 6.x does not like my secret key.
A: PGP probaly bails out on some private comment packets used by GnuPG.
These packets are fully in compliance with OpenPGP; however PGP is not
- really OPenPGP aware. A workaround is to eport the secret keys with
+ really OpenPGP aware. A workaround is to eport the secret keys with
this command:
gpg --export-secret-keys --no-comment -a your-key-id
+ Q: I can't decrypt my symmetrical only (-c) encrypted message with
+ a new version of GnuPG.
+ A: There used to be a bug in GnuPG < 1.0.1 which happens only if 3DES
+ was used for symmetric only encryption (this has never been the default).
+ The bug has been fixed but to enable you to decrypt old messages, you
+ should run gpg with the option "--emulate-3des-s2k-bug", decrypt the
+ message and encrypt it again without this option. The option will
+ be removed in 1.1, so better re/encrypt your message now.