-
Notifications
You must be signed in to change notification settings - Fork 3k
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
crypto: Update to Mbed Crypto 1.0.0d1 #9463
Conversation
@Patater, thank you for your changes. |
ad1a56f
to
adc242e
Compare
Rebased to correct explanation of NSPE and SPE. |
Obtain the version of Mbed Crypto to use not from the Mbed TLS submodule, but independently through the Mbed Crypto importer instead.
Use the Mbed-Crypto-specific importer script to re-import Mbed Crypto 0.1.0b2 to its new location.
Instead of doing a "pull --rebase" to update to the latest development branch, do a "fetch" followed by a "checkout" to update to the specified release. This enables us to get any new tags created since the last update to the development branch, and removes the noise of updating a local "development" branch.
adc242e
to
e71374f
Compare
Rebased to remove stray period. |
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.
Looks good to me.
Update tests in TESTS/mbed-crypto/sanity/main.cpp
Test key handles by adding a test to TESTS/mbed-crypto/sanity/main.cpp
e71374f
to
bd0037f
Compare
Rebased to update to Mbed Crypto 1.0.0d1. Added new commits from @itayzafrir to update the Mbed OS crypto tests. |
@mpg - Could you please review this PR and check it's consistent with your architecture proposal? |
@Patater I'm not that familiar with the importer, so I think it would help my review if you could describe at a high level what this does. Since you selected "refactor" as a PR type, I'm assuming the goal of this PR is to ensure that Mbed Crypto can be fetched from a different source (ie directly from the mbed-crypto repo rather than indirectly via the mbedtls repo and its submodule), but still be placed the same way in the Mbed OS source tree (ie still as a subdirectory of the mbedtls feature) and still built the same way (ie using Can you confirm if that is the case, or clarify if I made wrong assumptions? On an unrelated front, I'm getting the impression that updating to mbedcrypto 1.0.0d1 will break Mbed TLS, due to API changes that we haven't adapted to yet (and even if we had, we'd still need to import the relevant development version of Mbed TLS in Mbed OS for it to work). It looks like the CI isn't finding that issue so far, so perhaps it should be expanded as well? |
because of interdependency issues with PR#9192 (#9192) they will need to go through CI together (each will fail on it's own, but both should pass together). If they can be unified into a single PR this might make this easier. |
Yes, that's the case. At a high level, this PR essentially reverts the Mbed TLS importer to how it was before Mbed OS 5.11. It takes the changes we added to the Mbed TLS importer in Mbed OS 5.11 to import Mbed Crypto and places those changes into their own
Yes, that's also the case for when the disabled-by-default option |
@NirSonnenschein This PR doesn't depend on #9192 as it doesn't bring in ITS changes yet. I'll raise a new PR for both the ITS changes from #9192 as well as ARMmbed/mbed-crypto#23, so that the review and merge process is simpler for this PR. |
@Patater as long as there is no interdependency then this sounds like a good way forward. |
@Patater : I'm not sure if this requires final approval from the TLS team, but started CI in the mean time. |
@Patater looks like the PSA targets fail in compilation |
Test run: FAILEDSummary: 4 of 8 test jobs failed Failed test jobs:
|
Hi @Patater : FYI , CI ran into 2 failures at the build stage:
|
@Patater compilation failed for target |
#9529 should have all the dependent PRs inside and tests should pass. Individually it's not possible as all the PRs are mutually dependent. |
Closing in favor of #9529 |
Description
Update Mbed Crypto to development version
mbedcrypto-1.0.0d1
to facilitate rest-of-Mbed-OS integration with PSA Crypto API changes sooner.In order to do this, we needed to break out the Mbed Crypto importing code from the Mbed TLS importer. This, in effect, adds a separate importer script for Mbed Crypto which can be used to directly import Mbed Crypto into Mbed OS.
Pull request type
Reviewers
CC @avolinski @alzix @sbutcher-arm