wolfssl backend behavior differs from openssl when CURLOPT_SSLCERT is used but CURLOPT_SSLKEY wasn't #14007
Labels
Comments
alexsn
pushed a commit
to alexsn/curl
that referenced
this issue
Jun 24, 2024
When user sets CURLOPT_SSLCERT but leaves CURLOPT_SSLKEY unset assume the path passed in CURLOPT_SSLCERT holds the ssl key which is what we do in openssl implementation. Closed curl#14007
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I did this
I tried running
curl --cert <path> <url_requiring_client_cert>which works with openssl backend but fails with wolfssl.The reason being that openssl backend will assume key_file is the same as cert_file (code here) which wolfssl makes no such assumption (code here).
I expected the following
I expect wolfssl backend to assume key_file is the same as cert_file, which means both ssl backend show behave the same.
curl/libcurl version
curl 8.8.0
operating system
All
The text was updated successfully, but these errors were encountered: