2008-01-10 03:03:15 +00:00
|
|
|
@c Copyright (C) 2004, 2008 Free Software Foundation, Inc.
|
2004-09-29 11:04:30 +00:00
|
|
|
@c This is part of the GnuPG manual.
|
|
|
|
@c For copying conditions, see the file GnuPG.texi.
|
|
|
|
|
2015-06-09 21:29:15 +02:00
|
|
|
@include defs.inc
|
|
|
|
|
2004-09-29 11:04:30 +00:00
|
|
|
@node Helper Tools
|
|
|
|
@chapter Helper Tools
|
|
|
|
|
|
|
|
GnuPG comes with a couple of smaller tools:
|
|
|
|
|
|
|
|
@menu
|
|
|
|
* watchgnupg:: Read logs from a socket.
|
2006-08-22 14:26:35 +00:00
|
|
|
* gpgv:: Verify OpenPGP signatures.
|
2004-09-29 23:06:02 +00:00
|
|
|
* addgnupghome:: Create .gnupg home directories.
|
|
|
|
* gpgconf:: Modify .gnupg home directories.
|
2007-03-07 20:55:14 +00:00
|
|
|
* applygnupgdefaults:: Run gpgconf for all users.
|
2004-12-21 19:05:15 +00:00
|
|
|
* gpg-preset-passphrase:: Put a passphrase into the cache.
|
2005-02-24 17:36:11 +00:00
|
|
|
* gpg-connect-agent:: Communicate with a running agent.
|
2010-06-10 10:39:44 +00:00
|
|
|
* dirmngr-client:: How to use the Dirmngr client tool.
|
2005-12-16 15:52:48 +00:00
|
|
|
* gpgparsemail:: Parse a mail message into an annotated format
|
2005-04-27 13:39:16 +00:00
|
|
|
* symcryptrun:: Call a simple symmetric encryption tool.
|
2017-11-15 10:17:17 +01:00
|
|
|
* gpgtar:: Encrypt or sign files into an archive.
|
2004-09-29 11:04:30 +00:00
|
|
|
@end menu
|
|
|
|
|
2004-09-30 08:38:32 +00:00
|
|
|
@c
|
2004-12-21 19:05:15 +00:00
|
|
|
@c WATCHGNUPG
|
2004-09-30 08:38:32 +00:00
|
|
|
@c
|
2005-09-06 18:42:13 +00:00
|
|
|
@manpage watchgnupg.1
|
2004-09-29 11:04:30 +00:00
|
|
|
@node watchgnupg
|
|
|
|
@section Read logs from a socket
|
2005-09-06 18:42:13 +00:00
|
|
|
@ifset manverb
|
2006-08-17 19:58:28 +00:00
|
|
|
.B watchgnupg
|
|
|
|
\- Read and print logs from a socket
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B watchgnupg
|
|
|
|
.RB [ \-\-force ]
|
|
|
|
.RB [ \-\-verbose ]
|
|
|
|
.I socketname
|
2005-09-06 18:42:13 +00:00
|
|
|
@end ifset
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect description
|
2010-08-18 19:25:15 +00:00
|
|
|
Most of the main utilities are able to write their log files to a Unix
|
|
|
|
Domain socket if configured that way. @command{watchgnupg} is a simple
|
|
|
|
listener for such a socket. It ameliorates the output with a time stamp
|
|
|
|
and makes sure that long lines are not interspersed with log output from
|
|
|
|
other utilities. This tool is not available for Windows.
|
|
|
|
|
2004-09-29 11:04:30 +00:00
|
|
|
|
|
|
|
@noindent
|
2004-09-30 08:38:32 +00:00
|
|
|
@command{watchgnupg} is commonly invoked as
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@example
|
2017-01-09 08:54:45 +01:00
|
|
|
watchgnupg --force $(gpgconf --list-dirs socketdir)/S.log
|
2005-09-06 18:42:13 +00:00
|
|
|
@end example
|
|
|
|
@manpause
|
2004-09-29 11:04:30 +00:00
|
|
|
|
|
|
|
@noindent
|
2017-01-09 08:54:45 +01:00
|
|
|
This starts it on the current terminal for listening on the standard
|
|
|
|
logging socket (which is either @file{~/.gnupg/S.log} or
|
|
|
|
@file{/var/run/user/UID/gnupg/S.log}).
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2006-08-17 19:58:28 +00:00
|
|
|
@mansect options
|
2004-09-29 11:04:30 +00:00
|
|
|
@noindent
|
2004-09-30 08:38:32 +00:00
|
|
|
@command{watchgnupg} understands these options:
|
2004-09-29 11:04:30 +00:00
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
|
2011-02-23 10:15:34 +01:00
|
|
|
@item --force
|
2004-09-29 11:04:30 +00:00
|
|
|
@opindex force
|
|
|
|
Delete an already existing socket file.
|
|
|
|
|
2010-12-02 14:10:44 +00:00
|
|
|
@anchor{option watchgnupg --tcp}
|
2010-08-18 19:25:15 +00:00
|
|
|
@item --tcp @var{n}
|
|
|
|
Instead of reading from a local socket, listen for connects on TCP port
|
|
|
|
@var{n}.
|
|
|
|
|
2017-01-09 08:54:45 +01:00
|
|
|
@item --time-only
|
|
|
|
@opindex time-only
|
|
|
|
Do not print the date part of the timestamp.
|
|
|
|
|
2004-09-29 11:04:30 +00:00
|
|
|
@item --verbose
|
|
|
|
@opindex verbose
|
|
|
|
Enable extra informational output.
|
|
|
|
|
|
|
|
@item --version
|
|
|
|
@opindex version
|
2008-05-06 11:05:52 +00:00
|
|
|
Print version of the program and exit.
|
2004-09-29 11:04:30 +00:00
|
|
|
|
|
|
|
@item --help
|
|
|
|
@opindex help
|
2008-05-06 11:05:52 +00:00
|
|
|
Display a brief help page and exit.
|
2004-09-29 11:04:30 +00:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2010-08-18 19:25:15 +00:00
|
|
|
@noindent
|
|
|
|
@mansect examples
|
|
|
|
@chapheading Examples
|
|
|
|
|
|
|
|
@example
|
2017-01-09 08:54:45 +01:00
|
|
|
$ watchgnupg --force --time-only $(gpgconf --list-dirs socketdir)/S.log
|
2010-08-18 19:25:15 +00:00
|
|
|
@end example
|
|
|
|
|
|
|
|
This waits for connections on the local socket
|
2017-01-09 08:54:45 +01:00
|
|
|
(e.g. @file{/home/foo/.gnupg/S.log}) and shows all log entries. To
|
|
|
|
make this work the option @option{log-file} needs to be used with all
|
|
|
|
modules which logs are to be shown. The suggested entry for the
|
|
|
|
configuration files is:
|
2010-08-18 19:25:15 +00:00
|
|
|
|
|
|
|
@example
|
2017-01-09 08:54:45 +01:00
|
|
|
log-file socket://
|
2010-08-18 19:25:15 +00:00
|
|
|
@end example
|
|
|
|
|
2017-01-09 08:54:45 +01:00
|
|
|
If the default socket as given above and returned by "echo $(gpgconf
|
|
|
|
--list-dirs socketdir)/S.log" is not desired an arbitrary socket name
|
|
|
|
can be specified, for example @file{socket:///home/foo/bar/mysocket}.
|
2010-08-18 19:25:15 +00:00
|
|
|
For debugging purposes it is also possible to do remote logging. Take
|
|
|
|
care if you use this feature because the information is send in the
|
|
|
|
clear over the network. Use this syntax in the conf files:
|
|
|
|
|
|
|
|
@example
|
|
|
|
log-file tcp://192.168.1.1:4711
|
|
|
|
@end example
|
|
|
|
|
2017-01-09 08:54:45 +01:00
|
|
|
You may use any port and not just 4711 as shown above; only IP
|
|
|
|
addresses are supported (v4 and v6) and no host names. You need to
|
|
|
|
start @command{watchgnupg} with the @option{tcp} option. Note that
|
|
|
|
under Windows the registry entry
|
|
|
|
@var{HKCU\Software\GNU\GnuPG:DefaultLogFile} can be used to change the
|
|
|
|
default log output from @code{stderr} to whatever is given by that
|
|
|
|
entry. However the only useful entry is a TCP name for remote
|
|
|
|
debugging.
|
2010-08-18 19:25:15 +00:00
|
|
|
|
|
|
|
|
2006-08-17 19:58:28 +00:00
|
|
|
@mansect see also
|
2007-03-07 20:55:14 +00:00
|
|
|
@ifset isman
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg}(1),
|
|
|
|
@command{gpgsm}(1),
|
|
|
|
@command{gpg-agent}(1),
|
2006-08-17 19:58:28 +00:00
|
|
|
@command{scdaemon}(1)
|
2007-03-07 20:55:14 +00:00
|
|
|
@end ifset
|
2006-08-17 19:58:28 +00:00
|
|
|
@include see-also-note.texi
|
|
|
|
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2006-08-22 14:26:35 +00:00
|
|
|
@c
|
|
|
|
@c GPGV
|
|
|
|
@c
|
2006-12-06 10:16:50 +00:00
|
|
|
@include gpgv.texi
|
2006-08-22 14:26:35 +00:00
|
|
|
|
|
|
|
|
2004-09-30 08:38:32 +00:00
|
|
|
@c
|
|
|
|
@c ADDGNUPGHOME
|
|
|
|
@c
|
2005-09-06 18:42:13 +00:00
|
|
|
@manpage addgnupghome.8
|
2004-09-29 11:04:30 +00:00
|
|
|
@node addgnupghome
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Create .gnupg home directories
|
2005-09-06 18:42:13 +00:00
|
|
|
@ifset manverb
|
2011-02-23 10:15:34 +01:00
|
|
|
.B addgnupghome
|
2006-08-17 19:58:28 +00:00
|
|
|
\- Create .gnupg home directories
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B addgnupghome
|
|
|
|
.I account_1
|
|
|
|
.IR account_2 ... account_n
|
2005-09-06 18:42:13 +00:00
|
|
|
@end ifset
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect description
|
2004-09-29 11:04:30 +00:00
|
|
|
If GnuPG is installed on a system with existing user accounts, it is
|
|
|
|
sometimes required to populate the GnuPG home directory with existing
|
|
|
|
files. Especially a @file{trustlist.txt} and a keybox with some
|
2016-03-04 15:20:47 +00:00
|
|
|
initial certificates are often desired. This script helps to do this
|
2004-09-29 11:04:30 +00:00
|
|
|
by copying all files from @file{/etc/skel/.gnupg} to the home
|
|
|
|
directories of the accounts given on the command line. It takes care
|
|
|
|
not to overwrite existing GnuPG home directories.
|
|
|
|
|
|
|
|
@noindent
|
2004-09-30 08:38:32 +00:00
|
|
|
@command{addgnupghome} is invoked by root as:
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@example
|
|
|
|
addgnupghome account1 account2 ... accountn
|
|
|
|
@end example
|
2004-09-29 11:04:30 +00:00
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
|
2004-09-30 08:38:32 +00:00
|
|
|
@c
|
|
|
|
@c GPGCONF
|
|
|
|
@c
|
2005-09-06 18:42:13 +00:00
|
|
|
@manpage gpgconf.1
|
2004-09-29 23:06:02 +00:00
|
|
|
@node gpgconf
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Modify .gnupg home directories
|
2005-09-06 18:42:13 +00:00
|
|
|
@ifset manverb
|
2006-08-17 19:58:28 +00:00
|
|
|
.B gpgconf
|
|
|
|
\- Modify .gnupg home directories
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B gpgconf
|
|
|
|
.RI [ options ]
|
2006-08-18 13:05:39 +00:00
|
|
|
.B \-\-list-components
|
2006-08-17 19:58:28 +00:00
|
|
|
.br
|
|
|
|
.B gpgconf
|
|
|
|
.RI [ options ]
|
2011-02-23 10:15:34 +01:00
|
|
|
.B \-\-list-options
|
2006-08-18 13:05:39 +00:00
|
|
|
.I component
|
2006-08-17 19:58:28 +00:00
|
|
|
.br
|
|
|
|
.B gpgconf
|
|
|
|
.RI [ options ]
|
2006-08-18 13:05:39 +00:00
|
|
|
.B \-\-change-options
|
|
|
|
.I component
|
2005-09-06 18:42:13 +00:00
|
|
|
@end ifset
|
2004-09-29 23:06:02 +00:00
|
|
|
|
2006-08-17 19:58:28 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect description
|
2004-09-29 23:06:02 +00:00
|
|
|
The @command{gpgconf} is a utility to automatically and reasonable
|
|
|
|
safely query and modify configuration files in the @file{.gnupg} home
|
|
|
|
directory. It is designed not to be invoked manually by the user, but
|
|
|
|
automatically by graphical user interfaces (GUI).@footnote{Please note
|
|
|
|
that currently no locking is done, so concurrent access should be
|
|
|
|
avoided. There are some precautions to avoid corruption with
|
|
|
|
concurrent usage, but results may be inconsistent and some changes may
|
|
|
|
get lost. The stateless design makes it difficult to provide more
|
|
|
|
guarantees.}
|
|
|
|
|
|
|
|
@command{gpgconf} provides access to the configuration of one or more
|
|
|
|
components of the GnuPG system. These components correspond more or
|
2016-03-04 16:27:21 +00:00
|
|
|
less to the programs that exist in the GnuPG framework, like GPG,
|
2004-09-29 23:06:02 +00:00
|
|
|
GPGSM, DirMngr, etc. But this is not a strict one-to-one
|
|
|
|
relationship. Not all configuration options are available through
|
|
|
|
@command{gpgconf}. @command{gpgconf} provides a generic and abstract
|
|
|
|
method to access the most important configuration options that can
|
|
|
|
feasibly be controlled via such a mechanism.
|
|
|
|
|
|
|
|
@command{gpgconf} can be used to gather and change the options
|
|
|
|
available in each component, and can also provide their default
|
|
|
|
values. @command{gpgconf} will give detailed type information that
|
|
|
|
can be used to restrict the user's input without making an attempt to
|
|
|
|
commit the changes.
|
|
|
|
|
|
|
|
@command{gpgconf} provides the backend of a configuration editor. The
|
|
|
|
configuration editor would usually be a graphical user interface
|
More cleanup of "allow to".
* README, agent/command.c, agent/keyformat.txt, common/i18n.c,
common/iobuf.c, common/keyserver.h, dirmngr/cdblib.c,
dirmngr/ldap-wrapper.c, doc/DETAILS, doc/TRANSLATE,
doc/announce-2.1.txt, doc/gpg.texi, doc/gpgsm.texi,
doc/scdaemon.texi, doc/tools.texi, doc/whats-new-in-2.1.txt,
g10/export.c, g10/getkey.c, g10/import.c, g10/keyedit.c, m4/ksba.m4,
m4/libgcrypt.m4, m4/ntbtls.m4, po/ca.po, po/cs.po, po/da.po,
po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/fi.po,
po/fr.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po,
po/nb.po, po/pl.po, po/pt.po, po/ro.po, po/ru.po, po/sk.po,
po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po,
scd/app-p15.c, scd/ccid-driver.c, scd/command.c, sm/gpgsm.c,
sm/sign.c, tools/gpgconf-comp.c, tools/gpgtar.h: replace "Allow to"
with clearer text.
In standard English, the normal construction is "${XXX} allows ${YYY}
to" -- that is, the subject (${XXX}) of the sentence is allowing the
object (${YYY}) to do something. When the object is missing, the
phrasing sounds awkward, even if the object is implied by context.
There's almost always a better construction that isn't as awkward.
These changes should make the language a bit clearer.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
2016-08-01 22:19:17 -04:00
|
|
|
program that displays the current options, their default
|
2004-09-29 23:06:02 +00:00
|
|
|
values, and allows the user to make changes to the options. These
|
|
|
|
changes can then be made active with @command{gpgconf} again. Such a
|
|
|
|
program that uses @command{gpgconf} in this way will be called GUI
|
|
|
|
throughout this section.
|
|
|
|
|
|
|
|
@menu
|
2007-10-23 18:13:27 +00:00
|
|
|
* Invoking gpgconf:: List of all commands and options.
|
|
|
|
* Format conventions:: Formatting conventions relevant for all commands.
|
|
|
|
* Listing components:: List all gpgconf components.
|
2016-03-04 15:20:47 +00:00
|
|
|
* Checking programs:: Check all programs known to gpgconf.
|
2007-10-23 18:13:27 +00:00
|
|
|
* Listing options:: List all options of a component.
|
|
|
|
* Changing options:: Changing options of a component.
|
|
|
|
* Listing global options:: List all global options.
|
2016-11-02 17:54:32 +01:00
|
|
|
* Querying versions:: Get and compare software versions.
|
2007-10-23 18:13:27 +00:00
|
|
|
* Files used by gpgconf:: What files are used by gpgconf.
|
2004-09-29 23:06:02 +00:00
|
|
|
@end menu
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpause
|
2004-09-29 23:06:02 +00:00
|
|
|
@node Invoking gpgconf
|
|
|
|
@subsection Invoking gpgconf
|
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect commands
|
2004-09-29 23:06:02 +00:00
|
|
|
One of the following commands must be given:
|
|
|
|
|
|
|
|
@table @gnupgtabopt
|
2005-09-06 18:42:13 +00:00
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
@item --list-components
|
|
|
|
List all components. This is the default command used if none is
|
|
|
|
specified.
|
|
|
|
|
2007-08-29 09:51:37 +00:00
|
|
|
@item --check-programs
|
|
|
|
List all available backend programs and test whether they are runnable.
|
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
@item --list-options @var{component}
|
|
|
|
List all options of the component @var{component}.
|
|
|
|
|
|
|
|
@item --change-options @var{component}
|
|
|
|
Change the options of the component @var{component}.
|
2007-03-06 20:44:41 +00:00
|
|
|
|
2008-05-19 22:46:41 +00:00
|
|
|
@item --check-options @var{component}
|
|
|
|
Check the options for the component @var{component}.
|
|
|
|
|
2016-12-16 16:00:15 +01:00
|
|
|
@item --apply-profile @var{file}
|
|
|
|
Apply the configuration settings listed in @var{file} to the
|
|
|
|
configuration files. If @var{file} has no suffix and no slashes the
|
|
|
|
command first tries to read a file with the suffix @code{.prf} from
|
2018-06-06 17:25:51 +02:00
|
|
|
the data directory (@code{gpgconf --list-dirs datadir}) before it
|
2016-12-16 16:00:15 +01:00
|
|
|
reads the file verbatim. A profile is divided into sections using the
|
|
|
|
bracketed component name. Each section then lists the option which
|
|
|
|
shall go into the respective configuration file.
|
|
|
|
|
2007-03-06 20:44:41 +00:00
|
|
|
@item --apply-defaults
|
|
|
|
Update all configuration files with values taken from the global
|
|
|
|
configuration file (usually @file{/etc/gnupg/gpgconf.conf}).
|
|
|
|
|
2016-07-11 13:05:37 +02:00
|
|
|
@item --list-dirs [@var{names}]
|
2008-05-26 13:43:20 +00:00
|
|
|
Lists the directories used by @command{gpgconf}. One directory is
|
2009-01-20 19:24:24 +00:00
|
|
|
listed per line, and each line consists of a colon-separated list where
|
|
|
|
the first field names the directory type (for example @code{sysconfdir})
|
|
|
|
and the second field contains the percent-escaped directory. Although
|
|
|
|
they are not directories, the socket file names used by
|
|
|
|
@command{gpg-agent} and @command{dirmngr} are printed as well. Note
|
|
|
|
that the socket file names and the @code{homedir} lines are the default
|
2016-07-11 13:05:37 +02:00
|
|
|
names and they may be overridden by command line switches. If
|
|
|
|
@var{names} are given only the directories or file names specified by
|
|
|
|
the list names are printed without any escaping.
|
2008-05-26 13:43:20 +00:00
|
|
|
|
2007-10-23 18:13:27 +00:00
|
|
|
@item --list-config [@var{filename}]
|
|
|
|
List the global configuration file in a colon separated format. If
|
|
|
|
@var{filename} is given, check that file instead.
|
|
|
|
|
2007-03-06 20:44:41 +00:00
|
|
|
@item --check-config [@var{filename}]
|
2007-06-06 18:12:30 +00:00
|
|
|
Run a syntax check on the global configuration file. If @var{filename}
|
2007-03-06 20:44:41 +00:00
|
|
|
is given, check that file instead.
|
|
|
|
|
2016-11-02 17:54:32 +01:00
|
|
|
|
|
|
|
@item --query-swdb @var{package_name} [@var{version_string}]
|
|
|
|
Returns the current version for @var{package_name} and if
|
|
|
|
@var{version_string} is given also an indicator on whether an update
|
2016-11-17 10:07:11 +01:00
|
|
|
is available. The actual file with the software version is
|
|
|
|
automatically downloaded and checked by @command{dirmngr}.
|
|
|
|
@command{dirmngr} uses a thresholds to avoid download the file too
|
|
|
|
often and it does this by default only if it can be done via Tor. To
|
|
|
|
force an update of that file this command can be used:
|
|
|
|
|
|
|
|
@example
|
|
|
|
gpg-connect-agent --dirmngr 'loadswdb --force' /bye
|
|
|
|
@end example
|
2016-11-02 17:54:32 +01:00
|
|
|
|
|
|
|
|
2010-10-14 16:34:31 +00:00
|
|
|
@item --reload [@var{component}]
|
|
|
|
@opindex reload
|
2017-01-18 10:01:55 +01:00
|
|
|
Reload all or the given component. This is basically the same as
|
|
|
|
sending a SIGHUP to the component. Components which don't support
|
|
|
|
reloading are ignored. Without @var{component} or by using "all" for
|
|
|
|
@var{component} all components which are daemons are reloaded.
|
2010-10-14 16:34:31 +00:00
|
|
|
|
2014-04-08 15:55:51 +02:00
|
|
|
@item --launch [@var{component}]
|
|
|
|
@opindex launch
|
|
|
|
If the @var{component} is not already running, start it.
|
|
|
|
@command{component} must be a daemon. This is in general not required
|
|
|
|
because the system starts these daemons as needed. However, external
|
|
|
|
software making direct use of @command{gpg-agent} or @command{dirmngr}
|
2017-01-18 10:01:55 +01:00
|
|
|
may use this command to ensure that they are started. Using "all" for
|
|
|
|
@var{component} launches all components which are daemons.
|
2014-04-08 15:55:51 +02:00
|
|
|
|
2011-02-23 10:15:34 +01:00
|
|
|
@item --kill [@var{component}]
|
|
|
|
@opindex kill
|
2019-05-10 12:39:45 -04:00
|
|
|
Kill the given component that runs as a daemon, including
|
|
|
|
@command{gpg-agent}, @command{dirmngr}, and @command{scdaemon}. A
|
|
|
|
@command{component} which does not run as a daemon will be ignored.
|
|
|
|
Using "all" for @var{component} kills all components running as
|
|
|
|
daemons. Note that as of now reload and kill have the same effect for
|
|
|
|
@command{scdaemon}.
|
2011-02-23 10:15:34 +01:00
|
|
|
|
2016-06-08 14:04:47 +02:00
|
|
|
@item --create-socketdir
|
|
|
|
@opindex create-socketdir
|
|
|
|
Create a directory for sockets below /run/user or /var/run/user. This
|
|
|
|
is command is only required if a non default home directory is used
|
|
|
|
and the /run based sockets shall be used. For the default home
|
|
|
|
directory GnUPG creates a directory on the fly.
|
|
|
|
|
|
|
|
@item --remove-socketdir
|
|
|
|
@opindex remove-socketdir
|
|
|
|
Remove a directory created with command @option{--create-socketdir}.
|
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
2007-03-06 20:44:41 +00:00
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect options
|
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
The following options may be used:
|
|
|
|
|
|
|
|
@table @gnupgtabopt
|
2015-01-22 17:49:55 +01:00
|
|
|
|
|
|
|
@item -o @var{file}
|
|
|
|
@itemx --output @var{file}
|
|
|
|
Write output to @var{file}. Default is to write to stdout.
|
2004-09-29 23:06:02 +00:00
|
|
|
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
Outputs additional information while running. Specifically, this
|
|
|
|
extends numerical field values by human-readable descriptions.
|
|
|
|
|
2015-01-22 17:49:55 +01:00
|
|
|
@item -q
|
|
|
|
@itemx --quiet
|
|
|
|
@opindex quiet
|
|
|
|
Try to be as quiet as possible.
|
2019-05-15 08:50:15 +02:00
|
|
|
|
|
|
|
@include opt-homedir.texi
|
2015-01-22 17:49:55 +01:00
|
|
|
|
2008-05-19 22:46:41 +00:00
|
|
|
@item -n
|
|
|
|
@itemx --dry-run
|
|
|
|
Do not actually change anything. This is currently only implemented
|
|
|
|
for @code{--change-options} and can be used for testing purposes.
|
2004-09-29 23:06:02 +00:00
|
|
|
|
|
|
|
@item -r
|
|
|
|
@itemx --runtime
|
|
|
|
Only used together with @code{--change-options}. If one of the
|
|
|
|
modified options can be changed in a running daemon process, signal
|
|
|
|
the running daemon to ask it to reparse its configuration file after
|
|
|
|
changing.
|
|
|
|
|
|
|
|
This means that the changes will take effect at run-time, as far as
|
|
|
|
this is possible. Otherwise, they will take effect at the next start
|
|
|
|
of the respective backend programs.
|
2017-12-18 17:46:05 +01:00
|
|
|
|
|
|
|
@item --status-fd @var{n}
|
|
|
|
@opindex status-fd
|
|
|
|
Write special status strings to the file descriptor @var{n}. This
|
|
|
|
program returns the status messages SUCCESS or FAILURE which are
|
|
|
|
helpful when the caller uses a double fork approach and can't easily
|
|
|
|
get the return code of the process.
|
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@manpause
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
|
|
@node Format conventions
|
|
|
|
@subsection Format conventions
|
|
|
|
|
|
|
|
Some lines in the output of @command{gpgconf} contain a list of
|
|
|
|
colon-separated fields. The following conventions apply:
|
|
|
|
|
|
|
|
@itemize @bullet
|
|
|
|
@item
|
|
|
|
The GUI program is required to strip off trailing newline and/or
|
|
|
|
carriage return characters from the output.
|
|
|
|
|
|
|
|
@item
|
|
|
|
@command{gpgconf} will never leave out fields. If a certain version
|
|
|
|
provides a certain field, this field will always be present in all
|
|
|
|
@command{gpgconf} versions from that time on.
|
|
|
|
|
|
|
|
@item
|
|
|
|
Future versions of @command{gpgconf} might append fields to the list.
|
|
|
|
New fields will always be separated from the previously last field by
|
|
|
|
a colon separator. The GUI should be prepared to parse the last field
|
|
|
|
it knows about up until a colon or end of line.
|
|
|
|
|
|
|
|
@item
|
|
|
|
Not all fields are defined under all conditions. You are required to
|
|
|
|
ignore the content of undefined fields.
|
|
|
|
@end itemize
|
|
|
|
|
|
|
|
There are several standard types for the content of a field:
|
|
|
|
|
|
|
|
@table @asis
|
|
|
|
@item verbatim
|
|
|
|
Some fields contain strings that are not escaped in any way. Such
|
|
|
|
fields are described to be used @emph{verbatim}. These fields will
|
|
|
|
never contain a colon character (for obvious reasons). No de-escaping
|
|
|
|
or other formatting is required to use the field content. This is for
|
|
|
|
easy parsing of the output, when it is known that the content can
|
|
|
|
never contain any special characters.
|
|
|
|
|
|
|
|
@item percent-escaped
|
|
|
|
Some fields contain strings that are described to be
|
|
|
|
@emph{percent-escaped}. Such strings need to be de-escaped before
|
|
|
|
their content can be presented to the user. A percent-escaped string
|
2009-07-22 13:33:46 +00:00
|
|
|
is de-escaped by replacing all occurrences of @code{%XY} by the byte
|
2004-09-29 23:06:02 +00:00
|
|
|
that has the hexadecimal value @code{XY}. @code{X} and @code{Y} are
|
|
|
|
from the set @code{0-9a-f}.
|
|
|
|
|
2016-03-04 16:00:51 +00:00
|
|
|
@item localized
|
|
|
|
Some fields contain strings that are described to be @emph{localized}.
|
2004-09-29 23:06:02 +00:00
|
|
|
Such strings are translated to the active language and formatted in
|
|
|
|
the active character set.
|
|
|
|
|
|
|
|
@item @w{unsigned number}
|
|
|
|
Some fields contain an @emph{unsigned number}. This number will
|
|
|
|
always fit into a 32-bit unsigned integer variable. The number may be
|
|
|
|
followed by a space, followed by a human readable description of that
|
|
|
|
value (if the verbose option is used). You should ignore everything
|
|
|
|
in the field that follows the number.
|
|
|
|
|
|
|
|
@item @w{signed number}
|
|
|
|
Some fields contain a @emph{signed number}. This number will always
|
|
|
|
fit into a 32-bit signed integer variable. The number may be followed
|
|
|
|
by a space, followed by a human readable description of that value (if
|
|
|
|
the verbose option is used). You should ignore everything in the
|
|
|
|
field that follows the number.
|
|
|
|
|
2007-08-29 09:51:37 +00:00
|
|
|
@item @w{boolean value}
|
|
|
|
Some fields contain a @emph{boolean value}. This is a number with
|
|
|
|
either the value 0 or 1. The number may be followed by a space,
|
|
|
|
followed by a human readable description of that value (if the verbose
|
|
|
|
option is used). You should ignore everything in the field that follows
|
|
|
|
the number; checking just the first character is sufficient in this
|
|
|
|
case.
|
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
@item option
|
|
|
|
Some fields contain an @emph{option} argument. The format of an
|
|
|
|
option argument depends on the type of the option and on some flags:
|
|
|
|
|
|
|
|
@table @asis
|
|
|
|
@item no argument
|
|
|
|
The simplest case is that the option does not take an argument at all
|
|
|
|
(@var{type} @code{0}). Then the option argument is an unsigned number
|
|
|
|
that specifies how often the option occurs. If the @code{list} flag
|
|
|
|
is not set, then the only valid number is @code{1}. Options that do
|
|
|
|
not take an argument never have the @code{default} or @code{optional
|
|
|
|
arg} flag set.
|
|
|
|
|
|
|
|
@item number
|
|
|
|
If the option takes a number argument (@var{alt-type} is @code{2} or
|
|
|
|
@code{3}), and it can only occur once (@code{list} flag is not set),
|
|
|
|
then the option argument is either empty (only allowed if the argument
|
|
|
|
is optional), or it is a number. A number is a string that begins
|
|
|
|
with an optional minus character, followed by one or more digits. The
|
|
|
|
number must fit into an integer variable (unsigned or signed,
|
|
|
|
depending on @var{alt-type}).
|
|
|
|
|
|
|
|
@item number list
|
|
|
|
If the option takes a number argument and it can occur more than once,
|
|
|
|
then the option argument is either empty, or it is a comma-separated
|
|
|
|
list of numbers as described above.
|
|
|
|
|
|
|
|
@item string
|
|
|
|
If the option takes a string argument (@var{alt-type} is 1), and it
|
|
|
|
can only occur once (@code{list} flag is not set) then the option
|
|
|
|
argument is either empty (only allowed if the argument is optional),
|
|
|
|
or it starts with a double quote character (@code{"}) followed by a
|
|
|
|
percent-escaped string that is the argument value. Note that there is
|
|
|
|
only a leading double quote character, no trailing one. The double
|
|
|
|
quote character is only needed to be able to differentiate between no
|
|
|
|
value and the empty string as value.
|
|
|
|
|
|
|
|
@item string list
|
2016-03-04 16:27:21 +00:00
|
|
|
If the option takes a string argument and it can occur more than once,
|
2004-09-29 23:06:02 +00:00
|
|
|
then the option argument is either empty, or it is a comma-separated
|
|
|
|
list of string arguments as described above.
|
|
|
|
@end table
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The active language and character set are currently determined from
|
|
|
|
the locale environment of the @command{gpgconf} program.
|
|
|
|
|
|
|
|
@c FIXME: Document the active language and active character set. Allow
|
|
|
|
@c to change it via the command line?
|
|
|
|
|
|
|
|
|
2005-09-06 18:42:13 +00:00
|
|
|
@mansect usage
|
2004-09-29 23:06:02 +00:00
|
|
|
@node Listing components
|
|
|
|
@subsection Listing components
|
|
|
|
|
|
|
|
The command @code{--list-components} will list all components that can
|
|
|
|
be configured with @command{gpgconf}. Usually, one component will
|
|
|
|
correspond to one GnuPG-related program and contain the options of
|
2016-03-04 15:20:47 +00:00
|
|
|
that program's configuration file that can be modified using
|
2004-09-29 23:06:02 +00:00
|
|
|
@command{gpgconf}. However, this is not necessarily the case. A
|
|
|
|
component might also be a group of selected options from several
|
|
|
|
programs, or contain entirely virtual options that have a special
|
|
|
|
effect rather than changing exactly one option in one configuration
|
|
|
|
file.
|
|
|
|
|
|
|
|
A component is a set of configuration options that semantically belong
|
|
|
|
together. Furthermore, several changes to a component can be made in
|
|
|
|
an atomic way with a single operation. The GUI could for example
|
|
|
|
provide a menu with one entry for each component, or a window with one
|
|
|
|
tabulator sheet per component.
|
|
|
|
|
2016-03-04 16:27:21 +00:00
|
|
|
The command @code{--list-components} lists all available
|
2004-09-29 23:06:02 +00:00
|
|
|
components, one per line. The format of each line is:
|
|
|
|
|
2007-08-31 08:24:52 +00:00
|
|
|
@code{@var{name}:@var{description}:@var{pgmname}:}
|
2004-09-29 23:06:02 +00:00
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item name
|
|
|
|
This field contains a name tag of the component. The name tag is used
|
|
|
|
to specify the component in all communication with @command{gpgconf}.
|
|
|
|
The name tag is to be used @emph{verbatim}. It is thus not in any
|
|
|
|
escaped format.
|
|
|
|
|
|
|
|
@item description
|
|
|
|
The @emph{string} in this field contains a human-readable description
|
|
|
|
of the component. It can be displayed to the user of the GUI for
|
|
|
|
informational purposes. It is @emph{percent-escaped} and
|
|
|
|
@emph{localized}.
|
2007-08-31 08:24:52 +00:00
|
|
|
|
|
|
|
@item pgmname
|
|
|
|
The @emph{string} in this field contains the absolute name of the
|
|
|
|
program's file. It can be used to unambiguously invoke that program.
|
|
|
|
It is @emph{percent-escaped}.
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
Example:
|
|
|
|
@example
|
|
|
|
$ gpgconf --list-components
|
2007-08-31 08:24:52 +00:00
|
|
|
gpg:GPG for OpenPGP:/usr/local/bin/gpg2:
|
|
|
|
gpg-agent:GPG Agent:/usr/local/bin/gpg-agent:
|
|
|
|
scdaemon:Smartcard Daemon:/usr/local/bin/scdaemon:
|
|
|
|
gpgsm:GPG for S/MIME:/usr/local/bin/gpgsm:
|
|
|
|
dirmngr:Directory Manager:/usr/local/bin/dirmngr:
|
2004-09-29 23:06:02 +00:00
|
|
|
@end example
|
|
|
|
|
|
|
|
|
2007-08-29 09:51:37 +00:00
|
|
|
|
|
|
|
@node Checking programs
|
|
|
|
@subsection Checking programs
|
|
|
|
|
|
|
|
The command @code{--check-programs} is similar to
|
|
|
|
@code{--list-components} but works on backend programs and not on
|
2009-07-22 13:33:46 +00:00
|
|
|
components. It runs each program to test whether it is installed and
|
2007-08-29 09:51:37 +00:00
|
|
|
runnable. This also includes a syntax check of all config file options
|
|
|
|
of the program.
|
|
|
|
|
2016-03-04 16:27:21 +00:00
|
|
|
The command @code{--check-programs} lists all available
|
2007-08-29 09:51:37 +00:00
|
|
|
programs, one per line. The format of each line is:
|
|
|
|
|
2007-08-29 16:59:20 +00:00
|
|
|
@code{@var{name}:@var{description}:@var{pgmname}:@var{avail}:@var{okay}:@var{cfgfile}:@var{line}:@var{error}:}
|
2007-08-29 09:51:37 +00:00
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item name
|
|
|
|
This field contains a name tag of the program which is identical to the
|
|
|
|
name of the component. The name tag is to be used @emph{verbatim}. It
|
2007-08-29 16:59:20 +00:00
|
|
|
is thus not in any escaped format. This field may be empty to indicate
|
|
|
|
a continuation of error descriptions for the last name. The description
|
|
|
|
and pgmname fields are then also empty.
|
2007-08-29 09:51:37 +00:00
|
|
|
|
|
|
|
@item description
|
|
|
|
The @emph{string} in this field contains a human-readable description
|
|
|
|
of the component. It can be displayed to the user of the GUI for
|
|
|
|
informational purposes. It is @emph{percent-escaped} and
|
|
|
|
@emph{localized}.
|
|
|
|
|
2007-08-29 16:59:20 +00:00
|
|
|
@item pgmname
|
2007-08-29 09:51:37 +00:00
|
|
|
The @emph{string} in this field contains the absolute name of the
|
|
|
|
program's file. It can be used to unambiguously invoke that program.
|
|
|
|
It is @emph{percent-escaped}.
|
|
|
|
|
2007-08-29 16:59:20 +00:00
|
|
|
@item avail
|
2007-08-29 09:51:37 +00:00
|
|
|
The @emph{boolean value} in this field indicates whether the program is
|
|
|
|
installed and runnable.
|
|
|
|
|
2007-08-29 16:59:20 +00:00
|
|
|
@item okay
|
2007-08-29 09:51:37 +00:00
|
|
|
The @emph{boolean value} in this field indicates whether the program's
|
|
|
|
config file is syntactically okay.
|
|
|
|
|
2007-08-29 16:59:20 +00:00
|
|
|
@item cfgfile
|
2009-07-22 13:33:46 +00:00
|
|
|
If an error occurred in the configuration file (as indicated by a false
|
2007-08-29 16:59:20 +00:00
|
|
|
value in the field @code{okay}), this field has the name of the failing
|
|
|
|
configuration file. It is @emph{percent-escaped}.
|
|
|
|
|
|
|
|
@item line
|
2009-07-22 13:33:46 +00:00
|
|
|
If an error occurred in the configuration file, this field has the line
|
2011-02-23 10:15:34 +01:00
|
|
|
number of the failing statement in the configuration file.
|
2007-08-29 16:59:20 +00:00
|
|
|
It is an @emph{unsigned number}.
|
|
|
|
|
|
|
|
@item error
|
2009-07-22 13:33:46 +00:00
|
|
|
If an error occurred in the configuration file, this field has the error
|
2007-08-29 16:59:20 +00:00
|
|
|
text of the failing statement in the configuration file. It is
|
|
|
|
@emph{percent-escaped} and @emph{localized}.
|
|
|
|
|
2007-08-29 09:51:37 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
In the following example the @command{dirmngr} is not runnable and the
|
|
|
|
configuration file of @command{scdaemon} is not okay.
|
|
|
|
|
|
|
|
@example
|
|
|
|
$ gpgconf --check-programs
|
|
|
|
gpg:GPG for OpenPGP:/usr/local/bin/gpg2:1:1:
|
|
|
|
gpg-agent:GPG Agent:/usr/local/bin/gpg-agent:1:1:
|
|
|
|
scdaemon:Smartcard Daemon:/usr/local/bin/scdaemon:1:0:
|
|
|
|
gpgsm:GPG for S/MIME:/usr/local/bin/gpgsm:1:1:
|
|
|
|
dirmngr:Directory Manager:/usr/local/bin/dirmngr:0:0:
|
|
|
|
@end example
|
|
|
|
|
2008-05-19 22:46:41 +00:00
|
|
|
@noindent
|
|
|
|
The command @w{@code{--check-options @var{component}}} will verify the
|
|
|
|
configuration file in the same manner as @code{--check-programs}, but
|
|
|
|
only for the component @var{component}.
|
|
|
|
|
2007-08-29 09:51:37 +00:00
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
@node Listing options
|
|
|
|
@subsection Listing options
|
|
|
|
|
|
|
|
Every component contains one or more options. Options may be gathered
|
|
|
|
into option groups to allow the GUI to give visual hints to the user
|
|
|
|
about which options are related.
|
|
|
|
|
2016-03-04 16:27:21 +00:00
|
|
|
The command @code{@w{--list-options @var{component}}} lists
|
2004-09-29 23:06:02 +00:00
|
|
|
all options (and the groups they belong to) in the component
|
|
|
|
@var{component}, one per line. @var{component} must be the string in
|
|
|
|
the field @var{name} in the output of the @code{--list-components}
|
|
|
|
command.
|
|
|
|
|
|
|
|
There is one line for each option and each group. First come all
|
|
|
|
options that are not in any group. Then comes a line describing a
|
|
|
|
group. Then come all options that belong into each group. Then comes
|
|
|
|
the next group and so on. There does not need to be any group (and in
|
|
|
|
this case the output will stop after the last non-grouped option).
|
|
|
|
|
|
|
|
The format of each line is:
|
|
|
|
|
|
|
|
@code{@var{name}:@var{flags}:@var{level}:@var{description}:@var{type}:@var{alt-type}:@var{argname}:@var{default}:@var{argdef}:@var{value}}
|
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item name
|
|
|
|
This field contains a name tag for the group or option. The name tag
|
|
|
|
is used to specify the group or option in all communication with
|
|
|
|
@command{gpgconf}. The name tag is to be used @emph{verbatim}. It is
|
|
|
|
thus not in any escaped format.
|
|
|
|
|
|
|
|
@item flags
|
|
|
|
The flags field contains an @emph{unsigned number}. Its value is the
|
|
|
|
OR-wise combination of the following flag values:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item group (1)
|
|
|
|
If this flag is set, this is a line describing a group and not an
|
|
|
|
option.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The following flag values are only defined for options (that is, if
|
|
|
|
the @code{group} flag is not used).
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item optional arg (2)
|
|
|
|
If this flag is set, the argument is optional. This is never set for
|
|
|
|
@var{type} @code{0} (none) options.
|
|
|
|
|
|
|
|
@item list (4)
|
|
|
|
If this flag is set, the option can be given multiple times.
|
|
|
|
|
|
|
|
@item runtime (8)
|
|
|
|
If this flag is set, the option can be changed at runtime.
|
|
|
|
|
|
|
|
@item default (16)
|
|
|
|
If this flag is set, a default value is available.
|
|
|
|
|
|
|
|
@item default desc (32)
|
|
|
|
If this flag is set, a (runtime) default is available. This and the
|
|
|
|
@code{default} flag are mutually exclusive.
|
|
|
|
|
|
|
|
@item no arg desc (64)
|
|
|
|
If this flag is set, and the @code{optional arg} flag is set, then the
|
|
|
|
option has a special meaning if no argument is given.
|
2007-03-06 20:44:41 +00:00
|
|
|
|
|
|
|
@item no change (128)
|
2016-03-04 16:38:09 +00:00
|
|
|
If this flag is set, @command{gpgconf} ignores requests to change the
|
|
|
|
value. GUI frontends should grey out this option. Note, that manual
|
|
|
|
changes of the configuration files are still possible.
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
@item level
|
|
|
|
This field is defined for options and for groups. It contains an
|
|
|
|
@emph{unsigned number} that specifies the expert level under which
|
|
|
|
this group or option should be displayed. The following expert levels
|
|
|
|
are defined for options (they have analogous meaning for groups):
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item basic (0)
|
|
|
|
This option should always be offered to the user.
|
|
|
|
|
|
|
|
@item advanced (1)
|
|
|
|
This option may be offered to advanced users.
|
|
|
|
|
|
|
|
@item expert (2)
|
|
|
|
This option should only be offered to expert users.
|
|
|
|
|
|
|
|
@item invisible (3)
|
|
|
|
This option should normally never be displayed, not even to expert
|
|
|
|
users.
|
|
|
|
|
|
|
|
@item internal (4)
|
|
|
|
This option is for internal use only. Ignore it.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
The level of a group will always be the lowest level of all options it
|
|
|
|
contains.
|
|
|
|
|
|
|
|
@item description
|
|
|
|
This field is defined for options and groups. The @emph{string} in
|
|
|
|
this field contains a human-readable description of the option or
|
|
|
|
group. It can be displayed to the user of the GUI for informational
|
|
|
|
purposes. It is @emph{percent-escaped} and @emph{localized}.
|
|
|
|
|
|
|
|
@item type
|
|
|
|
This field is only defined for options. It contains an @emph{unsigned
|
|
|
|
number} that specifies the type of the option's argument, if any. The
|
|
|
|
following types are defined:
|
|
|
|
|
|
|
|
Basic types:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item none (0)
|
|
|
|
No argument allowed.
|
|
|
|
|
|
|
|
@item string (1)
|
|
|
|
An @emph{unformatted string}.
|
|
|
|
|
|
|
|
@item int32 (2)
|
|
|
|
A @emph{signed number}.
|
|
|
|
|
|
|
|
@item uint32 (3)
|
|
|
|
An @emph{unsigned number}.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
Complex types:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item pathname (32)
|
|
|
|
A @emph{string} that describes the pathname of a file. The file does
|
|
|
|
not necessarily need to exist.
|
|
|
|
|
|
|
|
@item ldap server (33)
|
|
|
|
A @emph{string} that describes an LDAP server in the format:
|
|
|
|
|
|
|
|
@code{@var{hostname}:@var{port}:@var{username}:@var{password}:@var{base_dn}}
|
2008-02-27 17:31:47 +00:00
|
|
|
|
|
|
|
@item key fingerprint (34)
|
|
|
|
A @emph{string} with a 40 digit fingerprint specifying a certificate.
|
|
|
|
|
|
|
|
@item pub key (35)
|
|
|
|
A @emph{string} that describes a certificate by user ID, key ID or
|
|
|
|
fingerprint.
|
|
|
|
|
|
|
|
@item sec key (36)
|
|
|
|
A @emph{string} that describes a certificate with a key by user ID,
|
|
|
|
key ID or fingerprint.
|
2008-06-19 13:09:40 +00:00
|
|
|
|
|
|
|
@item alias list (37)
|
|
|
|
A @emph{string} that describes an alias list, like the one used with
|
|
|
|
gpg's group option. The list consists of a key, an equal sign and space
|
|
|
|
separated values.
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
More types will be added in the future. Please see the @var{alt-type}
|
|
|
|
field for information on how to cope with unknown types.
|
|
|
|
|
|
|
|
@item alt-type
|
|
|
|
This field is identical to @var{type}, except that only the types
|
|
|
|
@code{0} to @code{31} are allowed. The GUI is expected to present the
|
|
|
|
user the option in the format specified by @var{type}. But if the
|
|
|
|
argument type @var{type} is not supported by the GUI, it can still
|
|
|
|
display the option in the more generic basic type @var{alt-type}. The
|
|
|
|
GUI must support all the defined basic types to be able to display all
|
|
|
|
options. More basic types may be added in future versions. If the
|
|
|
|
GUI encounters a basic type it doesn't support, it should report an
|
|
|
|
error and abort the operation.
|
|
|
|
|
|
|
|
@item argname
|
|
|
|
This field is only defined for options with an argument type
|
|
|
|
@var{type} that is not @code{0}. In this case it may contain a
|
2016-03-04 16:00:51 +00:00
|
|
|
@emph{percent-escaped} and @emph{localized string} that gives a short
|
2004-09-29 23:06:02 +00:00
|
|
|
name for the argument. The field may also be empty, though, in which
|
|
|
|
case a short name is not known.
|
|
|
|
|
|
|
|
@item default
|
2008-01-10 03:03:15 +00:00
|
|
|
This field is defined only for options for which the @code{default} or
|
|
|
|
@code{default desc} flag is set. If the @code{default} flag is set,
|
2016-03-04 15:51:22 +00:00
|
|
|
its format is that of an @emph{option argument} (@pxref{Format
|
2008-01-10 03:03:15 +00:00
|
|
|
conventions}, for details). If the default value is empty, then no
|
|
|
|
default is known. Otherwise, the value specifies the default value
|
|
|
|
for this option. If the @code{default desc} flag is set, the field is
|
|
|
|
either empty or contains a description of the effect if the option is
|
|
|
|
not given.
|
2004-09-29 23:06:02 +00:00
|
|
|
|
|
|
|
@item argdef
|
|
|
|
This field is defined only for options for which the @code{optional
|
|
|
|
arg} flag is set. If the @code{no arg desc} flag is not set, its
|
2016-03-04 15:51:22 +00:00
|
|
|
format is that of an @emph{option argument} (@pxref{Format
|
2004-09-29 23:06:02 +00:00
|
|
|
conventions}, for details). If the default value is empty, then no
|
2008-01-10 03:03:15 +00:00
|
|
|
default is known. Otherwise, the value specifies the default argument
|
2004-09-29 23:06:02 +00:00
|
|
|
for this option. If the @code{no arg desc} flag is set, the field is
|
|
|
|
either empty or contains a description of the effect of this option if
|
2008-01-10 03:03:15 +00:00
|
|
|
no argument is given.
|
2004-09-29 23:06:02 +00:00
|
|
|
|
|
|
|
@item value
|
|
|
|
This field is defined only for options. Its format is that of an
|
|
|
|
@emph{option argument}. If it is empty, then the option is not
|
2009-07-22 13:33:46 +00:00
|
|
|
explicitly set in the current configuration, and the default applies
|
2004-09-29 23:06:02 +00:00
|
|
|
(if any). Otherwise, it contains the current value of the option.
|
|
|
|
Note that this field is also meaningful if the option itself does not
|
2008-01-10 03:03:15 +00:00
|
|
|
take a real argument (in this case, it contains the number of times
|
|
|
|
the option appears).
|
2004-09-29 23:06:02 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
|
|
@node Changing options
|
|
|
|
@subsection Changing options
|
|
|
|
|
|
|
|
The command @w{@code{--change-options @var{component}}} will attempt
|
|
|
|
to change the options of the component @var{component} to the
|
|
|
|
specified values. @var{component} must be the string in the field
|
|
|
|
@var{name} in the output of the @code{--list-components} command. You
|
|
|
|
have to provide the options that shall be changed in the following
|
|
|
|
format on standard input:
|
|
|
|
|
|
|
|
@code{@var{name}:@var{flags}:@var{new-value}}
|
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item name
|
|
|
|
This is the name of the option to change. @var{name} must be the
|
|
|
|
string in the field @var{name} in the output of the
|
|
|
|
@code{--list-options} command.
|
|
|
|
|
|
|
|
@item flags
|
|
|
|
The flags field contains an @emph{unsigned number}. Its value is the
|
|
|
|
OR-wise combination of the following flag values:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item default (16)
|
|
|
|
If this flag is set, the option is deleted and the default value is
|
|
|
|
used instead (if applicable).
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item new-value
|
|
|
|
The new value for the option. This field is only defined if the
|
|
|
|
@code{default} flag is not set. The format is that of an @emph{option
|
|
|
|
argument}. If it is empty (or the field is omitted), the default
|
|
|
|
argument is used (only allowed if the argument is optional for this
|
|
|
|
option). Otherwise, the option will be set to the specified value.
|
|
|
|
@end table
|
|
|
|
|
2008-05-19 22:46:41 +00:00
|
|
|
@noindent
|
|
|
|
The output of the command is the same as that of
|
|
|
|
@code{--check-options} for the modified configuration file.
|
|
|
|
|
2004-09-29 23:06:02 +00:00
|
|
|
Examples:
|
|
|
|
|
|
|
|
To set the force option, which is of basic type @code{none (0)}:
|
|
|
|
|
|
|
|
@example
|
|
|
|
$ echo 'force:0:1' | gpgconf --change-options dirmngr
|
|
|
|
@end example
|
|
|
|
|
|
|
|
To delete the force option:
|
|
|
|
|
|
|
|
@example
|
|
|
|
$ echo 'force:16:' | gpgconf --change-options dirmngr
|
|
|
|
@end example
|
|
|
|
|
|
|
|
The @code{--runtime} option can influence when the changes take
|
|
|
|
effect.
|
2004-10-22 12:30:34 +00:00
|
|
|
|
2007-10-23 18:13:27 +00:00
|
|
|
|
|
|
|
@node Listing global options
|
|
|
|
@subsection Listing global options
|
|
|
|
|
|
|
|
Sometimes it is useful for applications to look at the global options
|
2011-02-23 10:15:34 +01:00
|
|
|
file @file{gpgconf.conf}.
|
2007-10-23 18:13:27 +00:00
|
|
|
The colon separated listing format is record oriented and uses the first
|
|
|
|
field to identify the record type:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item k
|
|
|
|
This describes a key record to start the definition of a new ruleset for
|
|
|
|
a user/group. The format of a key record is:
|
|
|
|
|
|
|
|
@code{k:@var{user}:@var{group}:}
|
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item user
|
|
|
|
This is the user field of the key. It is percent escaped. See the
|
|
|
|
definition of the gpgconf.conf format for details.
|
|
|
|
|
|
|
|
@item group
|
|
|
|
This is the group field of the key. It is percent escaped.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item r
|
|
|
|
This describes a rule record. All rule records up to the next key record
|
|
|
|
make up a rule set for that key. The format of a rule record is:
|
|
|
|
|
2016-03-04 16:27:21 +00:00
|
|
|
@code{r:::@var{component}:@var{option}:@var{flag}:@var{value}:}
|
2007-10-23 18:13:27 +00:00
|
|
|
|
|
|
|
@table @var
|
|
|
|
@item component
|
|
|
|
This is the component part of a rule. It is a plain string.
|
|
|
|
|
|
|
|
@item option
|
|
|
|
This is the option part of a rule. It is a plain string.
|
|
|
|
|
|
|
|
@item flag
|
|
|
|
This is the flags part of a rule. There may be only one flag per rule
|
|
|
|
but by using the same component and option, several flags may be
|
|
|
|
assigned to an option. It is a plain string.
|
|
|
|
|
|
|
|
@item value
|
|
|
|
This is the optional value for the option. It is a percent escaped
|
|
|
|
string with a single quotation mark to indicate a string. The quotation
|
|
|
|
mark is only required to distinguish between no value specified and an
|
|
|
|
empty string.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@noindent
|
2009-07-22 13:33:46 +00:00
|
|
|
Unknown record types should be ignored. Note that there is intentionally
|
2007-10-23 18:13:27 +00:00
|
|
|
no feature to change the global option file through @command{gpgconf}.
|
|
|
|
|
|
|
|
|
2016-11-02 17:54:32 +01:00
|
|
|
@node Querying versions
|
|
|
|
@subsection Get and compare software versions.
|
|
|
|
|
|
|
|
The GnuPG Project operates a server to query the current versions of
|
|
|
|
software packages related to GnuPG. @command{gpgconf} can be used to
|
|
|
|
access this online database. To allow for offline operations, this
|
|
|
|
feature works by having @command{dirmngr} download a file from
|
|
|
|
@code{https://versions.gnupg.org}, checking the signature of that file
|
|
|
|
and storing the file in the GnuPG home directory. If
|
|
|
|
@command{gpgconf} is used and @command{dirmngr} is running, it may ask
|
|
|
|
@command{dirmngr} to refresh that file before itself uses the file.
|
|
|
|
|
|
|
|
The command @option{--query-swdb} returns information for the given
|
|
|
|
package in a colon delimited format:
|
|
|
|
|
|
|
|
@table @var
|
|
|
|
|
|
|
|
@item name
|
|
|
|
This is the name of the package as requested. Note that "gnupg" is a
|
|
|
|
special name which is replaced by the actual package implementing this
|
|
|
|
version of GnuPG. For this name it is also not required to specify a
|
|
|
|
version because @command{gpgconf} takes its own version in this case.
|
|
|
|
|
2016-11-03 10:58:19 +01:00
|
|
|
@item iversion
|
|
|
|
The currently installed version or an empty string. The value is
|
|
|
|
taken from the command line argument but may be provided by gpg
|
|
|
|
if not given.
|
|
|
|
|
2016-11-02 17:54:32 +01:00
|
|
|
@item status
|
|
|
|
The status of the software package according to this table:
|
|
|
|
@table @code
|
|
|
|
@item -
|
|
|
|
No information available. This is either because no current version
|
|
|
|
has been specified or due to an error.
|
|
|
|
@item ?
|
|
|
|
The given name is not known in the online database.
|
|
|
|
@item u
|
|
|
|
An update of the software is available.
|
|
|
|
@item c
|
2016-11-03 10:58:19 +01:00
|
|
|
The installed version of the software is current.
|
2016-11-02 17:54:32 +01:00
|
|
|
@item n
|
2016-11-03 10:58:19 +01:00
|
|
|
The installed version is already newer than the released version.
|
2016-11-02 17:54:32 +01:00
|
|
|
@end table
|
|
|
|
|
|
|
|
@item urgency
|
|
|
|
If the value (the empty string should be considered as zero) is
|
|
|
|
greater than zero an important update is available.
|
|
|
|
|
|
|
|
@item error
|
|
|
|
This returns an @command{gpg-error} error code to distinguish between
|
|
|
|
various failure modes.
|
|
|
|
|
|
|
|
@item filedate
|
|
|
|
This gives the date of the file with the version numbers in standard
|
|
|
|
ISO format (@code{yyyymmddThhmmss}). The date has been extracted by
|
|
|
|
@command{dirmngr} from the signature of the file.
|
|
|
|
|
|
|
|
@item verified
|
|
|
|
This gives the date in ISO format the file was downloaded. This value
|
|
|
|
can be used to evaluate the freshness of the information.
|
|
|
|
|
|
|
|
@item version
|
|
|
|
This returns the version string for the requested software from the
|
|
|
|
file.
|
|
|
|
|
|
|
|
@item reldate
|
|
|
|
This returns the release date in ISO format.
|
|
|
|
|
|
|
|
@item size
|
|
|
|
This returns the size of the package as decimal number of bytes.
|
|
|
|
|
|
|
|
@item hash
|
|
|
|
This returns a hexified SHA-2 hash of the package.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
More fields may be added in future to the output.
|
|
|
|
|
2007-10-23 18:13:27 +00:00
|
|
|
|
2007-03-06 20:44:41 +00:00
|
|
|
@mansect files
|
|
|
|
@node Files used by gpgconf
|
|
|
|
@subsection Files used by gpgconf
|
|
|
|
|
|
|
|
@table @file
|
|
|
|
|
2007-03-07 20:55:14 +00:00
|
|
|
@item /etc/gnupg/gpgconf.conf
|
2007-03-06 20:44:41 +00:00
|
|
|
@cindex gpgconf.conf
|
|
|
|
If this file exists, it is processed as a global configuration file.
|
|
|
|
A commented example can be found in the @file{examples} directory of
|
|
|
|
the distribution.
|
2016-11-02 17:54:32 +01:00
|
|
|
|
|
|
|
@item @var{GNUPGHOME}/swdb.lst
|
|
|
|
@cindex swdb.lst
|
|
|
|
A file with current software versions. @command{dirmngr} creates
|
|
|
|
this file on demand from an online resource.
|
|
|
|
|
2007-03-06 20:44:41 +00:00
|
|
|
@end table
|
|
|
|
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect see also
|
2007-03-07 20:55:14 +00:00
|
|
|
@ifset isman
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg}(1),
|
|
|
|
@command{gpgsm}(1),
|
|
|
|
@command{gpg-agent}(1),
|
2006-08-18 13:05:39 +00:00
|
|
|
@command{scdaemon}(1),
|
|
|
|
@command{dirmngr}(1)
|
2007-03-07 20:55:14 +00:00
|
|
|
@end ifset
|
2006-08-18 13:05:39 +00:00
|
|
|
@include see-also-note.texi
|
|
|
|
|
|
|
|
|
2007-03-07 20:55:14 +00:00
|
|
|
|
|
|
|
@c
|
|
|
|
@c APPLYGNUPGDEFAULTS
|
|
|
|
@c
|
|
|
|
@manpage applygnupgdefaults.8
|
|
|
|
@node applygnupgdefaults
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Run gpgconf for all users
|
2007-03-07 20:55:14 +00:00
|
|
|
@ifset manverb
|
|
|
|
.B applygnupgdefaults
|
|
|
|
\- Run gpgconf --apply-defaults for all users.
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B applygnupgdefaults
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
|
|
|
This script is a wrapper around @command{gpgconf} to run it with the
|
|
|
|
command @code{--apply-defaults} for all real users with an existing
|
|
|
|
GnuPG home directory. Admins might want to use this script to update he
|
|
|
|
GnuPG configuration files for all users after
|
More cleanup of "allow to".
* README, agent/command.c, agent/keyformat.txt, common/i18n.c,
common/iobuf.c, common/keyserver.h, dirmngr/cdblib.c,
dirmngr/ldap-wrapper.c, doc/DETAILS, doc/TRANSLATE,
doc/announce-2.1.txt, doc/gpg.texi, doc/gpgsm.texi,
doc/scdaemon.texi, doc/tools.texi, doc/whats-new-in-2.1.txt,
g10/export.c, g10/getkey.c, g10/import.c, g10/keyedit.c, m4/ksba.m4,
m4/libgcrypt.m4, m4/ntbtls.m4, po/ca.po, po/cs.po, po/da.po,
po/de.po, po/el.po, po/eo.po, po/es.po, po/et.po, po/fi.po,
po/fr.po, po/gl.po, po/hu.po, po/id.po, po/it.po, po/ja.po,
po/nb.po, po/pl.po, po/pt.po, po/ro.po, po/ru.po, po/sk.po,
po/sv.po, po/tr.po, po/uk.po, po/zh_CN.po, po/zh_TW.po,
scd/app-p15.c, scd/ccid-driver.c, scd/command.c, sm/gpgsm.c,
sm/sign.c, tools/gpgconf-comp.c, tools/gpgtar.h: replace "Allow to"
with clearer text.
In standard English, the normal construction is "${XXX} allows ${YYY}
to" -- that is, the subject (${XXX}) of the sentence is allowing the
object (${YYY}) to do something. When the object is missing, the
phrasing sounds awkward, even if the object is implied by context.
There's almost always a better construction that isn't as awkward.
These changes should make the language a bit clearer.
Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
2016-08-01 22:19:17 -04:00
|
|
|
@file{/etc/gnupg/gpgconf.conf} has been changed. This allows enforcing
|
|
|
|
certain policies for all users. Note, that this is not a bulletproof way to
|
|
|
|
force a user to use certain options. A user may always directly edit
|
2007-03-07 20:55:14 +00:00
|
|
|
the configuration files and bypass gpgconf.
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
@command{applygnupgdefaults} is invoked by root as:
|
|
|
|
|
|
|
|
@example
|
|
|
|
applygnupgdefaults
|
|
|
|
@end example
|
|
|
|
|
|
|
|
|
2004-12-21 19:05:15 +00:00
|
|
|
@c
|
|
|
|
@c GPG-PRESET-PASSPHRASE
|
|
|
|
@c
|
|
|
|
@node gpg-preset-passphrase
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Put a passphrase into the cache
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpage gpg-preset-passphrase.1
|
|
|
|
@ifset manverb
|
|
|
|
.B gpg-preset-passphrase
|
|
|
|
\- Put a passphrase into gpg-agent's cache
|
|
|
|
@end ifset
|
2004-12-21 19:05:15 +00:00
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B gpg-preset-passphrase
|
|
|
|
.RI [ options ]
|
|
|
|
.RI [ command ]
|
2008-12-09 08:58:02 +00:00
|
|
|
.I cache-id
|
2006-08-18 13:05:39 +00:00
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
2004-12-21 20:47:04 +00:00
|
|
|
The @command{gpg-preset-passphrase} is a utility to seed the internal
|
2004-12-22 17:24:13 +00:00
|
|
|
cache of a running @command{gpg-agent} with passphrases. It is mainly
|
|
|
|
useful for unattended machines, where the usual @command{pinentry} tool
|
|
|
|
may not be used and the passphrases for the to be used keys are given at
|
|
|
|
machine startup.
|
2004-12-21 20:47:04 +00:00
|
|
|
|
2017-07-13 17:12:42 +02:00
|
|
|
This program works with GnuPG 2 and later. GnuPG 1.x is not supported.
|
|
|
|
|
2004-12-21 20:47:04 +00:00
|
|
|
Passphrases set with this utility don't expire unless the
|
2014-06-24 13:46:52 +02:00
|
|
|
@option{--forget} option is used to explicitly clear them from the
|
|
|
|
cache --- or @command{gpg-agent} is either restarted or reloaded (by
|
2014-10-29 17:10:03 +01:00
|
|
|
sending a SIGHUP to it). Note that the maximum cache time as set with
|
2014-06-24 13:46:52 +02:00
|
|
|
@option{--max-cache-ttl} is still honored. It is necessary to allow
|
|
|
|
this passphrase presetting by starting @command{gpg-agent} with the
|
2004-12-21 20:47:04 +00:00
|
|
|
@option{--allow-preset-passphrase}.
|
2004-12-21 19:05:15 +00:00
|
|
|
|
|
|
|
@menu
|
2004-12-21 20:47:04 +00:00
|
|
|
* Invoking gpg-preset-passphrase:: List of all commands and options.
|
2004-12-21 19:05:15 +00:00
|
|
|
@end menu
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpause
|
2004-12-21 20:47:04 +00:00
|
|
|
@node Invoking gpg-preset-passphrase
|
2016-03-04 14:45:19 +00:00
|
|
|
@subsection List of all commands and options
|
2006-08-18 13:05:39 +00:00
|
|
|
@mancont
|
2004-12-21 19:05:15 +00:00
|
|
|
|
2004-12-21 20:47:04 +00:00
|
|
|
@noindent
|
|
|
|
@command{gpg-preset-passphrase} is invoked this way:
|
|
|
|
|
|
|
|
@example
|
2008-12-09 08:58:02 +00:00
|
|
|
gpg-preset-passphrase [options] [command] @var{cacheid}
|
2004-12-21 20:47:04 +00:00
|
|
|
@end example
|
|
|
|
|
2008-12-09 08:58:02 +00:00
|
|
|
@var{cacheid} is either a 40 character keygrip of hexadecimal
|
|
|
|
characters identifying the key for which the passphrase should be set
|
|
|
|
or cleared. The keygrip is listed along with the key when running the
|
2017-08-08 13:04:12 +02:00
|
|
|
command: @code{gpgsm --with-keygrip --list-secret-keys}.
|
|
|
|
Alternatively an arbitrary string may be used to identify a
|
|
|
|
passphrase; it is suggested that such a string is prefixed with the
|
|
|
|
name of the application (e.g @code{foo:12346}). Scripts should always
|
|
|
|
use the option @option{--with-colons}, which provides the keygrip in a
|
|
|
|
"grp" line (cf. @file{doc/DETAILS})/
|
2008-12-09 08:58:02 +00:00
|
|
|
|
|
|
|
@noindent
|
|
|
|
One of the following command options must be given:
|
2004-12-21 19:05:15 +00:00
|
|
|
|
|
|
|
@table @gnupgtabopt
|
2004-12-21 20:47:04 +00:00
|
|
|
@item --preset
|
2006-08-18 13:05:39 +00:00
|
|
|
@opindex preset
|
2004-12-21 20:47:04 +00:00
|
|
|
Preset a passphrase. This is what you usually will
|
2004-12-22 17:24:13 +00:00
|
|
|
use. @command{gpg-preset-passphrase} will then read the passphrase from
|
2004-12-21 20:47:04 +00:00
|
|
|
@code{stdin}.
|
2004-12-21 19:05:15 +00:00
|
|
|
|
2004-12-21 20:47:04 +00:00
|
|
|
@item --forget
|
2006-08-18 13:05:39 +00:00
|
|
|
@opindex forget
|
2008-12-09 08:58:02 +00:00
|
|
|
Flush the passphrase for the given cache ID from the cache.
|
2004-12-21 19:05:15 +00:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2004-12-22 17:24:13 +00:00
|
|
|
@noindent
|
|
|
|
The following additional options may be used:
|
2004-12-21 19:05:15 +00:00
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
2004-12-21 20:47:04 +00:00
|
|
|
@opindex verbose
|
2011-02-23 10:15:34 +01:00
|
|
|
Output additional information while running.
|
2004-12-21 20:47:04 +00:00
|
|
|
|
|
|
|
@item -P @var{string}
|
|
|
|
@itemx --passphrase @var{string}
|
|
|
|
@opindex passphrase
|
|
|
|
Instead of reading the passphrase from @code{stdin}, use the supplied
|
|
|
|
@var{string} as passphrase. Note that this makes the passphrase visible
|
|
|
|
for other users.
|
2004-12-21 19:05:15 +00:00
|
|
|
@end table
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect see also
|
2007-03-07 20:55:14 +00:00
|
|
|
@ifset isman
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg}(1),
|
|
|
|
@command{gpgsm}(1),
|
|
|
|
@command{gpg-agent}(1),
|
2006-08-18 13:05:39 +00:00
|
|
|
@command{scdaemon}(1)
|
2007-03-07 20:55:14 +00:00
|
|
|
@end ifset
|
2006-08-18 13:05:39 +00:00
|
|
|
@include see-also-note.texi
|
2004-12-21 19:05:15 +00:00
|
|
|
|
|
|
|
|
2004-12-22 17:24:13 +00:00
|
|
|
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
@c
|
|
|
|
@c GPG-CONNECT-AGENT
|
|
|
|
@c
|
|
|
|
@node gpg-connect-agent
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Communicate with a running agent
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpage gpg-connect-agent.1
|
|
|
|
@ifset manverb
|
|
|
|
.B gpg-connect-agent
|
|
|
|
\- Communicate with a running agent
|
|
|
|
@end ifset
|
2005-02-24 17:36:11 +00:00
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B gpg-connect-agent
|
2008-05-26 16:48:05 +00:00
|
|
|
.RI [ options ] [commands]
|
2006-08-18 13:05:39 +00:00
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
2005-02-24 17:36:11 +00:00
|
|
|
The @command{gpg-connect-agent} is a utility to communicate with a
|
|
|
|
running @command{gpg-agent}. It is useful to check out the commands
|
2016-03-04 16:38:09 +00:00
|
|
|
@command{gpg-agent} provides using the Assuan interface. It might
|
|
|
|
also be useful for scripting simple applications. Input is expected
|
2016-03-04 15:20:47 +00:00
|
|
|
at stdin and output gets printed to stdout.
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
It is very similar to running @command{gpg-agent} in server mode; but
|
|
|
|
here we connect to a running instance.
|
|
|
|
|
|
|
|
@menu
|
2006-09-08 17:02:06 +00:00
|
|
|
* Invoking gpg-connect-agent:: List of all options.
|
|
|
|
* Controlling gpg-connect-agent:: Control commands.
|
2005-02-24 17:36:11 +00:00
|
|
|
@end menu
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpause
|
2005-02-24 17:36:11 +00:00
|
|
|
@node Invoking gpg-connect-agent
|
2016-03-04 14:45:19 +00:00
|
|
|
@subsection List of all options
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
@noindent
|
|
|
|
@command{gpg-connect-agent} is invoked this way:
|
|
|
|
|
|
|
|
@example
|
2008-05-26 16:48:05 +00:00
|
|
|
gpg-connect-agent [options] [commands]
|
2005-02-24 17:36:11 +00:00
|
|
|
@end example
|
2006-09-08 17:02:06 +00:00
|
|
|
@mancont
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
@noindent
|
|
|
|
The following options may be used:
|
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
@opindex verbose
|
2011-02-23 10:15:34 +01:00
|
|
|
Output additional information while running.
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
@item -q
|
|
|
|
@item --quiet
|
|
|
|
@opindex q
|
|
|
|
@opindex quiet
|
|
|
|
Try to be as quiet as possible.
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@include opt-homedir.texi
|
2005-05-18 10:48:06 +00:00
|
|
|
|
2010-10-14 16:34:31 +00:00
|
|
|
@item --agent-program @var{file}
|
|
|
|
@opindex agent-program
|
2014-10-30 09:55:51 +01:00
|
|
|
Specify the agent program to be started if none is running. The
|
|
|
|
default value is determined by running @command{gpgconf} with the
|
|
|
|
option @option{--list-dirs}. Note that the pipe symbol (@code{|}) is
|
|
|
|
used for a regression test suite hack and may thus not be used in the
|
|
|
|
file name.
|
2010-10-14 16:34:31 +00:00
|
|
|
|
2014-03-14 19:25:58 +01:00
|
|
|
@item --dirmngr-program @var{file}
|
|
|
|
@opindex dirmngr-program
|
|
|
|
Specify the directory manager (keyserver client) program to be started
|
|
|
|
if none is running. This has only an effect if used together with the
|
|
|
|
option @option{--dirmngr}.
|
|
|
|
|
|
|
|
@item --dirmngr
|
|
|
|
@opindex dirmngr
|
|
|
|
Connect to a running directory manager (keyserver client) instead of
|
|
|
|
to the gpg-agent. If a dirmngr is not running, start it.
|
2010-10-14 16:34:31 +00:00
|
|
|
|
2005-05-18 10:48:06 +00:00
|
|
|
@item -S
|
|
|
|
@itemx --raw-socket @var{name}
|
|
|
|
@opindex raw-socket
|
|
|
|
Connect to socket @var{name} assuming this is an Assuan style server.
|
|
|
|
Do not run any special initializations or environment checks. This may
|
|
|
|
be used to directly connect to any Assuan style socket server.
|
|
|
|
|
2006-09-13 15:57:30 +00:00
|
|
|
@item -E
|
|
|
|
@itemx --exec
|
|
|
|
@opindex exec
|
|
|
|
Take the rest of the command line as a program and it's arguments and
|
2016-03-04 15:20:47 +00:00
|
|
|
execute it as an Assuan server. Here is how you would run @command{gpgsm}:
|
2006-09-13 15:57:30 +00:00
|
|
|
@smallexample
|
|
|
|
gpg-connect-agent --exec gpgsm --server
|
|
|
|
@end smallexample
|
2008-05-26 16:48:05 +00:00
|
|
|
Note that you may not use options on the command line in this case.
|
2006-09-13 15:57:30 +00:00
|
|
|
|
|
|
|
@item --no-ext-connect
|
|
|
|
@opindex no-ext-connect
|
|
|
|
When using @option{-S} or @option{--exec}, @command{gpg-connect-agent}
|
2016-03-04 15:20:47 +00:00
|
|
|
connects to the Assuan server in extended mode to allow descriptor
|
2006-09-13 15:57:30 +00:00
|
|
|
passing. This option makes it use the old mode.
|
|
|
|
|
2014-11-28 09:44:19 +01:00
|
|
|
@item --no-autostart
|
|
|
|
@opindex no-autostart
|
|
|
|
Do not start the gpg-agent or the dirmngr if it has not yet been
|
|
|
|
started.
|
|
|
|
|
2015-01-22 17:49:55 +01:00
|
|
|
@item -r @var{file}
|
|
|
|
@itemx --run @var{file}
|
2011-02-23 10:15:34 +01:00
|
|
|
@opindex run
|
2007-10-19 14:51:39 +00:00
|
|
|
Run the commands from @var{file} at startup and then continue with the
|
2008-05-26 16:48:05 +00:00
|
|
|
regular input method. Note, that commands given on the command line are
|
|
|
|
executed after this file.
|
2007-10-19 14:51:39 +00:00
|
|
|
|
|
|
|
@item -s
|
|
|
|
@itemx --subst
|
|
|
|
@opindex subst
|
|
|
|
Run the command @code{/subst} at startup.
|
|
|
|
|
2007-04-03 16:57:37 +00:00
|
|
|
@item --hex
|
|
|
|
@opindex hex
|
|
|
|
Print data lines in a hex format and the ASCII representation of
|
|
|
|
non-control characters.
|
|
|
|
|
|
|
|
@item --decode
|
|
|
|
@opindex decode
|
|
|
|
Decode data lines. That is to remove percent escapes but make sure that
|
|
|
|
a new line always starts with a D and a space.
|
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@end table
|
|
|
|
|
2006-09-08 17:02:06 +00:00
|
|
|
@mansect control commands
|
|
|
|
@node Controlling gpg-connect-agent
|
2016-03-04 14:45:19 +00:00
|
|
|
@subsection Control commands
|
2006-09-08 17:02:06 +00:00
|
|
|
|
|
|
|
While reading Assuan commands, gpg-agent also allows a few special
|
|
|
|
commands to control its operation. These control commands all start
|
|
|
|
with a slash (@code{/}).
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
|
|
|
|
@item /echo @var{args}
|
|
|
|
Just print @var{args}.
|
|
|
|
|
2007-10-19 14:51:39 +00:00
|
|
|
@item /let @var{name} @var{value}
|
|
|
|
Set the variable @var{name} to @var{value}. Variables are only
|
|
|
|
substituted on the input if the @command{/subst} has been used.
|
2009-07-22 13:33:46 +00:00
|
|
|
Variables are referenced by prefixing the name with a dollar sign and
|
2007-10-19 14:51:39 +00:00
|
|
|
optionally include the name in curly braces. The rules for a valid name
|
2008-05-26 16:48:05 +00:00
|
|
|
are identically to those of the standard bourne shell. This is not yet
|
2007-10-19 14:51:39 +00:00
|
|
|
enforced but may be in the future. When used with curly braces no
|
2011-02-23 10:15:34 +01:00
|
|
|
leading or trailing white space is allowed.
|
2007-10-19 14:51:39 +00:00
|
|
|
|
|
|
|
If a variable is not found, it is searched in the environment and if
|
|
|
|
found copied to the table of variables.
|
|
|
|
|
|
|
|
Variable functions are available: The name of the function must be
|
|
|
|
followed by at least one space and the at least one argument. The
|
|
|
|
following functions are available:
|
|
|
|
|
|
|
|
@table @code
|
|
|
|
@item get
|
|
|
|
Return a value described by the argument. Available arguments are:
|
|
|
|
|
2011-02-23 10:15:34 +01:00
|
|
|
@table @code
|
2007-10-19 14:51:39 +00:00
|
|
|
@item cwd
|
|
|
|
The current working directory.
|
|
|
|
@item homedir
|
|
|
|
The gnupg homedir.
|
|
|
|
@item sysconfdir
|
|
|
|
GnuPG's system configuration directory.
|
|
|
|
@item bindir
|
|
|
|
GnuPG's binary directory.
|
|
|
|
@item libdir
|
|
|
|
GnuPG's library directory.
|
|
|
|
@item libexecdir
|
|
|
|
GnuPG's library directory for executable files.
|
|
|
|
@item datadir
|
|
|
|
GnuPG's data directory.
|
|
|
|
@item serverpid
|
|
|
|
The PID of the current server. Command @command{/serverpid} must
|
|
|
|
have been given to return a useful value.
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@item unescape @var{args}
|
|
|
|
Remove C-style escapes from @var{args}. Note that @code{\0} and
|
2008-01-28 08:03:08 +00:00
|
|
|
@code{\x00} terminate the returned string implicitly. The string to be
|
2007-10-19 14:51:39 +00:00
|
|
|
converted are the entire arguments right behind the delimiting space of
|
|
|
|
the function name.
|
|
|
|
|
|
|
|
@item unpercent @var{args}
|
|
|
|
@itemx unpercent+ @var{args}
|
2009-07-22 13:33:46 +00:00
|
|
|
Remove percent style escaping from @var{args}. Note that @code{%00}
|
2007-10-19 14:51:39 +00:00
|
|
|
terminates the string implicitly. The string to be converted are the
|
|
|
|
entire arguments right behind the delimiting space of the function
|
|
|
|
name. @code{unpercent+} also maps plus signs to a spaces.
|
|
|
|
|
|
|
|
@item percent @var{args}
|
2007-10-24 15:34:23 +00:00
|
|
|
@itemx percent+ @var{args}
|
2009-07-22 13:33:46 +00:00
|
|
|
Escape the @var{args} using percent style escaping. Tabs, formfeeds,
|
2007-10-19 14:51:39 +00:00
|
|
|
linefeeds, carriage returns and colons are escaped. @code{percent+} also
|
|
|
|
maps spaces to plus signs.
|
|
|
|
|
2008-03-05 10:08:10 +00:00
|
|
|
@item errcode @var{arg}
|
|
|
|
@itemx errsource @var{arg}
|
|
|
|
@itemx errstring @var{arg}
|
|
|
|
Assume @var{arg} is an integer and evaluate it using @code{strtol}. Return
|
|
|
|
the gpg-error error code, error source or a formatted string with the
|
|
|
|
error code and error source.
|
|
|
|
|
|
|
|
|
2007-10-24 15:34:23 +00:00
|
|
|
@item +
|
|
|
|
@itemx -
|
2008-03-05 10:08:10 +00:00
|
|
|
@itemx *
|
|
|
|
@itemx /
|
|
|
|
@itemx %
|
2007-10-24 15:34:23 +00:00
|
|
|
Evaluate all arguments as long integers using @code{strtol} and apply
|
|
|
|
this operator. A division by zero yields an empty string.
|
|
|
|
|
2008-03-05 10:08:10 +00:00
|
|
|
@item !
|
|
|
|
@itemx |
|
|
|
|
@itemx &
|
|
|
|
Evaluate all arguments as long integers using @code{strtol} and apply
|
2015-01-22 17:49:55 +01:00
|
|
|
the logical operators NOT, OR or AND. The NOT operator works on the
|
2008-03-05 10:08:10 +00:00
|
|
|
last argument only.
|
|
|
|
|
2007-10-24 15:34:23 +00:00
|
|
|
|
2007-10-19 14:51:39 +00:00
|
|
|
@end table
|
2006-09-08 17:02:06 +00:00
|
|
|
|
2007-10-19 14:51:39 +00:00
|
|
|
|
|
|
|
@item /definq @var{name} @var{var}
|
|
|
|
Use content of the variable @var{var} for inquiries with @var{name}.
|
|
|
|
@var{name} may be an asterisk (@code{*}) to match any inquiry.
|
|
|
|
|
|
|
|
|
|
|
|
@item /definqfile @var{name} @var{file}
|
2006-09-08 17:02:06 +00:00
|
|
|
Use content of @var{file} for inquiries with @var{name}.
|
2007-10-19 14:51:39 +00:00
|
|
|
@var{name} may be an asterisk (@code{*}) to match any inquiry.
|
2006-09-08 17:02:06 +00:00
|
|
|
|
|
|
|
@item /definqprog @var{name} @var{prog}
|
|
|
|
Run @var{prog} for inquiries matching @var{name} and pass the
|
2007-10-19 14:51:39 +00:00
|
|
|
entire line to it as command line arguments.
|
2006-09-08 17:02:06 +00:00
|
|
|
|
2008-10-01 16:17:39 +00:00
|
|
|
@item /datafile @var{name}
|
|
|
|
Write all data lines from the server to the file @var{name}. The file
|
2009-07-22 13:33:46 +00:00
|
|
|
is opened for writing and created if it does not exists. An existing
|
2008-10-01 16:17:39 +00:00
|
|
|
file is first truncated to 0. The data written to the file fully
|
2009-07-22 13:33:46 +00:00
|
|
|
decoded. Using a single dash for @var{name} writes to stdout. The
|
2008-10-01 16:17:39 +00:00
|
|
|
file is kept open until a new file is set using this command or this
|
|
|
|
command is used without an argument.
|
|
|
|
|
2006-09-08 17:02:06 +00:00
|
|
|
@item /showdef
|
|
|
|
Print all definitions
|
|
|
|
|
|
|
|
@item /cleardef
|
|
|
|
Delete all definitions
|
|
|
|
|
2006-09-13 15:57:30 +00:00
|
|
|
@item /sendfd @var{file} @var{mode}
|
|
|
|
Open @var{file} in @var{mode} (which needs to be a valid @code{fopen}
|
|
|
|
mode string) and send the file descriptor to the server. This is
|
|
|
|
usually followed by a command like @code{INPUT FD} to set the
|
|
|
|
input source for other commands.
|
|
|
|
|
|
|
|
@item /recvfd
|
|
|
|
Not yet implemented.
|
|
|
|
|
2007-10-19 14:51:39 +00:00
|
|
|
@item /open @var{var} @var{file} [@var{mode}]
|
|
|
|
Open @var{file} and assign the file descriptor to @var{var}. Warning:
|
|
|
|
This command is experimental and might change in future versions.
|
|
|
|
|
|
|
|
@item /close @var{fd}
|
|
|
|
Close the file descriptor @var{fd}. Warning: This command is
|
|
|
|
experimental and might change in future versions.
|
|
|
|
|
|
|
|
@item /showopen
|
2008-10-13 09:29:20 +00:00
|
|
|
Show a list of open files.
|
2007-10-19 14:51:39 +00:00
|
|
|
|
|
|
|
@item /serverpid
|
|
|
|
Send the Assuan command @command{GETINFO pid} to the server and store
|
|
|
|
the returned PID for internal purposes.
|
|
|
|
|
2007-10-24 15:34:23 +00:00
|
|
|
@item /sleep
|
|
|
|
Sleep for a second.
|
|
|
|
|
2007-04-03 16:57:37 +00:00
|
|
|
@item /hex
|
|
|
|
@itemx /nohex
|
|
|
|
Same as the command line option @option{--hex}.
|
|
|
|
|
|
|
|
@item /decode
|
|
|
|
@itemx /nodecode
|
|
|
|
Same as the command line option @option{--decode}.
|
|
|
|
|
2007-10-19 14:51:39 +00:00
|
|
|
@item /subst
|
|
|
|
@itemx /nosubst
|
|
|
|
Enable and disable variable substitution. It defaults to disabled
|
|
|
|
unless the command line option @option{--subst} has been used.
|
2008-01-28 08:03:08 +00:00
|
|
|
If /subst as been enabled once, leading whitespace is removed from
|
2007-10-24 15:34:23 +00:00
|
|
|
input lines which makes scripts easier to read.
|
|
|
|
|
|
|
|
@item /while @var{condition}
|
|
|
|
@itemx /end
|
2012-01-27 15:40:24 +01:00
|
|
|
These commands provide a way for executing loops. All lines between
|
|
|
|
the @code{while} and the corresponding @code{end} are executed as long
|
|
|
|
as the evaluation of @var{condition} yields a non-zero value or is the
|
|
|
|
string @code{true} or @code{yes}. The evaluation is done by passing
|
|
|
|
@var{condition} to the @code{strtol} function. Example:
|
2007-10-24 15:34:23 +00:00
|
|
|
|
|
|
|
@smallexample
|
|
|
|
/subst
|
|
|
|
/let i 3
|
|
|
|
/while $i
|
2018-10-24 14:39:56 -04:00
|
|
|
/echo loop counter is $i
|
2007-10-24 15:34:23 +00:00
|
|
|
/let i $@{- $i 1@}
|
|
|
|
/end
|
|
|
|
@end smallexample
|
|
|
|
|
2012-01-27 15:40:24 +01:00
|
|
|
@item /if @var{condition}
|
|
|
|
@itemx /end
|
|
|
|
These commands provide a way for conditional execution. All lines between
|
|
|
|
the @code{if} and the corresponding @code{end} are executed only if
|
|
|
|
the evaluation of @var{condition} yields a non-zero value or is the
|
|
|
|
string @code{true} or @code{yes}. The evaluation is done by passing
|
|
|
|
@var{condition} to the @code{strtol} function.
|
2007-10-19 14:51:39 +00:00
|
|
|
|
|
|
|
@item /run @var{file}
|
|
|
|
Run commands from @var{file}.
|
|
|
|
|
|
|
|
@item /bye
|
2016-03-04 16:13:14 +00:00
|
|
|
Terminate the connection and the program.
|
2007-10-19 14:51:39 +00:00
|
|
|
|
2006-09-08 17:02:06 +00:00
|
|
|
@item /help
|
|
|
|
Print a list of available control commands.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
|
|
|
|
@ifset isman
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect see also
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg-agent}(1),
|
2006-08-18 13:05:39 +00:00
|
|
|
@command{scdaemon}(1)
|
|
|
|
@include see-also-note.texi
|
2006-09-08 17:02:06 +00:00
|
|
|
@end ifset
|
2006-08-18 13:05:39 +00:00
|
|
|
|
2010-06-10 10:39:44 +00:00
|
|
|
@c
|
|
|
|
@c DIRMNGR-CLIENT
|
|
|
|
@c
|
|
|
|
@node dirmngr-client
|
|
|
|
@section The Dirmngr Client Tool
|
|
|
|
|
|
|
|
@manpage dirmngr-client.1
|
|
|
|
@ifset manverb
|
|
|
|
.B dirmngr-client
|
|
|
|
\- Tool to access the Dirmngr services
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B dirmngr-client
|
2011-02-23 10:15:34 +01:00
|
|
|
.RI [ options ]
|
|
|
|
.RI [ certfile | pattern ]
|
2010-06-10 10:39:44 +00:00
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
|
|
|
The @command{dirmngr-client} is a simple tool to contact a running
|
|
|
|
dirmngr and test whether a certificate has been revoked --- either by
|
|
|
|
being listed in the corresponding CRL or by running the OCSP protocol.
|
|
|
|
If no dirmngr is running, a new instances will be started but this is
|
|
|
|
in general not a good idea due to the huge performance overhead.
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
The usual way to run this tool is either:
|
|
|
|
|
|
|
|
@example
|
|
|
|
dirmngr-client @var{acert}
|
|
|
|
@end example
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
or
|
|
|
|
|
|
|
|
@example
|
|
|
|
dirmngr-client <@var{acert}
|
|
|
|
@end example
|
|
|
|
|
|
|
|
Where @var{acert} is one DER encoded (binary) X.509 certificates to be
|
2011-02-23 10:15:34 +01:00
|
|
|
tested.
|
2010-06-10 10:39:44 +00:00
|
|
|
@ifclear isman
|
|
|
|
The return value of this command is
|
|
|
|
@end ifclear
|
|
|
|
|
|
|
|
@mansect return value
|
|
|
|
@ifset isman
|
|
|
|
@command{dirmngr-client} returns these values:
|
|
|
|
@end ifset
|
|
|
|
@table @code
|
|
|
|
|
2011-02-23 10:15:34 +01:00
|
|
|
@item 0
|
2010-06-10 10:39:44 +00:00
|
|
|
The certificate under question is valid; i.e. there is a valid CRL
|
2015-10-27 17:09:43 -04:00
|
|
|
available and it is not listed there or the OCSP request returned that
|
2010-06-10 10:39:44 +00:00
|
|
|
that certificate is valid.
|
|
|
|
|
|
|
|
@item 1
|
|
|
|
The certificate has been revoked
|
|
|
|
|
|
|
|
@item 2 (and other values)
|
|
|
|
There was a problem checking the revocation state of the certificate.
|
|
|
|
A message to stderr has given more detailed information. Most likely
|
|
|
|
this is due to a missing or expired CRL or due to a network problem.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@mansect options
|
|
|
|
@noindent
|
|
|
|
@command{dirmngr-client} may be called with the following options:
|
|
|
|
|
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
@item --version
|
|
|
|
@opindex version
|
|
|
|
Print the program version and licensing information. Note that you cannot
|
|
|
|
abbreviate this command.
|
|
|
|
|
|
|
|
@item --help, -h
|
|
|
|
@opindex help
|
|
|
|
Print a usage message summarizing the most useful command-line options.
|
2016-09-20 08:32:25 +02:00
|
|
|
Note that you cannot abbreviate this command.
|
2010-06-10 10:39:44 +00:00
|
|
|
|
|
|
|
@item --quiet, -q
|
|
|
|
@opindex quiet
|
|
|
|
Make the output extra brief by suppressing any informational messages.
|
|
|
|
|
|
|
|
@item -v
|
|
|
|
@item --verbose
|
|
|
|
@opindex v
|
|
|
|
@opindex verbose
|
|
|
|
Outputs additional information while running.
|
|
|
|
You can increase the verbosity by giving several
|
|
|
|
verbose commands to @sc{dirmngr}, such as @samp{-vv}.
|
|
|
|
|
|
|
|
@item --pem
|
|
|
|
@opindex pem
|
|
|
|
Assume that the given certificate is in PEM (armored) format.
|
|
|
|
|
|
|
|
@item --ocsp
|
|
|
|
@opindex ocsp
|
|
|
|
Do the check using the OCSP protocol and ignore any CRLs.
|
|
|
|
|
|
|
|
@item --force-default-responder
|
|
|
|
@opindex force-default-responder
|
2016-03-04 15:20:47 +00:00
|
|
|
When checking using the OCSP protocol, force the use of the default OCSP
|
2010-06-10 10:39:44 +00:00
|
|
|
responder. That is not to use the Reponder as given by the certificate.
|
|
|
|
|
|
|
|
@item --ping
|
|
|
|
@opindex ping
|
|
|
|
Check whether the dirmngr daemon is up and running.
|
|
|
|
|
|
|
|
@item --cache-cert
|
|
|
|
@opindex cache-cert
|
|
|
|
Put the given certificate into the cache of a running dirmngr. This is
|
|
|
|
mainly useful for debugging.
|
|
|
|
|
|
|
|
@item --validate
|
|
|
|
@opindex validate
|
|
|
|
Validate the given certificate using dirmngr's internal validation code.
|
|
|
|
This is mainly useful for debugging.
|
|
|
|
|
|
|
|
@item --load-crl
|
|
|
|
@opindex load-crl
|
|
|
|
This command expects a list of filenames with DER encoded CRL files.
|
|
|
|
With the option @option{--url} URLs are expected in place of filenames
|
|
|
|
and they are loaded directly from the given location. All CRLs will be
|
|
|
|
validated and then loaded into dirmngr's cache.
|
|
|
|
|
|
|
|
@item --lookup
|
|
|
|
@opindex lookup
|
|
|
|
Take the remaining arguments and run a lookup command on each of them.
|
|
|
|
The results are Base-64 encoded outputs (without header lines). This
|
|
|
|
may be used to retrieve certificates from a server. However the output
|
|
|
|
format is not very well suited if more than one certificate is returned.
|
|
|
|
|
|
|
|
@item --url
|
|
|
|
@itemx -u
|
|
|
|
@opindex url
|
|
|
|
Modify the @command{lookup} and @command{load-crl} commands to take an URL.
|
|
|
|
|
|
|
|
@item --local
|
|
|
|
@itemx -l
|
|
|
|
@opindex url
|
|
|
|
Let the @command{lookup} command only search the local cache.
|
|
|
|
|
|
|
|
@item --squid-mode
|
|
|
|
@opindex squid-mode
|
|
|
|
Run @sc{dirmngr-client} in a mode suitable as a helper program for
|
|
|
|
Squid's @option{external_acl_type} option.
|
|
|
|
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@ifset isman
|
|
|
|
@mansect see also
|
|
|
|
@command{dirmngr}(8),
|
|
|
|
@command{gpgsm}(1)
|
|
|
|
@include see-also-note.texi
|
|
|
|
@end ifset
|
2015-06-08 19:27:08 +02:00
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
|
2005-12-16 15:52:48 +00:00
|
|
|
@c
|
|
|
|
@c GPGPARSEMAIL
|
|
|
|
@c
|
|
|
|
@node gpgparsemail
|
|
|
|
@section Parse a mail message into an annotated format
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpage gpgparsemail.1
|
|
|
|
@ifset manverb
|
|
|
|
.B gpgparsemail
|
|
|
|
\- Parse a mail message into an annotated format
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B gpgparsemail
|
|
|
|
.RI [ options ]
|
|
|
|
.RI [ file ]
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
|
|
|
The @command{gpgparsemail} is a utility currently only useful for
|
2005-12-16 15:52:48 +00:00
|
|
|
debugging. Run it with @code{--help} for usage information.
|
|
|
|
|
|
|
|
|
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@c
|
|
|
|
@c SYMCRYPTRUN
|
|
|
|
@c
|
|
|
|
@node symcryptrun
|
2016-03-04 14:45:19 +00:00
|
|
|
@section Call a simple symmetric encryption tool
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpage symcryptrun.1
|
|
|
|
@ifset manverb
|
|
|
|
.B symcryptrun
|
|
|
|
\- Call a simple symmetric encryption tool
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
|
|
|
.B symcryptrun
|
|
|
|
.B \-\-class
|
|
|
|
.I class
|
|
|
|
.B \-\-program
|
|
|
|
.I program
|
|
|
|
.B \-\-keyfile
|
|
|
|
.I keyfile
|
|
|
|
.RB [ --decrypt | --encrypt ]
|
|
|
|
.RI [ inputfile ]
|
|
|
|
@end ifset
|
2005-04-27 13:39:16 +00:00
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect description
|
2016-03-04 16:38:09 +00:00
|
|
|
Sometimes simple encryption tools are already in use for a long time
|
|
|
|
and there might be a desire to integrate them into the GnuPG
|
|
|
|
framework. The protocols and encryption methods might be non-standard
|
|
|
|
or not even properly documented, so that a full-fledged encryption
|
|
|
|
tool with an interface like @command{gpg} is not doable.
|
|
|
|
@command{symcryptrun} provides a solution: It operates by calling the
|
|
|
|
external encryption/decryption module and provides a passphrase for a
|
|
|
|
key using the standard @command{pinentry} based mechanism through
|
|
|
|
@command{gpg-agent}.
|
2005-04-27 13:39:16 +00:00
|
|
|
|
|
|
|
Note, that @command{symcryptrun} is only available if GnuPG has been
|
|
|
|
configured with @samp{--enable-symcryptrun} at build time.
|
|
|
|
|
|
|
|
@menu
|
|
|
|
* Invoking symcryptrun:: List of all commands and options.
|
|
|
|
@end menu
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@manpause
|
2005-04-27 13:39:16 +00:00
|
|
|
@node Invoking symcryptrun
|
2016-03-04 14:45:19 +00:00
|
|
|
@subsection List of all commands and options
|
2005-04-27 13:39:16 +00:00
|
|
|
|
|
|
|
@noindent
|
|
|
|
@command{symcryptrun} is invoked this way:
|
|
|
|
|
|
|
|
@example
|
2011-02-23 10:15:34 +01:00
|
|
|
symcryptrun --class CLASS --program PROGRAM --keyfile KEYFILE
|
2005-04-27 13:39:16 +00:00
|
|
|
[--decrypt | --encrypt] [inputfile]
|
|
|
|
@end example
|
2006-08-18 13:05:39 +00:00
|
|
|
@mancont
|
2005-04-27 13:39:16 +00:00
|
|
|
|
|
|
|
For encryption, the plain text must be provided on STDIN or as the
|
|
|
|
argument @var{inputfile}, and the ciphertext will be output to STDOUT.
|
|
|
|
For decryption vice versa.
|
|
|
|
|
|
|
|
@var{CLASS} describes the calling conventions of the external tool.
|
2009-07-22 13:33:46 +00:00
|
|
|
Currently it must be given as @samp{confucius}. @var{PROGRAM} is
|
2005-04-27 13:39:16 +00:00
|
|
|
the full filename of that external tool.
|
2011-02-23 10:15:34 +01:00
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
For the class @samp{confucius} the option @option{--keyfile} is
|
|
|
|
required; @var{keyfile} is the name of a file containing the secret key,
|
|
|
|
which may be protected by a passphrase. For detailed calling
|
|
|
|
conventions, see the source code.
|
2011-02-23 10:15:34 +01:00
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@noindent
|
|
|
|
Note, that @command{gpg-agent} must be running before starting
|
|
|
|
@command{symcryptrun}.
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
The following additional options may be used:
|
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
@item -v
|
|
|
|
@itemx --verbose
|
|
|
|
@opindex verbose
|
2011-02-23 10:15:34 +01:00
|
|
|
Output additional information while running.
|
2005-04-27 13:39:16 +00:00
|
|
|
|
|
|
|
@item -q
|
|
|
|
@item --quiet
|
|
|
|
@opindex q
|
|
|
|
@opindex quiet
|
|
|
|
Try to be as quiet as possible.
|
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@include opt-homedir.texi
|
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
|
|
|
|
@item --log-file @var{file}
|
|
|
|
@opindex log-file
|
2016-08-29 11:45:47 +02:00
|
|
|
Append all logging output to @var{file}. Use @file{socket://} to log
|
|
|
|
to socket. Default is to write logging information to STDERR.
|
2005-02-24 17:36:11 +00:00
|
|
|
|
|
|
|
@end table
|
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@noindent
|
|
|
|
The possible exit status codes of @command{symcryptrun} are:
|
2005-02-24 17:36:11 +00:00
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@table @code
|
2011-02-23 10:15:34 +01:00
|
|
|
@item 0
|
2005-04-27 13:39:16 +00:00
|
|
|
Success.
|
2011-02-23 10:15:34 +01:00
|
|
|
@item 1
|
2016-08-01 22:19:15 -04:00
|
|
|
Some error occurred.
|
2011-02-23 10:15:34 +01:00
|
|
|
@item 2
|
2005-04-27 13:39:16 +00:00
|
|
|
No valid passphrase was provided.
|
2011-02-23 10:15:34 +01:00
|
|
|
@item 3
|
2005-04-27 13:39:16 +00:00
|
|
|
The operation was canceled by the user.
|
2005-02-24 17:36:11 +00:00
|
|
|
|
2005-04-27 13:39:16 +00:00
|
|
|
@end table
|
2005-02-24 17:36:11 +00:00
|
|
|
|
2006-08-18 13:05:39 +00:00
|
|
|
@mansect see also
|
2007-03-07 20:55:14 +00:00
|
|
|
@ifset isman
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg}(1),
|
|
|
|
@command{gpgsm}(1),
|
|
|
|
@command{gpg-agent}(1),
|
2007-03-07 20:55:14 +00:00
|
|
|
@end ifset
|
2006-08-18 13:05:39 +00:00
|
|
|
@include see-also-note.texi
|
|
|
|
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@c
|
2017-11-15 10:17:17 +01:00
|
|
|
@c GPGTAR
|
2008-05-06 11:05:52 +00:00
|
|
|
@c
|
2017-11-15 10:17:17 +01:00
|
|
|
@manpage gpgtar.1
|
|
|
|
@node gpgtar
|
2008-05-06 11:05:52 +00:00
|
|
|
@section Encrypt or sign files into an archive
|
|
|
|
@ifset manverb
|
2017-11-15 10:17:17 +01:00
|
|
|
.B gpgtar
|
2016-03-04 15:20:47 +00:00
|
|
|
\- Encrypt or sign files into an archive
|
2008-05-06 11:05:52 +00:00
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect synopsis
|
|
|
|
@ifset manverb
|
2017-11-15 10:17:17 +01:00
|
|
|
.B gpgtar
|
2008-05-06 11:05:52 +00:00
|
|
|
.RI [ options ]
|
|
|
|
.I filename1
|
|
|
|
.I [ filename2, ... ]
|
|
|
|
.I directory1
|
|
|
|
.I [ directory2, ... ]
|
|
|
|
@end ifset
|
|
|
|
|
|
|
|
@mansect description
|
2017-11-15 10:17:17 +01:00
|
|
|
@command{gpgtar} encrypts or signs files into an archive. It is an
|
2008-05-06 11:05:52 +00:00
|
|
|
gpg-ized tar using the same format as used by PGP's PGP Zip.
|
|
|
|
|
|
|
|
@manpause
|
|
|
|
@noindent
|
2017-11-15 10:17:17 +01:00
|
|
|
@command{gpgtar} is invoked this way:
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@example
|
2017-11-15 10:17:17 +01:00
|
|
|
gpgtar [options] @var{filename1} [@var{filename2}, ...] @var{directory} [@var{directory2}, ...]
|
2008-05-06 11:05:52 +00:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@mansect options
|
|
|
|
@noindent
|
2017-11-15 10:17:17 +01:00
|
|
|
@command{gpgtar} understands these options:
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@table @gnupgtabopt
|
|
|
|
|
2017-11-15 10:17:17 +01:00
|
|
|
@item --create
|
|
|
|
@opindex create
|
|
|
|
Put given files and directories into a vanilla ``ustar'' archive.
|
|
|
|
|
|
|
|
@item --extract
|
|
|
|
@opindex extract
|
|
|
|
Extract all files from a vanilla ``ustar'' archive.
|
|
|
|
|
2008-05-06 11:05:52 +00:00
|
|
|
@item --encrypt
|
|
|
|
@itemx -e
|
|
|
|
@opindex encrypt
|
2017-11-15 10:17:17 +01:00
|
|
|
Encrypt given files and directories into an archive. This option may
|
|
|
|
be combined with option @option{--symmetric} for an archive that may
|
|
|
|
be decrypted via a secret key or a passphrase.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --decrypt
|
|
|
|
@itemx -d
|
|
|
|
@opindex decrypt
|
2017-11-15 10:17:17 +01:00
|
|
|
Extract all files from an encrypted archive.
|
|
|
|
|
|
|
|
@item --sign
|
|
|
|
@itemx -s
|
2018-10-24 14:39:56 -04:00
|
|
|
Make a signed archive from the given files and directories. This can
|
2017-11-15 10:17:17 +01:00
|
|
|
be combined with option @option{--encrypt} to create a signed and then
|
|
|
|
encrypted archive.
|
|
|
|
|
|
|
|
@item --list-archive
|
|
|
|
@itemx -t
|
|
|
|
@opindex list-archive
|
|
|
|
List the contents of the specified archive.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --symmetric
|
|
|
|
@itemx -c
|
|
|
|
Encrypt with a symmetric cipher using a passphrase. The default
|
2017-11-15 10:17:17 +01:00
|
|
|
symmetric cipher used is @value{GPGSYMENCALGO}, but may be chosen with the
|
2008-05-06 11:05:52 +00:00
|
|
|
@option{--cipher-algo} option to @command{gpg}.
|
|
|
|
|
|
|
|
@item --recipient @var{user}
|
|
|
|
@itemx -r @var{user}
|
|
|
|
@opindex recipient
|
2017-11-15 10:17:17 +01:00
|
|
|
Encrypt for user id @var{user}. For details see @command{gpg}.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --local-user @var{user}
|
|
|
|
@itemx -u @var{user}
|
|
|
|
@opindex local-user
|
2017-11-15 10:17:17 +01:00
|
|
|
Use @var{user} as the key to sign with. For details see @command{gpg}.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --output @var{file}
|
|
|
|
@itemx -o @var{file}
|
|
|
|
@opindex output
|
2017-11-15 10:17:17 +01:00
|
|
|
Write the archive to the specified file @var{file}.
|
|
|
|
|
|
|
|
@item --verbose
|
|
|
|
@itemx -v
|
|
|
|
@opindex verbose
|
|
|
|
Enable extra informational output.
|
|
|
|
|
|
|
|
@item --quiet
|
|
|
|
@itemx -q
|
|
|
|
@opindex quiet
|
|
|
|
Try to be as quiet as possible.
|
|
|
|
|
|
|
|
@item --skip-crypto
|
|
|
|
@opindex skip-crypto
|
|
|
|
Skip all crypto operations and create or extract vanilla ``ustar''
|
|
|
|
archives.
|
|
|
|
|
|
|
|
@item --dry-run
|
|
|
|
@opindex dry-run
|
|
|
|
Do not actually output the extracted files.
|
|
|
|
|
|
|
|
@item --directory @var{dir}
|
|
|
|
@itemx -C @var{dir}
|
|
|
|
@opindex directory
|
2019-03-06 20:08:26 +01:00
|
|
|
Extract the files into the directory @var{dir}. The default is to
|
|
|
|
take the directory name from the input filename. If no input filename
|
|
|
|
is known a directory named @file{GPGARCH} is used. For tarball
|
|
|
|
creation, switch to directory @var{dir} before performing any
|
|
|
|
operations.
|
2017-11-15 10:17:17 +01:00
|
|
|
|
|
|
|
@item --files-from @var{file}
|
|
|
|
@itemx -T @var{file}
|
|
|
|
Take the file names to work from the file @var{file}; one file per
|
|
|
|
line.
|
|
|
|
|
|
|
|
@item --null
|
|
|
|
@opindex null
|
|
|
|
Modify option @option{--files-from} to use a binary nul instead of a
|
|
|
|
linefeed to separate file names.
|
|
|
|
|
|
|
|
@item --openpgp
|
|
|
|
@opindex openpgp
|
2018-10-24 14:39:56 -04:00
|
|
|
This option has no effect because OpenPGP encryption and signing is
|
2017-11-15 10:17:17 +01:00
|
|
|
the default.
|
|
|
|
|
|
|
|
@item --cms
|
|
|
|
@opindex cms
|
|
|
|
This option is reserved and shall not be used. It will eventually be
|
|
|
|
used to encrypt or sign using the CMS protocol; but that is not yet
|
|
|
|
implemented.
|
|
|
|
|
|
|
|
|
|
|
|
@item --set-filename @var{file}
|
|
|
|
@opindex set-filename
|
|
|
|
Use the last component of @var{file} as the output directory. The
|
|
|
|
default is to take the directory name from the input filename. If no
|
|
|
|
input filename is known a directory named @file{GPGARCH} is used.
|
|
|
|
This option is deprecated in favor of option @option{--directory}.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --gpg @var{gpgcmd}
|
|
|
|
@opindex gpg
|
|
|
|
Use the specified command @var{gpgcmd} instead of @command{gpg}.
|
|
|
|
|
|
|
|
@item --gpg-args @var{args}
|
|
|
|
@opindex gpg-args
|
2017-11-15 10:17:17 +01:00
|
|
|
Pass the specified extra options to @command{gpg}.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --tar-args @var{args}
|
|
|
|
@opindex tar-args
|
2017-11-15 10:17:17 +01:00
|
|
|
Assume @var{args} are standard options of the command @command{tar}
|
|
|
|
and parse them. The only supported tar options are "--directory",
|
|
|
|
"--files-from", and "--null" This is an obsolete options because those
|
|
|
|
supported tar options can also be given directly.
|
2008-05-06 11:05:52 +00:00
|
|
|
|
|
|
|
@item --version
|
|
|
|
@opindex version
|
|
|
|
Print version of the program and exit.
|
|
|
|
|
|
|
|
@item --help
|
|
|
|
@opindex help
|
|
|
|
Display a brief help page and exit.
|
|
|
|
|
|
|
|
@end table
|
|
|
|
|
|
|
|
@mansect diagnostics
|
|
|
|
@noindent
|
|
|
|
The program returns 0 if everything was fine, 1 otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
@mansect examples
|
|
|
|
@ifclear isman
|
|
|
|
@noindent
|
|
|
|
Some examples:
|
|
|
|
|
|
|
|
@end ifclear
|
|
|
|
@noindent
|
|
|
|
Encrypt the contents of directory @file{mydocs} for user Bob to file
|
|
|
|
@file{test1}:
|
|
|
|
|
|
|
|
@example
|
2017-11-15 10:17:17 +01:00
|
|
|
gpgtar --encrypt --output test1 -r Bob mydocs
|
2008-05-06 11:05:52 +00:00
|
|
|
@end example
|
|
|
|
|
|
|
|
@noindent
|
|
|
|
List the contents of archive @file{test1}:
|
|
|
|
|
|
|
|
@example
|
2017-11-15 10:17:17 +01:00
|
|
|
gpgtar --list-archive test1
|
2008-05-06 11:05:52 +00:00
|
|
|
@end example
|
|
|
|
|
|
|
|
|
|
|
|
@mansect see also
|
|
|
|
@ifset isman
|
2011-02-23 10:15:34 +01:00
|
|
|
@command{gpg}(1),
|
|
|
|
@command{tar}(1),
|
2008-05-06 11:05:52 +00:00
|
|
|
@end ifset
|
|
|
|
@include see-also-note.texi
|