| Current File : //usr/man/man1/gpg2.1 |
'\" te
.\" Created from Texinfo source by yat2m 1.0
.TH GPG2 1 2015-08-20 "GnuPG 2.0.27" "GNU Privacy Guard"
.SH NAME
.B gpg2
\- OpenPGP encryption and signing tool
.SH SYNOPSIS
.B gpg2
.RB [ \-\-homedir
.IR dir ]
.RB [ \-\-options
.IR file ]
.RI [ options ]
.I command
.RI [ args ]
.SH DESCRIPTION
\fBgpg2\fR is the OpenPGP part of the GNU Privacy Guard (GnuPG). It
is a tool to provide digital encryption and signing services using the
OpenPGP standard. \fBgpg2\fR features complete key management and
all bells and whistles you can expect from a decent OpenPGP
implementation.
In contrast to the standalone version \fBgpg\fR, which is more
suited for server and embedded platforms, this version is commonly
installed under the name \fBgpg2\fR and more targeted to the desktop
as it requires several other modules to be installed. The standalone
version will be kept maintained and it is possible to install both
versions on the same system. If you need to use different configuration
files, you should make use of something like \(oq\fIgpg.conf-2\fR\(cq instead
of just \(oq\fIgpg.conf\fR\(cq.
.SH RETURN VALUE
The program returns 0 if everything was fine, 1 if at least
a signature was bad, and other error codes for fatal errors.
.SH WARNINGS
Use a *good* password for your user account and a *good* passphrase
to protect your secret key. This passphrase is the weakest part of the
whole system. Programs to do dictionary attacks on your secret keyring
are very easy to write and so you should protect your "~/.gnupg/"
directory very well.
Keep in mind that, if this program is used over a network (telnet), it
is *very* easy to spy out your passphrase!
If you are going to verify detached signatures, make sure that the
program knows about it; either give both filenames on the command line
or use \(aq-\(aq to specify STDIN.
.SH INTEROPERABILITY
GnuPG tries to be a very flexible implementation of the OpenPGP
standard. In particular, GnuPG implements many of the optional parts
of the standard, such as the SHA-512 hash, and the ZLIB and BZIP2
compression algorithms. It is important to be aware that not all
OpenPGP programs implement these optional algorithms and that by
forcing their use via the \fB--cipher-algo\fR,
\fB--digest-algo\fR, \fB--cert-digest-algo\fR, or
\fB--compress-algo\fR options in GnuPG, it is possible to create a
perfectly valid OpenPGP message, but one that cannot be read by the
intended recipient.
There are dozens of variations of OpenPGP programs available, and each
supports a slightly different subset of these optional algorithms.
For example, until recently, no (unhacked) version of PGP supported
the BLOWFISH cipher algorithm. A message using BLOWFISH simply could
not be read by a PGP user. By default, GnuPG uses the standard
OpenPGP preferences system that will always do the right thing and
create messages that are usable by all recipients, regardless of which
OpenPGP program they use. Only override this safe default if you
really know what you are doing.
If you absolutely must override the safe default, or if the preferences
on a given key are invalid for some reason, you are far better off using
the \fB--pgp6\fR, \fB--pgp7\fR, or \fB--pgp8\fR options. These
options are safe as they do not force any particular algorithms in
violation of OpenPGP, but rather reduce the available algorithms to a
"PGP-safe" list.
.SH COMMANDS
Commands are not distinguished from options except for the fact that
only one command is allowed.
\fBgpg2\fR may be run with no commands, in which case it will
perform a reasonable action depending on the type of file it is given
as input (an encrypted message is decrypted, a signature is verified,
a file containing keys is listed).
Please remember that option as well as command parsing stops as soon as
a non-option is encountered, you can explicitly stop parsing by
using the special option \fB--\fR.
.SS Commands not specific to the function
\
.TP
.B --version
Print the program version and licensing information. Note that you
cannot abbreviate this command.
.TP
.B --help
.TP
.B -h
Print a usage message summarizing the most useful command line options.
Note that you cannot abbreviate this command.
.TP
.B --warranty
Print warranty information.
.TP
.B --dump-options
Print a list of all available options and commands. Note that you cannot
abbreviate this command.
.SS Commands to select the type of operation
\
.TP
.B --sign
.TP
.B -s
Make a signature. This command may be combined with \fB--encrypt\fR
(for a signed and encrypted message), \fB--symmetric\fR (for a
signed and symmetrically encrypted message), or \fB--encrypt\fR and
\fB--symmetric\fR together (for a signed message that may be
decrypted via a secret key or a passphrase). The key to be used for
signing is chosen by default or can be set with the
\fB--local-user\fR and \fB--default-key\fR options.
.TP
.B --clearsign
Make a clear text signature. The content in a clear text signature is
readable without any special software. OpenPGP software is only needed
to verify the signature. Clear text signatures may modify end-of-line
whitespace for platform independence and are not intended to be
reversible. The key to be used for signing is chosen by default or
can be set with the \fB--local-user\fR and \fB--default-key\fR
options.
.TP
.B --detach-sign
.TP
.B -b
Make a detached signature.
.TP
.B --encrypt
.TP
.B -e
Encrypt data. This option may be combined with \fB--sign\fR (for a
signed and encrypted message), \fB--symmetric\fR (for a message that
may be decrypted via a secret key or a passphrase), or \fB--sign\fR
and \fB--symmetric\fR together (for a signed message that may be
decrypted via a secret key or a passphrase).
.TP
.B --symmetric
.TP
.B -c
Encrypt with a symmetric cipher using a passphrase. The default
symmetric cipher used is CAST5, but may be chosen with the
\fB--cipher-algo\fR option. This option may be combined with
\fB--sign\fR (for a signed and symmetrically encrypted message),
\fB--encrypt\fR (for a message that may be decrypted via a secret key
or a passphrase), or \fB--sign\fR and \fB--encrypt\fR together
(for a signed message that may be decrypted via a secret key or a
passphrase).
.TP
.B --store
Store only (make a simple RFC1991 literal data packet).
.TP
.B --decrypt
.TP
.B -d
Decrypt the file given on the command line (or STDIN if no file
is specified) and write it to STDOUT (or the file specified with
\fB--output\fR). If the decrypted file is signed, the signature is also
verified. This command differs from the default operation, as it never
writes to the filename which is included in the file and it rejects
files which don't begin with an encrypted message.
.TP
.B --verify
Assume that the first argument is a signed file or a detached signature
and verify it without generating any output. With no arguments, the
signature packet is read from STDIN. If only a sigfile is given, it may
be a complete signature or a detached signature, in which case the
signed stuff is expected in a file without the ".sig" or ".asc"
extension. With more than 1 argument, the first should be a detached
signature and the remaining files are the signed stuff. To read the
signed stuff from STDIN, use \(aq-\(aq as the second filename. For
security reasons a detached signature cannot read the signed material
from STDIN without denoting it in the above way.
Note: When verifying a cleartext signature, \fBgpg\fR verifies
only what makes up the cleartext signed data and not any extra data
outside of the cleartext signature or header lines following directly
the dash marker line. The option \fB--output\fR may be used to write
out the actual signed data; but there are other pitfalls with this
format as well. It is suggested to avoid cleartext signatures in
favor of detached signatures.
.TP
.B --multifile
This modifies certain other commands to accept multiple files for
processing on the command line or read from STDIN with each filename on
a separate line. This allows for many files to be processed at
once. \fB--multifile\fR may currently be used along with
\fB--verify\fR, \fB--encrypt\fR, and \fB--decrypt\fR. Note that
\fB--multifile --verify\fR may not be used with detached signatures.
.TP
.B --verify-files
Identical to \fB--multifile --verify\fR.
.TP
.B --encrypt-files
Identical to \fB--multifile --encrypt\fR.
.TP
.B --decrypt-files
Identical to \fB--multifile --decrypt\fR.
.TP
.B --list-keys
.TP
.B -k
.TP
.B --list-public-keys
List all keys from the public keyrings, or just the keys given on the
command line.
Avoid using the output of this command in scripts or other programs as
it is likely to change as GnuPG changes. See \fB--with-colons\fR for a
machine-parseable key listing command that is appropriate for use in
scripts and other programs.
.TP
.B --list-secret-keys
.TP
.B -K
List all keys from the secret keyrings, or just the ones given on the
command line. A \fB#\fR after the letters \fBsec\fR means that the
secret key is not usable (for example, if it was created via
\fB--export-secret-subkeys\fR).
.TP
.B --list-sigs
Same as \fB--list-keys\fR, but the signatures are listed too.
This command has the same effect as
using \fB--list-keys\fR with \fB--with-sig-list\fR.
For each signature listed, there are several flags in between the "sig"
tag and keyid. These flags give additional information about each
signature. From left to right, they are the numbers 1-3 for certificate
check level (see \fB--ask-cert-level\fR), "L" for a local or
non-exportable signature (see \fB--lsign-key\fR), "R" for a
nonRevocable signature (see the \fB--edit-key\fR command "nrsign"),
"P" for a signature that contains a policy URL (see
\fB--cert-policy-url\fR), "N" for a signature that contains a
notation (see \fB--cert-notation\fR), "X" for an eXpired signature
(see \fB--ask-cert-expire\fR), and the numbers 1-9 or "T" for 10 and
above to indicate trust signature levels (see the \fB--edit-key\fR
command "tsign").
.TP
.B --check-sigs
Same as \fB--list-sigs\fR, but the signatures are verified. Note
that for performance reasons the revocation status of a signing key is
not shown.
This command has the same effect as
using \fB--list-keys\fR with \fB--with-sig-check\fR.
The status of the verification is indicated by a flag directly following
the "sig" tag (and thus before the flags described above for
\fB--list-sigs\fR). A "!" indicates that the signature has been
successfully verified, a "-" denotes a bad signature and a "%" is used
if an error occurred while checking the signature (e.g. a non supported
algorithm).
.TP
.B --locate-keys
Locate the keys given as arguments. This command basically uses the
same algorithm as used when locating keys for encryption or signing and
may thus be used to see what keys \fBgpg2\fR might use. In
particular external methods as defined by \fB--auto-key-locate\fR may
be used to locate a key. Only public keys are listed.
.TP
.B --fingerprint
List all keys (or the specified ones) along with their
fingerprints. This is the same output as \fB--list-keys\fR but with
the additional output of a line with the fingerprint. May also be
combined with \fB--list-sigs\fR or \fB--check-sigs\fR. If this
command is given twice, the fingerprints of all secondary keys are
listed too.
.TP
.B --list-packets
List only the sequence of packets. This is mainly
useful for debugging.
.TP
.B --card-edit
Present a menu to work with a smartcard. The subcommand "help" provides
an overview on available commands. For a detailed description, please
see the Card HOWTO at
https://gnupg.org/documentation/howtos.html#GnuPG-cardHOWTO .
.TP
.B --card-status
Show the content of the smart card.
.TP
.B --change-pin
Present a menu to allow changing the PIN of a smartcard. This
functionality is also available as the subcommand "passwd" with the
\fB--card-edit\fR command.
.TP
.B --delete-key \fBname\fR
Remove key from the public keyring. In batch mode either \fB--yes\fR is
required or the key must be specified by fingerprint. This is a
safeguard against accidental deletion of multiple keys.
.TP
.B --delete-secret-key \fBname\fR
Remove key from the secret keyring. In batch mode the key
must be specified by fingerprint.
.TP
.B --delete-secret-and-public-key \fBname\fR
Same as \fB--delete-key\fR, but if a secret key exists, it will be
removed first. In batch mode the key must be specified by fingerprint.
.TP
.B --export
Either export all keys from all keyrings (default keyrings and those
registered via option \fB--keyring\fR), or if at least one name is given,
those of the given name. The exported keys are written to STDOUT or to the
file given with option \fB--output\fR. Use together with
\fB--armor\fR to mail those keys.
.TP
.B --send-keys \fBkey IDs\fR
Similar to \fB--export\fR but sends the keys to a keyserver.
Fingerprints may be used instead of key IDs. Option \fB--keyserver\fR
must be used to give the name of this keyserver. Don't send your
complete keyring to a keyserver --- select only those keys which are new
or changed by you. If no key IDs are given, \fBgpg\fR does nothing.
.TP
.B --export-secret-keys
.TP
.B --export-secret-subkeys
Same as \fB--export\fR, but exports the secret keys instead. The
exported keys are written to STDOUT or to the file given with option
\fB--output\fR. This command is often used along with the option
\fB--armor\fR to allow easy printing of the key for paper backup;
however the external tool \fBpaperkey\fR does a better job for
creating backups on paper. Note that exporting a secret key can be a
security risk if the exported keys are send over an insecure channel.
The second form of the command has the special property to render the
secret part of the primary key useless; this is a GNU extension to
OpenPGP and other implementations can not be expected to successfully
import such a key. Its intended use is to generated a full key with
an additional signing subkey on a dedicated machine and then using
this command to export the key without the primary key to the main
machine.
See the option \fB--simple-sk-checksum\fR if you want to import an
exported secret key into ancient OpenPGP implementations.
.TP
.B --import
.TP
.B --fast-import
Import/merge keys. This adds the given keys to the
keyring. The fast version is currently just a synonym.
There are a few other options which control how this command works.
Most notable here is the \fB--import-options merge-only\fR option
which does not insert new keys but does only the merging of new
signatures, user-IDs and subkeys.
.TP
.B --recv-keys \fBkey IDs\fR
Import the keys with the given key IDs from a keyserver. Option
\fB--keyserver\fR must be used to give the name of this keyserver.
.TP
.B --refresh-keys
Request updates from a keyserver for keys that already exist on the
local keyring. This is useful for updating a key with the latest
signatures, user IDs, etc. Calling this with no arguments will refresh
the entire keyring. Option \fB--keyserver\fR must be used to give the
name of the keyserver for all keys that do not have preferred keyservers
set (see \fB--keyserver-options honor-keyserver-url\fR).
.TP
.B --search-keys \fBnames\fR
Search the keyserver for the given names. Multiple names given here will
be joined together to create the search string for the keyserver.
Option \fB--keyserver\fR must be used to give the name of this
keyserver. Keyservers that support different search methods allow using
the syntax specified in "How to specify a user ID" below. Note that
different keyserver types support different search methods. Currently
only LDAP supports them all.
.TP
.B --fetch-keys \fBURIs\fR
Retrieve keys located at the specified URIs. Note that different
installations of GnuPG may support different protocols (HTTP, FTP,
LDAP, etc.)
.TP
.B --update-trustdb
Do trust database maintenance. This command iterates over all keys and
builds the Web of Trust. This is an interactive command because it may
have to ask for the "ownertrust" values for keys. The user has to give
an estimation of how far she trusts the owner of the displayed key to
correctly certify (sign) other keys. GnuPG only asks for the ownertrust
value if it has not yet been assigned to a key. Using the
\fB--edit-key\fR menu, the assigned value can be changed at any time.
.TP
.B --check-trustdb
Do trust database maintenance without user interaction. From time to
time the trust database must be updated so that expired keys or
signatures and the resulting changes in the Web of Trust can be
tracked. Normally, GnuPG will calculate when this is required and do it
automatically unless \fB--no-auto-check-trustdb\fR is set. This
command can be used to force a trust database check at any time. The
processing is identical to that of \fB--update-trustdb\fR but it
skips keys with a not yet defined "ownertrust".
For use with cron jobs, this command can be used together with
\fB--batch\fR in which case the trust database check is done only if
a check is needed. To force a run even in batch mode add the option
\fB--yes\fR.
.TP
.B --export-ownertrust
Send the ownertrust values to STDOUT. This is useful for backup purposes
as these values are the only ones which can't be re-created from a
corrupted trustdb. Example:
.RS
.RS 2
.nf
gpg2 --export-ownertrust > otrust.txt
.fi
.RE
.RE
.TP
.B --import-ownertrust
Update the trustdb with the ownertrust values stored in \fBfiles\fR (or
STDIN if not given); existing values will be overwritten. In case of a
severely damaged trustdb and if you have a recent backup of the
ownertrust values (e.g. in the file \(oq\fIotrust.txt\fR\(cq, you may re-create
the trustdb using these commands:
.RS
.RS 2
.nf
cd ~/.gnupg
rm trustdb.gpg
gpg2 --import-ownertrust < otrust.txt
.fi
.RE
.RE
.TP
.B --rebuild-keydb-caches
When updating from version 1.0.6 to 1.0.7 this command should be used
to create signature caches in the keyring. It might be handy in other
situations too.
.TP
.B --print-md \fBalgo\fR
.TP
.B --print-mds
Print message digest of algorithm ALGO for all given files or STDIN.
With the second form (or a deprecated "*" as algo) digests for all
available algorithms are printed.
.TP
.B --gen-random \fB0|1|2\fR \fBcount\fR
Emit \fIcount\fR random bytes of the given quality level 0, 1 or 2. If
\fIcount\fR is not given or zero, an endless sequence of random bytes
will be emitted. If used with \fB--armor\fR the output will be
base64 encoded. PLEASE, don't use this command unless you know what
you are doing; it may remove precious entropy from the system!
.TP
.B --gen-prime \fBmode\fR \fBbits\fR
Use the source, Luke :-). The output format is still subject to change.
.TP
.B --enarmor
.TP
.B --dearmor
Pack or unpack an arbitrary input into/from an OpenPGP ASCII armor.
This is a GnuPG extension to OpenPGP and in general not very useful.
.SS How to manage your keys
\
This section explains the main commands for key management
.TP
.B --gen-key
Generate a new key pair. This command is normally only used
interactively.
There is an experimental feature which allows you to create keys in
batch mode. See the file \(oq\fIdoc/DETAILS\fR\(cq in the source distribution
on how to use this.
.TP
.B --gen-revoke \fBname\fR
Generate a revocation certificate for the complete key. To revoke
a subkey or a signature, use the \fB--edit\fR command.
.TP
.B --desig-revoke \fBname\fR
Generate a designated revocation certificate for a key. This allows a
user (with the permission of the keyholder) to revoke someone else's
key.
.TP
.B --edit-key
Present a menu which enables you to do most of the key management
related tasks. It expects the specification of a key on the command
line.
.RS
.TP
.B uid \fBn\fR
Toggle selection of user ID or photographic user ID with index \fBn\fR.
Use \fB*\fR to select all and \fB0\fR to deselect all.
.TP
.B key \fBn\fR
Toggle selection of subkey with index \fBn\fR.
Use \fB*\fR to select all and \fB0\fR to deselect all.
.TP
.B sign
Make a signature on key of user \fBname\fR If the key is not yet
signed by the default user (or the users given with -u), the program
displays the information of the key again, together with its
fingerprint and asks whether it should be signed. This question is
repeated for all users specified with
-u.
.TP
.B lsign
Same as "sign" but the signature is marked as non-exportable and will
therefore never be used by others. This may be used to make keys
valid only in the local environment.
.TP
.B nrsign
Same as "sign" but the signature is marked as non-revocable and can
therefore never be revoked.
.TP
.B tsign
Make a trust signature. This is a signature that combines the notions
of certification (like a regular signature), and trust (like the
"trust" command). It is generally only useful in distinct communities
or groups.
.RE
.RS
Note that "l" (for local / non-exportable), "nr" (for non-revocable,
and "t" (for trust) may be freely mixed and prefixed to "sign" to
create a signature of any type desired.
.RE
.RS
.TP
.B delsig
Delete a signature. Note that it is not possible to retract a signature,
once it has been send to the public (i.e. to a keyserver). In that case
you better use \fBrevsig\fR.
.TP
.B revsig
Revoke a signature. For every signature which has been generated by
one of the secret keys, GnuPG asks whether a revocation certificate
should be generated.
.TP
.B check
Check the signatures on all selected user IDs.
.TP
.B adduid
Create an additional user ID.
.TP
.B addphoto
Create a photographic user ID. This will prompt for a JPEG file that
will be embedded into the user ID. Note that a very large JPEG will make
for a very large key. Also note that some programs will display your
JPEG unchanged (GnuPG), and some programs will scale it to fit in a
dialog box (PGP).
.TP
.B showphoto
Display the selected photographic user ID.
.TP
.B deluid
Delete a user ID or photographic user ID. Note that it is not
possible to retract a user id, once it has been send to the public
(i.e. to a keyserver). In that case you better use \fBrevuid\fR.
.TP
.B revuid
Revoke a user ID or photographic user ID.
.TP
.B primary
Flag the current user id as the primary one, removes the primary user
id flag from all other user ids and sets the timestamp of all affected
self-signatures one second ahead. Note that setting a photo user ID
as primary makes it primary over other photo user IDs, and setting a
regular user ID as primary makes it primary over other regular user
IDs.
.TP
.B keyserver
Set a preferred keyserver for the specified user ID(s). This allows
other users to know where you prefer they get your key from. See
\fB--keyserver-options honor-keyserver-url\fR for more on how this
works. Setting a value of "none" removes an existing preferred
keyserver.
.TP
.B notation
Set a name=value notation for the specified user ID(s). See
\fB--cert-notation\fR for more on how this works. Setting a value of
"none" removes all notations, setting a notation prefixed with a minus
sign (-) removes that notation, and setting a notation name (without the
=value) prefixed with a minus sign removes all notations with that name.
.TP
.B pref
List preferences from the selected user ID. This shows the actual
preferences, without including any implied preferences.
.TP
.B showpref
More verbose preferences listing for the selected user ID. This shows
the preferences in effect by including the implied preferences of 3DES
(cipher), SHA-1 (digest), and Uncompressed (compression) if they are
not already included in the preference list. In addition, the
preferred keyserver and signature notations (if any) are shown.
.TP
.B setpref \fBstring\fR
Set the list of user ID preferences to \fBstring\fR for all (or just
the selected) user IDs. Calling setpref with no arguments sets the
preference list to the default (either built-in or set via
\fB--default-preference-list\fR), and calling setpref with "none"
as the argument sets an empty preference list. Use \fBgpg2
--version\fR to get a list of available algorithms. Note that while you
can change the preferences on an attribute user ID (aka "photo ID"),
GnuPG does not select keys via attribute user IDs so these preferences
will not be used by GnuPG.
When setting preferences, you should list the algorithms in the order
which you'd like to see them used by someone else when encrypting a
message to your key. If you don't include 3DES, it will be
automatically added at the end. Note that there are many factors that
go into choosing an algorithm (for example, your key may not be the
only recipient), and so the remote OpenPGP application being used to
send to you may or may not follow your exact chosen order for a given
message. It will, however, only choose an algorithm that is present
on the preference list of every recipient key. See also the
INTEROPERABILITY WITH OTHER OPENPGP PROGRAMS section below.
.TP
.B addkey
Add a subkey to this key.
.TP
.B addcardkey
Generate a subkey on a card and add it to this key.
.TP
.B keytocard
Transfer the selected secret subkey (or the primary key if no subkey
has been selected) to a smartcard. The secret key in the keyring will
be replaced by a stub if the key could be stored successfully on the
card and you use the save command later. Only certain key types may be
transferred to the card. A sub menu allows you to select on what card
to store the key. Note that it is not possible to get that key back
from the card - if the card gets broken your secret key will be lost
unless you have a backup somewhere.
.TP
.B bkuptocard \fBfile\fR
Restore the given file to a card. This command may be used to restore a
backup key (as generated during card initialization) to a new card. In
almost all cases this will be the encryption key. You should use this
command only with the corresponding public key and make sure that the
file given as argument is indeed the backup to restore. You should then
select 2 to restore as encryption key. You will first be asked to enter
the passphrase of the backup key and then for the Admin PIN of the card.
.TP
.B delkey
Remove a subkey (secondart key). Note that it is not possible to retract
a subkey, once it has been send to the public (i.e. to a keyserver). In
that case you better use \fBrevkey\fR.
.TP
.B revkey
Revoke a subkey.
.TP
.B expire
Change the key or subkey expiration time. If a subkey is selected, the
expiration time of this subkey will be changed. With no selection, the
key expiration of the primary key is changed.
.TP
.B trust
Change the owner trust value for the key. This updates the trust-db
immediately and no save is required.
.TP
.B disable
.TP
.B enable
Disable or enable an entire key. A disabled key can not normally be
used for encryption.
.TP
.B addrevoker
Add a designated revoker to the key. This takes one optional argument:
"sensitive". If a designated revoker is marked as sensitive, it will
not be exported by default (see export-options).
.TP
.B passwd
Change the passphrase of the secret key.
.TP
.B toggle
Toggle between public and secret key listing.
.TP
.B clean
Compact (by removing all signatures except the selfsig) any user ID
that is no longer usable (e.g. revoked, or expired). Then, remove any
signatures that are not usable by the trust calculations.
Specifically, this removes any signature that does not validate, any
signature that is superseded by a later signature, revoked signatures,
and signatures issued by keys that are not present on the keyring.
.TP
.B minimize
Make the key as small as possible. This removes all signatures from
each user ID except for the most recent self-signature.
.TP
.B cross-certify
Add cross-certification signatures to signing subkeys that may not
currently have them. Cross-certification signatures protect against a
subtle attack against signing subkeys. See
\fB--require-cross-certification\fR. All new keys generated have
this signature by default, so this option is only useful to bring
older keys up to date.
.TP
.B save
Save all changes to the key rings and quit.
.TP
.B quit
Quit the program without updating the
key rings.
.RE
.RS
The listing shows you the key with its secondary keys and all user
ids. The primary user id is indicated by a dot, and selected keys or
user ids are indicated by an asterisk. The trust
value is displayed with the primary key: the first is the assigned owner
trust and the second is the calculated trust value. Letters are used for
the values:
.RE
.RS
.TP
.B -
No ownertrust assigned / not yet calculated.
.TP
.B e
Trust
calculation has failed; probably due to an expired key.
.TP
.B q
Not enough information for calculation.
.TP
.B n
Never trust this key.
.TP
.B m
Marginally trusted.
.TP
.B f
Fully trusted.
.TP
.B u
Ultimately trusted.
.RE
.TP
.B --sign-key \fBname\fR
Signs a public key with your secret key. This is a shortcut version of
the subcommand "sign" from \fB--edit\fR.
.TP
.B --lsign-key \fBname\fR
Signs a public key with your secret key but marks it as
non-exportable. This is a shortcut version of the subcommand "lsign"
from \fB--edit-key\fR.
.TP
.B --passwd \fIuser_id\fR
Change the passphrase of the secret key belonging to the certificate
specified as \fIuser_id\fR. This is a shortcut for the sub-command
\fBpasswd\fR of the edit key menu.
.SH OPTIONS
\fBgpg2\fR features a bunch of options to control the exact
behaviour and to change the default configuration.
Long options can be put in an options file (default
"~/.gnupg/gpg.conf"). Short option names will not work - for example,
"armor" is a valid option for the options file, while "a" is not. Do not
write the 2 dashes, but simply the name of the option and any required
arguments. Lines with a hash ('#') as the first non-white-space
character are ignored. Commands may be put in this file too, but that is
not generally useful as the command will execute automatically with
every execution of gpg.
Please remember that option parsing stops as soon as a non-option is
encountered, you can explicitly stop parsing by using the special option
\fB--\fR.
.SS How to change the configuration
\
These options are used to change the configuration and are usually found
in the option file.
.TP
.B --default-key \fIname\fR
Use \fIname\fR as the default key to sign with. If this option is not
used, the default key is the first key found in the secret keyring.
Note that \fB-u\fR or \fB--local-user\fR overrides this option.
.TP
.B --default-recipient \fIname\fR
Use \fIname\fR as default recipient if option \fB--recipient\fR is
not used and don't ask if this is a valid one. \fIname\fR must be
non-empty.
.TP
.B --default-recipient-self
Use the default key as default recipient if option \fB--recipient\fR is not
used and don't ask if this is a valid one. The default key is the first
one from the secret keyring or the one set with \fB--default-key\fR.
.TP
.B --no-default-recipient
Reset \fB--default-recipient\fR and \fB--default-recipient-self\fR.
.TP
.B -v, --verbose
Give more information during processing. If used
twice, the input data is listed in detail.
.TP
.B --no-verbose
Reset verbose level to 0.
.TP
.B -q, --quiet
Try to be as quiet as possible.
.TP
.B --batch
.TP
.B --no-batch
Use batch mode. Never ask, do not allow interactive commands.
\fB--no-batch\fR disables this option. Note that even with a
filename given on the command line, gpg might still need to read from
STDIN (in particular if gpg figures that the input is a
detached signature and no data file has been specified). Thus if you
do not want to feed data via STDIN, you should connect STDIN to
\(oq\fI/dev/null\fR\(cq.
.TP
.B --no-tty
Make sure that the TTY (terminal) is never used for any output.
This option is needed in some cases because GnuPG sometimes prints
warnings to the TTY even if \fB--batch\fR is used.
.TP
.B --yes
Assume "yes" on most questions.
.TP
.B --no
Assume "no" on most questions.
.TP
.B --list-options \fBparameters\fR
This is a space or comma delimited string that gives options used when
listing keys and signatures (that is, \fB--list-keys\fR,
\fB--list-sigs\fR, \fB--list-public-keys\fR,
\fB--list-secret-keys\fR, and the \fB--edit-key\fR functions).
Options can be prepended with a \fBno-\fR (after the two dashes) to
give the opposite meaning. The options are:
.RS
.TP
.B show-photos
Causes \fB--list-keys\fR, \fB--list-sigs\fR,
\fB--list-public-keys\fR, and \fB--list-secret-keys\fR to
display any photo IDs attached to the key. Defaults to no. See also
\fB--photo-viewer\fR. Does not work with \fB--with-colons\fR:
see \fB--attribute-fd\fR for the appropriate way to get photo data
for scripts and other frontends.
.TP
.B show-policy-urls
Show policy URLs in the \fB--list-sigs\fR or \fB--check-sigs\fR
listings. Defaults to no.
.TP
.B show-notations
.TP
.B show-std-notations
.TP
.B show-user-notations
Show all, IETF standard, or user-defined signature notations in the
\fB--list-sigs\fR or \fB--check-sigs\fR listings. Defaults to no.
.TP
.B show-keyserver-urls
Show any preferred keyserver URL in the \fB--list-sigs\fR or
\fB--check-sigs\fR listings. Defaults to no.
.TP
.B show-uid-validity
Display the calculated validity of user IDs during key listings.
Defaults to no.
.TP
.B show-unusable-uids
Show revoked and expired user IDs in key listings. Defaults to no.
.TP
.B show-unusable-subkeys
Show revoked and expired subkeys in key listings. Defaults to no.
.TP
.B show-keyring
Display the keyring name at the head of key listings to show which
keyring a given key resides on. Defaults to no.
.TP
.B show-sig-expire
Show signature expiration dates (if any) during \fB--list-sigs\fR or
\fB--check-sigs\fR listings. Defaults to no.
.TP
.B show-sig-subpackets
Include signature subpackets in the key listing. This option can take an
optional argument list of the subpackets to list. If no argument is
passed, list all subpackets. Defaults to no. This option is only
meaningful when using \fB--with-colons\fR along with
\fB--list-sigs\fR or \fB--check-sigs\fR.
.RE
.TP
.B --verify-options \fBparameters\fR
This is a space or comma delimited string that gives options used when
verifying signatures. Options can be prepended with a `no-' to give
the opposite meaning. The options are:
.RS
.TP
.B show-photos
Display any photo IDs present on the key that issued the signature.
Defaults to no. See also \fB--photo-viewer\fR.
.TP
.B show-policy-urls
Show policy URLs in the signature being verified. Defaults to no.
.TP
.B show-notations
.TP
.B show-std-notations
.TP
.B show-user-notations
Show all, IETF standard, or user-defined signature notations in the
signature being verified. Defaults to IETF standard.
.TP
.B show-keyserver-urls
Show any preferred keyserver URL in the signature being verified.
Defaults to no.
.TP
.B show-uid-validity
Display the calculated validity of the user IDs on the key that issued
the signature. Defaults to no.
.TP
.B show-unusable-uids
Show revoked and expired user IDs during signature verification.
Defaults to no.
.TP
.B show-primary-uid-only
Show only the primary user ID during signature verification. That is
all the AKA lines as well as photo Ids are not shown with the signature
verification status.
.TP
.B pka-lookups
Enable PKA lookups to verify sender addresses. Note that PKA is based
on DNS, and so enabling this option may disclose information on when
and what signatures are verified or to whom data is encrypted. This
is similar to the "web bug" described for the auto-key-retrieve
feature.
.TP
.B pka-trust-increase
Raise the trust in a signature to full if the signature passes PKA
validation. This option is only meaningful if pka-lookups is set.
.RE
.TP
.B --enable-large-rsa
.TP
.B --disable-large-rsa
With --gen-key and --batch, enable the creation of larger RSA secret
keys than is generally recommended (up to 8192 bits). These large
keys are more expensive to use, and their signatures and
certifications are also larger.
.TP
.B --enable-dsa2
.TP
.B --disable-dsa2
Enable hash truncation for all DSA keys even for old DSA Keys up to
1024 bit. This is also the default with \fB--openpgp\fR. Note
that older versions of GnuPG also required this flag to allow the
generation of DSA larger than 1024 bit.
.TP
.B --photo-viewer \fBstring\fR
This is the command line that should be run to view a photo ID. "%i"
will be expanded to a filename containing the photo. "%I" does the
same, except the file will not be deleted once the viewer exits.
Other flags are "%k" for the key ID, "%K" for the long key ID, "%f"
for the key fingerprint, "%t" for the extension of the image type
(e.g. "jpg"), "%T" for the MIME type of the image (e.g. "image/jpeg"),
"%v" for the single-character calculated validity of the image being
viewed (e.g. "f"), "%V" for the calculated validity as a string (e.g.
"full"), "%U" for a base32 encoded hash of the user ID,
and "%%" for an actual percent sign. If neither %i or %I are present,
then the photo will be supplied to the viewer on standard input.
The default viewer is "xloadimage -fork -quiet -title 'KeyID 0x%k'
STDIN". Note that if your image viewer program is not secure, then
executing it from GnuPG does not make it secure.
.TP
.B --exec-path \fBstring\fR
Sets a list of directories to search for photo viewers and keyserver
helpers. If not provided, keyserver helpers use the compiled-in
default directory, and photo viewers use the $PATH environment
variable.
Note, that on W32 system this value is ignored when searching for
keyserver helpers.
.TP
.B --keyring \fBfile\fR
Add \fBfile\fR to the current list of keyrings. If \fBfile\fR begins
with a tilde and a slash, these are replaced by the $HOME directory. If
the filename does not contain a slash, it is assumed to be in the GnuPG
home directory ("~/.gnupg" if \fB--homedir\fR or $GNUPGHOME is not
used).
Note that this adds a keyring to the current list. If the intent is to
use the specified keyring alone, use \fB--keyring\fR along with
\fB--no-default-keyring\fR.
.TP
.B --secret-keyring \fBfile\fR
Same as \fB--keyring\fR but for the secret keyrings.
.TP
.B --primary-keyring \fBfile\fR
Designate \fBfile\fR as the primary public keyring. This means that
newly imported keys (via \fB--import\fR or keyserver
\fB--recv-from\fR) will go to this keyring.
.TP
.B --trustdb-name \fBfile\fR
Use \fBfile\fR instead of the default trustdb. If \fBfile\fR begins
with a tilde and a slash, these are replaced by the $HOME directory. If
the filename does not contain a slash, it is assumed to be in the GnuPG
home directory (\(oq\fI~/.gnupg\fR\(cq if \fB--homedir\fR or $GNUPGHOME is
not used).
.TP
.B --homedir \fIdir\fR
Set the name of the home directory to \fIdir\fR. If this option is not
used, the home directory defaults to \(oq\fI~/.gnupg\fR\(cq. It is only
recognized when given on the command line. It also overrides any home
directory stated through the environment variable \(oq\fIGNUPGHOME\fR\(cq or
(on W32 systems) by means of the Registry entry
\fIHKCU\\Software\\GNU\\GnuPG:HomeDir\fR.
.TP
.B --display-charset \fBname\fR
Set the name of the native character set. This is used to convert
some informational strings like user IDs to the proper UTF-8 encoding.
Note that this has nothing to do with the character set of data to be
encrypted or signed; GnuPG does not recode user-supplied data. If
this option is not used, the default character set is determined from
the current locale. A verbosity level of 3 shows the chosen set.
Valid values for \fBname\fR are:
.RS
.TP
.B iso-8859-1
This is the Latin 1 set.
.TP
.B iso-8859-2
The Latin 2 set.
.TP
.B iso-8859-15
This is currently an alias for
the Latin 1 set.
.TP
.B koi8-r
The usual Russian set (rfc1489).
.TP
.B utf-8
Bypass all translations and assume
that the OS uses native UTF-8 encoding.
.RE
.TP
.B --utf8-strings
.TP
.B --no-utf8-strings
Assume that command line arguments are given as UTF8 strings. The
default (\fB--no-utf8-strings\fR) is to assume that arguments are
encoded in the character set as specified by
\fB--display-charset\fR. These options affect all following
arguments. Both options may be used multiple times.
.TP
.B --options \fBfile\fR
Read options from \fBfile\fR and do not try to read them from the
default options file in the homedir (see \fB--homedir\fR). This
option is ignored if used in an options file.
.TP
.B --no-options
Shortcut for \fB--options /dev/null\fR. This option is detected
before an attempt to open an option file. Using this option will also
prevent the creation of a \(oq\fI~/.gnupg\fR\(cq homedir.
.TP
.B -z \fBn\fR
.TP
.B --compress-level \fBn\fR
.TP
.B --bzip2-compress-level \fBn\fR
Set compression level to \fBn\fR for the ZIP and ZLIB compression
algorithms. The default is to use the default compression level of zlib
(normally 6). \fB--bzip2-compress-level\fR sets the compression level
for the BZIP2 compression algorithm (defaulting to 6 as well). This is a
different option from \fB--compress-level\fR since BZIP2 uses a
significant amount of memory for each additional compression level.
\fB-z\fR sets both. A value of 0 for \fBn\fR disables compression.
.TP
.B --bzip2-decompress-lowmem
Use a different decompression method for BZIP2 compressed files. This
alternate method uses a bit more than half the memory, but also runs
at half the speed. This is useful under extreme low memory
circumstances when the file was originally compressed at a high
\fB--bzip2-compress-level\fR.
.TP
.B --mangle-dos-filenames
.TP
.B --no-mangle-dos-filenames
Older version of Windows cannot handle filenames with more than one
dot. \fB--mangle-dos-filenames\fR causes GnuPG to replace (rather
than add to) the extension of an output filename to avoid this
problem. This option is off by default and has no effect on non-Windows
platforms.
.TP
.B --ask-cert-level
.TP
.B --no-ask-cert-level
When making a key signature, prompt for a certification level. If this
option is not specified, the certification level used is set via
\fB--default-cert-level\fR. See \fB--default-cert-level\fR for
information on the specific levels and how they are
used. \fB--no-ask-cert-level\fR disables this option. This option
defaults to no.
.TP
.B --default-cert-level \fBn\fR
The default to use for the check level when signing a key.
0 means you make no particular claim as to how carefully you verified
the key.
1 means you believe the key is owned by the person who claims to own
it but you could not, or did not verify the key at all. This is
useful for a "persona" verification, where you sign the key of a
pseudonymous user.
2 means you did casual verification of the key. For example, this
could mean that you verified the key fingerprint and checked the
user ID on the key against a photo ID.
3 means you did extensive verification of the key. For example, this
could mean that you verified the key fingerprint with the owner of the
key in person, and that you checked, by means of a hard to forge
document with a photo ID (such as a passport) that the name of the key
owner matches the name in the user ID on the key, and finally that you
verified (by exchange of email) that the email address on the key
belongs to the key owner.
Note that the examples given above for levels 2 and 3 are just that:
examples. In the end, it is up to you to decide just what "casual"
and "extensive" mean to you.
This option defaults to 0 (no particular claim).
.TP
.B --min-cert-level
When building the trust database, treat any signatures with a
certification level below this as invalid. Defaults to 2, which
disregards level 1 signatures. Note that level 0 "no particular
claim" signatures are always accepted.
.TP
.B --trusted-key \fBlong key ID\fR
Assume that the specified key (which must be given
as a full 8 byte key ID) is as trustworthy as one of
your own secret keys. This option is useful if you
don't want to keep your secret keys (or one of them)
online but still want to be able to check the validity of a given
recipient's or signator's key.
.TP
.B --trust-model \fBpgp|classic|direct|always|auto\fR
Set what trust model GnuPG should follow. The models are:
.RS
.TP
.B pgp
This is the Web of Trust combined with trust signatures as used in PGP
5.x and later. This is the default trust model when creating a new
trust database.
.TP
.B classic
This is the standard Web of Trust as used in PGP 2.x and earlier.
.TP
.B direct
Key validity is set directly by the user and not calculated via the
Web of Trust.
.TP
.B always
Skip key validation and assume that used keys are always fully
trusted. You generally won't use this unless you are using some
external validation scheme. This option also suppresses the
"[uncertain]" tag printed with signature checks when there is no
evidence that the user ID is bound to the key. Note that this
trust model still does not allow the use of expired, revoked, or
disabled keys.
.TP
.B auto
Select the trust model depending on whatever the internal trust
database says. This is the default model if such a database already
exists.
.RE
.TP
.B --auto-key-locate \fBparameters\fR
.TP
.B --no-auto-key-locate
GnuPG can automatically locate and retrieve keys as needed using this
option. This happens when encrypting to an email address (in the
"user@example.com" form), and there are no user@example.com keys on
the local keyring. This option takes any number of the following
mechanisms, in the order they are to be tried:
.RS
.TP
.B cert
Locate a key using DNS CERT, as specified in rfc4398.
.TP
.B pka
Locate a key using DNS PKA.
.TP
.B ldap
Using DNS Service Discovery, check the domain in question for any LDAP
keyservers to use. If this fails, attempt to locate the key using the
PGP Universal method of checking \(aqldap://keys.(thedomain)\(aq.
.TP
.B keyserver
Locate a key using whatever keyserver is defined using the
\fB--keyserver\fR option.
.TP
.B keyserver-URL
In addition, a keyserver URL as used in the \fB--keyserver\fR option
may be used here to query that particular keyserver.
.TP
.B local
Locate the key using the local keyrings. This mechanism allows to
select the order a local key lookup is done. Thus using
\(aq--auto-key-locate local\(aq is identical to
\fB--no-auto-key-locate\fR.
.TP
.B nodefault
This flag disables the standard local key lookup, done before any of the
mechanisms defined by the \fB--auto-key-locate\fR are tried. The
position of this mechanism in the list does not matter. It is not
required if \fBlocal\fR is also used.
.TP
.B clear
Clear all defined mechanisms. This is useful to override
mechanisms given in a config file.
.RE
.TP
.B --keyid-format \fBshort|0xshort|long|0xlong\fR
Select how to display key IDs. "short" is the traditional 8-character
key ID. "long" is the more accurate (but less convenient)
16-character key ID. Add an "0x" to either to include an "0x" at the
beginning of the key ID, as in 0x99242560. Note that this option is
ignored if the option --with-colons is used.
.TP
.B --keyserver \fBname\fR
Use \fBname\fR as your keyserver. This is the server that
\fB--recv-keys\fR, \fB--send-keys\fR, and \fB--search-keys\fR
will communicate with to receive keys from, send keys to, and search for
keys on. The format of the \fBname\fR is a URI:
`scheme:[//]keyservername[:port]' The scheme is the type of keyserver:
"hkp" for the HTTP (or compatible) keyservers, "ldap" for the LDAP
keyservers, or "mailto" for the Graff email keyserver. Note that your
particular installation of GnuPG may have other keyserver types
available as well. Keyserver schemes are case-insensitive. After the
keyserver name, optional keyserver configuration options may be
provided. These are the same as the global \fB--keyserver-options\fR
from below, but apply only to this particular keyserver.
Most keyservers synchronize with each other, so there is generally no
need to send keys to more than one server. The keyserver
\fBhkp://keys.gnupg.net\fR uses round robin DNS to give a different
keyserver each time you use it.
.TP
.B --keyserver-options \fBname=value1 \fR
This is a space or comma delimited string that gives options for the
keyserver. Options can be prefixed with a `no-' to give the opposite
meaning. Valid import-options or export-options may be used here as
well to apply to importing (\fB--recv-key\fR) or exporting
(\fB--send-key\fR) a key from a keyserver. While not all options
are available for all keyserver types, some common options are:
.RS
.TP
.B include-revoked
When searching for a key with \fB--search-keys\fR, include keys that
are marked on the keyserver as revoked. Note that not all keyservers
differentiate between revoked and unrevoked keys, and for such
keyservers this option is meaningless. Note also that most keyservers do
not have cryptographic verification of key revocations, and so turning
this option off may result in skipping keys that are incorrectly marked
as revoked.
.TP
.B include-disabled
When searching for a key with \fB--search-keys\fR, include keys that
are marked on the keyserver as disabled. Note that this option is not
used with HKP keyservers.
.TP
.B auto-key-retrieve
This option enables the automatic retrieving of keys from a keyserver
when verifying signatures made by keys that are not on the local
keyring.
Note that this option makes a "web bug" like behavior possible.
Keyserver operators can see which keys you request, so by sending you
a message signed by a brand new key (which you naturally will not have
on your local keyring), the operator can tell both your IP address and
the time when you verified the signature.
.TP
.B honor-keyserver-url
When using \fB--refresh-keys\fR, if the key in question has a preferred
keyserver URL, then use that preferred keyserver to refresh the key
from. In addition, if auto-key-retrieve is set, and the signature
being verified has a preferred keyserver URL, then use that preferred
keyserver to fetch the key from. Defaults to yes.
.TP
.B honor-pka-record
If auto-key-retrieve is set, and the signature being verified has a
PKA record, then use the PKA information to fetch the key. Defaults
to yes.
.TP
.B include-subkeys
When receiving a key, include subkeys as potential targets. Note that
this option is not used with HKP keyservers, as they do not support
retrieving keys by subkey id.
.TP
.B use-temp-files
On most Unix-like platforms, GnuPG communicates with the keyserver
helper program via pipes, which is the most efficient method. This
option forces GnuPG to use temporary files to communicate. On some
platforms (such as Win32 and RISC OS), this option is always enabled.
.TP
.B keep-temp-files
If using `use-temp-files', do not delete the temp files after using
them. This option is useful to learn the keyserver communication
protocol by reading the temporary files.
.TP
.B verbose
Tell the keyserver helper program to be more verbose. This option can
be repeated multiple times to increase the verbosity level.
.TP
.B timeout
Tell the keyserver helper program how long (in seconds) to try and
perform a keyserver action before giving up. Note that performing
multiple actions at the same time uses this timeout value per action.
For example, when retrieving multiple keys via \fB--recv-keys\fR, the
timeout applies separately to each key retrieval, and not to the
\fB--recv-keys\fR command as a whole. Defaults to 30 seconds.
.TP
.B http-proxy=\fBvalue\fR
Set the proxy to use for HTTP and HKP keyservers. This overrides the
"http_proxy" environment variable, if any.
.TP
.B max-cert-size
When retrieving a key via DNS CERT, only accept keys up to this size.
Defaults to 16384 bytes.
.TP
.B debug
Turn on debug output in the keyserver helper program. Note that the
details of debug output depends on which keyserver helper program is
being used, and in turn, on any libraries that the keyserver helper
program uses internally (libcurl, openldap, etc).
.TP
.B check-cert
Enable certificate checking if the keyserver presents one (for hkps or
ldaps). Defaults to on.
.TP
.B ca-cert-file
Provide a certificate store to override the system default. Only
necessary if check-cert is enabled, and the keyserver is using a
certificate that is not present in a system default certificate list.
Note that depending on the SSL library that the keyserver helper is
built with, this may actually be a directory or a file.
.RE
.TP
.B --completes-needed \fBn\fR
Number of completely trusted users to introduce a new
key signer (defaults to 1).
.TP
.B --marginals-needed \fBn\fR
Number of marginally trusted users to introduce a new
key signer (defaults to 3)
.TP
.B --max-cert-depth \fBn\fR
Maximum depth of a certification chain (default is 5).
.TP
.B --simple-sk-checksum
Secret keys are integrity protected by using a SHA-1 checksum. This
method is part of the upcoming enhanced OpenPGP specification but
GnuPG already uses it as a countermeasure against certain attacks.
Old applications don't understand this new format, so this option may
be used to switch back to the old behaviour. Using this option bears
a security risk. Note that using this option only takes effect when
the secret key is encrypted - the simplest way to make this happen is
to change the passphrase on the key (even changing it to the same
value is acceptable).
.TP
.B --no-sig-cache
Do not cache the verification status of key signatures.
Caching gives a much better performance in key listings. However, if
you suspect that your public keyring is not save against write
modifications, you can use this option to disable the caching. It
probably does not make sense to disable it because all kind of damage
can be done if someone else has write access to your public keyring.
.TP
.B --no-sig-create-check
GnuPG normally verifies each signature right after creation to protect
against bugs and hardware malfunctions which could leak out bits from
the secret key. This extra verification needs some time (about 115%
for DSA keys), and so this option can be used to disable it.
However, due to the fact that the signature creation needs manual
interaction, this performance penalty does not matter in most settings.
.TP
.B --auto-check-trustdb
.TP
.B --no-auto-check-trustdb
If GnuPG feels that its information about the Web of Trust has to be
updated, it automatically runs the \fB--check-trustdb\fR command
internally. This may be a time consuming
process. \fB--no-auto-check-trustdb\fR disables this option.
.TP
.B --use-agent
.TP
.B --no-use-agent
This is dummy option. \fBgpg2\fR always requires the agent.
.TP
.B --gpg-agent-info
This is dummy option. It has no effect when used with \fBgpg2\fR.
.TP
.B --agent-program \fIfile\fR
Specify an agent program to be used for secret key operations. The
default value is the \(oq\fI/usr/bin/gpg-agent\fR\(cq. This is only used
as a fallback when the environment variable \fBGPG_AGENT_INFO\fR is not
set or a running agent cannot be connected.
.TP
.B --lock-once
Lock the databases the first time a lock is requested
and do not release the lock until the process
terminates.
.TP
.B --lock-multiple
Release the locks every time a lock is no longer
needed. Use this to override a previous \fB--lock-once\fR
from a config file.
.TP
.B --lock-never
Disable locking entirely. This option should be used only in very
special environments, where it can be assured that only one process
is accessing those files. A bootable floppy with a stand-alone
encryption system will probably use this. Improper usage of this
option may lead to data and key corruption.
.TP
.B --exit-on-status-write-error
This option will cause write errors on the status FD to immediately
terminate the process. That should in fact be the default but it never
worked this way and thus we need an option to enable this, so that the
change won't break applications which close their end of a status fd
connected pipe too early. Using this option along with
\fB--enable-progress-filter\fR may be used to cleanly cancel long
running gpg operations.
.TP
.B --limit-card-insert-tries \fBn\fR
With \fBn\fR greater than 0 the number of prompts asking to insert a
smartcard gets limited to N-1. Thus with a value of 1 gpg won't at
all ask to insert a card if none has been inserted at startup. This
option is useful in the configuration file in case an application does
not know about the smartcard support and waits ad infinitum for an
inserted card.
.TP
.B --no-random-seed-file
GnuPG uses a file to store its internal random pool over invocations.
This makes random generation faster; however sometimes write operations
are not desired. This option can be used to achieve that with the cost of
slower random generation.
.TP
.B --no-greeting
Suppress the initial copyright message.
.TP
.B --no-secmem-warning
Suppress the warning about "using insecure memory".
.TP
.B --no-permission-warning
Suppress the warning about unsafe file and home directory (\fB--homedir\fR)
permissions. Note that the permission checks that GnuPG performs are
not intended to be authoritative, but rather they simply warn about
certain common permission problems. Do not assume that the lack of a
warning means that your system is secure.
Note that the warning for unsafe \fB--homedir\fR permissions cannot be
suppressed in the gpg.conf file, as this would allow an attacker to
place an unsafe gpg.conf file in place, and use this file to suppress
warnings about itself. The \fB--homedir\fR permissions warning may only be
suppressed on the command line.
.TP
.B --no-mdc-warning
Suppress the warning about missing MDC integrity protection.
.TP
.B --require-secmem
.TP
.B --no-require-secmem
Refuse to run if GnuPG cannot get secure memory. Defaults to no
(i.e. run, but give a warning).
.TP
.B --require-cross-certification
.TP
.B --no-require-cross-certification
When verifying a signature made from a subkey, ensure that the cross
certification "back signature" on the subkey is present and valid. This
protects against a subtle attack against subkeys that can sign.
Defaults to \fB--require-cross-certification\fR for
\fBgpg2\fR.
.TP
.B --expert
.TP
.B --no-expert
Allow the user to do certain nonsensical or "silly" things like
signing an expired or revoked key, or certain potentially incompatible
things like generating unusual key types. This also disables certain
warning messages about potentially incompatible actions. As the name
implies, this option is for experts only. If you don't fully
understand the implications of what it allows you to do, leave this
off. \fB--no-expert\fR disables this option.
.SS Key related options
\
.TP
.B --recipient \fIname\fR
.TP
.B -r
Encrypt for user id \fIname\fR. If this option or
\fB--hidden-recipient\fR is not specified, GnuPG asks for the user-id
unless \fB--default-recipient\fR is given.
.TP
.B --hidden-recipient \fIname\fR
.TP
.B -R
Encrypt for user ID \fIname\fR, but hide the key ID of this user's
key. This option helps to hide the receiver of the message and is a
limited countermeasure against traffic analysis. If this option or
\fB--recipient\fR is not specified, GnuPG asks for the user ID unless
\fB--default-recipient\fR is given.
.TP
.B --encrypt-to \fBname\fR
Same as \fB--recipient\fR but this one is intended for use in the
options file and may be used with your own user-id as an
"encrypt-to-self". These keys are only used when there are other
recipients given either by use of \fB--recipient\fR or by the asked
user id. No trust checking is performed for these user ids and even
disabled keys can be used.
.TP
.B --hidden-encrypt-to \fBname\fR
Same as \fB--hidden-recipient\fR but this one is intended for use in the
options file and may be used with your own user-id as a hidden
"encrypt-to-self". These keys are only used when there are other
recipients given either by use of \fB--recipient\fR or by the asked user id.
No trust checking is performed for these user ids and even disabled
keys can be used.
.TP
.B --no-encrypt-to
Disable the use of all \fB--encrypt-to\fR and
\fB--hidden-encrypt-to\fR keys.
.TP
.B --group \fBname=value1 \fR
Sets up a named group, which is similar to aliases in email programs.
Any time the group name is a recipient (\fB-r\fR or
\fB--recipient\fR), it will be expanded to the values
specified. Multiple groups with the same name are automatically merged
into a single group.
The values are \fBkey IDs\fR or fingerprints, but any key description
is accepted. Note that a value with spaces in it will be treated as
two different values. Note also there is only one level of expansion
--- you cannot make an group that points to another group. When used
from the command line, it may be necessary to quote the argument to
this option to prevent the shell from treating it as multiple
arguments.
.TP
.B --ungroup \fBname\fR
Remove a given entry from the \fB--group\fR list.
.TP
.B --no-groups
Remove all entries from the \fB--group\fR list.
.TP
.B --local-user \fIname\fR
.TP
.B -u
Use \fIname\fR as the key to sign with. Note that this option overrides
\fB--default-key\fR.
.TP
.B --try-all-secrets
Don't look at the key ID as stored in the message but try all secret
keys in turn to find the right decryption key. This option forces the
behaviour as used by anonymous recipients (created by using
\fB--throw-keyids\fR or \fB--hidden-recipient\fR) and might come
handy in case where an encrypted message contains a bogus key ID.
.TP
.B --skip-hidden-recipients
.TP
.B --no-skip-hidden-recipients
During decryption skip all anonymous recipients. This option helps in
the case that people use the hidden recipients feature to hide there
own encrypt-to key from others. If oneself has many secret keys this
may lead to a major annoyance because all keys are tried in turn to
decrypt soemthing which was not really intended for it. The drawback
of this option is that it is currently not possible to decrypt a
message which includes real anonymous recipients.
.SS Input and Output
\
.TP
.B --armor
.TP
.B -a
Create ASCII armored output. The default is to create the binary
OpenPGP format.
.TP
.B --no-armor
Assume the input data is not in ASCII armored format.
.TP
.B --output \fIfile\fR
.TP
.B -o \fIfile\fR
Write output to \fIfile\fR.
.TP
.B --max-output \fBn\fR
This option sets a limit on the number of bytes that will be generated
when processing a file. Since OpenPGP supports various levels of
compression, it is possible that the plaintext of a given message may be
significantly larger than the original OpenPGP message. While GnuPG
works properly with such messages, there is often a desire to set a
maximum file size that will be generated before processing is forced to
stop by the OS limits. Defaults to 0, which means "no limit".
.TP
.B --import-options \fBparameters\fR
This is a space or comma delimited string that gives options for
importing keys. Options can be prepended with a `no-' to give the
opposite meaning. The options are:
.RS
.TP
.B import-local-sigs
Allow importing key signatures marked as "local". This is not
generally useful unless a shared keyring scheme is being used.
Defaults to no.
.TP
.B import-keep-ownertrust
Normally possible still existing ownertrust values of a key are
cleared if a key is imported. This is in general desirable so that
a formerly deleted key does not automatically gain an ownertrust
values merely due to import. On the other hand it is sometimes
necessary to re-import a trusted set of keys again but keeping
already assigned ownertrust values. This can be achived by using
this option.
.TP
.B repair-pks-subkey-bug
During import, attempt to repair the damage caused by the PKS keyserver
bug (pre version 0.9.6) that mangles keys with multiple subkeys. Note
that this cannot completely repair the damaged key as some crucial data
is removed by the keyserver, but it does at least give you back one
subkey. Defaults to no for regular \fB--import\fR and to yes for
keyserver \fB--recv-keys\fR.
.TP
.B merge-only
During import, allow key updates to existing keys, but do not allow
any new keys to be imported. Defaults to no.
.TP
.B import-clean
After import, compact (remove all signatures except the
self-signature) any user IDs from the new key that are not usable.
Then, remove any signatures from the new key that are not usable.
This includes signatures that were issued by keys that are not present
on the keyring. This option is the same as running the \fB--edit-key\fR
command "clean" after import. Defaults to no.
.TP
.B import-minimal
Import the smallest key possible. This removes all signatures except
the most recent self-signature on each user ID. This option is the
same as running the \fB--edit-key\fR command "minimize" after import.
Defaults to no.
.RE
.TP
.B --export-options \fBparameters\fR
This is a space or comma delimited string that gives options for
exporting keys. Options can be prepended with a `no-' to give the
opposite meaning. The options are:
.RS
.TP
.B export-local-sigs
Allow exporting key signatures marked as "local". This is not
generally useful unless a shared keyring scheme is being used.
Defaults to no.
.TP
.B export-attributes
Include attribute user IDs (photo IDs) while exporting. This is
useful to export keys if they are going to be used by an OpenPGP
program that does not accept attribute user IDs. Defaults to yes.
.TP
.B export-sensitive-revkeys
Include designated revoker information that was marked as
"sensitive". Defaults to no.
.TP
.B export-reset-subkey-passwd
When using the \fB--export-secret-subkeys\fR command, this option resets
the passphrases for all exported subkeys to empty. This is useful
when the exported subkey is to be used on an unattended machine where
a passphrase doesn't necessarily make sense. Defaults to no.
.TP
.B export-clean
Compact (remove all signatures from) user IDs on the key being
exported if the user IDs are not usable. Also, do not export any
signatures that are not usable. This includes signatures that were
issued by keys that are not present on the keyring. This option is
the same as running the \fB--edit-key\fR command "clean" before export
except that the local copy of the key is not modified. Defaults to
no.
.TP
.B export-minimal
Export the smallest key possible. This removes all signatures except the
most recent self-signature on each user ID. This option is the same as
running the \fB--edit-key\fR command "minimize" before export except
that the local copy of the key is not modified. Defaults to no.
.RE
.TP
.B --with-colons
Print key listings delimited by colons. Note that the output will be
encoded in UTF-8 regardless of any \fB--display-charset\fR setting. This
format is useful when GnuPG is called from scripts and other programs
as it is easily machine parsed. The details of this format are
documented in the file \(oq\fIdoc/DETAILS\fR\(cq, which is included in the GnuPG
source distribution.
.TP
.B --fixed-list-mode
Do not merge primary user ID and primary key in \fB--with-colon\fR
listing mode and print all timestamps as seconds since 1970-01-01.
Since GnuPG 2.0.10, this mode is always used and thus this option is
obsolete; it does not harm to use it though.
.TP
.B --with-fingerprint
Same as the command \fB--fingerprint\fR but changes only the format
of the output and may be used together with another command.
.SS OpenPGP protocol specific options.
\
.TP
.B -t, --textmode
.TP
.B --no-textmode
Treat input files as text and store them in the OpenPGP canonical text
form with standard "CRLF" line endings. This also sets the necessary
flags to inform the recipient that the encrypted or signed data is text
and may need its line endings converted back to whatever the local
system uses. This option is useful when communicating between two
platforms that have different line ending conventions (UNIX-like to Mac,
Mac to Windows, etc). \fB--no-textmode\fR disables this option, and
is the default.
.TP
.B --force-v3-sigs
.TP
.B --no-force-v3-sigs
OpenPGP states that an implementation should generate v4 signatures
but PGP versions 5 through 7 only recognize v4 signatures on key
material. This option forces v3 signatures for signatures on data.
Note that this option implies \fB--no-ask-sig-expire\fR, and unsets
\fB--sig-policy-url\fR, \fB--sig-notation\fR, and
\fB--sig-keyserver-url\fR, as these features cannot be used with v3
signatures. \fB--no-force-v3-sigs\fR disables this option.
Defaults to no.
.TP
.B --force-v4-certs
.TP
.B --no-force-v4-certs
Always use v4 key signatures even on v3 keys. This option also
changes the default hash algorithm for v3 RSA keys from MD5 to SHA-1.
\fB--no-force-v4-certs\fR disables this option.
.TP
.B --force-mdc
Force the use of encryption with a modification detection code. This
is always used with the newer ciphers (those with a blocksize greater
than 64 bits), or if all of the recipient keys indicate MDC support in
their feature flags.
.TP
.B --disable-mdc
Disable the use of the modification detection code. Note that by
using this option, the encrypted message becomes vulnerable to a
message modification attack.
.TP
.B --personal-cipher-preferences \fBstring\fR
Set the list of personal cipher preferences to \fBstring\fR. Use
\fBgpg2 --version\fR to get a list of available algorithms,
and use \fBnone\fR to set no preference at all. This allows the user
to safely override the algorithm chosen by the recipient key
preferences, as GPG will only select an algorithm that is usable by
all recipients. The most highly ranked cipher in this list is also
used for the \fB--symmetric\fR encryption command.
.TP
.B --personal-digest-preferences \fBstring\fR
Set the list of personal digest preferences to \fBstring\fR. Use
\fBgpg2 --version\fR to get a list of available algorithms,
and use \fBnone\fR to set no preference at all. This allows the user
to safely override the algorithm chosen by the recipient key
preferences, as GPG will only select an algorithm that is usable by
all recipients. The most highly ranked digest algorithm in this list
is also used when signing without encryption
(e.g. \fB--clearsign\fR or \fB--sign\fR).
.TP
.B --personal-compress-preferences \fBstring\fR
Set the list of personal compression preferences to \fBstring\fR.
Use \fBgpg2 --version\fR to get a list of available
algorithms, and use \fBnone\fR to set no preference at all. This
allows the user to safely override the algorithm chosen by the
recipient key preferences, as GPG will only select an algorithm that
is usable by all recipients. The most highly ranked compression
algorithm in this list is also used when there are no recipient keys
to consider (e.g. \fB--symmetric\fR).
.TP
.B --s2k-cipher-algo \fBname\fR
Use \fBname\fR as the cipher algorithm used to protect secret keys.
The default cipher is CAST5. This cipher is also used for
conventional encryption if \fB--personal-cipher-preferences\fR and
\fB--cipher-algo\fR is not given.
.TP
.B --s2k-digest-algo \fBname\fR
Use \fBname\fR as the digest algorithm used to mangle the passphrases.
The default algorithm is SHA-1.
.TP
.B --s2k-mode \fBn\fR
Selects how passphrases are mangled. If \fBn\fR is 0 a plain
passphrase (which is not recommended) will be used, a 1 adds a salt to
the passphrase and a 3 (the default) iterates the whole process a
number of times (see --s2k-count). Unless \fB--rfc1991\fR is used,
this mode is also used for conventional encryption.
.TP
.B --s2k-count \fBn\fR
Specify how many times the passphrase mangling is repeated. This
value may range between 1024 and 65011712 inclusive. The default is
inquired from gpg-agent. Note that not all values in the
1024-65011712 range are legal and if an illegal value is selected,
GnuPG will round up to the nearest legal value. This option is only
meaningful if \fB--s2k-mode\fR is 3.
.SS Compliance options
\
These options control what GnuPG is compliant to. Only one of these
options may be active at a time. Note that the default setting of
this is nearly always the correct one. See the INTEROPERABILITY WITH
OTHER OPENPGP PROGRAMS section below before using one of these
options.
.TP
.B --gnupg
Use standard GnuPG behavior. This is essentially OpenPGP behavior
(see \fB--openpgp\fR), but with some additional workarounds for common
compatibility problems in different versions of PGP. This is the
default option, so it is not generally needed, but it may be useful to
override a different compliance option in the gpg.conf file.
.TP
.B --openpgp
Reset all packet, cipher and digest options to strict OpenPGP
behavior. Use this option to reset all previous options like
\fB--s2k-*\fR, \fB--cipher-algo\fR, \fB--digest-algo\fR and
\fB--compress-algo\fR to OpenPGP compliant values. All PGP
workarounds are disabled.
.TP
.B --rfc4880
Reset all packet, cipher and digest options to strict RFC-4880
behavior. Note that this is currently the same thing as
\fB--openpgp\fR.
.TP
.B --rfc2440
Reset all packet, cipher and digest options to strict RFC-2440
behavior.
.TP
.B --rfc1991
Try to be more RFC-1991 (PGP 2.x) compliant.
.TP
.B --pgp2
Set up all options to be as PGP 2.x compliant as possible, and warn if
an action is taken (e.g. encrypting to a non-RSA key) that will create
a message that PGP 2.x will not be able to handle. Note that `PGP
2.x' here means `MIT PGP 2.6.2'. There are other versions of PGP 2.x
available, but the MIT release is a good common baseline.
This option implies
\fB--rfc1991 --disable-mdc --no-force-v4-certs
--escape-from-lines --force-v3-sigs --allow-weak-digest-algos
--cipher-algo IDEA --digest-algo MD5 --compress-algo ZIP\fR.
It also disables \fB--textmode\fR when encrypting.
.TP
.B --pgp6
Set up all options to be as PGP 6 compliant as possible. This
restricts you to the ciphers IDEA (if the IDEA plugin is installed),
3DES, and CAST5, the hashes MD5, SHA1 and RIPEMD160, and the
compression algorithms none and ZIP. This also disables
--throw-keyids, and making signatures with signing subkeys as PGP 6
does not understand signatures made by signing subkeys.
This option implies \fB--disable-mdc --escape-from-lines
--force-v3-sigs\fR.
.TP
.B --pgp7
Set up all options to be as PGP 7 compliant as possible. This is
identical to \fB--pgp6\fR except that MDCs are not disabled, and the
list of allowable ciphers is expanded to add AES128, AES192, AES256, and
TWOFISH.
.TP
.B --pgp8
Set up all options to be as PGP 8 compliant as possible. PGP 8 is a lot
closer to the OpenPGP standard than previous versions of PGP, so all
this does is disable \fB--throw-keyids\fR and set
\fB--escape-from-lines\fR. All algorithms are allowed except for the
SHA224, SHA384, and SHA512 digests.
.SS Doing things one usually doesn't want to do.
\
.TP
.B -n
.TP
.B --dry-run
Don't make any changes (this is not completely implemented).
.TP
.B --list-only
Changes the behaviour of some commands. This is like \fB--dry-run\fR but
different in some cases. The semantic of this command may be extended in
the future. Currently it only skips the actual decryption pass and
therefore enables a fast listing of the encryption keys.
.TP
.B -i
.TP
.B --interactive
Prompt before overwriting any files.
.TP
.B --debug-level \fIlevel\fR
Select the debug level for investigating problems. \fIlevel\fR may be
a numeric value or by a keyword:
.RS
.TP
.B none
No debugging at all. A value of less than 1 may be used instead of
the keyword.
.TP
.B basic
Some basic debug messages. A value between 1 and 2 may be used
instead of the keyword.
.TP
.B advanced
More verbose debug messages. A value between 3 and 5 may be used
instead of the keyword.
.TP
.B expert
Even more detailed messages. A value between 6 and 8 may be used
instead of the keyword.
.TP
.B guru
All of the debug messages you can get. A value greater than 8 may be
used instead of the keyword. The creation of hash tracing files is
only enabled if the keyword is used.
.RE
How these messages are mapped to the actual debugging flags is not
specified and may change with newer releases of this program. They are
however carefully selected to best aid in debugging.
.TP
.B --debug \fIflags\fR
Set debugging flags. All flags are or-ed and \fIflags\fR may
be given in C syntax (e.g. 0x0042).
.TP
.B --debug-all
Set all useful debugging flags.
.TP
.B --faked-system-time \fIepoch\fR
This option is only useful for testing; it sets the system time back or
forth to \fIepoch\fR which is the number of seconds elapsed since the year
1970. Alternatively \fIepoch\fR may be given as a full ISO time string
(e.g. "20070924T154812").
.TP
.B --enable-progress-filter
Enable certain PROGRESS status outputs. This option allows frontends
to display a progress indicator while gpg is processing larger files.
There is a slight performance overhead using it.
.TP
.B --status-fd \fBn\fR
Write special status strings to the file descriptor \fBn\fR.
See the file DETAILS in the documentation for a listing of them.
.TP
.B --status-file \fBfile\fR
Same as \fB--status-fd\fR, except the status data is written to file
\fBfile\fR.
.TP
.B --logger-fd \fBn\fR
Write log output to file descriptor \fBn\fR and not to STDERR.
.TP
.B --log-file \fBfile\fR
.TP
.B --logger-file \fBfile\fR
Same as \fB--logger-fd\fR, except the logger data is written to file
\fBfile\fR. Note that \fB--log-file\fR is only implemented for
GnuPG-2.
.TP
.B --attribute-fd \fBn\fR
Write attribute subpackets to the file descriptor \fBn\fR. This is most
useful for use with \fB--status-fd\fR, since the status messages are
needed to separate out the various subpackets from the stream delivered
to the file descriptor.
.TP
.B --attribute-file \fBfile\fR
Same as \fB--attribute-fd\fR, except the attribute data is written to
file \fBfile\fR.
.TP
.B --comment \fBstring\fR
.TP
.B --no-comments
Use \fBstring\fR as a comment string in clear text signatures and ASCII
armored messages or keys (see \fB--armor\fR). The default behavior is
not to use a comment string. \fB--comment\fR may be repeated multiple
times to get multiple comment strings. \fB--no-comments\fR removes
all comments. It is a good idea to keep the length of a single comment
below 60 characters to avoid problems with mail programs wrapping such
lines. Note that comment lines, like all other header lines, are not
protected by the signature.
.TP
.B --emit-version
.TP
.B --no-emit-version
Force inclusion of the version string in ASCII armored output. If
given once only the name of the program and the major number is
emitted (default), given twice the minor is also emitted, given triple
the micro is added, and given quad an operating system identification
is also emitted. \fB--no-emit-version\fR disables the version
line.
.TP
.B --sig-notation \fBname=value\fR
.TP
.B --cert-notation \fBname=value\fR
.TP
.B -N, --set-notation \fBname=value\fR
Put the name value pair into the signature as notation data.
\fBname\fR must consist only of printable characters or spaces, and
must contain a '@' character in the form keyname@domain.example.com
(substituting the appropriate keyname and domain name, of course). This
is to help prevent pollution of the IETF reserved notation
namespace. The \fB--expert\fR flag overrides the '@'
check. \fBvalue\fR may be any printable string; it will be encoded in
UTF8, so you should check that your \fB--display-charset\fR is set
correctly. If you prefix \fBname\fR with an exclamation mark (!), the
notation data will be flagged as critical
(rfc4880:5.2.3.16). \fB--sig-notation\fR sets a notation for data
signatures. \fB--cert-notation\fR sets a notation for key signatures
(certifications). \fB--set-notation\fR sets both.
There are special codes that may be used in notation names. "%k" will
be expanded into the key ID of the key being signed, "%K" into the
long key ID of the key being signed, "%f" into the fingerprint of the
key being signed, "%s" into the key ID of the key making the
signature, "%S" into the long key ID of the key making the signature,
"%g" into the fingerprint of the key making the signature (which might
be a subkey), "%p" into the fingerprint of the primary key of the key
making the signature, "%c" into the signature count from the OpenPGP
smartcard, and "%%" results in a single "%". %k, %K, and %f are only
meaningful when making a key signature (certification), and %c is only
meaningful when using the OpenPGP smartcard.
.TP
.B --sig-policy-url \fBstring\fR
.TP
.B --cert-policy-url \fBstring\fR
.TP
.B --set-policy-url \fBstring\fR
Use \fBstring\fR as a Policy URL for signatures (rfc4880:5.2.3.20). If
you prefix it with an exclamation mark (!), the policy URL packet will
be flagged as critical. \fB--sig-policy-url\fR sets a policy url for
data signatures. \fB--cert-policy-url\fR sets a policy url for key
signatures (certifications). \fB--set-policy-url\fR sets both.
The same %-expandos used for notation data are available here as well.
.TP
.B --sig-keyserver-url \fBstring\fR
Use \fBstring\fR as a preferred keyserver URL for data signatures. If
you prefix it with an exclamation mark (!), the keyserver URL packet
will be flagged as critical.
The same %-expandos used for notation data are available here as well.
.TP
.B --set-filename \fBstring\fR
Use \fBstring\fR as the filename which is stored inside messages.
This overrides the default, which is to use the actual filename of the
file being encrypted.
.TP
.B --for-your-eyes-only
.TP
.B --no-for-your-eyes-only
Set the `for your eyes only' flag in the message. This causes GnuPG to
refuse to save the file unless the \fB--output\fR option is given,
and PGP to use a "secure viewer" with a claimed Tempest-resistant font
to display the message. This option overrides \fB--set-filename\fR.
\fB--no-for-your-eyes-only\fR disables this option.
.TP
.B --use-embedded-filename
.TP
.B --no-use-embedded-filename
Try to create a file with a name as embedded in the data. This can be
a dangerous option as it allows to overwrite files. Defaults to no.
.TP
.B --cipher-algo \fBname\fR
Use \fBname\fR as cipher algorithm. Running the program with the
command \fB--version\fR yields a list of supported algorithms. If
this is not used the cipher algorithm is selected from the preferences
stored with the key. In general, you do not want to use this option as
it allows you to violate the OpenPGP standard.
\fB--personal-cipher-preferences\fR is the safe way to accomplish the
same thing.
.TP
.B --digest-algo \fBname\fR
Use \fBname\fR as the message digest algorithm. Running the program
with the command \fB--version\fR yields a list of supported algorithms. In
general, you do not want to use this option as it allows you to
violate the OpenPGP standard. \fB--personal-digest-preferences\fR is the
safe way to accomplish the same thing.
.TP
.B --compress-algo \fBname\fR
Use compression algorithm \fBname\fR. "zlib" is RFC-1950 ZLIB
compression. "zip" is RFC-1951 ZIP compression which is used by PGP.
"bzip2" is a more modern compression scheme that can compress some
things better than zip or zlib, but at the cost of more memory used
during compression and decompression. "uncompressed" or "none"
disables compression. If this option is not used, the default
behavior is to examine the recipient key preferences to see which
algorithms the recipient supports. If all else fails, ZIP is used for
maximum compatibility.
ZLIB may give better compression results than ZIP, as the compression
window size is not limited to 8k. BZIP2 may give even better
compression results than that, but will use a significantly larger
amount of memory while compressing and decompressing. This may be
significant in low memory situations. Note, however, that PGP (all
versions) only supports ZIP compression. Using any algorithm other
than ZIP or "none" will make the message unreadable with PGP. In
general, you do not want to use this option as it allows you to
violate the OpenPGP standard. \fB--personal-compress-preferences\fR is the
safe way to accomplish the same thing.
.TP
.B --cert-digest-algo \fBname\fR
Use \fBname\fR as the message digest algorithm used when signing a
key. Running the program with the command \fB--version\fR yields a
list of supported algorithms. Be aware that if you choose an algorithm
that GnuPG supports but other OpenPGP implementations do not, then some
users will not be able to use the key signatures you make, or quite
possibly your entire key.
.TP
.B --disable-cipher-algo \fBname\fR
Never allow the use of \fBname\fR as cipher algorithm.
The given name will not be checked so that a later loaded algorithm
will still get disabled.
.TP
.B --disable-pubkey-algo \fBname\fR
Never allow the use of \fBname\fR as public key algorithm.
The given name will not be checked so that a later loaded algorithm
will still get disabled.
.TP
.B --throw-keyids
.TP
.B --no-throw-keyids
Do not put the recipient key IDs into encrypted messages. This helps to
hide the receivers of the message and is a limited countermeasure
against traffic analysis. ([Using a little social engineering
anyone who is able to decrypt the message can check whether one of the
other recipients is the one he suspects.]) On the receiving side, it may
slow down the decryption process because all available secret keys must
be tried. \fB--no-throw-keyids\fR disables this option. This option
is essentially the same as using \fB--hidden-recipient\fR for all
recipients.
.TP
.B --not-dash-escaped
This option changes the behavior of cleartext signatures
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 at the beginning of a
line, patch files don't have this. A special armor header
line tells GnuPG about this cleartext signature option.
.TP
.B --escape-from-lines
.TP
.B --no-escape-from-lines
Because some mailers change lines starting with "From " to ">From " it
is good to handle such lines in a special way when creating cleartext
signatures to prevent the mail system from breaking the signature. Note
that all other PGP versions do it this way too. Enabled by
default. \fB--no-escape-from-lines\fR disables this option.
.TP
.B --passphrase-repeat \fBn\fR
Specify how many times \fBgpg2\fR will request a new
passphrase be repeated. This is useful for helping memorize a
passphrase. Defaults to 1 repetition.
.TP
.B --passphrase-fd \fBn\fR
Read the passphrase from file descriptor \fBn\fR. Only the first line
will be read from file descriptor \fBn\fR. If you use 0 for \fBn\fR,
the passphrase will be read from STDIN. This can only be used if only
one passphrase is supplied.
Note that this passphrase is only used if the option \fB--batch\fR
has also been given. This is different from \fBgpg\fR.
.TP
.B --passphrase-file \fBfile\fR
Read the passphrase from file \fBfile\fR. Only the first line will
be read from file \fBfile\fR. This can only be used if only one
passphrase is supplied. Obviously, a passphrase stored in a file is
of questionable security if other users can read this file. Don't use
this option if you can avoid it.
Note that this passphrase is only used if the option \fB--batch\fR
has also been given. This is different from \fBgpg\fR.
.TP
.B --passphrase \fBstring\fR
Use \fBstring\fR as the passphrase. This can only be used if only one
passphrase is supplied. Obviously, this is of very questionable
security on a multi-user system. Don't use this option if you can
avoid it.
Note that this passphrase is only used if the option \fB--batch\fR
has also been given. This is different from \fBgpg\fR.
.TP
.B --command-fd \fBn\fR
This is a replacement for the deprecated shared-memory IPC mode.
If this option is enabled, user input on questions is not expected
from the TTY but from the given file descriptor. It should be used
together with \fB--status-fd\fR. See the file doc/DETAILS in the source
distribution for details on how to use it.
.TP
.B --command-file \fBfile\fR
Same as \fB--command-fd\fR, except the commands are read out of file
\fBfile\fR
.TP
.B --allow-non-selfsigned-uid
.TP
.B --no-allow-non-selfsigned-uid
Allow the import and use of keys with user IDs which are not
self-signed. This is not recommended, as a non self-signed user ID is
trivial to forge. \fB--no-allow-non-selfsigned-uid\fR disables.
.TP
.B --allow-freeform-uid
Disable all checks on the form of the user ID while generating a new
one. This option should only be used in very special environments as
it does not ensure the de-facto standard format of user IDs.
.TP
.B --ignore-time-conflict
GnuPG normally checks that the timestamps associated with keys and
signatures have plausible values. However, sometimes a signature
seems to be older than the key due to clock problems. This option
makes these checks just a warning. See also \fB--ignore-valid-from\fR for
timestamp issues on subkeys.
.TP
.B --ignore-valid-from
GnuPG normally does not select and use subkeys created in the future.
This option allows the use of such keys and thus exhibits the
pre-1.0.7 behaviour. You should not use this option unless there
is some clock problem. See also \fB--ignore-time-conflict\fR for timestamp
issues with signatures.
.TP
.B --ignore-crc-error
The ASCII armor used by OpenPGP is protected by a CRC checksum against
transmission errors. Occasionally the CRC gets mangled somewhere on
the transmission channel but the actual content (which is protected by
the OpenPGP protocol anyway) is still okay. This option allows GnuPG
to ignore CRC errors.
.TP
.B --ignore-mdc-error
This option changes a MDC integrity protection failure into a warning.
This can be useful if a message is partially corrupt, but it is
necessary to get as much data as possible out of the corrupt message.
However, be aware that a MDC protection failure may also mean that the
message was tampered with intentionally by an attacker.
.TP
.B --allow-weak-digest-algos
Signatures made with the broken MD5 algorithm are normally rejected
with an ``invalid digest algorithm'' message. This option allows the
verification of signatures made with such weak algorithms.
.TP
.B --no-default-keyring
Do not add the default keyrings to the list of keyrings. Note that
GnuPG will not operate without any keyrings, so if you use this option
and do not provide alternate keyrings via \fB--keyring\fR or
\fB--secret-keyring\fR, then GnuPG will still use the default public or
secret keyrings.
.TP
.B --skip-verify
Skip the signature verification step. This may be
used to make the decryption faster if the signature
verification is not needed.
.TP
.B --with-key-data
Print key listings delimited by colons (like \fB--with-colons\fR) and
print the public key data.
.TP
.B --fast-list-mode
Changes the output of the list commands to work faster; this is achieved
by leaving some parts empty. Some applications don't need the user ID
and the trust information given in the listings. By using this options
they can get a faster listing. The exact behaviour of this option may
change in future versions. If you are missing some information, don't
use this option.
.TP
.B --no-literal
This is not for normal use. Use the source to see for what it might be useful.
.TP
.B --set-filesize
This is not for normal use. Use the source to see for what it might be useful.
.TP
.B --show-session-key
Display the session key used for one message. See
\fB--override-session-key\fR for the counterpart of this option.
We think that Key Escrow is a Bad Thing; however the user should have
the freedom to decide whether to go to prison or to reveal the content
of one specific message without compromising all messages ever
encrypted for one secret key. DON'T USE IT UNLESS YOU ARE REALLY
FORCED TO DO SO.
.TP
.B --override-session-key \fBstring\fR
Don't use the public key but the session key \fBstring\fR. The format
of this string is the same as the one printed by
\fB--show-session-key\fR. This option is normally not used but comes
handy in case someone forces you to reveal the content of an encrypted
message; using this option you can do this without handing out the
secret key.
.TP
.B --ask-sig-expire
.TP
.B --no-ask-sig-expire
When making a data signature, prompt for an expiration time. If this
option is not specified, the expiration time set via
\fB--default-sig-expire\fR is used. \fB--no-ask-sig-expire\fR
disables this option.
.TP
.B --default-sig-expire
The default expiration time to use for signature expiration. Valid
values are "0" for no expiration, a number followed by the letter d
(for days), w (for weeks), m (for months), or y (for years) (for
example "2m" for two months, or "5y" for five years), or an absolute
date in the form YYYY-MM-DD. Defaults to "0".
.TP
.B --ask-cert-expire
.TP
.B --no-ask-cert-expire
When making a key signature, prompt for an expiration time. If this
option is not specified, the expiration time set via
\fB--default-cert-expire\fR is used. \fB--no-ask-cert-expire\fR
disables this option.
.TP
.B --default-cert-expire
The default expiration time to use for key signature expiration.
Valid values are "0" for no expiration, a number followed by the
letter d (for days), w (for weeks), m (for months), or y (for years)
(for example "2m" for two months, or "5y" for five years), or an
absolute date in the form YYYY-MM-DD. Defaults to "0".
.TP
.B --allow-secret-key-import
This is an obsolete option and is not used anywhere.
.TP
.B --allow-multiple-messages
.TP
.B --no-allow-multiple-messages
Allow processing of multiple OpenPGP messages contained in a single file
or stream. Some programs that call GPG are not prepared to deal with
multiple messages being processed together, so this option defaults to
no. Note that versions of GPG prior to 1.4.7 always allowed multiple
messages.
Warning: Do not use this option unless you need it as a temporary
workaround!
.TP
.B --enable-special-filenames
This options enables a mode in which filenames of the form
\(oq\fI-&n\fR\(cq, where n is a non-negative decimal number,
refer to the file descriptor n and not to a file with that name.
.TP
.B --no-expensive-trust-checks
Experimental use only.
.TP
.B --preserve-permissions
Don't change the permissions of a secret keyring back to user
read/write only. Use this option only if you really know what you are doing.
.TP
.B --default-preference-list \fBstring\fR
Set the list of default preferences to \fBstring\fR. This preference
list is used for new keys and becomes the default for "setpref" in the
edit menu.
.TP
.B --default-keyserver-url \fBname\fR
Set the default keyserver URL to \fBname\fR. This keyserver will be
used as the keyserver URL when writing a new self-signature on a key,
which includes key generation and changing preferences.
.TP
.B --list-config
Display various internal configuration parameters of GnuPG. This option
is intended for external programs that call GnuPG to perform tasks, and
is thus not generally useful. See the file \(oq\fIdoc/DETAILS\fR\(cq in the
source distribution for the details of which configuration items may be
listed. \fB--list-config\fR is only usable with
\fB--with-colons\fR set.
.TP
.B --gpgconf-list
This command is similar to \fB--list-config\fR but in general only
internally used by the \fBgpgconf\fR tool.
.TP
.B --gpgconf-test
This is more or less dummy action. However it parses the configuration
file and returns with failure if the configuration file would prevent
\fBgpg\fR from startup. Thus it may be used to run a syntax check
on the configuration file.
.SS Deprecated options
\
.TP
.B --show-photos
.TP
.B --no-show-photos
Causes \fB--list-keys\fR, \fB--list-sigs\fR,
\fB--list-public-keys\fR, \fB--list-secret-keys\fR, and verifying
a signature to also display the photo ID attached to the key, if
any. See also \fB--photo-viewer\fR. These options are deprecated. Use
\fB--list-options [no-]show-photos\fR and/or \fB--verify-options
[no-]show-photos\fR instead.
.TP
.B --show-keyring
Display the keyring name at the head of key listings to show which
keyring a given key resides on. This option is deprecated: use
\fB--list-options [no-]show-keyring\fR instead.
.TP
.B --always-trust
Identical to \fB--trust-model always\fR. This option is deprecated.
.TP
.B --show-notation
.TP
.B --no-show-notation
Show signature notations in the \fB--list-sigs\fR or \fB--check-sigs\fR listings
as well as when verifying a signature with a notation in it. These
options are deprecated. Use \fB--list-options [no-]show-notation\fR
and/or \fB--verify-options [no-]show-notation\fR instead.
.TP
.B --show-policy-url
.TP
.B --no-show-policy-url
Show policy URLs in the \fB--list-sigs\fR or \fB--check-sigs\fR
listings as well as when verifying a signature with a policy URL in
it. These options are deprecated. Use \fB--list-options
[no-]show-policy-url\fR and/or \fB--verify-options
[no-]show-policy-url\fR instead.
.SH EXAMPLES
.TP
.B gpg -se -r \fBBob\fR \fBfile\fR
sign and encrypt for user Bob
.TP
.B gpg --clearsign \fBfile\fR
make a clear text signature
.TP
.B gpg -sb \fBfile\fR
make a detached signature
.TP
.B gpg -u 0x12345678 -sb \fBfile\fR
make a detached signature with the key 0x12345678
.TP
.B gpg --list-keys \fBuser_ID\fR
show keys
.TP
.B gpg --fingerprint \fBuser_ID\fR
show fingerprint
.TP
.B gpg --verify \fBpgpfile\fR
.TP
.B gpg --verify \fBsigfile\fR
Verify the signature of the file but do not output the data. The
second form is used for detached signatures, where \fBsigfile\fR
is the detached signature (either ASCII armored or binary) and
are the signed data; if this is not given, the name of
the file holding the signed data is constructed by cutting off the
extension (".asc" or ".sig") of \fBsigfile\fR or by asking the
user for the filename.
.SH HOW TO SPECIFY A USER ID
There are different ways to specify a user ID to GnuPG. Some of them
are only valid for \fBgpg\fR others are only good for
\fBgpgsm\fR. Here is the entire list of ways to specify a key:
.TP
.B By key Id.
This format is deduced from the length of the string and its content or
\fB0x\fR prefix. The key Id of an X.509 certificate are the low 64 bits
of its SHA-1 fingerprint. The use of key Ids is just a shortcut, for
all automated processing the fingerprint should be used.
When using \fBgpg\fR an exclamation mark (!) may be appended to
force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The last four lines of the example give the key ID in their long form as
internally used by the OpenPGP protocol. You can see the long key ID
using the option \fB--with-colons\fR.
.RS 2
.nf
234567C4
0F34E556E
01347A56A
0xAB123456
234AABBCC34567C4
0F323456784E56EAB
01AB3FED1347A5612
0x234AABBCC34567C4
.fi
.RE
.TP
.B By fingerprint.
This format is deduced from the length of the string and its content or
the \fB0x\fR prefix. Note, that only the 20 byte version fingerprint
is available with \fBgpgsm\fR (i.e. the SHA-1 hash of the
certificate).
When using \fBgpg\fR an exclamation mark (!) may be appended to
force using the specified primary or secondary key and not to try and
calculate which primary or secondary key to use.
The best way to specify a key Id is by using the fingerprint. This
avoids any ambiguities in case that there are duplicated key IDs.
.RS 2
.nf
1234343434343434C434343434343434
123434343434343C3434343434343734349A3434
0E12343434343434343434EAB3484343434343434
0xE12343434343434343434EAB3484343434343434
.fi
.RE
(\fBgpgsm\fR also accepts colons between each pair of hexadecimal
digits because this is the de-facto standard on how to present X.509
fingerprints.)
.TP
.B By exact match on OpenPGP user ID.
This is denoted by a leading equal sign. It does not make sense for
X.509 certificates.
.RS 2
.nf
=Heinrich Heine <heinrichh@uni-duesseldorf.de>
.fi
.RE
.TP
.B By exact match on an email address.
This is indicated by enclosing the email address in the usual way
with left and right angles.
.RS 2
.nf
<heinrichh@uni-duesseldorf.de>
.fi
.RE
.TP
.B By word match.
All words must match exactly (not case sensitive) but can appear in any
order in the user ID or a subjects name. Words are any sequences of
letters, digits, the underscore and all characters with bit 7 set.
.RS 2
.nf
+Heinrich Heine duesseldorf
.fi
.RE
.TP
.B By exact match on the subject's DN.
This is indicated by a leading slash, directly followed by the RFC-2253
encoded DN of the subject. Note that you can't use the string printed
by "gpgsm --list-keys" because that one as been reordered and modified
for better readability; use --with-colons to print the raw (but standard
escaped) RFC-2253 string
.RS 2
.nf
/CN=Heinrich Heine,O=Poets,L=Paris,C=FR
.fi
.RE
.TP
.B By exact match on the issuer's DN.
This is indicated by a leading hash mark, directly followed by a slash
and then directly followed by the rfc2253 encoded DN of the issuer.
This should return the Root cert of the issuer. See note above.
.RS 2
.nf
#/CN=Root Cert,O=Poets,L=Paris,C=FR
.fi
.RE
.TP
.B By exact match on serial number and issuer's DN.
This is indicated by a hash mark, followed by the hexadecimal
representation of the serial number, then followed by a slash and the
RFC-2253 encoded DN of the issuer. See note above.
.RS 2
.nf
#4F03/CN=Root Cert,O=Poets,L=Paris,C=FR
.fi
.RE
.TP
.B By keygrip
This is indicated by an ampersand followed by the 40 hex digits of a
keygrip. \fBgpgsm\fR prints the keygrip when using the command
\fB--dump-cert\fR. It does not yet work for OpenPGP keys.
.RS 2
.nf
&D75F22C3F86E355877348498CDC92BD21010A480
.fi
.RE
.TP
.B By substring match.
This is the default mode but applications may want to explicitly
indicate this by putting the asterisk in front. Match is not case
sensitive.
.RS 2
.nf
Heine
*Heine
.fi
.RE
Please note that we have reused the hash mark identifier which was used
in old GnuPG versions to indicate the so called local-id. It is not
anymore used and there should be no conflict when used with X.509 stuff.
Using the RFC-2253 format of DNs has the drawback that it is not
possible to map them back to the original encoding, however we don't
have to do this because our key database stores this encoding as meta
data.
.SH FILES
There are a few configuration files to control certain aspects of
\fBgpg2\fR's operation. Unless noted, they are expected in the
current home directory (see: [option --homedir]).
.TP
.B gpg.conf
This is the standard configuration file read by \fBgpg2\fR on
startup. It may contain any valid long option; the leading two dashes
may not be entered and the option may not be abbreviated. This default
name may be changed on the command line (see: [gpg-option --options]).
You should backup this file.
.RE
Note that on larger installations, it is useful to put predefined files
into the directory \(oq\fI/etc/skel/.gnupg/\fR\(cq so that newly created users
start up with a working configuration.
For existing users the a small
helper script is provided to create these files (see: [addgnupghome]).
For internal purposes \fBgpg2\fR creates and maintains a few other
files; They all live in in the current home directory (see: [option
--homedir]). Only the \fBgpg2\fR may modify these files.
.TP
.B ~/.gnupg/pubring.gpg
The public keyring. You should backup this file.
.TP
.B ~/.gnupg/pubring.gpg.lock
The lock file for the public keyring.
.TP
.B ~/.gnupg/secring.gpg
The secret keyring. You should backup this file.
.TP
.B ~/.gnupg/trustdb.gpg
The trust database. There is no need to backup this file; it is better
to backup the ownertrust values (see: [option --export-ownertrust]).
.TP
.B ~/.gnupg/trustdb.gpg.lock
The lock file for the trust database.
.TP
.B ~/.gnupg/random_seed
A file used to preserve the state of the internal random pool.
.TP
.B ~/.gnupg/secring.gpg.lock
The lock file for the secret keyring.
.TP
.B /usr[/local]/share/gnupg/options.skel
The skeleton options file.
.TP
.B /usr[/local]/lib/gnupg/
Default location for extensions.
.RE
Operation is further controlled by a few environment variables:
.TP
.B HOME
Used to locate the default home directory.
.TP
.B GNUPGHOME
If set directory used instead of "~/.gnupg".
.TP
.B GPG_AGENT_INFO
Used to locate the gpg-agent.
The value consists of 3 colon delimited fields: The first is the path
to the Unix Domain Socket, the second the PID of the gpg-agent and the
protocol version which should be set to 1. When starting the gpg-agent
as described in its documentation, this variable is set to the correct
value. The option \fB--gpg-agent-info\fR can be used to override it.
.TP
.B PINENTRY_USER_DATA
This value is passed via gpg-agent to pinentry. It is useful to convey
extra information to a custom pinentry.
.TP
.B COLUMNS
.TP
.B LINES
Used to size some displays to the full size of the screen.
.TP
.B LANGUAGE
Apart from its use by GNU, it is used in the W32 version to override the
language selection done through the Registry. If used and set to a
valid and available language name (\fIlangid\fR), the file with the
translation is loaded from
\fB\fIgpgdir\fR/gnupg.nls/\fIlangid\fR.mo\fR. Here \fIgpgdir\fR is the
directory out of which the gpg binary has been loaded. If it can't be
loaded the Registry is tried and as last resort the native Windows
locale system is used.
.SH BUGS
On older systems this program should be installed as setuid(root). This
is necessary to lock memory pages. Locking memory pages prevents the
operating system from writing memory pages (which may contain
passphrases or other sensitive material) to disk. If you get no
warning message about insecure memory your operating system supports
locking without being root. The program drops root privileges as soon
as locked memory is allocated.
Note also that some systems (especially laptops) have the ability to
``suspend to disk'' (also known as ``safe sleep'' or ``hibernate'').
This writes all memory to disk before going into a low power or even
powered off mode. Unless measures are taken in the operating system
to protect the saved memory, passphrases or other sensitive material
may be recoverable from it later.
Before you report a bug you should first search the mailing list
archives for similar problems and second check whether such a bug has
already been reported to our bug tracker at http://bugs.gnupg.org .
.\" Oracle has added the ARC stability level to this manual page
.SH ATTRIBUTES
See
.BR attributes (5)
for descriptions of the following attributes:
.sp
.TS
box;
cbp-1 | cbp-1
l | l .
ATTRIBUTE TYPE ATTRIBUTE VALUE
=
Availability crypto/gnupg
=
Stability Uncommitted
.TE
.PP
.SH SEE ALSO
\fBgpgv\fR(1),
\fBgpgsm\fR(1),
\fBgpg-agent\fR(1)
The full documentation for this tool is maintained as a Texinfo manual.
If GnuPG and the info program are properly installed at your site, the
command
.RS 2
.nf
info gnupg
.fi
.RE
should give you access to the complete manual including a menu structure
and an index.
.SH NOTES
.\" Oracle has added source availability information to this manual page
This software was built from source available at https://java.net/projects/solaris-userland. The original community source was downloaded from ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.0.27.tar.bz2
Further information about this software can be found on the open source community website at http://www.gnupg.org/.