mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
Expiration time works (I hope so)
This commit is contained in:
parent
f9d2bd8cb9
commit
47c61bafe3
35 changed files with 7147 additions and 2848 deletions
|
@ -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
|
||||
|
||||
|
||||
|
||||
|
|
10
doc/gpg.1pod
10
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
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue