/usr/share/doc/gnupg-doc/GNU_Privacy_Handbook/de/html/r929.htm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>gpg manpage</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Das GNU-Handbuch zum Schutze der Privatsphäre"
HREF="book1.htm"><LINK
REL="UP"
TITLE="Referenz"
HREF="a925.htm"><LINK
REL="PREVIOUS"
TITLE="Referenz"
HREF="a925.htm"><LINK
REL="NEXT"
TITLE="Glossar"
HREF="a1855.htm"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Das GNU-Handbuch zum Schutze der Privatsphäre</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="a925.htm"
ACCESSKEY="P"
>Zurück</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="a1855.htm"
ACCESSKEY="N"
>Weiter</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="GPG"
></A
>gpg manpage</H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN934"
></A
><H2
>Name</H2
>gpg&nbsp;--&nbsp;encryption and signing tool</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN937"
></A
><H2
>Synopsis</H2
><PRE
CLASS="SYNOPSIS"
><B
CLASS="COMMAND"
>gpg</B
>
 [<SPAN
CLASS="OPTIONAL"
>--homedir <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></SPAN
>]
 [<SPAN
CLASS="OPTIONAL"
>--options <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></SPAN
>]
 [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>options</I
></TT
></SPAN
>]
 <TT
CLASS="PARAMETER"
><I
>command</I
></TT
>
 [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>args</I
></TT
></SPAN
>]
  </PRE
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN949"
></A
><H2
>DESCRIPTION</H2
><P
><B
CLASS="COMMAND"
>gpg</B
> is the main program for the GnuPG system.
    </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN953"
