diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/FAQ | 16 | ||||
| -rw-r--r-- | doc/gpg.1pod | 3 |
2 files changed, 17 insertions, 2 deletions
@@ -99,7 +99,7 @@ at least for decryption). To be more inter-operable, GNUPG (starting with version 0.3.3) now also uses type 16 for the ElGamal subkey which is created if the default key algorithm - is chosen. You may add an type 16 ElGamal key to your public + is chosen. You may add an type 16 ElGamal key to your public key which is easy as your key signatures are still valid. Q: Why is PGP 5.x not able to verify my messages? @@ -304,9 +304,21 @@ dash and these are then quoted and that is not good for patch ;-). To use a patch file without removing the cleartext signature, the special option --not-dash-escaped may be used to suppress generation of these - escape sequences. You should not mail such a patch because spaces and + escape sequences. You should not mail such a patch because spaces and line endings are also subject to the signature and a mailer may not preserve these. If you want to mail a file you can simply sign it using your MUA. + Q: Where is the "encrypt-to-self" option? + A: Use "--encrypt-to your_keyid". You can use more than one + of these options. To temporary override the use of this additional + keys, you can use the option "--no-encrypt-to". + + + Q: How can I get rid of the Version and Comment headers in + armored messages? + A: Use "--no-version --comment ''". Note that the left over blank line + is required by the protocol. + + diff --git a/doc/gpg.1pod b/doc/gpg.1pod index 2ac02cecc..5fa703dab 100644 --- a/doc/gpg.1pod +++ b/doc/gpg.1pod @@ -265,6 +265,9 @@ B<--encrypt-to> I<name> either by use of --recipient or by the asked user id. No trust checking is performed for these user ids. +B<--no-encrypt-to> + Disable the use of all B<--encrypt-to> keys. + B<-v>, B<--verbose> Give more information during processing. If used twice, the input data is listed in detail. |