The documentation for CURLOPT_SSLKEY contains the following note: "(iOS and Mac OS X only) This option is ignored if curl was built against Secure Transport. Secure Transport expects the private key to be already present in the keychain or PKCS#12 file containing the certificate."
From my experiments it seems that this is also true on Windows when curl is built against schannel - if the certificate does not contain the private key, attempting to AcquireCrerdentialsHandle fails with SEC_E_NO_CREDENTIALS. Does that agree with what others see and expect? Happy to open issue/create a PR if it is. -- Richard ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.html
