Skip to content
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

curl built with DarwinSSL doesn't collect server cert #4130

Closed
0golovatyi opened this issue Jul 19, 2019 · 4 comments
Closed

curl built with DarwinSSL doesn't collect server cert #4130

0golovatyi opened this issue Jul 19, 2019 · 4 comments
Labels
known-issue not-a-curl-bug This is not a bug in curl TLS

Comments

@0golovatyi
Copy link

I did this

./buildconfig
./configure --withdarwin-ssl
make
cd docs/examples
make && certinfo

I expected the following

1 certs!
...some cert data here...

curl/libcurl version

built from the latest master (aa73eb4).

operating system

macOS 10.14.5

@0golovatyi
Copy link
Author

The output I see with running certinfo is 0 certs!

@bagder
Copy link
Member

bagder commented Jul 19, 2019

It isn't supported with the Secure Transport backend. Allow me to quote the CURLINFO_CERTINFO man page:

AVAILABILITY

This option is only working in libcurl built with OpenSSL, NSS, Schannel or GSKit support. Schannel support added in 7.50.0

@bagder bagder added not-a-curl-bug This is not a bug in curl TLS labels Jul 19, 2019
@0golovatyi
Copy link
Author

@bagder Thank you for the information.

Is there any other way to collect server cert info in security layer independent way? Seems like now my options are to check CURLINFO_TLS_SSL_PTR, then get a pointer to a backend (openssl, darwinssl, etc.) and use that backend API.

@bagder
Copy link
Member

bagder commented Jul 19, 2019

Other than write a patch for curl that brings the certinfo feature to the Secure Transport backend, no.

@bagder bagder closed this as completed Jul 25, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 23, 2019
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 10, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 10, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 10, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 11, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 14, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Jul 15, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Aug 8, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Aug 9, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Aug 9, 2021
sergio-nsk added a commit to sergio-nsk/curl that referenced this issue Aug 16, 2021
bagder pushed a commit that referenced this issue Aug 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
known-issue not-a-curl-bug This is not a bug in curl TLS
Development

Successfully merging a pull request may close this issue.

2 participants