KNOWN_BUGS: remove 2.5 client cert handling differs between backends

This was resolved in #4958

Closes #16175

diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index bdb029bf049c00ae04616e5a9495788bdaecb927..d6e8a5a9b530be165ce781db279acb33a914dca7 100644 (file)
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -17,7 +17,6 @@ problems may have been fixed or changed somewhat since this was written.
  2.1 IMAPS connection fails with Rustls error
  2.3 Unable to use PKCS12 certificate with Secure Transport
  2.4 Secure Transport does not import PKCS#12 client certificates without a password
- 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
  2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel
@@ -136,14 +135,6 @@ problems may have been fixed or changed somewhat since this was written.
  function rejects certificates that do not have a password.
  https://github.com/curl/curl/issues/1308
 
-2.5 Client cert handling with Issuer DN differs between backends
-
- When the specified client certificate does not match any of the
- server-specified DNs, the OpenSSL and GnuTLS backends behave differently.
- The github discussion may contain a solution.
-
- See https://github.com/curl/curl/issues/1411
-
 2.7 Client cert (MTLS) issues with Schannel
 
  See https://github.com/curl/curl/issues/3145