-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Backport 3.6: psa_generate_key_custom #9235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport 3.6: psa_generate_key_custom #9235
Conversation
452ded4
to
4afef10
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Initial pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the replies and the fix.
LGTM :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
ABI-API check failure expected. The Windows-2013-Release-x64-cmake-retarget failure is unrelated:
|
(minor, related to PR title) it's not really a backport, it's normal development, just against the 3.6 branch, not the development branch. There will be a (quite different!) forward port - effectively a different fix - for development |
Don't formally deprecate them because we don't do that in a long-time support branch. But do point readers away from them. Signed-off-by: Gilles Peskine <[email protected]>
We know it's a thin wrapper around psa_generate_key_custom, so we just need to check that it's passing the information through, we don't need coverage of the parameter interpretation. Signed-off-by: Gilles Peskine <[email protected]>
Document psa_generate_key_ext() and psa_key_derivation_output_key_ext() as deprecated in favor of psa_generate_key_custom() and psa_key_derivation_output_key_custom(), and no longer declared in C++ builds. Resolves Mbed-TLS#9020. Signed-off-by: Gilles Peskine <[email protected]>
In public headers, we want to avoid things that are not standard C++, including features that GCC and Clang support as extensions, such as flexible array members. So compile with `-pedantic`. Non-regression for Mbed-TLS#9020. Signed-off-by: Gilles Peskine <[email protected]>
Signed-off-by: Gilles Peskine <[email protected]>
Signed-off-by: Gilles Peskine <[email protected]>
Signed-off-by: Gilles Peskine <[email protected]>
Signed-off-by: Gilles Peskine <[email protected]>
Signed-off-by: Gilles Peskine <[email protected]>
14b87f6
4acd8c9
to
14b87f6
Compare
Rebased for the
|
@tom-cosgrove-arm Technically, yes, this is the original PR and the development version is a forward port. But once both PR are up, it doesn't make a difference any longer. And for gatekeeping, it's easier if the title convention is uniform. |
By the way, |
Hi all, commit 52504f8, which got merged with this pull request, removed (renamed) This is currently holding back upgrading to the latest MbedTLS LTS release in Debian. |
@Tachi107 Our build scripts are not set to hide symbols that are not exposed in public headers because the way to do that depends on the toolchain, and we don't like to maintain toolchain-dependent code. That being said, we have considered adding |
Migrate from
psa_generate_key_ext()
andpsa_key_derivation_output_key_ext()
topsa_generate_key_custom()
andpsa_key_derivation_output_key_custom()
:The API now matches the current state of ARM-software/psa-api#194.
Resolves #9020.
I started with the 3.6 PR because that's the hardest part where we care about backward compatibility. In development, since we're working on a new major version, we can just remove the old function.
PR checklist