KNOWN_BUGS: fixed "wolfSSL lacks support for renegotiation"

Fixed by #6411
This commit is contained in:
Daniel Stenberg 2021-01-05 10:08:06 +01:00
parent f927f38f1e
commit eacfe36991
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
1 changed files with 0 additions and 9 deletions

View File

@ -35,7 +35,6 @@ problems may have been fixed or changed somewhat since this was written!
2.10 Store TLS context per transfer instead of per connection
2.11 Schannel TLS 1.2 handshake bug in old Windows versions
2.12 FTPS with Schannel times out file list operation
2.13 curl with wolfSSL lacks support for renegotiation
2.14 Secure Transport disabling hostname validation also disables SNI
3. Email protocols
@ -317,14 +316,6 @@ problems may have been fixed or changed somewhat since this was written!
expires." - the same command line seems to work with other TLS backends and
other operating systems. See https://github.com/curl/curl/issues/5284.
2.13 curl with wolfSSL lacks support for renegotiation
I am using curl (with wolfSSL) to connect https endpoint, but connection with
this https endpoint gets terminated because server initiates the
renegotiation and client does not handle renegotiation.
See https://github.com/curl/curl/issues/5839
2.14 Secure Transport disabling hostname validation also disables SNI
SNI is the hostname that is sent by the TLS library to the server as part of