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
There are several places where functions from the MD modules (md.h sha256.h sha512.h etc) are called in the TLS stack (ssl_tls.c in particular), but it is assumed that the underlying implementation of the MD functionality can never fail. However, this is not the case when the underlying implementation of the MD module is a hardware accelerator instead of the default Mbed TLS software implementation.
Given that the PR #1294 adds return codes to the MD modules to facilitate checking for errors, the code in the TLS stack should be revised to make use of the return values.
The text was updated successfully, but these errors were encountered:
Description
There are several places where functions from the MD modules (md.h sha256.h sha512.h etc) are called in the TLS stack (ssl_tls.c in particular), but it is assumed that the underlying implementation of the MD functionality can never fail. However, this is not the case when the underlying implementation of the MD module is a hardware accelerator instead of the default Mbed TLS software implementation.
Given that the PR #1294 adds return codes to the MD modules to facilitate checking for errors, the code in the TLS stack should be revised to make use of the return values.
The text was updated successfully, but these errors were encountered: