From aefb0bde4e91291329fc08d03cd565e74c97f5ca Mon Sep 17 00:00:00 2001 From: Joel Depooter Date: Fri, 2 Feb 2024 17:58:04 -0800 Subject: [PATCH] docs: add missing slashes to SChannel client certificate documentation When setting the CURLOPT_SSLCERT option to a certificate thumprint, it is required to have a backslash between the "store location", "store name" and "thumbprint" tokens. These slashes were present in the previous documentation, but were missed in the transition to markdown documentation. Closes #12854 --- docs/libcurl/opts/CURLOPT_SSLCERT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/libcurl/opts/CURLOPT_SSLCERT.md b/docs/libcurl/opts/CURLOPT_SSLCERT.md index 21f052ff76..8400e6e2a8 100644 --- a/docs/libcurl/opts/CURLOPT_SSLCERT.md +++ b/docs/libcurl/opts/CURLOPT_SSLCERT.md @@ -36,9 +36,9 @@ in order to avoid confusion with a nickname. (Schannel only) Client certificates can be specified by a path expression to a certificate store. (You can import *PFX* to a store first). You can use -"" to refer to a certificate in the +"\\\\" to refer to a certificate in the system certificates store, for example, -**"CurrentUserMY934a7ac6f8a5d579285a74fa"**. The thumbprint is usually a SHA-1 +**"CurrentUser\\MY\\934a7ac6f8a5d579285a74fa"**. The thumbprint is usually a SHA-1 hex string which you can see in certificate details. Following store locations are supported: **CurrentUser**, **LocalMachine**, **CurrentService**, **Services**, **CurrentUserGroupPolicy**, **LocalMachineGroupPolicy**, -- 2.47.3