My various dotfiles

dirmngr.conf 2.6KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. # dirmngr.conf - Options for Dirmngr
  2. # Written in 2015 by The GnuPG Project <https://gnupg.org>
  3. #
  4. # To the extent possible under law, the authors have dedicated all
  5. # copyright and related and neighboring rights to this file to the
  6. # public domain worldwide. This file is distributed without any
  7. # warranty. You should have received a copy of the CC0 Public Domain
  8. # Dedication along with this file. If not, see
  9. # <http://creativecommons.org/publicdomain/zero/1.0/>.
  10. #
  11. #
  12. # Unless you specify which option file to use (with the command line
  13. # option "--options filename"), the file ~/.gnupg/dirmngr.conf is used
  14. # by dirmngr. The file can contain any long options which are valid
  15. # for Dirmngr. If the first non white space character of a line is a
  16. # '#', the line is ignored. Empty lines are also ignored. See the
  17. # dirmngr man page or the manual for a list of options.
  18. #
  19. # --keyserver URI
  20. #
  21. # GPG can send and receive keys to and from a keyserver. These
  22. # servers can be HKP, Email, or LDAP (if GnuPG is built with LDAP
  23. # support).
  24. #
  25. # Example HKP keyservers:
  26. # hkp://keys.gnupg.net
  27. #
  28. # Example HKP keyserver using a Tor OnionBalance service
  29. # hkp://jirk5u4osbsr34t5.onion
  30. #
  31. # Example HKPS keyservers (see --hkp-cacert below):
  32. # hkps://hkps.pool.sks-keyservers.net
  33. #
  34. # Example LDAP keyservers:
  35. # ldap://pgp.surfnet.nl:11370
  36. #
  37. # Regular URL syntax applies, and you can set an alternate port
  38. # through the usual method:
  39. # hkp://keyserver.example.net:22742
  40. #
  41. # Most users just set the name and type of their preferred keyserver.
  42. # Note that most servers (with the notable exception of
  43. # ldap://keyserver.pgp.com) synchronize changes with each other. Note
  44. # also that a single server name may actually point to multiple
  45. # servers via DNS round-robin. hkp://keys.gnupg.net is an example of
  46. # such a "server", which spreads the load over a number of physical
  47. # servers.
  48. #
  49. # If exactly two keyservers are configured and only one is a Tor hidden
  50. # service, Dirmngr selects the keyserver to use depending on whether
  51. # Tor is locally running or not (on a per session base).
  52. keyserver hkp://jirk5u4osbsr34t5.onion
  53. keyserver hkp://keys.gnupg.net
  54. # --hkp-cacert FILENAME
  55. #
  56. # For the "hkps" scheme (keyserver access over TLS), Dirmngr needs to
  57. # know the root certificates for verification of the TLS certificates
  58. # used for the connection. Enter the full name of a file with the
  59. # root certificates here. If that file is in PEM format a ".pem"
  60. # suffix is expected. This option may be given multiple times to add
  61. # more root certificates. Tilde expansion is supported.
  62. #hkp-cacert /path/to/CA/sks-keyservers.netCA.pem