{
    "mode": "man",
    "parameter": "gpgconf",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/gpgconf/1/json",
    "generated": "2026-05-30T05:14:56Z",
    "synopsis": "gpgconf [options] --list-components\ngpgconf [options] --list-options component\ngpgconf [options] --change-options component",
    "sections": {
        "NAME": {
            "content": "gpgconf - Modify .gnupg home directories\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "gpgconf [options] --list-components\ngpgconf [options] --list-options component\ngpgconf [options] --change-options component\n\n\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "The  gpgconf  is a utility to automatically and reasonable safely query and modify configura‐\ntion files in the ‘.gnupg’ home directory.  It is designed not to be invoked manually by  the\nuser,  but  automatically by graphical user interfaces (GUI). ([Please note that currently no\nlocking is done, so concurrent access should be avoided.  There are some precautions to avoid\ncorruption  with  concurrent  usage, but results may be inconsistent and some changes may get\nlost.  The stateless design makes it difficult to provide more guarantees.])\n\ngpgconf provides access to the configuration of one or more components of the  GnuPG  system.\nThese  components  correspond more or less to the programs that exist in the GnuPG framework,\nlike GPG, GPGSM, DirMngr, etc.  But this is not a strict one-to-one  relationship.   Not  all\nconfiguration options are available through gpgconf.  gpgconf provides a generic and abstract\nmethod to access the most important configuration options that can feasibly be controlled via\nsuch a mechanism.\n\ngpgconf  can  be  used  to gather and change the options available in each component, and can\nalso provide their default values.  gpgconf will give detailed type information that  can  be\nused to restrict the user's input without making an attempt to commit the changes.\n\ngpgconf  provides the backend of a configuration editor.  The configuration editor would usu‐\nally be a graphical user interface program that displays the current options,  their  default\nvalues,  and  allows the user to make changes to the options.  These changes can then be made\nactive with gpgconf again.  Such a program that uses gpgconf in this way will be  called  GUI\nthroughout this section.\n\n\n",
            "subsections": []
        },
        "COMMANDS": {
            "content": "One of the following commands must be given:\n\n\n",
            "subsections": [
                {
                    "name": "--list-components",
                    "content": "List all components.  This is the default command used if none is specified.\n\n",
                    "long": "--list-components"
                },
                {
                    "name": "--check-programs",
                    "content": "List all available backend programs and test whether they are runnable.\n\n\n--list-options component\nList all options of the component component.\n\n\n--change-options component\nChange the options of the component component.\n\n\n--check-options component\nCheck the options for the component component.\n\n\n--apply-profile file\nApply  the  configuration settings listed in file to the configuration files.  If file\nhas no suffix and no slashes the command first tries to read a file  with  the  suffix\n.prf  from  the  data directory (gpgconf --list-dirs datadir) before it reads the file\nverbatim.  A profile is divided into sections using  the  bracketed   component  name.\nEach  section  then  lists the option which shall go into the respective configuration\nfile.\n\n",
                    "long": "--check-programs"
                },
                {
                    "name": "--apply-defaults",
                    "content": "Update all configuration files with values taken from the  global  configuration  file\n(usually ‘/etc/gnupg/gpgconf.conf’).\n\n\n--list-dirs [names]\nLists  the  directories  used  by gpgconf.  One directory is listed per line, and each\nline consists of a colon-separated list where the first field names the directory type\n(for  example sysconfdir) and the second field contains the percent-escaped directory.\nAlthough they are not directories, the socket file names used by gpg-agent and dirmngr\nare  printed  as  well.  Note that the socket file names and the homedir lines are the\ndefault names and they may be overridden by command line switches.  If names are given\nonly the directories or file names specified by the list names are printed without any\nescaping.\n\n\n--list-config [filename]\nList the global configuration file in a colon separated format.  If filename is given,\ncheck that file instead.\n\n\n--check-config [filename]\nRun a syntax check on the global configuration file.  If filename is given, check that\nfile instead.\n\n\n\n--query-swdb packagename [versionstring]\nReturns the current version for packagename and if versionstring is  given  also  an\nindicator  on  whether an update is available.  The actual file with the software ver‐\nsion is automatically downloaded and checked by dirmngr.  dirmngr uses a thresholds to\navoid  download  the file too often and it does this by default only if it can be done\nvia Tor.  To force an update of that file this command can be used:\n\ngpg-connect-agent --dirmngr 'loadswdb --force' /bye\n\n\n\n--reload [component]\nReload all or the given component. This is basically the same as sending a  SIGHUP  to\nthe  component.  Components which don't support reloading are ignored.  Without compo‐\nnent or by using \"all\" for component all components which are daemons are reloaded.\n\n\n--launch [component]\nIf the component is not already running, start it.  component must be a daemon.   This\nis  in  general  not required because the system starts these daemons as needed.  How‐\never, external software making direct use of gpg-agent or dirmngr may use this command\nto  ensure  that  they are started.  Using \"all\" for component launches all components\nwhich are daemons.\n\n\n--kill [component]\nKill the given component that runs as a daemon, including gpg-agent, dirmngr, and  sc‐‐\ndaemon.   A component which does not run as a daemon will be ignored.  Using \"all\" for\ncomponent kills all components running as daemons.  Note that as  of  now  reload  and\nkill have the same effect for scdaemon.\n\n",
                    "long": "--apply-defaults"
                },
                {
                    "name": "--create-socketdir",
                    "content": "Create  a  directory for sockets below /run/user or /var/run/user.  This is command is\nonly required if a non default home directory is used and the /run based sockets shall\nbe used.  For the default home directory GnUPG creates a directory on the fly.\n\n",
                    "long": "--create-socketdir"
                },
                {
                    "name": "--remove-socketdir",
                    "content": "Remove a directory created with command --create-socketdir.\n\n",
                    "long": "--remove-socketdir"
                }
            ]
        },
        "OPTIONS": {
            "content": "The following options may be used:\n\n\n",
            "subsections": [
                {
                    "name": "-o",
                    "content": "--output file\nWrite output to file.  Default is to write to stdout.\n\n",
                    "flag": "-o"
                },
                {
                    "name": "-v",
                    "content": "",
                    "flag": "-v"
                },
                {
                    "name": "--verbose",
                    "content": "Outputs  additional  information  while running.  Specifically, this extends numerical\nfield values by human-readable descriptions.\n\n",
                    "long": "--verbose"
                },
                {
                    "name": "-q",
                    "content": "",
                    "flag": "-q"
                },
                {
                    "name": "--quiet",
                    "content": "Try to be as quiet as possible.\n\n\n--homedir dir\nSet the name of the home directory to dir. If this option is not used, the home direc‐\ntory  defaults  to  ‘~/.gnupg’.  It is only recognized when given on the command line.\nIt  also  overrides  any  home  directory  stated  through  the  environment  variable\n‘GNUPGHOME’  or  (on  Windows  systems)  by  means  of  the  Registry entry HKCU\\Soft‐\nware\\GNU\\GnuPG:HomeDir.\n\nOn Windows systems it is possible to install GnuPG as a portable application.  In this\ncase  only this command line option is considered, all other ways to set a home direc‐\ntory are ignored.\n\nTo install GnuPG as a portable application under Windows, create an empty  file  named\n‘gpgconf.ctl’  in  the  same directory as the tool ‘gpgconf.exe’.  The root of the in‐\nstallation is then that directory; or, if ‘gpgconf.exe’ has  been  installed  directly\nbelow  a directory named ‘bin’, its parent directory.  You also need to make sure that\nthe following directories exist and are writable: ‘ROOT/home’ for the GnuPG  home  and\n‘ROOT/var/cache/gnupg’ for internal cache files.\n\n",
                    "long": "--quiet"
                },
                {
                    "name": "-n",
                    "content": "",
                    "flag": "-n"
                },
                {
                    "name": "--dry-run",
                    "content": "Do  not actually change anything.  This is currently only implemented for --change-op‐‐\ntions and can be used for testing purposes.\n\n",
                    "long": "--dry-run"
                },
                {
                    "name": "-r",
                    "content": "",
                    "flag": "-r"
                },
                {
                    "name": "--runtime",
                    "content": "Only used together with --change-options.  If one  of  the  modified  options  can  be\nchanged  in  a  running daemon process, signal the running daemon to ask it to reparse\nits configuration file after changing.\n\nThis means that the changes will take effect at run-time, as far as this is  possible.\nOtherwise, they will take effect at the next start of the respective backend programs.\n\n\n--status-fd n\nWrite  special status strings to the file descriptor n.  This program returns the sta‐\ntus messages SUCCESS or FAILURE which are helpful when the caller uses a  double  fork\napproach and can't easily get the return code of the process.\n\n",
                    "long": "--runtime"
                }
            ]
        },
        "USAGE": {
            "content": "The  command  --list-components will list all components that can be configured with gpgconf.\nUsually, one component will correspond to one GnuPG-related program and contain  the  options\nof  that  program's  configuration file that can be modified using gpgconf.  However, this is\nnot necessarily the case.  A component might also be a group of selected options from several\nprograms, or contain entirely virtual options that have a special effect rather than changing\nexactly one option in one configuration file.\n\nA component is a set of configuration options that semantically  belong  together.   Further‐\nmore,  several  changes  to a component can be made in an atomic way with a single operation.\nThe GUI could for example provide a menu with one entry for each component, or a window  with\none tabulator sheet per component.\n\nThe  command  --list-components  lists all available components, one per line.  The format of\neach line is:\n\nname:description:pgmname:\n\n\nname   This field contains a name tag of the component.  The name tag is used to specify  the\ncomponent in all communication with gpgconf.  The name tag is to be used verbatim.  It\nis thus not in any escaped format.\n\n",
            "subsections": [
                {
                    "name": "description",
                    "content": "The string in this field contains a human-readable description of the  component.   It\ncan be displayed to the user of the GUI for informational purposes.  It is percent-es‐\ncaped and localized.\n\n"
                },
                {
                    "name": "pgmname",
                    "content": "The string in this field contains the absolute name of the program's file.  It can  be\nused to unambiguously invoke that program.  It is percent-escaped.\n\nExample:\n$ gpgconf --list-components\ngpg:GPG for OpenPGP:/usr/local/bin/gpg2:\ngpg-agent:GPG Agent:/usr/local/bin/gpg-agent:\nscdaemon:Smartcard Daemon:/usr/local/bin/scdaemon:\ngpgsm:GPG for S/MIME:/usr/local/bin/gpgsm:\ndirmngr:Directory Manager:/usr/local/bin/dirmngr:\n\n\n\n\n"
                },
                {
                    "name": "Checking programs",
                    "content": "The  command  --check-programs  is similar to --list-components but works on backend programs\nand not on components.  It runs each program to test whether it is  installed  and  runnable.\nThis also includes a syntax check of all config file options of the program.\n\nThe  command --check-programs lists all available programs, one per line.  The format of each\nline is:\n\nname:description:pgmname:avail:okay:cfgfile:line:error:\n\n\nname   This field contains a name tag of the program which is identical to the  name  of  the\ncomponent.   The  name tag is to be used verbatim.  It is thus not in any escaped for‐\nmat.  This field may be empty to indicate a continuation of error descriptions for the\nlast name.  The description and pgmname fields are then also empty.\n\n"
                },
                {
                    "name": "description",
                    "content": "The  string  in this field contains a human-readable description of the component.  It\ncan be displayed to the user of the GUI for informational purposes.  It is percent-es‐\ncaped and localized.\n\n"
                },
                {
                    "name": "pgmname",
                    "content": "The  string in this field contains the absolute name of the program's file.  It can be\nused to unambiguously invoke that program.  It is percent-escaped.\n\n\navail  The boolean value in this  field  indicates  whether  the  program  is  installed  and\nrunnable.\n\n\nokay   The boolean value in this field indicates whether the program's config file is syntac‐\ntically okay.\n\n"
                },
                {
                    "name": "cfgfile",
                    "content": "If an error occurred in the configuration file (as indicated by a false value  in  the\nfield  okay),  this  field has the name of the failing configuration file.  It is per‐\ncent-escaped.\n\n\nline   If an error occurred in the configuration file, this field has the line number of  the\nfailing statement in the configuration file.  It is an unsigned number.\n\n\nerror  If  an  error occurred in the configuration file, this field has the error text of the\nfailing statement in the configuration file.  It is percent-escaped and localized.\n\n\nIn the following example the dirmngr is not runnable and the configuration file  of  scdaemon\nis not okay.\n\n$ gpgconf --check-programs\ngpg:GPG for OpenPGP:/usr/local/bin/gpg2:1:1:\ngpg-agent:GPG Agent:/usr/local/bin/gpg-agent:1:1:\nscdaemon:Smartcard Daemon:/usr/local/bin/scdaemon:1:0:\ngpgsm:GPG for S/MIME:/usr/local/bin/gpgsm:1:1:\ndirmngr:Directory Manager:/usr/local/bin/dirmngr:0:0:\n\n\nThe  command configuration file in the same manner as --check-programs, but only for the com‐\nponent component.\n\n\n\n"
                },
                {
                    "name": "Listing options",
                    "content": "Every component contains one or more options.  Options may be gathered into option groups  to\nallow the GUI to give visual hints to the user about which options are related.\n\nThe  command   lists  all options (and the groups they belong to) in the component component,\none per line.  component must be the string in the field name in the output  of  the  --list-\ncomponents command.\n\nThere is one line for each option and each group.  First come all options that are not in any\ngroup.  Then comes a line describing a group.  Then come all options that  belong  into  each\ngroup.   Then  comes  the  next group and so on.  There does not need to be any group (and in\nthis case the output will stop after the last non-grouped option).\n\nThe format of each line is:\n\nname:flags:level:description:type:alt-type:argname:default:argdef:value\n\n\nname   This field contains a name tag for the group or option.  The name tag is used to spec‐\nify the group or option in all communication with gpgconf.  The name tag is to be used\nverbatim.  It is thus not in any escaped format.\n\n\nflags  The flags field contains an unsigned number.  Its value is the OR-wise combination  of\nthe following flag values:\n\n\ngroup (1)\nIf this flag is set, this is a line describing a group and not an option.\n\nThe  following  flag  values  are only defined for options (that is, if the group flag is not\nused).\n\n\noptional arg (2)\nIf this flag is set, the argument is optional.  This is never set  for  type  0\n(none) options.\n\n\nlist (4)\nIf this flag is set, the option can be given multiple times.\n\n\nruntime (8)\nIf this flag is set, the option can be changed at runtime.\n\n\ndefault (16)\nIf this flag is set, a default value is available.\n\n\ndefault desc (32)\nIf  this  flag  is set, a (runtime) default is available.  This and the default\nflag are mutually exclusive.\n\n\nno arg desc (64)\nIf this flag is set, and the optional arg flag is set, then the  option  has  a\nspecial meaning if no argument is given.\n\n\nno change (128)\nIf  this flag is set, gpgconf ignores requests to change the value.  GUI front‐\nends should grey out this option.  Note, that manual changes of the  configura‐\ntion files are still possible.\n\n\nlevel  This field is defined for options and for groups.  It contains an unsigned number that\nspecifies the expert level under which this group or option should be displayed.   The\nfollowing  expert  levels  are  defined  for  options (they have analogous meaning for\ngroups):\n\n\nbasic (0)\nThis option should always be offered to the user.\n\n\nadvanced (1)\nThis option may be offered to advanced users.\n\n\nexpert (2)\nThis option should only be offered to expert users.\n\n\ninvisible (3)\nThis option should normally never be displayed, not even to expert users.\n\n\ninternal (4)\nThis option is for internal use only.  Ignore it.\n\nThe level of a group will always be the lowest level of all options it contains.\n\n"
                },
                {
                    "name": "description",
                    "content": "This field is defined for options and groups.  The string in this field contains a hu‐\nman-readable  description  of the option or group.  It can be displayed to the user of\nthe GUI for informational purposes.  It is percent-escaped and localized.\n\n\ntype   This field is only defined for options.  It contains an unsigned number that specifies\nthe type of the option's argument, if any.  The following types are defined:\n\nBasic types:\n\n\nnone (0)\nNo argument allowed.\n\n\nstring (1)\nAn unformatted string.\n\n\nint32 (2)\nA signed number.\n\n\nuint32 (3)\nAn unsigned number.\n\nComplex types:\n\n\npathname (32)\nA  string that describes the pathname of a file.  The file does not necessarily\nneed to exist.\n\n\nldap server (33)\nA string that describes an LDAP server in the format:\n\nhostname:port:username:password:basedn\n\n\nkey fingerprint (34)\nA string with a 40 digit fingerprint specifying a certificate.\n\n\npub key (35)\nA string that describes a certificate by user ID, key ID or fingerprint.\n\n\nsec key (36)\nA string that describes a certificate with a key by user ID, key ID or  finger‐\nprint.\n\n\nalias list (37)\nA  string  that describes an alias list, like the one used with gpg's group op‐\ntion.  The list consists of a key, an equal sign and space separated values.\n\nMore types will be added in the future.  Please see the alt-type field for information on how\nto cope with unknown types.\n\n"
                },
                {
                    "name": "alt-type",
                    "content": "This  field is identical to type, except that only the types 0 to 31 are allowed.  The\nGUI is expected to present the user the option in the format specified by  type.   But\nif the argument type type is not supported by the GUI, it can still display the option\nin the more generic basic type alt-type.  The GUI must support all the  defined  basic\ntypes to be able to display all options.  More basic types may be added in future ver‐\nsions.  If the GUI encounters a basic type it doesn't support, it should report an er‐\nror and abort the operation.\n\n"
                },
                {
                    "name": "argname",
                    "content": "This  field  is only defined for options with an argument type type that is not 0.  In\nthis case it may contain a percent-escaped and localized string  that  gives  a  short\nname  for  the  argument.   The field may also be empty, though, in which case a short\nname is not known.\n\n"
                },
                {
                    "name": "default",
                    "content": "This field is defined only for options for which the default or default desc  flag  is\nset.  If the default flag is set, its format is that of an option argument (see: [For‐\nmat conventions], for details).  If the default value is empty,  then  no  default  is\nknown.   Otherwise, the value specifies the default value for this option.  If the de‐‐\nfault desc flag is set, the field is either empty or contains a description of the ef‐\nfect if the option is not given.\n\n\nargdef This field is defined only for options for which the optional arg flag is set.  If the\nno arg desc flag is not set, its format is that of an option  argument  (see:  [Format\nconventions],  for details).  If the default value is empty, then no default is known.\nOtherwise, the value specifies the default argument for this option.  If  the  no  arg\ndesc flag is set, the field is either empty or contains a description of the effect of\nthis option if no argument is given.\n\n\nvalue  This field is defined only for options.  Its format is that of an option argument.  If\nit  is  empty, then the option is not explicitly set in the current configuration, and\nthe default applies (if any).  Otherwise, it contains the current value of the option.\nNote  that this field is also meaningful if the option itself does not take a real ar‐\ngument (in this case, it contains the number of times the option appears).\n"
                },
                {
                    "name": "Changing options",
                    "content": "The command to change the options of the component component to the specified values.  compo‐\nnent  must  be  the  string in the field name in the output of the --list-components command.\nYou have to provide the options that shall be changed in the following format on standard in‐\nput:\n\nname:flags:new-value\n\n\nname   This  is  the name of the option to change.  name must be the string in the field name\nin the output of the --list-options command.\n\n\nflags  The flags field contains an unsigned number.  Its value is the OR-wise combination  of\nthe following flag values:\n\n\ndefault (16)\nIf  this  flag  is set, the option is deleted and the default value is used in‐\nstead (if applicable).\n\n"
                },
                {
                    "name": "new-value",
                    "content": "The new value for the option.  This field is only defined if the default flag  is  not\nset.  The format is that of an option argument.  If it is empty (or the field is omit‐\nted), the default argument is used (only allowed if the argument is optional for  this\noption).  Otherwise, the option will be set to the specified value.\n\nThe  output of the command is the same as that of --check-options for the modified configura‐\ntion file.\n\nExamples:\n\nTo set the force option, which is of basic type none (0):\n\n$ echo 'force:0:1' | gpgconf --change-options dirmngr\n\nTo delete the force option:\n\n$ echo 'force:16:' | gpgconf --change-options dirmngr\n\nThe --runtime option can influence when the changes take effect.\n\n\n\n"
                },
                {
                    "name": "Listing global options",
                    "content": "Sometimes it is useful for applications to look at the global  options  file  ‘gpgconf.conf’.\nThe  colon  separated  listing format is record oriented and uses the first field to identify\nthe record type:\n\n\nk      This describes a key record to start the definition of a new ruleset for a user/group.\nThe format of a key record is:\n\nk:user:group:\n\n\nuser   This  is the user field of the key.  It is percent escaped.  See the definition\nof the gpgconf.conf format for details.\n\n\ngroup  This is the group field of the key.  It is percent escaped.\n\n\nr      This describes a rule record. All rule records up to the next key  record  make  up  a\nrule set for that key.  The format of a rule record is:\n\nr:::component:option:flag:value:\n\n\ncomponent\nThis is the component part of a rule.  It is a plain string.\n\n\noption This is the option part of a rule.  It is a plain string.\n\n\nflag   This  is  the flags part of a rule.  There may be only one flag per rule but by\nusing the same component and option, several flags may be assigned  to  an  op‐\ntion.  It is a plain string.\n\n\nvalue  This is the optional value for the option.  It is a percent escaped string with\na single quotation mark to indicate a string.  The quotation mark is  only  re‐\nquired to distinguish between no value specified and an empty string.\n\n\nUnknown  record  types  should  be  ignored.   Note that there is intentionally no feature to\nchange the global option file through gpgconf.\n\n\n\n"
                },
                {
                    "name": "Get and compare software versions.",
                    "content": "The GnuPG Project operates a server to query the current versions of  software  packages  re‐\nlated  to  GnuPG.   gpgconf can be used to access this online database.  To allow for offline\noperations,  this  feature  works  by  having  dirmngr  download  a  file  from  https://ver‐‐\nsions.gnupg.org,  checking  the signature of that file and storing the file in the GnuPG home\ndirectory.  If gpgconf is used and dirmngr is running, it may ask  dirmngr  to  refresh  that\nfile before itself uses the file.\n\nThe  command --query-swdb returns information for the given package in a colon delimited for‐\nmat:\n\n\n\nname   This is the name of the package as requested.  Note that \"gnupg\"  is  a  special  name\nwhich  is replaced by the actual package implementing this version of GnuPG.  For this\nname it is also not required to specify a version because gpgconf takes its  own  ver‐\nsion in this case.\n\n"
                },
                {
                    "name": "iversion",
                    "content": "The  currently installed version or an empty string.  The value is taken from the com‐\nmand line argument but may be provided by gpg if not given.\n\n\nstatus The status of the software package according to this table:\n\n-      No information available.  This is either because no current version  has  been\nspecified or due to an error.\n\n?      The given name is not known in the online database.\n\nu      An update of the software is available.\n\nc      The installed version of the software is current.\n\nn      The installed version is already newer than the released version.\n\n"
                },
                {
                    "name": "urgency",
                    "content": "If  the  value (the empty string should be considered as zero) is greater than zero an\nimportant update is available.\n\n\nerror  This returns an gpg-error error code to distinguish between various failure modes.\n\n"
                },
                {
                    "name": "filedate",
                    "content": "This gives the date of the file with  the  version  numbers  in  standard  ISO  format\n(yyyymmddThhmmss).   The  date has been extracted by dirmngr from the signature of the\nfile.\n\n"
                },
                {
                    "name": "verified",
                    "content": "This gives the date in ISO format the file was downloaded.  This value can be used  to\nevaluate the freshness of the information.\n\n"
                },
                {
                    "name": "version",
                    "content": "This returns the version string for the requested software from the file.\n\n"
                },
                {
                    "name": "reldate",
                    "content": "This returns the release date in ISO format.\n\n\nsize   This returns the size of the package as decimal number of bytes.\n\n\nhash   This returns a hexified SHA-2 hash of the package.\n\n\nMore fields may be added in future to the output.\n\n\n"
                }
            ]
        },
        "FILES": {
            "content": "",
            "subsections": [
                {
                    "name": "/etc/gnupg/gpgconf.conf",
                    "content": "If this file exists, it is processed as a global configuration file.\nA commented example can be found in the ‘examples’ directory of\nthe distribution.\n\n\nGNUPGHOME/swdb.lst\nA file with current software versions.  dirmngr creates\nthis file on demand from an online resource.\n\n"
                }
            ]
        },
        "SEE ALSO": {
            "content": "gpg(1), gpgsm(1), gpg-agent(1), scdaemon(1), dirmngr(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\n\n\nGnuPG 2.2.27                                 2020-12-21                                   GPGCONF(1)",
            "subsections": []
        }
    },
    "summary": "gpgconf - Modify .gnupg home directories",
    "flags": [
        {
            "flag": "-o",
            "long": null,
            "arg": null,
            "description": "--output file Write output to file. Default is to write to stdout."
        },
        {
            "flag": "-v",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "",
            "long": "--verbose",
            "arg": null,
            "description": "Outputs additional information while running. Specifically, this extends numerical field values by human-readable descriptions."
        },
        {
            "flag": "-q",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "",
            "long": "--quiet",
            "arg": null,
            "description": "Try to be as quiet as possible. --homedir dir Set the name of the home directory to dir. If this option is not used, the home direc‐ tory defaults to ‘~/.gnupg’. It is only recognized when given on the command line. It also overrides any home directory stated through the environment variable ‘GNUPGHOME’ or (on Windows systems) by means of the Registry entry HKCU\\Soft‐ ware\\GNU\\GnuPG:HomeDir. On Windows systems it is possible to install GnuPG as a portable application. In this case only this command line option is considered, all other ways to set a home direc‐ tory are ignored. To install GnuPG as a portable application under Windows, create an empty file named ‘gpgconf.ctl’ in the same directory as the tool ‘gpgconf.exe’. The root of the in‐ stallation is then that directory; or, if ‘gpgconf.exe’ has been installed directly below a directory named ‘bin’, its parent directory. You also need to make sure that the following directories exist and are writable: ‘ROOT/home’ for the GnuPG home and ‘ROOT/var/cache/gnupg’ for internal cache files."
        },
        {
            "flag": "-n",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "",
            "long": "--dry-run",
            "arg": null,
            "description": "Do not actually change anything. This is currently only implemented for --change-op‐‐ tions and can be used for testing purposes."
        },
        {
            "flag": "-r",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "",
            "long": "--runtime",
            "arg": null,
            "description": "Only used together with --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. --status-fd n Write special status strings to the file descriptor n. This program returns the sta‐ tus 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."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "gpg",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/gpg/1/json"
        },
        {
            "name": "gpgsm",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/gpgsm/1/json"
        },
        {
            "name": "gpg-agent",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/gpg-agent/1/json"
        },
        {
            "name": "scdaemon",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/scdaemon/1/json"
        },
        {
            "name": "dirmngr",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/dirmngr/1/json"
        }
    ]
}