aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>1998-11-20 17:42:18 +0000
committerWerner Koch <[email protected]>1998-11-20 17:42:18 +0000
commit47c61bafe3545f17e8244902dca0ff00077d0feb (patch)
tree0867aa7d405a1df94ac360b5cc2814e97dcbe115 /doc
parentsome bug fixes (diff)
downloadgnupg-47c61bafe3545f17e8244902dca0ff00077d0feb.tar.gz
gnupg-47c61bafe3545f17e8244902dca0ff00077d0feb.zip
Expiration time works (I hope so)
Diffstat (limited to 'doc')
-rw-r--r--doc/OpenPGP3
-rw-r--r--doc/gpg.1pod10
2 files changed, 12 insertions, 1 deletions
diff --git a/doc/OpenPGP b/doc/OpenPGP
index 62f9cbac0..60fede3e0 100644
--- a/doc/OpenPGP
+++ b/doc/OpenPGP
@@ -1,7 +1,8 @@
GnuPG and OpenPGP
=================
- See RFC2440 for a description of OpenPGP.
+ See RFC2440 for a description of OpenPGP. I have an annotated version
+ of this RFC online: http://www.d.shuttle.de/isil/gnupg/rfc2440.html
diff --git a/doc/gpg.1pod b/doc/gpg.1pod
index 025813956..ebee20db7 100644
--- a/doc/gpg.1pod
+++ b/doc/gpg.1pod
@@ -401,6 +401,16 @@ B<--throw-keyid>
against traffic analysis. It may slow down the decryption
process because all available secret keys are tried.
+B<--not-dash-escaped>
+ This option changes the behaviour of cleartext signature
+ so that they can be used for patch files. You should not
+ send such an armored file via email because all spaces
+ and line endings are hashed too. You can not use this
+ option for data which has 5 dashes somewhere at the
+ beginning of a line - patch files don't have this.
+ A special armor header line tells GnuPG about this
+ cleartext signature framework.
+
B<--passphrase-fd> I<n>
Read the passphrase from file descriptor I<n>. If you use
0 for I<n>, the passphrase will be read from stdin. This