mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2025-06-16 14:40:24 +00:00
Revise ChangeLog entry for empty data records fixes
This commit is contained in:
parent
642ddb555e
commit
be9c2dce5b
11
ChangeLog
11
ChangeLog
|
@ -21,11 +21,12 @@ Bugfix
|
||||||
Philippe Antoine from Catena cyber. #1663.
|
Philippe Antoine from Catena cyber. #1663.
|
||||||
* Fix namespacing in header files. Remove the `mbedtls` namespacing in
|
* Fix namespacing in header files. Remove the `mbedtls` namespacing in
|
||||||
the `#include` in the header files. Resolves #857
|
the `#include` in the header files. Resolves #857
|
||||||
* Fix decryption of zero length messages (all padding) in some circumstances:
|
* Fix decryption for zero length messages (which contain all padding) when a
|
||||||
DTLS 1.0 and 1.2, and CBC ciphersuites using encrypt-then-MAC. Most often
|
CBC based ciphersuite is used together with Encrypt-then-MAC. Previously,
|
||||||
seen when communicating with OpenSSL using TLS 1.0. Reported by @kFYatek
|
such a message was wrongly reported as an invalid record and therefore lead
|
||||||
(#1632) and by Conor Murphy on the forum. Fix contributed by Espressif
|
to the connection being terminated. Seen most often with OpenSSL using
|
||||||
Systems.
|
TLS 1.0. Reported by @kFYatek and by Conor Murphy on the forum. Fix
|
||||||
|
contributed by Espressif Systems. Fixes #1632
|
||||||
* Fail when receiving a TLS alert message with an invalid length, or invalid
|
* Fail when receiving a TLS alert message with an invalid length, or invalid
|
||||||
zero-length messages when using TLS 1.2. Contributed by Espressif Systems.
|
zero-length messages when using TLS 1.2. Contributed by Espressif Systems.
|
||||||
* Fix ssl_client2 example to send application data with 0-length content
|
* Fix ssl_client2 example to send application data with 0-length content
|
||||||
|
|
Loading…
Reference in a new issue