mirror of
https://github.com/curl/curl.git
synced 2026-08-14 19:03:39 +03:00
docs/opts: Mention Schannel client cert type is P12
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
This commit is contained in:
parent
ba4a8fa4d1
commit
cabcf403ed
7 changed files with 28 additions and 16 deletions
|
|
@ -62,7 +62,7 @@ const struct helptxt helptext[] = {
|
|||
"Verify the status of the server cert via OCSP-staple",
|
||||
CURLHELP_TLS},
|
||||
{" --cert-type <type>",
|
||||
"Certificate type (DER/PEM/ENG)",
|
||||
"Certificate type (DER/PEM/ENG/P12)",
|
||||
CURLHELP_TLS},
|
||||
{" --ciphers <list of ciphers>",
|
||||
"SSL ciphers to use",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue