HKPS fails on GPG 2.1
Kristian Fiskerstrand
kristian.fiskerstrand at sumptuouscapital.com
Sat Jan 3 16:31:03 CET 2015
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 01/03/2015 02:19 PM, Juan Miguel Navarro Martínez wrote:
> Refreshing, receiving, sending and searching for keys using a hkps
> server fails with a "No keyserver available" error as seen in this
> debug:
Make sure dirmngr is built with gnutls support, use e.g.
$ dirmngr
..
OK Dirmngr 2.1.1 at your service
KEYSERVER --help
S # Known schemata:
S # hkp
S # hkps
^^ Make sure the scheme is there
S # http
S # finger
S # kdns
S # (Use an URL for engine specific help.)
OK
>
> It does not matter which hkps server is, I have tried
> hkps://keys.riseup.net as well. But if I use hkp, it works.
>
> The certification file is added in the dirmngr.conf as below:
>
> hkp-cacert
> C:\Users\Juanmi\AppData\Roaming\gnupg\sks-keyservers.netCA.pem
>
> And gpg.conf file is the one made at riseup.net but with
> 'default-key' changed to mine and the old 'keyserver-option
> ca-cert' option commented:
> https://raw.githubusercontent.com/ioerror/duraconf/master/configs/gnupg/gpg.conf
>
>
>
>
I'm wondering if it is because gnupg-curl and its libraries do not
> come with gnupg2.1.1 for Windows installer as it does with GPG4win
> installer, and I assume GPGTools for Mac.
>
Gnupg 2.1 does not use curl for these matters
- --
- ----------------------------
Kristian Fiskerstrand
Blog: http://blog.sumptuouscapital.com
Twitter: @krifisk
- ----------------------------
Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
- ----------------------------
Prævenire melius est quam præveniri
It is better to precede than to be preceded
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJUqAsxAAoJEPw7F94F4TagiPQQAKGW9VlXXW5oHFKKyLOgORw0
uTuUlelNQVsiQH/7z7bT2FF24UKuaPwlwfGiDH/NHyNPjKS4vlJjSL1z9MWnUhGl
Ds0MRqLCUCv2G+sf2w4xX21Z2O/yIjnUhvBRfTRsFav3pqmCM96HIvzFRqlOXQe0
CAnzfW0ALSa7AWu3YOHHOrS2OCovUWpKJS9RDZ0HlrUFPGEQU3Yvn49UaR7vG/Vs
AVfyX2ItDQVs1FH77bgNiczXOo/lGOv+fw4yKjyhE47K2kr63Ugl3NH5TpB0nZUZ
wRUuOYzGNglIaV1brosIxrg5hlnNL/a1alQAoB34GQUa5+YWF/K0nctZWaI6B2vb
yZihhyYYRaj7LpKMHLK2eqIf65xJLi3yjZKNc0tEtjvZqUtAgaBGRrbrFzGWDotK
uv1x77eO5A2ALq2Yitk7Lxu9pM21kG5i6ebdeAhaYTKyjHqkDSIKCrJyaFNPn3lE
PULeC+hPBtEX0QlmsTUO+EiP4s5HhGqPGoBrWEq+hsSoRoXynovFIdRmu/c7U5aG
wHq/0LDzqFgOrObkCvOfP1bO6EOkazwQjmUBttxnMBHDy9nqrfB/8iwy6M9Q/pGI
KM1znzaf3TsV3OnP4v9cBYN5A4SX9oSzjpsy7bQ1n513ENaOJdKJT3VF9Or0o1pZ
j2+tFtyBFYczknYIunWx
=Yfbm
-----END PGP SIGNATURE-----
More information about the Gnupg-users
mailing list