diff options
| author | Werner Koch <[email protected]> | 1998-11-25 11:55:58 +0000 |
|---|---|---|
| committer | Werner Koch <[email protected]> | 1998-11-25 11:55:58 +0000 |
| commit | 71134011e3dc4beec17306c797b72d37aa2f52da (patch) | |
| tree | d717032e418f5b93bb63b560913b142e168d64d3 /doc/FAQ | |
| parent | Restructured the RNG source and add support for loadable (diff) | |
| download | gnupg-71134011e3dc4beec17306c797b72d37aa2f52da.tar.gz gnupg-71134011e3dc4beec17306c797b72d37aa2f52da.zip | |
Some experimental support for other random gatheres
Diffstat (limited to 'doc/FAQ')
| -rw-r--r-- | doc/FAQ | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -299,3 +299,18 @@ above key and user ID, if it is a signature which is direct on a key, the user ID part is empty (..//..). + + Q: How do I sign a patch file? + A: Use "gpg --clearsign --not-dash-escaped ...". + The problem with --clearsign is + that all lines starting with a dash are quoted with "- "; obviously + diff produces many of lines starting with a dash and these are + then quoted and that is not good for patch ;-). In order 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 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. + + |