Summary: | app-crypt/gnupg-2.0.26-r3 static build is unable to access HKPS keyservers | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Juraj Variny <rini17> |
Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | k_f |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
curl build log
gnupg build log |
Description
Juraj Variny
2015-02-04 21:34:35 UTC
Can you please confirm that curl and the crypto provider for HTTP has been built staticly? Please provide the configure log from the build of gnupg and libgcrypt. fwiw, "gpgkeys: HTTP fetch error 1: unsupported protocol" is an error you will get independent of whether a key exists on a keyserver or not simply because it isn't making a connection to https (which hkps translates into with a specific path) Created attachment 395720 [details]
curl build log
Created attachment 395722 [details]
gnupg build log
(In reply to Juraj Variny from comment #3) > Created attachment 395722 [details] > gnupg build log Can you please run with --keyserver-options verbose,debug and report what curl version is used. I suspect this is using curl-shim? Created thread in gnupg-users: http://lists.gnupg.org/pipermail/gnupg-users/2015-February/052386.html Summary: Linking with curl when ssl provider is enabled doesn't work statically and test fails during gnupg building, so curl helpers are built with curl-shim that doesn't support hkps instead of using a full curl version. This is not a downstream breakage of the distro and it is not likely to change (although there is potentially better luck for static linking on alternative libc providers such as musl). Static linking for gnupg 2.0 is likely to be removed in future version altogether , gnupg 1.4 should be used if such situations are needed. Closing WONTFIX |