PSA crypto API: some cases of overlapping parameters are not supported #3266
Labels
bug
component-crypto
Crypto primitives and low-level interfaces
size-l
Estimated task size: large (2w+)
Comments
gilles-peskine-arm
added
bug
component-crypto
bensze01
modified the milestone:
PSA Crypto: Q4 Implement missing v1.0 spec functionality
bensze01
removed this from the
PSA Crypto: Q4 Implement missing v1.0 spec functionality milestone
minosgalanakis
pushed a commit
that referenced
this issue
Mar 28, 2024
This is the issue that tracks incomplete support for buffer overlap, so we should refer to it when we discuss partial support whenever MBEDTLS_PSA_ASSUME_EXCLUSIVE_BUFFERS is set. Signed-off-by: David Horstmann <[email protected]>
minosgalanakis
pushed a commit
that referenced
this issue
Mar 28, 2024
This is the issue that tracks incomplete support for buffer overlap, so we should refer to it when we discuss partial support whenever MBEDTLS_PSA_ASSUME_EXCLUSIVE_BUFFERS is set. Signed-off-by: David Horstmann <[email protected]>
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PSA Crypto API specifies that functions must support arbitrary overlap between input buffers and output buffers. This is mostly implemented correctly in Mbed Crypto, but there are a few exceptions. We don't systematically test overlapping parameters, so we don't know what the exceptions are.
The goal of this issue is to have systematic tests of overlapping parameters and to fix all failures revealed by these tests.
As a byproduct of analyzing whether overlapping parameters are supported, update the documentation in
include/mbedtls/*.hwhere this information is currently missing.The text was updated successfully, but these errors were encountered: