romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-07-23 15:47:15 +03:00
Code Issues Projects Releases Packages Wiki Activity

KNOWN_BUGS: Access violation sending client cert with SChannel

Browse source 
It seems we can select between crashing or leaking sensitive files
because Schannel is buggy.

Closes #17626
Closes #18679
This commit is contained in:
Daniel Stenberg 2025-09-22 10:09:18 +02:00
parent 9d3f878e59
commit 97e5a471e0
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
docs/KNOWN_BUGS
View file

@ -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