cabcf403ed
Schannel backend code behaves same as Secure Transport, it expects a P12 certificate file or the name of a certificate already in the user's OS key store. Also, both backends ignore CURLOPT_SSLKEY (tool: --key) because they expect the private key to already be available from the keystore or P12 certificate. Ref: https://github.com/curl/curl/discussions/8581#discussioncomment-2337260 Closes https://github.com/curl/curl/pull/8587
18 lines
533 B
D
18 lines
533 B
D
Long: cert-type
|
|
Protocols: TLS
|
|
Arg: <type>
|
|
Help: Certificate type (DER/PEM/ENG/P12)
|
|
See-also: cert key key-type
|
|
Category: tls
|
|
Example: --cert-type PEM --cert file $URL
|
|
Added: 7.9.3
|
|
---
|
|
Tells curl what type the provided client certificate is using. PEM, DER, ENG
|
|
and P12 are recognized types.
|
|
|
|
The default type depends on the TLS backend and is usually PEM, however for
|
|
Secure Transport and Schannel it is P12. If --cert is a pkcs11: URI then ENG is
|
|
the default type.
|
|
|
|
If this option is used several times, the last one will be used.
|