97e5a471e0
Daniel Stenberg
2025-09-25
Subject
KNOWN_BUGS: Access violation sending client cert with SChannel
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/KNOWN_BUGS+9 -0
| @@ -15,6 +15,7 @@ problems may have been fixed or changed somewhat since this was written. | |
| 2. TLS | |
| 2.1 IMAPS connection fails with Rustls error | |
| + | 2.2 Access violation sending client cert with Schannel |
| 2.5 Client cert handling with Issuer DN differs between backends | |
| 2.7 Client cert (MTLS) issues with Schannel | |
| 2.11 Schannel TLS 1.2 handshake bug in old Windows versions | |
| @@ -120,6 +121,14 @@ problems may have been fixed or changed somewhat since this was written. | |
| https://github.com/curl/curl/issues/10457 | |
| + | 2.2 Access violation sending client cert with Schannel |
| + | |
| + | When using Schannel to do client certs, curl sets PKCS12_NO_PERSIST_KEY to |
| + | avoid leaking the private key into the filesystem. Unfortunately that flag |
| + | instead seems to trigger a crash. |
| + | |
| + | See https://github.com/curl/curl/issues/17626 |
| + | |
| 2.5 Client cert handling with Issuer DN differs between backends | |
| When the specified client certificate does not match any of the | |