-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 12/10/2014 06:26 PM, Samir Nassar wrote: > On Wednesday, 2014-12-10 12:10:28 Daniel Kahn Gillmor wrote: >>> Can you provide more detail (or a link to a bug report) about >>> the problem with hkps in 2.1.0 ? > > On upgrade to 2.1.0 looking up keys from a keyserver stopped > working for me. I tracked down the following comment from Hugo > Hinterberger: > http://lists.gnupg.org/pipermail/gnupg-users/2014-November/051695.html > and Kristian Fiskerstrand's suggestion: > http://lists.gnupg.org/pipermail/gnupg-users/2014-November/051698.html > > On Wednesday, 2014-12-10 18:10:58 Kristian Fiskerstrand wrote: >> The SNI issue last discussed in [0] springs to mind. But I still >> experience this on gpg (GnuPG) 2.1.1-beta67 > > I had the impression that this bug is getting fixed in 2.1.1 and > that I shouldn't increase noise to an existing and known problem. > At this stage I can report that despite trying out Kristian's > suggestion I am not able to interact with either the hkps pool or > individual hkps keyservers. Arch Linux, GnuPG 2.1.0. >
Individual keyserver should be no issue as long as you don't hit the SNI issue, are you sure gnupg is built with gnutls / hkps support? I know that at least earlier builds of arch did not include gnutls support, which caused some headache to debug while helping a user on IRC (the reason for the patch to only report hkps scheme earlier). Do an ldd on dirmngr binary and see if it is linked with gnutls. - -- - ---------------------------- 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 - ---------------------------- "We can only see a short distance ahead, but we can see plenty there that needs to be done." (Alan Turing) -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJUiIWfAAoJEPw7F94F4Tag31UQAJKSimTMhBif5PCUexU2fUZi zEquZ41JJEyrcVqhmB2MWHDRWl0uZ0NrRomxig/w99BQKUSNN147rEI/mcF1vSa7 g2Fmbi/WSd+lJGrBZAJ56uEGI/o7WcHoMRDiGucESCHE3zv4r9ZrIoWlHC1gZ/xj GBDLgk6kt5UiuRUYIcMjwe0lWowqyyUJGozm8ZGivULozNhU8CEGoame/NTCrE56 H8o6KaqpML1WMAEO9b2CnfVqOGJTYCJ0OwcunhuMlMiWG4ZsH5u7TlES67lY1Bzq TRbu5zsasJD5t81hCb90t69vOh1qH/K80h/WG0qXHjzOim41fSk9NbrZjp84i6Tk R6D0pAUnDxV0bst0mkhDjI3Sh0+VCsZg7PxtVnSruXYrL3LSCy30xHNzaSrMKxtH cRkoIcspl8E0tgMUDdSC/T0Z9KFNWKHf0/gkuv99K8z9k0uBDMAq/vgzoekR25cd ukyYEfhhsS9JSHaPX620g2fZ/qFxk/m3loNlYgXb6XyxPSYkNewqcMlrHpFFSUOv vx1kFfOzyxpH/al1ihsSLLnawP6xX5NSS729HHYL7RVaUFtexXiyR9PWd8Yt7nnL ZRIWB4MW2pugS1FUdiCAepYe5sQGx1uLcKGUP9zsoUsdkFDAVrAS4rEq5hNzbjDv 0LTrQMcxREE3yx5c45bi =Ro0f -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
