summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJay Satiro <raysatiro@yahoo.com>2021-08-24 12:54:03 -0400
committerJay Satiro <raysatiro@yahoo.com>2021-08-25 03:37:37 -0400
commit1e67c73b5addc790e7890eb72ce9b2394f83db3a (patch)
tree348a15b96080269d855cac71fd64b6b1bf597898
parent825911be587bbabc3b7e4777ed3bd1bb7c858b58 (diff)
downloadcurl-1e67c73b5addc790e7890eb72ce9b2394f83db3a.tar.gz
KNOWN_BUGS: FTPS upload data loss with TLS 1.3
Bug: https://github.com/curl/curl/issues/6149 Reported-by: Bylon2@users.noreply.github.com Closes https://github.com/curl/curl/pull/7623
-rw-r--r--docs/KNOWN_BUGS18
1 files changed, 18 insertions, 0 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 22f7bc420..7032a2d56 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -86,6 +86,7 @@ problems may have been fixed or changed somewhat since this was written!
7.8 Premature transfer end but healthy control channel
7.9 Passive transfer tries only one IP address
7.10 FTPS needs session reuse
+ 7.11 FTPS upload data loss with TLS 1.3
8. TELNET
8.1 TELNET and time limitations don't work
@@ -723,6 +724,23 @@ problems may have been fixed or changed somewhat since this was written!
https://github.com/curl/curl/issues/4654
+7.11 FTPS upload data loss with TLS 1.3
+
+ During FTPS upload curl does not attempt to read TLS handshake messages sent
+ after the initial handshake. OpenSSL servers running TLS 1.3 may send such a
+ message. When curl closes the upload connection if unread data has been
+ received (such as a TLS handshake message) then the TCP protocol sends an
+ RST to the server, which may cause the server to discard or truncate the
+ upload if it hasn't read all sent data yet, and then return an error to curl
+ on the control channel connection.
+
+ Since 7.78.0 this is mostly fixed. curl will do a single read before closing
+ TLS connections (which causes the TLS library to read handshake messages),
+ however there is still possibility of an RST if more messages need to be read
+ or a message arrives after the read but before close (network race condition).
+
+ https://github.com/curl/curl/issues/6149
+
8. TELNET
8.1 TELNET and time limitations don't work