-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
certinfo: b0rked pubkey/signature algorithm with openssl>=1.0.2 #3706
Labels
Comments
Ugh. That's one of the dark magic parts of the OpenSSL APIs that I really don't understand much. But yeah, I can confirm that running your test code with openssl 1.0.2 returns a different output than with an openssl 1.1.1 build for me as well. 😕 |
Yeah, I tried to fix it, but that openssl API is, well, ugh |
ngg
added a commit
to tresorit/curl
that referenced
this issue
Jun 16, 2019
Certinfo gives the same result for all OpenSSL versions. Also made printing RSA pubkeys consistent with older versions. Fixes curl#3706
ngg
added a commit
to tresorit/curl
that referenced
this issue
Jun 16, 2019
Certinfo gives the same result for all OpenSSL versions. Also made printing RSA pubkeys consistent with older versions. Fixes curl#3706
Sorry, posted the output (now as expected) over at #4030
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I did this
Retrieved CURLINFO_CERTINFO
I expected the following
Sane Public Key/Signature Algorithm entries.
Got instead
curl/libcurl version
master + openssl 1.1.1b
operating system
Linux
Testcase
https://gist.github.com/m6w6/7acc0943b024eee3bdc60df70d1f8e3e
The text was updated successfully, but these errors were encountered: