From 03441afccfae37cf9ca5b184de940125ab770c3c Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Wed, 24 Jun 2026 13:35:47 -0400 Subject: [PATCH] winldap: Clarify SDK differences in VERIFYSERVERCERT prototype - Clarify that the incorrect VERIFYSERVERCERT function prototype is limited to some older SDKs. Prior to this change the doc implied that the bad prototype was always declared, but any recent SDK (including what is used to generate the function prototype for the doc) does not have this issue. Ref: https://github.com/curl/curl/pull/22152#discussion_r3466825612 Closes #xxxx --- sdk-api-src/content/winldap/nc-winldap-verifyservercert.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/sdk-api-src/content/winldap/nc-winldap-verifyservercert.md b/sdk-api-src/content/winldap/nc-winldap-verifyservercert.md index 437767f3bce2..c8ec1bc8a517 100644 --- a/sdk-api-src/content/winldap/nc-winldap-verifyservercert.md +++ b/sdk-api-src/content/winldap/nc-winldap-verifyservercert.md @@ -83,9 +83,12 @@ conn, LDAP_OPT_SERVER_CERTIFICATE, &CertRoutine The server calls VERIFYSERVERCERT after the secure connection has been established. The server's certificate context is supplied for examination by the client. + +Even though in some old SDKs VERIFYSERVERCERT is declared as receiving a PCCERT_CONTEXT, it in fact receives a PCCERT_CONTEXT*. + An application should use the ppServerCert parameter as: PCCERT_CONTEXT* ppServerCert = (PCCERT_CONTEXT*)pServerCert; -Even though VERIFYSERVERCERT is declared as receiving a PCCERT_CONTEXT, it in fact receives a PCCERT_CONTEXT*. The ppServerCert can be used to verify the certificate. CertFreeCertificateContext should be called before this function returns. The call to this function should be made as follows: +The ppServerCert can be used to verify the certificate. CertFreeCertificateContext should be called before this function returns. The call to this function should be made as follows: ```cpp