mirror of
git://git.gnupg.org/gnupg.git
synced 2025-01-21 14:47:03 +01:00
About to release 1.2.4 - forgot to manually update this file
This commit is contained in:
parent
be3412b72a
commit
9c7f081826
57
doc/gpg.texi
57
doc/gpg.texi
@ -352,11 +352,11 @@ must be specified by fingerprint.
|
|||||||
Same as ---delete-key, but if a secret key exists, it will be removed
|
Same as ---delete-key, but if a secret key exists, it will be removed
|
||||||
first. In batch mode the key must be specified by fingerprint.
|
first. In batch mode the key must be specified by fingerprint.
|
||||||
|
|
||||||
@item ---gen-revoke
|
@item ---gen-revoke @code{name}
|
||||||
Generate a revocation certificate for the complete key. To revoke
|
Generate a revocation certificate for the complete key. To revoke
|
||||||
a subkey or a signature, use the ---edit command.
|
a subkey or a signature, use the ---edit command.
|
||||||
|
|
||||||
@item ---desig-revoke
|
@item ---desig-revoke @code{name}
|
||||||
Generate a designated revocation certificate for a key. This allows a
|
Generate a designated revocation certificate for a key. This allows a
|
||||||
user (with the permission of the keyholder) to revoke someone else's
|
user (with the permission of the keyholder) to revoke someone else's
|
||||||
key.
|
key.
|
||||||
@ -506,9 +506,9 @@ have GnuPG append the new extension. This option has no effect on
|
|||||||
non-Windows platforms.
|
non-Windows platforms.
|
||||||
|
|
||||||
@item -u, ---local-user @code{name}
|
@item -u, ---local-user @code{name}
|
||||||
Use @code{name} as the user ID to sign.
|
Use @code{name} as the user ID to sign with. This option is silently
|
||||||
This option is silently ignored for the list commands,
|
ignored for the list commands, so that it can be used in an options
|
||||||
so that it can be used in an options file.
|
file.
|
||||||
|
|
||||||
@item ---default-key @code{name}
|
@item ---default-key @code{name}
|
||||||
Use @code{name} as default user ID for signatures. If this
|
Use @code{name} as default user ID for signatures. If this
|
||||||
@ -643,22 +643,20 @@ ID is bound to the key.
|
|||||||
Identical to `---trust-model always'. This option is deprecated.
|
Identical to `---trust-model always'. This option is deprecated.
|
||||||
|
|
||||||
@item ---keyserver @code{name}
|
@item ---keyserver @code{name}
|
||||||
Use @code{name} as your keyserver. This is the server that ---recv-keys,
|
Use @code{name} as your keyserver. This is the server that
|
||||||
---send-keys, and --search-keys will communicate with to receive keys
|
---recv-keys, --send-keys, and --search-keys will communicate with to
|
||||||
from, send keys to, and search for keys on. The format of the
|
receive keys from, send keys to, and search for keys on. The format
|
||||||
@code{name} is a URI: `scheme:[//]keyservername[:port]' The scheme is
|
of the @code{name} is a URI: `scheme:[//]keyservername[:port]' The
|
||||||
the type of keyserver: "hkp" for the HTTP (or compatible) keyservers,
|
scheme is the type of keyserver: "hkp" for the HTTP (or compatible)
|
||||||
"ldap" for the NAI LDAP keyserver, or "mailto" for the Graff email
|
keyservers, "ldap" for the NAI LDAP keyserver, or "mailto" for the
|
||||||
keyserver. Note that your particular installation of GnuPG may have
|
Graff email keyserver. Note that your particular installation of
|
||||||
other keyserver types available as well. Keyserver schemes are
|
GnuPG may have other keyserver types available as well. Keyserver
|
||||||
case-insensitive.
|
schemes are case-insensitive.
|
||||||
|
|
||||||
Most keyservers synchronize with each other, so there is generally no
|
Most keyservers synchronize with each other, so there is generally no
|
||||||
need to send keys to more than one server. Using the command "host -l
|
need to send keys to more than one server. The keyserver
|
||||||
pgp.net | grep wwwkeys" gives you a list of HKP keyservers. When
|
"hkp://subkeys.pgp.net" uses round robin DNS to give a different
|
||||||
using one of the wwwkeys servers, due to load balancing using
|
keyserver each time you use it.
|
||||||
round-robin DNS you may notice that you get a different key server
|
|
||||||
each time.
|
|
||||||
|
|
||||||
@item ---keyserver-options @code{parameters}
|
@item ---keyserver-options @code{parameters}
|
||||||
This is a space or comma delimited string that gives options for the
|
This is a space or comma delimited string that gives options for the
|
||||||
@ -936,7 +934,7 @@ must contain a '@@' character. This is to help prevent pollution of
|
|||||||
the IETF reserved notation namespace. The ---expert flag overrides the
|
the IETF reserved notation namespace. The ---expert flag overrides the
|
||||||
'@@' check. @code{value} may be any printable string; it will be
|
'@@' check. @code{value} may be any printable string; it will be
|
||||||
encoded in UTF8, so you should check that your ---charset is set
|
encoded in UTF8, so you should check that your ---charset is set
|
||||||
correctly. If you prefix @code{name} with an exclamation mark, the
|
correctly. If you prefix @code{name} with an exclamation mark (!), the
|
||||||
notation data will be flagged as critical (rfc2440:5.2.3.15).
|
notation data will be flagged as critical (rfc2440:5.2.3.15).
|
||||||
---sig-notation sets a notation for data signatures. --cert-notation
|
---sig-notation sets a notation for data signatures. --cert-notation
|
||||||
sets a notation for key signatures (certifications). ---set-notation
|
sets a notation for key signatures (certifications). ---set-notation
|
||||||
@ -962,8 +960,8 @@ as well as when verifying a signature with a notation in it.
|
|||||||
@itemx ---cert-policy-url @code{string}
|
@itemx ---cert-policy-url @code{string}
|
||||||
@itemx ---set-policy-url @code{string}
|
@itemx ---set-policy-url @code{string}
|
||||||
Use @code{string} as Policy URL for signatures (rfc2440:5.2.3.19). If
|
Use @code{string} as Policy URL for signatures (rfc2440:5.2.3.19). If
|
||||||
you prefix it with an exclamation mark, the policy URL packet will be
|
you prefix it with an exclamation mark (!), the policy URL packet will
|
||||||
flagged as critical. ---sig-policy-url sets a a policy url for data
|
be flagged as critical. ---sig-policy-url sets a a policy url for data
|
||||||
signatures. ---cert-policy-url sets a policy url for key signatures
|
signatures. ---cert-policy-url sets a policy url for key signatures
|
||||||
(certifications). ---set-policy-url sets both.
|
(certifications). ---set-policy-url sets both.
|
||||||
|
|
||||||
@ -1529,7 +1527,7 @@ in front.
|
|||||||
|
|
||||||
@end table
|
@end table
|
||||||
|
|
||||||
Note that you can append an exclamation mark to key IDs or
|
Note that you can append an exclamation mark (!) to key IDs or
|
||||||
fingerprints. This flag tells GnuPG to use exactly the given primary
|
fingerprints. This flag tells GnuPG to use exactly the given primary
|
||||||
or secondary key and not to try to figure out which secondary or
|
or secondary key and not to try to figure out which secondary or
|
||||||
primary key to use.
|
primary key to use.
|
||||||
@ -1557,12 +1555,13 @@ show fingerprint
|
|||||||
|
|
||||||
@item gpg ---verify @code{pgpfile}
|
@item gpg ---verify @code{pgpfile}
|
||||||
@itemx gpg ---verify @code{sigfile} @code{files}
|
@itemx gpg ---verify @code{sigfile} @code{files}
|
||||||
Verify the signature of the file but do not output the data. The second form
|
Verify the signature of the file but do not output the data. The
|
||||||
is used for detached signatures, where @code{sigfile} is the detached
|
second form is used for detached signatures, where @code{sigfile}
|
||||||
signature (either ASCII armored of binary) and @code{files} are the signed
|
is the detached signature (either ASCII armored or binary) and
|
||||||
data; if this is not given the name of the file holding the signed data is
|
@code{files} are the signed data; if this is not given, the name of
|
||||||
constructed by cutting off the extension (".asc" or ".sig") of
|
the file holding the signed data is constructed by cutting off the
|
||||||
@code{sigfile} or by asking the user for the filename.
|
extension (".asc" or ".sig") of @code{sigfile} or by asking the
|
||||||
|
user for the filename.
|
||||||
|
|
||||||
@end table
|
@end table
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user