mirror of
https://github.com/yuzu-emu/mbedtls.git
synced 2025-07-18 21:17:40 +00:00
Refine the language in the ChangeLog
Fix the language and descriptions in the ChangeLog and some duplicate entries, following review of the Release Notes for the next release.
This commit is contained in:
parent
a2c8691c0d
commit
90e6c3b941
22
ChangeLog
22
ChangeLog
|
@ -4,27 +4,27 @@ mbed TLS ChangeLog (Sorted per branch, date)
|
||||||
|
|
||||||
Security
|
Security
|
||||||
* Fix overly strict DN comparison when looking for CRLs belonging to a
|
* Fix overly strict DN comparison when looking for CRLs belonging to a
|
||||||
particular CA. This previously lead to ignoring CRLs when the CRL's issuer
|
particular CA. This previously led to ignoring CRLs when the CRL's issuer
|
||||||
name and the CA's subject name differed in their string encoding (e.g.,
|
name and the CA's subject name differed in their string encoding (e.g.,
|
||||||
one using PrintableString and the other UTF8String) or in the choice of
|
one using PrintableString and the other UTF8String) or in the choice of
|
||||||
upper and lower case. Reported by Henrik Andersson of Bosch GmbH in issue
|
upper and lower case. Reported by Henrik Andersson of Bosch GmbH in issue
|
||||||
#1784.
|
#1784.
|
||||||
|
* Fix a flawed bounds check in server PSK hint parsing. In case the
|
||||||
|
incoming message buffer was placed within the first 64KiB of address
|
||||||
|
space and a PSK-(EC)DHE ciphersuite was used, this allowed an attacker
|
||||||
|
to trigger a memory access up to 64KiB beyond the incoming message buffer,
|
||||||
|
potentially leading to application crash or information disclosure.
|
||||||
* Fix mbedtls_mpi_is_prime() to use more rounds of probabilistic testing. The
|
* Fix mbedtls_mpi_is_prime() to use more rounds of probabilistic testing. The
|
||||||
previous settings for the number of rounds made it practical for an
|
previous settings for the number of rounds made it practical for an
|
||||||
adversary to construct non-primes that would be erroneously accepted as
|
adversary to construct non-primes that would be erroneously accepted as
|
||||||
primes with high probability. This does not have an impact on the
|
primes with high probability. This does not have an impact on the
|
||||||
security of TLS, but can matter in other contexts with potentially
|
security of TLS, but can matter in other contexts with numbers chosen
|
||||||
adversarially-chosen numbers that should be prime and can be validated.
|
potentially by an adversary that should be prime and can be validated.
|
||||||
For example, the number of rounds was enough to securely generate RSA key
|
For example, the number of rounds was enough to securely generate RSA key
|
||||||
pairs or Diffie-Hellman parameters, but was insufficient to validate
|
pairs or Diffie-Hellman parameters, but was insufficient to validate
|
||||||
Diffie-Hellman parameters properly.
|
Diffie-Hellman parameters properly.
|
||||||
See "Prime and Prejudice" by by Martin R. Albrecht and Jake Massimo and
|
See "Prime and Prejudice" by by Martin R. Albrecht and Jake Massimo and
|
||||||
Kenneth G. Paterson and Juraj Somorovsky.
|
Kenneth G. Paterson and Juraj Somorovsky.
|
||||||
* Fix a flawed bounds check in server PSK hint parsing. In case the
|
|
||||||
incoming message buffer was placed within the first 64KB of address
|
|
||||||
space and a PSK-(EC)DHE ciphersuite was used, this allowed an attacker
|
|
||||||
to trigger a memory access up to 64KB beyond the incoming message buffer,
|
|
||||||
potentially leading to application crash or information disclosure.
|
|
||||||
|
|
||||||
Bugfix
|
Bugfix
|
||||||
* Fix failure in hmac_drbg in the benchmark sample application, when
|
* Fix failure in hmac_drbg in the benchmark sample application, when
|
||||||
|
@ -34,7 +34,7 @@ Bugfix
|
||||||
* Fix potential build failures related to the 'apidoc' target, introduced
|
* Fix potential build failures related to the 'apidoc' target, introduced
|
||||||
in the previous patch release. Found by Robert Scheck. #390 #391
|
in the previous patch release. Found by Robert Scheck. #390 #391
|
||||||
* Fix a bug in the record decryption routine ssl_decrypt_buf()
|
* Fix a bug in the record decryption routine ssl_decrypt_buf()
|
||||||
which lead to accepting properly authenticated but improperly
|
which led to accepting properly authenticated but improperly
|
||||||
padded records in case of CBC ciphersuites using Encrypt-then-MAC.
|
padded records in case of CBC ciphersuites using Encrypt-then-MAC.
|
||||||
* Fix wrong order of freeing in programs/ssl/ssl_server2 example
|
* Fix wrong order of freeing in programs/ssl/ssl_server2 example
|
||||||
application leading to a memory leak in case both
|
application leading to a memory leak in case both
|
||||||
|
@ -44,10 +44,6 @@ Bugfix
|
||||||
program programs/x509/cert_write. Fixes #1422.
|
program programs/x509/cert_write. Fixes #1422.
|
||||||
* Ignore IV in mbedtls_cipher_set_iv() when the cipher mode is
|
* Ignore IV in mbedtls_cipher_set_iv() when the cipher mode is
|
||||||
MBEDTLS_MODE_ECB. Found by ezdevelop, Fixes #1091.
|
MBEDTLS_MODE_ECB. Found by ezdevelop, Fixes #1091.
|
||||||
* Fix failure in hmac_drbg in the benchmark sample application, when
|
|
||||||
MBEDTLS_THREADING_C is defined. Found by TrinityTonic, #1095
|
|
||||||
* Fix a bug in the update function for SSL ticket keys which previously
|
|
||||||
invalidated keys of a lifetime of less than a 1s. Fixes #1968.
|
|
||||||
* Zeroize memory used for reassembling handshake messages after use.
|
* Zeroize memory used for reassembling handshake messages after use.
|
||||||
* Use `mbedtls_zeroize()` instead of `memset()` for zeroization of
|
* Use `mbedtls_zeroize()` instead of `memset()` for zeroization of
|
||||||
sensitive data in the example programs aescrypt2 and crypt_and_hash.
|
sensitive data in the example programs aescrypt2 and crypt_and_hash.
|
||||||
|
|
Loading…
Reference in a new issue