You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the configuration option MBEDTLS_SHA512_NO_SHA384 is enabled, the SHA-384 algorithm is disabled, and in particular TLS cipher suites that use SHA-384 cannot be used. However they are still offered by mbedtls_ssl_list_ciphersuites, leading to an internal error when selected.
Steps to reproduce:
$ scripts/config.py set MBEDTLS_SHA512_NO_SHA384
$ make
$ programs/ssl/ssl_client2 force_ciphersuite=TLS-ECDH-ECDSA-WITH-AES-256-GCM-SHA384
. Seeding the random number generator... ok
. Loading the CA root certificate ... ok (0 skipped)
. Loading the client cert. and key... ok (key type: RSA)
. Connecting to tcp/localhost/4433... ok
. Setting up the SSL/TLS structure... ok
. Performing the SSL/TLS handshake... failed
! mbedtls_ssl_handshake returned -0x6c00
Last error was: -0x6C00 - SSL - Internal error (eg, unexpected failure in lower-level module)
This only applies to 2.2x. In 2.16, MBEDTLS_SHA512_NO_SHA384 did not exist yet. In 3.0 this is fixed by #4304.
The text was updated successfully, but these errors were encountered:
They depended on MBEDTLS_SHA512_C only. A check for !MBEDTLS_SHA512_NO_SHA384
was missing.
FixMbed-TLS#4499.
Signed-off-by: Gilles Peskine <[email protected]>
They depended on MBEDTLS_SHA512_C only. A check for !MBEDTLS_SHA512_NO_SHA384
was missing.
FixMbed-TLS#4499.
Signed-off-by: Gilles Peskine <[email protected]>
They depended on MBEDTLS_SHA512_C only. A check for !MBEDTLS_SHA512_NO_SHA384
was missing.
FixMbed-TLS#4499.
Signed-off-by: Gilles Peskine <[email protected]>
They depended on MBEDTLS_SHA512_C only. A check for !MBEDTLS_SHA512_NO_SHA384
was missing.
FixMbed-TLS#4499.
Signed-off-by: Gilles Peskine <[email protected]>
When the configuration option
MBEDTLS_SHA512_NO_SHA384
is enabled, the SHA-384 algorithm is disabled, and in particular TLS cipher suites that use SHA-384 cannot be used. However they are still offered bymbedtls_ssl_list_ciphersuites
, leading to an internal error when selected.Steps to reproduce:
This only applies to 2.2x. In 2.16,
MBEDTLS_SHA512_NO_SHA384
did not exist yet. In 3.0 this is fixed by #4304.The text was updated successfully, but these errors were encountered: