Commit 3a3d515f82 for openssl.org
commit 3a3d515f821b8032cc5fef7a0c1fc960d384de9d
Author: Ryan Hooper <ryanh@openssl.foundation>
Date: Wed Oct 21 13:20:45 2026 -0400
Document DTLS listener error-reporting known issues
Add OpenSSL 4.1.0 release notes for permanent receive failures reported
as retries and retryable writes reported as fatal errors on connections
accepted from DTLS listeners.
Refs: #33277
Refs: #33278
Assisted-by: OpenAI:gpt-6-astra
Reviewed-by: Tomas Mraz <tomas@openssl.foundation>
Reviewed-by: Milan Broz <mbroz@openssl.org>
Merge-date: Thu Oct 22 14:56:47 2026
Merged-from: https://github.com/openssl/openssl/pull/33295
diff --git a/NEWS.md b/NEWS.md
index c483f70545..e192ea35b7 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -87,6 +87,18 @@ Known issues in 4.1.0
transmission is lost. A fix is in progress and planned for a future
release.
+ * <https://github.com/openssl/openssl/issues/33277>
+ A permanent receive failure on a DTLS listener can be reported as
+ `SSL_ERROR_WANT_READ` on an accepted connection. Polling and subsequent
+ accept calls may also fail to report the error, causing applications
+ to continue waiting after a permanent failure.
+
+ * <https://github.com/openssl/openssl/issues/33278>
+ A retryable write failure on a nonblocking connection accepted from a
+ DTLS listener can be reported as `SSL_ERROR_SYSCALL` instead of
+ `SSL_ERROR_WANT_WRITE`. Applications treating this result as fatal may
+ close a connection that is still usable.
+
OpenSSL 4.0
-----------