-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
CURLOPT_CERTINFO not working with HTTP/3 (either backend) #9584
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
Comments
First double-check that the correct and same logic is done in libcurl for the QUIC case as it is for normal TLS when this option is set. |
The problem reproduces for me against |
The reason for this problem is that no QUIC code calls the necessary |
This problem exists for all QUIC backends. |
Curl_get_certchain() is now an exported function in lib/vtls/openssl.c that can also be used from quiche.c and ngtcp2.c to get the cert chain for QUIC connections as well. The *certchain function was moved to the top of the file for this reason. Reported-by: Eloy Degen Fixes #9584
Although I am using
pycurl
and not directly calling thelibcurl
API from C, I think this is the most appropriate place to report the bug. According to the documentation, only OpenSSL is supported. This uses the BoringSSL fork with the Quiche library for QUIC. I suspect that it could be a missing API in Quiche, but I'm not sure.I did this
I expected the following
I expected it to print the certificate information. When the
c.setopt(pycurl.HTTP_VERSION, c.CURL_HTTP_VERSION_3)
line is removed, it works fine. I was using a local test server but replace it with Facebook to make it reproducible. It prints an empty list when using HTTP/3.curl/libcurl version
PycURL/7.45.1 libcurl/7.86.0-DEV BoringSSL quiche/0.14.0
operating system
Fedora Linux 36, in a Python venv
The text was updated successfully, but these errors were encountered: