{ "mode": "man", "parameter": "dirmngr", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/dirmngr/8/json", "generated": "2026-06-10T20:13:57Z", "synopsis": "dirmngr [options] command [args]", "sections": { "NAME": { "content": "dirmngr - CRL and OCSP daemon\n", "subsections": [] }, "SYNOPSIS": { "content": "dirmngr [options] command [args]\n\n", "subsections": [] }, "DESCRIPTION": { "content": "Since version 2.1 of GnuPG, dirmngr takes care of accessing the OpenPGP keyservers. As with\nprevious versions it is also used as a server for managing and downloading certificate revo‐\ncation lists (CRLs) for X.509 certificates, downloading X.509 certificates, and providing ac‐\ncess to OCSP providers. Dirmngr is invoked internally by gpg, gpgsm, or via the gpg-connect-\nagent tool.\n\n\n\n\n\n", "subsections": [] }, "COMMANDS": { "content": "Commands are not distinguished from options except for the fact that only one command is al‐\nlowed.\n\n", "subsections": [ { "name": "--version", "content": "Print the program version and licensing information. Note that you cannot abbreviate\nthis command.\n\n", "long": "--version" }, { "name": "--help, -h", "content": "Print a usage message summarizing the most useful command-line options. Note that you\ncannot abbreviate this command.\n\n", "flag": "-h", "long": "--help" }, { "name": "--dump-options", "content": "Print a list of all available options and commands. Note that you cannot abbreviate\nthis command.\n\n", "long": "--dump-options" }, { "name": "--server", "content": "Run in server mode and wait for commands on the stdin. The default mode is to create\na socket and listen for commands there. This is only used for testing.\n\n", "long": "--server" }, { "name": "--daemon", "content": "Run in background daemon mode and listen for commands on a socket. This is the way\ndirmngr is started on demand by the other GnuPG components. To force starting dirmngr\nit is in general best to use gpgconf --launch dirmngr.\n\n", "long": "--daemon" }, { "name": "--supervised", "content": "Run in the foreground, sending logs to stderr, and listening on file descriptor 3,\nwhich must already be bound to a listening socket. This is useful when running under\nsystemd or other similar process supervision schemes. This option is not supported on\nWindows.\n\n", "long": "--supervised" }, { "name": "--list-crls", "content": "List the contents of the CRL cache on stdout. This is probably only useful for debug‐\nging purposes.\n\n\n--load-crl file\nThis command requires a filename as additional argument, and it will make Dirmngr try\nto import the CRL in file into it's cache. Note, that this is only possible if Dirm‐\nngr is able to retrieve the CA's certificate directly by its own means. In general it\nis better to use gpgsm's --call-dirmngr loadcrl filename command so that gpgsm can\nhelp dirmngr.\n\n\n--fetch-crl url\nThis command requires an URL as additional argument, and it will make dirmngr try to\nretrieve and import the CRL from that url into it's cache. This is mainly useful for\ndebugging purposes. The dirmngr-client provides the same feature for a running dirm‐\nngr.\n\n", "long": "--list-crls" }, { "name": "--shutdown", "content": "This commands shuts down an running instance of Dirmngr. This command has currently\nno effect.\n\n", "long": "--shutdown" }, { "name": "--flush", "content": "This command removes all CRLs from Dirmngr's cache. Client requests will thus trigger\nreading of fresh CRLs.\n\n", "long": "--flush" } ] }, "OPTIONS": { "content": "Note that all long options with the exception of --options and --homedir may also be given in\nthe configuration file after stripping off the two leading dashes.\n\n\n\n--options file\nReads configuration from file instead of from the default per-user configuration file.\nThe default configuration file is named ‘dirmngr.conf’ and expected in the home direc‐\ntory.\n\n\n--homedir dir\nSet the name of the home directory to dir. This option is only effective when used on\nthe command line. The default is the directory named ‘.gnupg’ directly below the home\ndirectory of the user unless the environment variable GNUPGHOME has been set in which\ncase its value will be used. Many kinds of data are stored within this directory.\n\n\n", "subsections": [ { "name": "-v", "content": "", "flag": "-v" }, { "name": "--verbose", "content": "Outputs additional information while running. You can increase the verbosity by giv‐\ning several verbose commands to dirmngr, such as -vv.\n\n\n\n--log-file file\nAppend all logging output to file. This is very helpful in seeing what the agent ac‐\ntually does. Use ‘socket://’ to log to socket.\n\n\n--debug-level level\nSelect the debug level for investigating problems. level may be a numeric value or by\na keyword:\n\n\nnone No debugging at all. A value of less than 1 may be used instead of the key‐\nword.\n\nbasic Some basic debug messages. A value between 1 and 2 may be used instead of the\nkeyword.\n\nadvanced\nMore verbose debug messages. A value between 3 and 5 may be used instead of\nthe keyword.\n\nexpert Even more detailed messages. A value between 6 and 8 may be used instead of\nthe keyword.\n\nguru All of the debug messages you can get. A value greater than 8 may be used in‐\nstead of the keyword. The creation of hash tracing files is only enabled if\nthe keyword is used.\n\nHow these messages are mapped to the actual debugging flags is not specified and may change\nwith newer releases of this program. They are however carefully selected to best aid in de‐\nbugging.\n\n\n--debug flags\nSet debugging flags. This option is only useful for debugging and its behavior may\nchange with a new release. All flags are or-ed and may be given in C syntax (e.g.\n0x0042) or as a comma separated list of flag names. To get a list of all supported\nflags the single word \"help\" can be used.\n\n", "long": "--verbose" }, { "name": "--debug-all", "content": "Same as --debug=0xffffffff\n\n\n--tls-debug level\nEnable debugging of the TLS layer at level. The details of the debug level depend on\nthe used TLS library and are not set in stone.\n\n\n--debug-wait n\nWhen running in server mode, wait n seconds before entering the actual processing loop\nand print the pid. This gives time to attach a debugger.\n\n", "long": "--debug-all" }, { "name": "--disable-check-own-socket", "content": "On some platforms dirmngr is able to detect the removal of its socket file and shut‐\ndown itself. This option disable this self-test for debugging purposes.\n\n", "long": "--disable-check-own-socket" }, { "name": "-s", "content": "", "flag": "-s" }, { "name": "--sh", "content": "", "long": "--sh" }, { "name": "-c", "content": "--csh Format the info output in daemon mode for use with the standard Bourne shell respec‐\ntive the C-shell. The default is to guess it based on the environment variable SHELL\nwhich is in almost all cases sufficient.\n\n", "flag": "-c" }, { "name": "--force", "content": "Enabling this option forces loading of expired CRLs; this is only useful for debug‐\nging.\n\n", "long": "--force" }, { "name": "--use-tor", "content": "", "long": "--use-tor" }, { "name": "--no-use-tor", "content": "The option --use-tor switches Dirmngr and thus GnuPG into ``Tor mode'' to route all\nnetwork access via Tor (an anonymity network). Certain other features are disabled in\nthis mode. The effect of --use-tor cannot be overridden by any other command or even\nby reloading dirmngr. The use of --no-use-tor disables the use of Tor. The default\nis to use Tor if it is available on startup or after reloading dirmngr.\n\n", "long": "--no-use-tor" }, { "name": "--standard-resolver", "content": "This option forces the use of the system's standard DNS resolver code. This is mainly\nused for debugging. Note that on Windows a standard resolver is not used and all DNS\naccess will return the error ``Not Implemented'' if this option is used. Using this\ntogether with enabled Tor mode returns the error ``Not Enabled''.\n\n", "long": "--standard-resolver" }, { "name": "--recursive-resolver", "content": "When possible use a recursive resolver instead of a stub resolver.\n\n\n--resolver-timeout n\nSet the timeout for the DNS resolver to N seconds. The default are 30 seconds.\n\n\n--connect-timeout n\n\n--connect-quick-timeout n\nSet the timeout for HTTP and generic TCP connection attempts to N seconds. The value\nset with the quick variant is used when the --quick option has been given to certain\nAssuan commands. The quick value is capped at the value of the regular connect time‐\nout. The default values are 15 and 2 seconds. Note that the timeout values are for\neach connection attempt; the connection code will attempt to connect all addresses\nlisted for a server.\n\n\n--listen-backlog n\nSet the size of the queue for pending connections. The default is 64.\n\n", "long": "--recursive-resolver" }, { "name": "--allow-version-check", "content": "Allow Dirmngr to connect to https://versions.gnupg.org to get the list of current\nsoftware versions. On debian-packaged versions, this option does nothing since soft‐\nware updates should be handled by the distribution. See the option --query-swdb of\nthe command gpgconf for more details. Note, that regardless of this option a version\ncheck can always be triggered using this command:\n\ngpg-connect-agent --dirmngr 'loadswdb --force' /bye\n\n\n\n--keyserver name\nUse name as your keyserver. This is the server that gpg communicates with to receive\nkeys, send keys, and search for keys. The format of the name is a URI:\n`scheme:[//]keyservername[:port]' The scheme is the type of keyserver: \"hkp\" for the\nHTTP (or compatible) keyservers, \"ldap\" for the LDAP keyservers, or \"mailto\" for the\nGraff email keyserver. Note that your particular installation of GnuPG may have other\nkeyserver types available as well. Keyserver schemes are case-insensitive. After the\nkeyserver name, optional keyserver configuration options may be provided. These are\nthe same as the --keyserver-options of gpg, but apply only to this particular key‐\nserver.\n\nMost keyservers synchronize with each other, so there is generally no need to send\nkeys to more than one server. The keyserver hkp://keys.gnupg.net uses round robin DNS\nto give a different keyserver each time you use it.\n\nIf exactly two keyservers are configured and only one is a Tor hidden service\n(.onion), Dirmngr selects the keyserver to use depending on whether Tor is locally\nrunning or not. The check for a running Tor is done for each new connection.\n\nIf no keyserver is explicitly configured, dirmngr will use the built-in default of\nhkps://keys.openpgp.org.\n\nNote that the above default is a Debian-specific choice. Upstream GnuPG prefers\nhkps://hkps.pool.sks-keyservers.net. See /usr/share/doc/gpgconf/NEWS.Debian.gz for\nmore details.\n\nWindows users with a keyserver running on their Active Directory should use ldap:///\nfor name to access this directory.\n\nFor accessing anonymous LDAP keyservers name is in general just a ldaps://ldap.exam‐‐\nple.com. A BaseDN parameter should never be specified. If authentication is required\nthe value of name is for example:\n\nkeyserver ldaps://ldap.example.com/????bindname=uid=USERNAME\n%2Cou=GnuPG%20Users%2Cdc=example%2Cdc=com,password=PASSWORD\n\nPut this all on one line without any spaces and keep the '%2C' as given.\nReplace USERNAME, PASSWORD, and the 'dc' parts according to the\ninstructions received from the LDAP administrator. Note that only\nsimple authentication (i.e. cleartext passwords) is supported and thus\nusing ldaps is strongly suggested.\n\n\n--nameserver ipaddr\nIn ``Tor mode'' Dirmngr uses a public resolver via Tor to resolve DNS names. If the\ndefault public resolver, which is 8.8.8.8, shall not be used a different one can be\ngiven using this option. Note that a numerical IP address must be given (IPv6 or\nIPv4) and that no error checking is done for ipaddr.\n\n", "long": "--allow-version-check" }, { "name": "--disable-ipv4", "content": "", "long": "--disable-ipv4" }, { "name": "--disable-ipv6", "content": "Disable the use of all IPv4 or IPv6 addresses.\n\n", "long": "--disable-ipv6" }, { "name": "--disable-ldap", "content": "Entirely disables the use of LDAP.\n\n", "long": "--disable-ldap" }, { "name": "--disable-http", "content": "Entirely disables the use of HTTP.\n\n", "long": "--disable-http" }, { "name": "--ignore-http-dp", "content": "When looking for the location of a CRL, the to be tested certificate usually contains\nso called CRL Distribution Point (DP) entries which are URLs describing the way to ac‐\ncess the CRL. The first found DP entry is used. With this option all entries using\nthe HTTP scheme are ignored when looking for a suitable DP.\n\n", "long": "--ignore-http-dp" }, { "name": "--ignore-ldap-dp", "content": "This is similar to --ignore-http-dp but ignores entries using the LDAP scheme. Both\noptions may be combined resulting in ignoring DPs entirely.\n\n", "long": "--ignore-ldap-dp" }, { "name": "--ignore-ocsp-service-url", "content": "Ignore all OCSP URLs contained in the certificate. The effect is to force the use of\nthe default responder.\n\n", "long": "--ignore-ocsp-service-url" }, { "name": "--honor-http-proxy", "content": "If the environment variable ‘httpproxy’ has been set, use its value to access HTTP\nservers.\n\n\n--http-proxy host[:port]\nUse host and port to access HTTP servers. The use of this option overrides the envi‐\nronment variable ‘httpproxy’ regardless whether --honor-http-proxy has been set.\n\n\n\n--ldap-proxy host[:port]\nUse host and port to connect to LDAP servers. If port is omitted, port 389 (standard\nLDAP port) is used. This overrides any specified host and port part in a LDAP URL and\nwill also be used if host and port have been omitted from the URL.\n\n", "long": "--honor-http-proxy" }, { "name": "--only-ldap-proxy", "content": "Never use anything else but the LDAP \"proxy\" as configured with --ldap-proxy. Usually\ndirmngr tries to use other configured LDAP server if the connection using the \"proxy\"\nfailed.\n\n\n\n--ldapserverlist-file file\nRead the list of LDAP servers to consult for CRLs and certificates from file instead\nof the default per-user ldap server list file. The default value for file is ‘dirm‐\nngrldapservers.conf’.\n\nThis server list file contains one LDAP server per line in the format\n\nhostname:port:username:password:basedn\n\nLines starting with a ‘#’ are comments.\n\nNote that as usual all strings entered are expected to be UTF-8 encoded. Obviously\nthis will lead to problems if the password has originally been encoded as Latin-1.\nThere is no other solution here than to put such a password in the binary encoding\ninto the file (i.e. non-ascii characters won't show up readable). ([The gpgconf tool\nmight be helpful for frontends as it enables editing this configuration file using\npercent-escaped strings.])\n\n\n\n--ldaptimeout secs\nSpecify the number of seconds to wait for an LDAP query before timing out. The de‐\nfault are 15 seconds. 0 will never timeout.\n\n\n", "long": "--only-ldap-proxy" }, { "name": "--add-servers", "content": "This option makes dirmngr add any servers it discovers when validating certificates\nagainst CRLs to the internal list of servers to consult for certificates and CRLs.\n\nThis option is useful when trying to validate a certificate that has a CRL distribu‐\ntion point that points to a server that is not already listed in the ldapserverlist.\nDirmngr will always go to this server and try to download the CRL, but chances are\nhigh that the certificate used to sign the CRL is located on the same server. So if\ndirmngr doesn't add that new server to list, it will often not be able to verify the\nsignature of the CRL unless the --add-servers option is used.\n\nNote: The current version of dirmngr has this option disabled by default.\n\n\n", "long": "--add-servers" }, { "name": "--allow-ocsp", "content": "This option enables OCSP support if requested by the client.\n\nOCSP requests are rejected by default because they may violate the privacy of the\nuser; for example it is possible to track the time when a user is reading a mail.\n\n\n\n--ocsp-responder url\nUse url as the default OCSP Responder if the certificate does not contain information\nabout an assigned responder. Note, that --ocsp-signer must also be set to a valid\ncertificate.\n\n\n--ocsp-signer fpr|file\nUse the certificate with the fingerprint fpr to check the responses of the default\nOCSP Responder. Alternatively a filename can be given in which case the response is\nexpected to be signed by one of the certificates described in that file. Any argument\nwhich contains a slash, dot or tilde is considered a filename. Usual filename expan‐\nsion takes place: A tilde at the start followed by a slash is replaced by the content\nof ‘HOME’, no slash at start describes a relative filename which will be searched at\nthe home directory. To make sure that the file is searched in the home directory, ei‐\nther prepend the name with \"./\" or use a name which contains a dot.\n\nIf a response has been signed by a certificate described by these fingerprints no fur‐\nther check upon the validity of this certificate is done.\n\nThe format of the FILE is a list of SHA-1 fingerprint, one per line with optional\ncolons between the bytes. Empty lines and lines prefix with a hash mark are ignored.\n\n\n\n--ocsp-max-clock-skew n\nThe number of seconds a skew between the OCSP responder and them local clock is ac‐\ncepted. Default is 600 (10 minutes).\n\n\n--ocsp-max-period n\nSeconds a response is at maximum considered valid after the time given in the thisUp‐\ndate field. Default is 7776000 (90 days).\n\n\n--ocsp-current-period n\nThe number of seconds an OCSP response is considered valid after the time given in the\nNEXTUPDATE datum. Default is 10800 (3 hours).\n\n\n\n--max-replies n\nDo not return more that n items in one query. The default is 10.\n\n\n--ignore-cert-extension oid\nAdd oid to the list of ignored certificate extensions. The oid is expected to be in\ndotted decimal form, like 2.5.29.3. This option may be used more than once. Critical\nflagged certificate extensions matching one of the OIDs in the list are treated as if\nthey are actually handled and thus the certificate won't be rejected due to an unknown\ncritical extension. Use this option with care because extensions are usually flagged\nas critical for a reason.\n\n\n--hkp-cacert file\nUse the root certificates in file for verification of the TLS certificates used with\nhkps (keyserver access over TLS). If the file is in PEM format a suffix of .pem is\nexpected for file. This option may be given multiple times to add more root certifi‐\ncates. Tilde expansion is supported.\n\nIf no hkp-cacert directive is present, dirmngr will make a reasonable choice: if the\nkeyserver in question is the special pool hkps.pool.sks-keyservers.net, it will use\nthe bundled root certificate for that pool. Otherwise, it will use the system CAs.\n\n", "long": "--allow-ocsp" } ] }, "EXAMPLES": { "content": "Here is an example on how to show dirmngr's internal table of OpenPGP keyserver addresses.\nThe output is intended for debugging purposes and not part of a defined API.\n\ngpg-connect-agent --dirmngr 'keyserver --hosttable' /bye\n\nTo inhibit the use of a particular host you have noticed in one of the keyserver pools, you\nmay use\n\ngpg-connect-agent --dirmngr 'keyserver --dead pgpkeys.bnd.de' /bye\n\nThe description of the keyserver command can be printed using\n\ngpg-connect-agent --dirmngr 'help keyserver' /bye\n\n\n\n\n", "subsections": [] }, "FILES": { "content": "Dirmngr makes use of several directories when running in daemon mode: There are a few config‐\nuration files whih control the operation of dirmngr. By default they may all be found in the\ncurrent home directory (see: [option --homedir]).\n\n\n", "subsections": [ { "name": "dirmngr.conf", "content": "This is the standard configuration file read by dirmngr on startup. It may contain\nany valid long option; the leading two dashes may not be entered and the option may\nnot be abbreviated. This file is also read after a SIGHUP however not all options\nwill actually have an effect. This default name may be changed on the command line\n(see: [option --options]). You should backup this file.\n\n" }, { "name": "/etc/gnupg/trusted-certs", "content": "This directory should be filled with certificates of Root CAs you are trusting in\nchecking the CRLs and signing OCSP Responses.\n\nUsually these are the same certificates you use with the applications making use of\ndirmngr. It is expected that each of these certificate files contain exactly one DER\nencoded certificate in a file with the suffix ‘.crt’ or ‘.der’. dirmngr reads those\ncertificates on startup and when given a SIGHUP. Certificates which are not readable\nor do not make up a proper X.509 certificate are ignored; see the log file for de‐\ntails.\n\nApplications using dirmngr (e.g. gpgsm) can request these certificates to complete a\ntrust chain in the same way as with the extra-certs directory (see below).\n\nNote that for OCSP responses the certificate specified using the option --ocsp-signer\nis always considered valid to sign OCSP requests.\n\n" }, { "name": "/etc/gnupg/extra-certs", "content": "This directory may contain extra certificates which are preloaded into the internal\ncache on startup. Applications using dirmngr (e.g. gpgsm) can request cached certifi‐\ncates to complete a trust chain. This is convenient in cases you have a couple inter‐\nmediate CA certificates or certificates usually used to sign OCSP responses. These\ncertificates are first tried before going out to the net to look for them. These cer‐\ntificates must also be DER encoded and suffixed with ‘.crt’ or ‘.der’.\n\n" }, { "name": "~/.gnupg/crls.d", "content": "This directory is used to store cached CRLs. The ‘crls.d’ part will be created by\ndirmngr if it does not exists but you need to make sure that the upper directory ex‐\nists.\n\n\n" } ] }, "SIGNALS": { "content": "A running dirmngr may be controlled by signals, i.e. using the kill command to send a signal\nto the process.\n\nHere is a list of supported signals:\n\n\n\nSIGHUP This signal flushes all internally cached CRLs as well as any cached certificates.\nThen the certificate cache is reinitialized as on startup. Options are re-read from\nthe configuration file. Instead of sending this signal it is better to use\ngpgconf --reload dirmngr\n\n\nSIGTERM\nShuts down the process but waits until all current requests are fulfilled. If the\nprocess has received 3 of these signals and requests are still pending, a shutdown is\nforced. You may also use\ngpgconf --kill dirmngr\ninstead of this signal\n\n\nSIGINT Shuts down the process immediately.\n\n\n\nSIGUSR1\nThis prints some caching statistics to the log file.\n\n", "subsections": [] }, "SEE ALSO": { "content": "gpgsm(1), dirmngr-client(1)\n\nThe full documentation for this tool is maintained as a Texinfo manual. If GnuPG and the\ninfo program are properly installed at your site, the command\n\ninfo gnupg\n\nshould give you access to the complete manual including a menu structure and an index.\n\n\n\n\n\nGnuPG 2.2.27 2020-12-21 DIRMNGR(8)", "subsections": [] } }, "summary": "dirmngr - CRL and OCSP daemon", "flags": [ { "flag": "-v", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--verbose", "arg": null, "description": "Outputs additional information while running. You can increase the verbosity by giv‐ ing several verbose commands to dirmngr, such as -vv. --log-file file Append all logging output to file. This is very helpful in seeing what the agent ac‐ tually does. Use ‘socket://’ to log to socket. --debug-level level Select the debug level for investigating problems. level may be a numeric value or by a keyword: none No debugging at all. A value of less than 1 may be used instead of the key‐ word. basic Some basic debug messages. A value between 1 and 2 may be used instead of the keyword. advanced More verbose debug messages. A value between 3 and 5 may be used instead of the keyword. expert Even more detailed messages. A value between 6 and 8 may be used instead of the keyword. guru All of the debug messages you can get. A value greater than 8 may be used in‐ stead of the keyword. The creation of hash tracing files is only enabled if the keyword is used. How these messages are mapped to the actual debugging flags is not specified and may change with newer releases of this program. They are however carefully selected to best aid in de‐ bugging. --debug flags Set debugging flags. This option is only useful for debugging and its behavior may change with a new release. All flags are or-ed and may be given in C syntax (e.g. 0x0042) or as a comma separated list of flag names. To get a list of all supported flags the single word \"help\" can be used." }, { "flag": "", "long": "--debug-all", "arg": null, "description": "Same as --debug=0xffffffff --tls-debug level Enable debugging of the TLS layer at level. The details of the debug level depend on the used TLS library and are not set in stone. --debug-wait n When running in server mode, wait n seconds before entering the actual processing loop and print the pid. This gives time to attach a debugger." }, { "flag": "", "long": "--disable-check-own-socket", "arg": null, "description": "On some platforms dirmngr is able to detect the removal of its socket file and shut‐ down itself. This option disable this self-test for debugging purposes." }, { "flag": "-s", "long": null, "arg": null, "description": "" }, { "flag": "", "long": "--sh", "arg": null, "description": "" }, { "flag": "-c", "long": null, "arg": null, "description": "--csh Format the info output in daemon mode for use with the standard Bourne shell respec‐ tive the C-shell. The default is to guess it based on the environment variable SHELL which is in almost all cases sufficient." }, { "flag": "", "long": "--force", "arg": null, "description": "Enabling this option forces loading of expired CRLs; this is only useful for debug‐ ging." }, { "flag": "", "long": "--use-tor", "arg": null, "description": "" }, { "flag": "", "long": "--no-use-tor", "arg": null, "description": "The option --use-tor switches Dirmngr and thus GnuPG into ``Tor mode'' to route all network access via Tor (an anonymity network). Certain other features are disabled in this mode. The effect of --use-tor cannot be overridden by any other command or even by reloading dirmngr. The use of --no-use-tor disables the use of Tor. The default is to use Tor if it is available on startup or after reloading dirmngr." }, { "flag": "", "long": "--standard-resolver", "arg": null, "description": "This option forces the use of the system's standard DNS resolver code. This is mainly used for debugging. Note that on Windows a standard resolver is not used and all DNS access will return the error ``Not Implemented'' if this option is used. Using this together with enabled Tor mode returns the error ``Not Enabled''." }, { "flag": "", "long": "--recursive-resolver", "arg": null, "description": "When possible use a recursive resolver instead of a stub resolver. --resolver-timeout n Set the timeout for the DNS resolver to N seconds. The default are 30 seconds. --connect-timeout n --connect-quick-timeout n Set the timeout for HTTP and generic TCP connection attempts to N seconds. The value set with the quick variant is used when the --quick option has been given to certain Assuan commands. The quick value is capped at the value of the regular connect time‐ out. The default values are 15 and 2 seconds. Note that the timeout values are for each connection attempt; the connection code will attempt to connect all addresses listed for a server. --listen-backlog n Set the size of the queue for pending connections. The default is 64." }, { "flag": "", "long": "--allow-version-check", "arg": null, "description": "Allow Dirmngr to connect to https://versions.gnupg.org to get the list of current software versions. On debian-packaged versions, this option does nothing since soft‐ ware updates should be handled by the distribution. See the option --query-swdb of the command gpgconf for more details. Note, that regardless of this option a version check can always be triggered using this command: gpg-connect-agent --dirmngr 'loadswdb --force' /bye --keyserver name Use name as your keyserver. This is the server that gpg communicates with to receive keys, send keys, and search for keys. The format of the name is a URI: `scheme:[//]keyservername[:port]' The scheme is the type of keyserver: \"hkp\" for the HTTP (or compatible) keyservers, \"ldap\" for the LDAP keyservers, or \"mailto\" for the Graff email keyserver. Note that your particular installation of GnuPG may have other keyserver types available as well. Keyserver schemes are case-insensitive. After the keyserver name, optional keyserver configuration options may be provided. These are the same as the --keyserver-options of gpg, but apply only to this particular key‐ server. Most keyservers synchronize with each other, so there is generally no need to send keys to more than one server. The keyserver hkp://keys.gnupg.net uses round robin DNS to give a different keyserver each time you use it. If exactly two keyservers are configured and only one is a Tor hidden service (.onion), Dirmngr selects the keyserver to use depending on whether Tor is locally running or not. The check for a running Tor is done for each new connection. If no keyserver is explicitly configured, dirmngr will use the built-in default of hkps://keys.openpgp.org. Note that the above default is a Debian-specific choice. Upstream GnuPG prefers hkps://hkps.pool.sks-keyservers.net. See /usr/share/doc/gpgconf/NEWS.Debian.gz for more details. Windows users with a keyserver running on their Active Directory should use ldap:/// for name to access this directory. For accessing anonymous LDAP keyservers name is in general just a ldaps://ldap.exam‐‐ ple.com. A BaseDN parameter should never be specified. If authentication is required the value of name is for example: keyserver ldaps://ldap.example.com/????bindname=uid=USERNAME %2Cou=GnuPG%20Users%2Cdc=example%2Cdc=com,password=PASSWORD Put this all on one line without any spaces and keep the '%2C' as given. Replace USERNAME, PASSWORD, and the 'dc' parts according to the instructions received from the LDAP administrator. Note that only simple authentication (i.e. cleartext passwords) is supported and thus using ldaps is strongly suggested. --nameserver ipaddr In ``Tor mode'' Dirmngr uses a public resolver via Tor to resolve DNS names. If the default public resolver, which is 8.8.8.8, shall not be used a different one can be given using this option. Note that a numerical IP address must be given (IPv6 or IPv4) and that no error checking is done for ipaddr." }, { "flag": "", "long": "--disable-ipv4", "arg": null, "description": "" }, { "flag": "", "long": "--disable-ipv6", "arg": null, "description": "Disable the use of all IPv4 or IPv6 addresses." }, { "flag": "", "long": "--disable-ldap", "arg": null, "description": "Entirely disables the use of LDAP." }, { "flag": "", "long": "--disable-http", "arg": null, "description": "Entirely disables the use of HTTP." }, { "flag": "", "long": "--ignore-http-dp", "arg": null, "description": "When looking for the location of a CRL, the to be tested certificate usually contains so called CRL Distribution Point (DP) entries which are URLs describing the way to ac‐ cess the CRL. The first found DP entry is used. With this option all entries using the HTTP scheme are ignored when looking for a suitable DP." }, { "flag": "", "long": "--ignore-ldap-dp", "arg": null, "description": "This is similar to --ignore-http-dp but ignores entries using the LDAP scheme. Both options may be combined resulting in ignoring DPs entirely." }, { "flag": "", "long": "--ignore-ocsp-service-url", "arg": null, "description": "Ignore all OCSP URLs contained in the certificate. The effect is to force the use of the default responder." }, { "flag": "", "long": "--honor-http-proxy", "arg": null, "description": "If the environment variable ‘httpproxy’ has been set, use its value to access HTTP servers. --http-proxy host[:port] Use host and port to access HTTP servers. The use of this option overrides the envi‐ ronment variable ‘httpproxy’ regardless whether --honor-http-proxy has been set. --ldap-proxy host[:port] Use host and port to connect to LDAP servers. If port is omitted, port 389 (standard LDAP port) is used. This overrides any specified host and port part in a LDAP URL and will also be used if host and port have been omitted from the URL." }, { "flag": "", "long": "--only-ldap-proxy", "arg": null, "description": "Never use anything else but the LDAP \"proxy\" as configured with --ldap-proxy. Usually dirmngr tries to use other configured LDAP server if the connection using the \"proxy\" failed. --ldapserverlist-file file Read the list of LDAP servers to consult for CRLs and certificates from file instead of the default per-user ldap server list file. The default value for file is ‘dirm‐ ngrldapservers.conf’. This server list file contains one LDAP server per line in the format hostname:port:username:password:basedn Lines starting with a ‘#’ are comments. Note that as usual all strings entered are expected to be UTF-8 encoded. Obviously this will lead to problems if the password has originally been encoded as Latin-1. There is no other solution here than to put such a password in the binary encoding into the file (i.e. non-ascii characters won't show up readable). ([The gpgconf tool might be helpful for frontends as it enables editing this configuration file using percent-escaped strings.]) --ldaptimeout secs Specify the number of seconds to wait for an LDAP query before timing out. The de‐ fault are 15 seconds. 0 will never timeout." }, { "flag": "", "long": "--add-servers", "arg": null, "description": "This option makes dirmngr add any servers it discovers when validating certificates against CRLs to the internal list of servers to consult for certificates and CRLs. This option is useful when trying to validate a certificate that has a CRL distribu‐ tion point that points to a server that is not already listed in the ldapserverlist. Dirmngr will always go to this server and try to download the CRL, but chances are high that the certificate used to sign the CRL is located on the same server. So if dirmngr doesn't add that new server to list, it will often not be able to verify the signature of the CRL unless the --add-servers option is used. Note: The current version of dirmngr has this option disabled by default." }, { "flag": "", "long": "--allow-ocsp", "arg": null, "description": "This option enables OCSP support if requested by the client. OCSP requests are rejected by default because they may violate the privacy of the user; for example it is possible to track the time when a user is reading a mail. --ocsp-responder url Use url as the default OCSP Responder if the certificate does not contain information about an assigned responder. Note, that --ocsp-signer must also be set to a valid certificate. --ocsp-signer fpr|file Use the certificate with the fingerprint fpr to check the responses of the default OCSP Responder. Alternatively a filename can be given in which case the response is expected to be signed by one of the certificates described in that file. Any argument which contains a slash, dot or tilde is considered a filename. Usual filename expan‐ sion takes place: A tilde at the start followed by a slash is replaced by the content of ‘HOME’, no slash at start describes a relative filename which will be searched at the home directory. To make sure that the file is searched in the home directory, ei‐ ther prepend the name with \"./\" or use a name which contains a dot. If a response has been signed by a certificate described by these fingerprints no fur‐ ther check upon the validity of this certificate is done. The format of the FILE is a list of SHA-1 fingerprint, one per line with optional colons between the bytes. Empty lines and lines prefix with a hash mark are ignored. --ocsp-max-clock-skew n The number of seconds a skew between the OCSP responder and them local clock is ac‐ cepted. Default is 600 (10 minutes). --ocsp-max-period n Seconds a response is at maximum considered valid after the time given in the thisUp‐ date field. Default is 7776000 (90 days). --ocsp-current-period n The number of seconds an OCSP response is considered valid after the time given in the NEXTUPDATE datum. Default is 10800 (3 hours). --max-replies n Do not return more that n items in one query. The default is 10. --ignore-cert-extension oid Add oid to the list of ignored certificate extensions. The oid is expected to be in dotted decimal form, like 2.5.29.3. This option may be used more than once. Critical flagged certificate extensions matching one of the OIDs in the list are treated as if they are actually handled and thus the certificate won't be rejected due to an unknown critical extension. Use this option with care because extensions are usually flagged as critical for a reason. --hkp-cacert file Use the root certificates in file for verification of the TLS certificates used with hkps (keyserver access over TLS). If the file is in PEM format a suffix of .pem is expected for file. This option may be given multiple times to add more root certifi‐ cates. Tilde expansion is supported. If no hkp-cacert directive is present, dirmngr will make a reasonable choice: if the keyserver in question is the special pool hkps.pool.sks-keyservers.net, it will use the bundled root certificate for that pool. Otherwise, it will use the system CAs." } ], "examples": [ "Here is an example on how to show dirmngr's internal table of OpenPGP keyserver addresses.", "The output is intended for debugging purposes and not part of a defined API.", "gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye", "To inhibit the use of a particular host you have noticed in one of the keyserver pools, you", "may use", "gpg-connect-agent --dirmngr 'keyserver --dead pgpkeys.bnd.de' /bye", "The description of the keyserver command can be printed using", "gpg-connect-agent --dirmngr 'help keyserver' /bye" ], "see_also": [ { "name": "gpgsm", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/gpgsm/1/json" }, { "name": "dirmngr-client", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/dirmngr-client/1/json" } ] }