></A
><H2
>COMMANDS</H2
><P
><B
CLASS="COMMAND"
>gpg</B
> recognizes these commands:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>-s, --sign</DT
><DD
><P
>Make a signature. This command may be combined
with --encrypt.</P
></DD
><DT
>--clearsign</DT
><DD
><P
>Make a clear text signature.</P
></DD
><DT
>-b, --detach-sign</DT
><DD
><P
>Make a detached signature.</P
></DD
><DT
>-e, --encrypt</DT
><DD
><P
>Encrypt data. This option may be combined with --sign.</P
></DD
><DT
>-c, --symmetric</DT
><DD
><P
>Encrypt with symmetric cipher only
This command asks for a passphrase.</P
></DD
><DT
>--store</DT
><DD
><P
>Store only (make a simple RFC1991 packet).</P
></DD
><DT
>--decrypt [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>file</I
></TT
></SPAN
>]</DT
><DD
><P
>Decrypt <TT
CLASS="PARAMETER"
><I
>file</I
></TT
> (or stdin if no file is specified) and
write it to stdout (or the file specified with
--output). 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.</P
></DD
><DT
>--verify [<SPAN
CLASS="OPTIONAL"
>[<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>sigfile</I
></TT
></SPAN
>]
 [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>signed-files</I
></TT
></SPAN
>]</SPAN
>]</DT
><DD
><P
>Assume that <TT
CLASS="PARAMETER"
><I
>sigfile</I
></TT
> is a signature and verify it
without generating any output.	With no arguments,
the signature packet is read from stdin (it may be a
detached signature when not used in batch mode). 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 (if such a file does
not exist it is expected at stdin; use a single dash ("-") as
filename to force a read from stdin). With more than
1 argument, the first should be a detached signature
and the remaining files are the signed stuff.</P
></DD
><DT
>--verify-files [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>]</DT
><DD
><P
>This is a special version of the --verify command which does not work with
detached signatures.  The command expects the files to bee verified either
on the commandline or reads the filenames from stdin;  each anem muts be on
separate line. The command is intended for quick checking of many files.</P
></DD
><DT
>--list-keys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>], --list-public-keys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>List all keys from the public keyrings, or just the
ones given on the command line.</P
></DD
><DT
>--list-secret-keys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>List all keys from the secret keyrings, or just the
ones given on the command line.</P
></DD
><DT
>--list-sigs [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Same as --list-keys, but the signatures are listed too.</P
></DD
><DT
>--check-sigs [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Same as --list-sigs, but the signatures are verified.</P
></DD
><DT
>--fingerprint [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>List all keys with their fingerprints. This is the
same output as --list-keys but with the additional output
of a line with the fingerprint. May also be combined
with --list-sigs or --check-sigs.
If this command is given twice, the fingerprints of all
secondary keys are listed too.</P
></DD
><DT
>--list-packets</DT
><DD
><P
>List only the sequence of packets. This is mainly
useful for debugging.</P
></DD
><DT
>--gen-key</DT
><DD
><P
>Generate a new key pair. This command is normally only used
interactive.</P
><P
>There is an experimental feature which allows to create keys
in batch mode. See the file <TT
CLASS="FILENAME"
>doc/DETAILS</TT
>
in the source distribution on how to use this.</P
></DD
><DT
>--edit-key <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Present a menu which enables you to do all key
related tasks:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>sign</DT
><DD
><P
>Make a signature on key of user <TT
CLASS="PARAMETER"
><I
>name</I
></TT
>
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.</P
></DD
><DT
>lsign</DT
><DD
><P
>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.</P
></DD
><DT
>revsig</DT
><DD
><P
>Revoke a signature.  GnuPG asks for every
signature which has been done by one of
the secret keys, whether a revocation
certificate should be generated.</P
></DD
><DT
>trust</DT
><DD
><P
>Change the owner trust value. This updates the
trust-db immediately and no save is required.</P
></DD
><DT
>disable, enable</DT
><DD
><P
>Disable or enable an entire key. A disabled key can normally not be used
for encryption.</P
></DD
><DT
>adduid</DT
><DD
><P
>Create an alternate user id.</P
></DD
><DT
>deluid</DT
><DD
><P
>Delete an user id.</P
></DD
><DT
>addkey</DT
><DD
><P
>Add a subkey to this key.</P
></DD
><DT
>delkey</DT
><DD
><P
>Remove a subkey.</P
></DD
><DT
>revkey</DT
><DD
><P
>Revoke a subkey.</P
></DD
><DT
>expire</DT
><DD
><P
>Change the key expiration time.  If a key is
selected, the time of this key will be changed.
With no selection the key expiration of the
primary key is changed.</P
></DD
><DT
>passwd</DT
><DD
><P
>Change the passphrase of the secret key.</P
></DD
><DT
>uid <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Toggle selection of user id with index <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>.
Use 0 to deselect all.</P
></DD
><DT
>key <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Toggle selection of subkey with index <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>.
Use 0 to deselect all.</P
></DD
><DT
>check</DT
><DD
><P
>Check all selected user ids.</P
></DD
><DT
>pref</DT
><DD
><P
>List preferences.</P
></DD
><DT
>toggle</DT
><DD
><P
>Toggle between public and secret key listing.</P
></DD
><DT
>save</DT
><DD
><P
>Save all changes to the key rings and quit.</P
></DD
><DT
>quit</DT
><DD
><P
>Quit the program without updating the
key rings.</P
></DD
></DL
></DIV
><P
>The listing shows you the key with its secondary
keys and all user ids. 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:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>-</DT
><DD
><P
>No ownertrust assigned / not yet calculated.</P
></DD
><DT
>e</DT
><DD
><P
>Trust calculation has failed.</P
></DD
><DT
>q</DT
><DD
><P
>Not enough information for calculation.</P
></DD
><DT
>n</DT
><DD
><P
>Never trust this key.</P
></DD
><DT
>m</DT
><DD
><P
>Marginally trusted.</P
></DD
><DT
>f</DT
><DD
><P
>Fully trusted.</P
></DD
><DT
>u</DT
><DD
><P
>Ultimately trusted.</P
></DD
></DL
></DIV
></DD
><DT
>--sign-key <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Sign a public key with you secret key.	This is a shortcut version
of the subcommand "sign" from --edit.</P
></DD
><DT
>--lsign-key <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Sign a public key with you secret key but mark it as non-exportable.
This is a shortcut version of the subcommand "lsign" from --edit.</P
></DD
><DT
>--delete-key <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Remove key from the public keyring</P
></DD
><DT
>--delete-secret-key  <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Remove key from the secret and public keyring</P
></DD
><DT
>--gen-revoke</DT
><DD
><P
>Generate a revocation certificate for the complete key. To revoke
a subkey or a signature, use the --edit command.</P
></DD
><DT
>--export [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Either export all keys from all keyrings (default
keyrings and those registered via option --keyring),
or if at least one name is given, those of the given
name. The new keyring is written to stdout or to
the file given with option "output".  Use together
with --armor to mail those keys.</P
></DD
><DT
>--send-keys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Same as --export but sends the keys to a keyserver.
Option --keyserver 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.</P
></DD
><DT
>--export-all [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Same as --export, but does also export keys which
are not compatible to OpenPGP.</P
></DD
><DT
>--export-secret-keys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>], --export-secret-subkeys [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>names</I
></TT
></SPAN
>]</DT
><DD
><P
>Same as --export, but does export the secret keys.
This is normally not very useful and a security risk.
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 successful import such a key.</P
></DD
><DT
>--import [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>], --fast-import [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>]</DT
><DD
><P
>Import/merge keys. This adds the given keys to the
keyring.
The fast version does not build
the trustdb; this can be done at any time with the
command --update-trustdb.</P
></DD
><DT
>--recv-keys <TT
CLASS="PARAMETER"
><I
>key IDs</I
></TT
></DT
><DD
><P
>Import the keys with the given key IDs from a HKP
keyserver. Option --keyserver must be used to
give the name of this keyserver.</P
></DD
><DT
>--export-ownertrust</DT
><DD
><P
>List the assigned ownertrust values in ASCII format
for backup purposes</P
></DD
><DT
>--import-ownertrust [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>]</DT
><DD
><P
>Update the trustdb with the ownertrust values stored
in <TT
CLASS="PARAMETER"
><I
>files</I
></TT
> (or stdin if not given); existing
values will be overwritten.</P
></DD
><DT
>--print-md <TT
CLASS="PARAMETER"
><I
>algo</I
></TT
> [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>]</DT
><DD
><P
>Print message digest of algorithm ALGO for all given files of stdin.
If "*" is used for the algorithm, digests for all available algorithms
are printed.</P
></DD
><DT
>--gen-random <TT
CLASS="PARAMETER"
><I
>0|1|2</I
></TT
>
		   [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>count</I
></TT
></SPAN
>]</DT
><DD
><P
>Emit COUNT random bytes of the given quality level. If count is not given
or zero, an endless sequence of random bytes will be emitted.
PLEASE, don't use this command unless you know what you are doing, it may
remove precious entropy from the system!</P
></DD
><DT
>--gen-prime <TT
CLASS="PARAMETER"
><I
>mode</I
></TT
>
		  <TT
CLASS="PARAMETER"
><I
>bits</I
></TT
>
		   [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>qbits</I
></TT
></SPAN
>]</DT
><DD
><P
>Use the source, Luke :-). The output format is still subject to change.</P
></DD
><DT
>--version</DT
><DD
><P
>Print version information along with a list
of supported algorithms.</P
></DD
><DT
>--warranty</DT
><DD
><P
>Print warranty information.</P
></DD
><DT
>-h, --help</DT
><DD
><P
>Print usage information.  This is a really long list even it does list
not all options.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1276"
></A
><H2
>OPTIONS</H2
><P
>Long options can be put in an options file (default "~/.gnupg/options").
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
does not make sense.</P
><P
><B
CLASS="COMMAND"
>gpg</B
> recognizes these options:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>-a, --armor</DT
><DD
><P
>Create ASCII armored output.</P
></DD
><DT
>-o, --output <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>Write output to <TT
CLASS="PARAMETER"
><I
>file</I
></TT
>.</P
></DD
><DT
>-u, --local-user <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as the user ID to sign.
This option is silently ignored for the list commands,
so that it can be used in an options file.</P
></DD
><DT
>--default-key <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as default user ID for signatures.  If this
is not used the default user ID is the first user ID
found in the secret keyring.</P
></DD
><DT
>-r, --recipient <TT
CLASS="PARAMETER"
><I
>name</I
></TT
>, </DT
><DD
><P
>Encrypt for user id <TT
CLASS="PARAMETER"
><I
>name</I
></TT
>. If this option is not
specified, GnuPG asks for the user-id unless --default-recipient is given</P
></DD
><DT
>--default-recipient <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as default recipient if option --recipient is not used and
don't ask if this is a valid one. <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> must be a non empty.</P
></DD
><DT
>--default-recipient-self</DT
><DD
><P
>Use the default key as default recipient if option --recipient 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 --default-key.</P
></DD
><DT
>--no-default-recipient</DT
><DD
><P
>Reset --default-recipient and --default-recipient-self.</P
></DD
><DT
>--encrypt-to <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Same as --recipient but this one is intended for
in the options file and may be used together with
an own user-id as an "encrypt-to-self".  These keys
are only used when there are other recipients given
either by use of --recipient or by the asked user id.
No trust checking is performed for these user ids and
even disabled keys can be used.</P
></DD
><DT
>--no-encrypt-to</DT
><DD
><P
>Disable the use of all --encrypt-to keys.</P
></DD
><DT
>-v, --verbose</DT
><DD
><P
>Give more information during processing. If used
twice, the input data is listed in detail.</P
></DD
><DT
>-q, --quiet</DT
><DD
><P
>Try to be as quiet as possible.</P
></DD
><DT
>-z <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Set compression level to <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>. A value of 0 for <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>
disables compression. Default is to use the default
compression level of zlib (normally 6).</P
></DD
><DT
>-t, --textmode</DT
><DD
><P
>Use canonical text mode.  If -t (but not
--textmode) is used together with armoring
and signing, this enables clearsigned messages.
This kludge is needed for PGP compatibility;
normally you would use --sign or --clearsign
to selected the type of the signature.</P
></DD
><DT
>-n, --dry-run</DT
><DD
><P
>Don't make any changes (this is not completely implemented).</P
></DD
><DT
>-i, --interactive</DT
><DD
><P
>Prompt before overwriting any files.</P
></DD
><DT
>--batch</DT
><DD
><P
>Use batch mode.  Never ask, do not allow interactive
commands.</P
></DD
><DT
>--no-batch</DT
><DD
><P
>Disable batch mode.  This may be of use if --batch
is enabled from an options file.</P
></DD
><DT
>--yes</DT
><DD
><P
>Assume "yes" on most questions.</P
></DD
><DT
>--no</DT
><DD
><P
> Assume "no" on most questions.</P
></DD
><DT
>--always-trust</DT
><DD
><P
>Skip key validation and assume that used keys are always fully trusted.
You won't use this unless you have installed some external validation scheme.</P
></DD
><DT
>--keyserver <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> to lookup keys which are not yet in
your keyring.  This is only done while verifying
messages with signatures.  The option is also
required for the command --send-keys to
specify the keyserver to where the keys should
be send.  All keyservers synchronize with each
other - so there is no need to send keys to more
than one server.  Using the command
"host -l pgp.net | grep wwwkeys" gives you a
list of keyservers.  Because there is load
balancing using round-robin DNS you may notice
that you get different key servers.</P
></DD
><DT
>--honor-http-proxy</DT
><DD
><P
>Try to access the keyserver over the proxy set with the variable
"http_proxy".</P
></DD
><DT
>--keyring <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>Add <TT
CLASS="PARAMETER"
><I
>file</I
></TT
> to the list of keyrings.
If <TT
CLASS="PARAMETER"
><I
>file</I
></TT
> 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
home-directory ("~/.gnupg" if --homedir is not used).
The filename may be prefixed with a scheme:</P
><P
>"gnupg-ring:" is the default one.</P
><P
>"gnupg-gdbm:" may be used for a GDBM ring. Note that GDBM
is experimental and likely to be removed in future versions.</P
><P
>It might make sense to use it together with --no-default-keyring.</P
></DD
><DT
>--secret-keyring <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>Same as --keyring but for the secret keyrings.</P
></DD
><DT
>--homedir <TT
CLASS="PARAMETER"
><I
>directory</I
></TT
></DT
><DD
><P
>Set the name of the home directory to <TT
CLASS="PARAMETER"
><I
>directory</I
></TT
> If this
option is not used it defaults to "~/.gnupg". It does
not make sense to use this in a options file. This
also overrides the environment variable "GNUPGHOME".</P
></DD
><DT
>--charset <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Set the name of the native character set.  This is used
to convert some strings to proper UTF-8 encoding.
Valid values for <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> are:</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>iso-8859-1</DT
><DD
><P
>This is the default Latin 1 set.</P
></DD
><DT
>iso-8859-2</DT
><DD
><P
>The Latin 2 set.</P
></DD
><DT
>koi8-r</DT
><DD
><P
>The usual Russian set (rfc1489).</P
></DD
></DL
></DIV
></DD
><DT
>--utf8-strings, --no-utf8-strings</DT
><DD
><P
>Assume that the arguments are already given as UTF8 strings.  The default
(--no-utf8-strings)
is to assume that arguments are encoded in the character set as specified
by --charset. These options effects all following arguments.  Both options may
used multiple times.</P
></DD
><DT
>--options <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>Read options from <TT
CLASS="PARAMETER"
><I
>file</I
></TT
> and do not try to read
them from the default options file in the homedir
(see --homedir). This option is ignored if used
in an options file.</P
></DD
><DT
>--no-options</DT
><DD
><P
>Shortcut for "--options /dev/null".  This option is
detected before an attempt to open an option file.</P
></DD
><DT
>--load-extension <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Load an extension module. If <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> does not
contain a slash it is searched in "/usr/local/lib/gnupg"
See the manual for more information about extensions.</P
></DD
><DT
>--debug <TT
CLASS="PARAMETER"
><I
>flags</I
></TT
></DT
><DD
><P
>Set debugging flags. All flags are or-ed and <TT
CLASS="PARAMETER"
><I
>flags</I
></TT
> may
be given in C syntax (e.g. 0x0042).</P
></DD
><DT
>--debug-all</DT
><DD
><P
> Set all useful debugging flags.</P
></DD
><DT
>--status-fd <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Write special status strings to the file descriptor <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>.
See the file DETAILS in the documentation for a listing of them.</P
></DD
><DT
>--logger-fd <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Write log output to file descriptor <TT
CLASS="PARAMETER"
><I
>n</I
></TT
> and not to stderr.</P
></DD
><DT
>--no-comment</DT
><DD
><P
>Do not write comment packets.  This option affects only
the generation of secret keys.	Output of option packets
is disabled since version 0.4.2.</P
></DD
><DT
>--comment <TT
CLASS="PARAMETER"
><I
>string</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>string</I
></TT
> as comment string in clear text signatures.</P
></DD
><DT
>--default-comment</DT
><DD
><P
>Force to write the standard comment string in clear
text signatures.  Use this to overwrite a --comment
from a config file.</P
></DD
><DT
>--no-version</DT
><DD
><P
>Omit the version string in clear text signatures.</P
></DD
><DT
>--emit-version</DT
><DD
><P
>Force to write the version string in clear text
signatures.  Use this to overwrite a previous
--no-version from a config file.</P
></DD
><DT
>-N, --notation-data <TT
CLASS="PARAMETER"
><I
>name=value</I
></TT
></DT
><DD
><P
>Put the name value pair into the signature as notation data.
<TT
CLASS="PARAMETER"
><I
>name</I
></TT
> must consists only of alphanumeric characters, digits
or the underscore; the first character must not be a digit.
<TT
CLASS="PARAMETER"
><I
>value</I
></TT
> may be any printable string; it will encoded in UTF8,
so sou should have check that your --charset is set right.
If you prefix <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> with an exclamation mark, the notation
data will be flagged as critical (rfc2440:5.2.3.15).</P
></DD
><DT
>--set-policy-url <TT
CLASS="PARAMETER"
><I
>string</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>string</I
></TT
> as Policy URL for signatures (rfc2440:5.2.3.19).
If you prefix it with an exclamation mark, the policy URL
packet will be flagged as critical.</P
></DD
><DT
>--set-filename <TT
CLASS="PARAMETER"
><I
>string</I
></TT
></DT
><DD
><P
>Use <TT
CLASS="PARAMETER"
><I
>string</I
></TT
> as the name of file which is stored in
messages.</P
></DD
><DT
>--use-embedded-filename</DT
><DD
><P
>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.</P
></DD
><DT
>--completes-needed <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Number of completely trusted users to introduce a new
key signer (defaults to 1).</P
></DD
><DT
>--marginals-needed <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Number of marginally trusted users to introduce a new
key signer (defaults to 3)</P
></DD
><DT
>--max-cert-depth <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Maximum depth of a certification chain (default is 5).</P
></DD
><DT
>--cipher-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use  <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as cipher algorithm. Running the program
with the command --version yields a list of supported
algorithms. If this is not used the cipher algorithm is
selected from the preferences stored with the key.</P
></DD
><DT
>--digest-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use  <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as message digest algorithm. Running the
program with the command --version yields a list of
supported algorithms.  Please note that using this
option may violate the OpenPGP requirement, that a
160 bit hash is to be used for DSA.</P
></DD
><DT
>--s2k-cipher-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use  <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as the cipher algorithm used to protect secret
keys.  The default cipher is BLOWFISH.	This cipher is
also used for conventional encryption if --cipher-algo
is not given.</P
></DD
><DT
>--s2k-digest-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Use  <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as the digest algorithm used to mangle the
passphrases.  The default algorithm is RIPE-MD-160.
This digest algorithm is also used for conventional
encryption if --digest-algo is not given.</P
></DD
><DT
>--s2k-mode <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Selects how passphrases are mangled. If <TT
CLASS="PARAMETER"
><I
>n</I
></TT
> is 0
a plain passphrase (which is not recommended) will be used,
a 1 (default) adds a salt to the passphrase and
a 3 iterates the whole process a couple of times.
Unless --rfc1991 is used, this mode is also used
for conventional encryption.</P
></DD
><DT
>--compress-algo <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Use compress algorithm	<TT
CLASS="PARAMETER"
><I
>n</I
></TT
>. Default is 2 which is
RFC1950 compression. You may use 1 to use the old zlib
version which is used by PGP. The default algorithm may
give better results because the window size is not limited
to 8K. If this is not used the OpenPGP behavior is used,
i.e. the compression algorithm is selected from the
preferences; note, that this can't be done if you do
not encrypt the data.</P
></DD
><DT
>--disable-cipher-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Never allow the use of <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as cipher algorithm.
The given name will not be checked so that a later loaded algorithm
will still get disabled.</P
></DD
><DT
>--disable-pubkey-algo <TT
CLASS="PARAMETER"
><I
>name</I
></TT
></DT
><DD
><P
>Never allow the use of <TT
CLASS="PARAMETER"
><I
>name</I
></TT
> as public key algorithm.
The given name will not be checked so that a later loaded algorithm
will still get disabled.</P
></DD
><DT
>--throw-keyid</DT
><DD
><P
>Do not put the keyid into encrypted packets.  This option
hides the receiver of the message and is a countermeasure
against traffic analysis.  It may slow down the decryption
process because all available secret keys are tried.</P
></DD
><DT
>--not-dash-escaped</DT
><DD
><P
>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.</P
></DD
><DT
>--escape-from-lines</DT
><DD
><P
>Because some mailers change lines starting with "From "
to "&#60;From " it is good to handle such lines in a special
way when creating cleartext signatures. All other PGP
versions do it this way too. This option is not enabled
by default because it would violate rfc2440.</P
></DD
><DT
>--passphrase-fd <TT
CLASS="PARAMETER"
><I
>n</I
></TT
></DT
><DD
><P
>Read the passphrase from file descriptor <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>. If you use
0 for <TT
CLASS="PARAMETER"
><I
>n</I
></TT
>, the passphrase will be read from stdin.	This
can only be used if only one passphrase is supplied.
Don't use this option if you can avoid it.</P
></DD
><DT
>--rfc1991</DT
><DD
><P
>Try to be more RFC1991 (PGP 2.x) compliant.</P
></DD
><DT
>--openpgp</DT
><DD
><P
>Reset all packet, cipher and digest options to OpenPGP
behavior. Use this option to reset all previous
options like --rfc1991, --force-v3-sigs, --s2k-*,
--cipher-algo, --digest-algo and --compress-algo to
OpenPGP compliant values.  All PGP workarounds are also
disabled.</P
></DD
><DT
>--force-v3-sigs</DT
><DD
><P
>OpenPGP states that an implementation should generate
v4 signatures but PGP 5.x recognizes v4 signatures only
on key material.  This options forces v3 signatures for
signatures on data.</P
></DD
><DT
>--force-mdc</DT
><DD
><P
>Force the use of encryption with appended manipulation
code.  This is always used with the newer cipher (those
with a blocksize greater than 64 bit).
This option might not be implemented yet.</P
></DD
><DT
>--allow-non-selfsigned-uid</DT
><DD
><P
>Allow the import of keys with user IDs which are not self-signed.
This is only allows the import - key validation will fail and you
have to check the validity of the key my other means.  This hack is
needed for some German keys generated with pgp 2.6.3in. You should really
avoid using it, because OpenPGP has better mechanics to do separate signing
and encryption keys.</P
></DD
><DT
>--ignore-time-conflict</DT
><DD
><P
>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.</P
></DD
><DT
>--lock-once</DT
><DD
><P
>Lock the databases the first time a lock is requested
and do not release the lock until the process
terminates.</P
></DD
><DT
>--lock-multiple</DT
><DD
><P
>Release the locks every time a lock is no longer
needed. Use this to override a previous --lock-once
from a config file.</P
></DD
><DT
>--lock-never</DT
><DD
><P
>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 standalone
encryption system will probably use this.  Improper usage of this
option may lead to data and key corruption.</P
></DD
><DT
>--no-random-seed-file</DT
><DD
><P
>GnuPG uses a file to store it's internal random pool over invocations.
This makes random generation faster; however sometimes write operations
are not desired.  This option can be used to achive that with the cost of
slower random generation.</P
></DD
><DT
>--no-verbose</DT
><DD
><P
>Reset verbose level to 0.</P
></DD
><DT
>--no-greeting</DT
><DD
><P
>Suppress the initial copyright message but do not
enter batch mode.</P
></DD
><DT
>--no-secmem-warning</DT
><DD
><P
>Suppress the warning about "using insecure memory".</P
></DD
><DT
>--no-armor</DT
><DD
><P
>Assume the input data is not in ASCII armored format.</P
></DD
><DT
>--no-default-keyring</DT
><DD
><P
>Do not add the default keyrings to the list of
keyrings.</P
></DD
><DT
>--skip-verify</DT
><DD
><P
>Skip the signature verification step.  This may be
used to make the decryption faster if the signature
verification is not needed.</P
></DD
><DT
>--with-colons</DT
><DD
><P
>Print key listings delimited by colons.</P
></DD
><DT
>--with-key-data</DT
><DD
><P
>Print key listings delimited by colons and print the public key data.</P
></DD
><DT
>--with-fingerprint</DT
><DD
><P
>Same as the command --fingerprint but changes only the format of the output
and may be used together with another command.</P
></DD
><DT
>--fast-list-mode</DT
><DD
><P
>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 excact behaviour of this option may change
in future versions.</P
></DD
><DT
>--list-only</DT
><DD
><P
>Changes the behaviour of some commands.  This is like --dry-run but
different in some cases.  The semantic of this command may be extended in
the future.  Currently it does only skip the actual decryption pass and
therefore enables a fast listing of the encryption keys.</P
></DD
><DT
>--no-literal</DT
><DD
><P
>This is not for normal use.  Use the source to see for what it might be useful.</P
></DD
><DT
>--set-filesize</DT
><DD
><P
>This is not for normal use.  Use the source to see for what it might be useful.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1695"
></A
><H2
>How to specify a user ID</H2
><P
>There are different ways on how to specify a user ID to GnuPG;
here are some examples:
    </P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
></DT
><DD
><P
>Used to locate the default home directory.</P
></DD
><DT
>234567C4, 0F34E556E, 01347A56A, 0xAB123456</DT
><DD
><P
>Here the key ID is given in the usual short form.</P
></DD
><DT
>234AABBCC34567C4, 0F323456784E56EAB, 01AB3FED1347A5612, 0x234AABBCC34567C4</DT
><DD
><P
>Here the key ID is given in the long form as used by OpenPGP.</P
></DD
><DT
>1234343434343434C434343434343434, 123434343434343C3434343434343734349A3434, 0E12343434343434343434EAB3484343434343434, 0xE12343434343434343434EAB3484343434343434</DT
><DD
><P
>The best way to specify a key ID is by using the fingerprint of
the key.  This avoids any ambiguities in case that there are duplicated
key IDs (which are really rare for the long key IDs).</P
></DD
><DT
>=Heinrich Heine &lt;heinrichh@uni-duesseldorf.de&gt;</DT
><DD
><P
>Using an exact to match string.  The equal sign indicates this.</P
></DD
><DT
>&lt;heinrichh@uni-duesseldorf.de&gt;</DT
><DD
><P
>Using the email address part which must match exactly.	The left angle bracket
indicates this email address mode.</P
></DD
><DT
>+Heinrich Heine duesseldorf</DT
><DD
><P
>All words must match exactly (not case sensitive) but can appear in
any order in the user ID.  Words are any sequences of letters,
digits, the underscore and all characters with bit 7 set.</P
></DD
><DT
>#34</DT
><DD
><P
>Using the Local ID.  This is a very low level method and should
only be used by applications which really need it.  The hash character
indicates this method.	An application should not assume that this is
only a number.</P
></DD
><DT
>Heine, *Heine</DT
><DD
><P
>By case insensitive substring matching.  This is the default mode but
applications may want to explicitely indicate this by putting the asterisk
in front.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1745"
></A
><H2
>RETURN VALUE</H2
><P
>The program returns 0 if everything was fine, 1 if at least
a signature was bad, and other error codes for fatal errors.
    </P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1748"
></A
><H2
>EXAMPLES</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>gpg -se -r <TT
CLASS="PARAMETER"
><I
>Bob</I
></TT
> <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>sign and encrypt for user Bob</P
></DD
><DT
>gpg --clearsign <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>make a clear text signature</P
></DD
><DT
>gpg -sb  <TT
CLASS="PARAMETER"
><I
>file</I
></TT
></DT
><DD
><P
>make a detached signature</P
></DD
><DT
>gpg --list-keys  <TT
CLASS="PARAMETER"
><I
>user_ID</I
></TT
></DT
><DD
><P
>show keys</P
></DD
><DT
>gpg --fingerprint  <TT
CLASS="PARAMETER"
><I
>user_ID</I
></TT
></DT
><DD
><P
>show fingerprint</P
></DD
><DT
>gpg --verify  <TT
CLASS="PARAMETER"
><I
>pgpfile</I
></TT
>, gpg --verify  <TT
CLASS="PARAMETER"
><I
>sigfile</I
></TT
> [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>]</DT
><DD
><P
>Verify the signature of the file but do not output the data. The second form
is used for detached signatures, where <TT
CLASS="PARAMETER"
><I
>sigfile</I
></TT
> is the detached
signature (either ASCII armored of binary) and [<SPAN
CLASS="OPTIONAL"
><TT
CLASS="PARAMETER"
><I
>files</I
></TT
></SPAN
>] 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
<TT
CLASS="PARAMETER"
><I
>sigfile</I
></TT
> or by asking the user for the filename.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1790"
></A
><H2
>ENVIRONMENT</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>HOME</DT
><DD
><P
>Used to locate the default home directory.</P
></DD
><DT
>GNUPGHOME</DT
><DD
><P
>If set directory used instead of "~/.gnupg".</P
></DD
><DT
>http_proxy</DT
><DD
><P
>Only honored when the option --honor-http-proxy is set.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1805"
></A
><H2
>FILES</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>~/.gnupg/secring.gpg</DT
><DD
><P
>The secret keyring</P
></DD
><DT
>~/.gnupg/secring.gpg.lock</DT
><DD
><P
>and the lock file</P
></DD
><DT
>~/.gnupg/pubring.gpg</DT
><DD
><P
>The public keyring</P
></DD
><DT
>~/.gnupg/pubring.gpg.lock</DT
><DD
><P
>and the lock file</P
></DD
><DT
>~/.gnupg/trustdb.gpg</DT
><DD
><P
>The trust database</P
></DD
><DT
>~/.gnupg/trustdb.gpg.lock</DT
><DD
><P
>and the lock file</P
></DD
><DT
>~/.gnupg/random_seed</DT
><DD
><P
>used to preserve the internal random pool</P
></DD
><DT
>~/.gnupg/options</DT
><DD
><P
>May contain options</P
></DD
><DT
>/usr[/local]/share/gnupg/options.skel</DT
><DD
><P
>Skeleton options file</P
></DD
><DT
>/usr[/local]/lib/gnupg/</DT
><DD
><P
>Default location for extensions</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1848"
></A
><H2
>WARNINGS</H2
><P
>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.</P
><P
>Keep in mind that, if this program is used over a network (telnet), it
is *very* easy to spy out your passphrase!</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN1852"
></A
><H2
>BUGS</H2
><P
>On many 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 to disk. If you get no
warning message about insecure memory 3our operating system supports
locking without being root. The program drops root privileges as soon
as locked memory is allocated.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="a925.htm"
ACCESSKEY="P"
>Zurück</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="book1.htm"
ACCESSKEY="H"
>Zum Anfang</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="a1855.htm"
ACCESSKEY="N"
>Weiter</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Referenz</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="a925.htm"
ACCESSKEY="U"
>Nach oben</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Glossar</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
gnupg-doc 2003.04.06+dak1-1ubuntu1 / usr / share / doc / gnupg-doc / GNU_Privacy_Handbook / de / html / r929.htm
