-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 03/18/2015 08:39 PM, Samir Nassar wrote: > On Wednesday, March 18, 2015 07:28:31 PM Kristian Fiskerstrand > wrote: >> Likely related to the PTR issues[0, 1], its already in the >> roadmap[2] > > Thank you Kristian, > > So I understand this better. When using non-encrypted connections > GnuPG doesn't have a problem, but when I am using a wildcard > certificate GPG 2.1 has a problem? > > Is there anything I can do to mitigate for now?
Hmm, I didn't notice that it was a wildcard cert, that should also support holdfast.myriapolis.net in the cert matching, however it results a redirect and 404 for [0]. If you add this as a vhost I suspect it will work in your configuration. References: [0] https://holdfast.myriapolis.net/pks/lookup?op=stats - -- - ---------------------------- 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 - ---------------------------- Acta est fabula So ends the story -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJVCdgDAAoJEP7VAChXwav6KAYH/jXuBobsYer/R16EFNHeCyz5 wa+9azd3oJP0t/ucVwM59vCv5dGbG4bRGqoNOp5pE9D7/BDY/F+7Y4UGJKsT1z5D yiEL/xyfWmv18YaSYLU+WCC5UaQHZxagaJF9pcZE3VTPrBf21SIyvKm8LQ+ijrj9 iY+RHJZpOGS4U0s3M+2M3rsbZxSvO1vBeXB6KR9jzRpApcTpsZlB5tewxJGZjeGh 90RYecK8KDnjvPCOB3t7tT4/1JQHVhAIizTxc4ZoqcT3VuiAkNYEdryqUiCIeMAQ wsnNynaXREWybQ2bkImHN4NyRzfSRbm50TNPl7RxuKQcOfkO3RC/2hhwrjoALUs= =IGgm -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users