From 47c61bafe3545f17e8244902dca0ff00077d0feb Mon Sep 17 00:00:00 2001 From: Werner Koch Date: Fri, 20 Nov 1998 17:42:18 +0000 Subject: Expiration time works (I hope so) --- doc/OpenPGP | 3 ++- doc/gpg.1pod | 10 ++++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) (limited to 'doc') 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 Read the passphrase from file descriptor I. If you use 0 for I, the passphrase will be read from stdin. This -- cgit v1.2.3