diff options
| author | Tharre <tharre3@gmail.com> | 2017-09-04 15:49:23 +0200 |
|---|---|---|
| committer | Tharre <tharre3@gmail.com> | 2017-09-04 15:49:23 +0200 |
| commit | e10f47cb4d3b1f05d57ad0aad7b352e697606a3e (patch) | |
| tree | 9482b50d32b4653c53cdfbedff2883f9f96d6540 | |
| parent | d3f24ecae44e04f421d651f0970a296a27d8da96 (diff) | |
| download | dotfiles-e10f47cb4d3b1f05d57ad0aad7b352e697606a3e.tar.gz dotfiles-e10f47cb4d3b1f05d57ad0aad7b352e697606a3e.tar.xz dotfiles-e10f47cb4d3b1f05d57ad0aad7b352e697606a3e.zip | |
gnupg: fix keyserver configuration
GnuPG only honors the last given keyserver[0]. So specifying multiple
keyservers does nothing. Furthermore, hkps requires the certificate file
to be specified[1], which may or may be installed. IPv6 may also cause
problems, and gpg does not retry if a connection fails.
For these reasons, we use the IPv4 only pool of sks.
[0] https://lists.gnupg.org/pipermail/gnupg-users/2003-May/018147.html
[1] https://sks-keyservers.net/overview-of-pools.php
| -rw-r--r-- | .gnupg/gpg.conf | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/.gnupg/gpg.conf b/.gnupg/gpg.conf index 77b71a8..70f1734 100644 --- a/.gnupg/gpg.conf +++ b/.gnupg/gpg.conf @@ -6,7 +6,4 @@ encrypt-to 0xC8F0B2F4 # automatically fetch keys keyserver-options auto-key-retrieve - -keyserver hkps://hkps.sks-keyservers.net -keyserver hkp://pool.sks-keyservers.net -keyserver http://pgp.mit.edu +keyserver hkp://ipv4.pool.sks-keyservers.net |