From 858894056dc3bf7bc49b7ed6b7ce4c5e328a60b6 Mon Sep 17 00:00:00 2001 From: Dave Rodgman Date: Tue, 29 Jun 2021 09:43:55 +0100 Subject: [PATCH] Improve changelog Signed-off-by: Dave Rodgman --- ChangeLog.d/fix_fragment_len_return.txt | 5 ----- ChangeLog.d/fix_tls_alert_codes.txt | 6 ++++++ 2 files changed, 6 insertions(+), 5 deletions(-) delete mode 100644 ChangeLog.d/fix_fragment_len_return.txt create mode 100644 ChangeLog.d/fix_tls_alert_codes.txt diff --git a/ChangeLog.d/fix_fragment_len_return.txt b/ChangeLog.d/fix_fragment_len_return.txt deleted file mode 100644 index bfbf93cd2..000000000 --- a/ChangeLog.d/fix_fragment_len_return.txt +++ /dev/null @@ -1,5 +0,0 @@ -Bugfix - * Fix the error returned when a client requests an invalid - * fragment length, as per RFC6066 section 4. We now return - * MBEDTLS_ERR_SSL_ILLEGAL_PARAMETER, and raise the corresponding - * alert. diff --git a/ChangeLog.d/fix_tls_alert_codes.txt b/ChangeLog.d/fix_tls_alert_codes.txt new file mode 100644 index 000000000..abe3a5e6d --- /dev/null +++ b/ChangeLog.d/fix_tls_alert_codes.txt @@ -0,0 +1,6 @@ +Bugfix + * Fix the alert raised when a client requests an invalid + * fragment length, as per RFC6066 section 4. We now alert with + * MBEDTLS_SSL_ALERT_MSG_ILLEGAL_PARAMETER. Similarly, raise + * MBEDTLS_SSL_ALERT_MSG_DECRYPT_ERROR for an invalid finished + * message, as per RFC5247 section 7.2.2.