-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remove NORDIC_SECURITY_BACKEND selections for BLE/FAST_PAIR #17961
Conversation
The following west manifest projects have been modified in this Pull Request: Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 18c243e91f12b40e772464f6ffef4a5121e811ce more detailssdk-nrf:
nrfxlib:
find-my:
Github labels
List of changed files detected by CI (5)
File list hidden for private repositories. Outputs:ToolchainVersion: 3dd8985b56 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
@frkv, could you also align the Find My part and revert my change from upmerge? https://github.com/nrfconnect/sdk-find-my/commit/42d731a502932ccec09a75461b2d4316d4c3aa6b |
@@ -203,7 +203,7 @@ endif() | |||
add_subdirectory(drivers) | |||
|
|||
# Add legacy Mbed TLS APIs | |||
if(CONFIG_MBEDTLS_LEGACY_CRYPTO_C) | |||
if(CONFIG_MBEDTLS_LEGACY_CRYPTO_C OR (CONFIG_NRF_OBERON AND CONFIG_BUILD_WITH_TFM)) |
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.
Why AND CONFIG_BUILD_WITH_TFM
?
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.
Because we use the same code in both TF-M (secure image) and NS image builds. We don't want to load legacy libraries just based on CONFIG_NRF_OBERON
. Checking that CONFIG_BUILD_WITH_TFM
is set means we can be sure we are in an NS image...
b6879f0
to
a481129
Compare
Contacting you offline |
a481129
to
897a295
Compare
897a295
to
41f68af
Compare
be63881
to
bf1fbb5
Compare
2a5e49e
to
921bdad
Compare
-This allows for direct calls to nrf_oberon with TF-M builds without also enabling NORDIC_SECURITY_BACKEND ref: NCSDK-29217 Signed-off-by: Frank Audun Kvamtrø <[email protected]>
-This commit allows linking to nrf_oberon for samples/apps that enable TF-M but still rely on ocrypto_ prefixed APIs because some of the crypto not being available in PSA crypto APIs. Note: Previous to this it was required to enable NORDIC_SECURITY_BACKEND to get access to nrf_oberon library (and ocrypto_ prefixed APIs). This commit will allow CONFIG_NRF_OBERON to be used as a signal that ocrypto_ APIs are required with NRF_SECURITY being enabled ref: NCSDK-29217 Signed-off-by: Frank Audun Kvamtrø <[email protected]>
-This commit removes selection of legacy crypto just to get acces to nrf_oberon (and ocrypto_ prefixed APIs) -This commit enables NRF_OBERON regardless if TF-M is enabled or not ref: NCSDK-29217 Signed-off-by: Frank Audun Kvamtrø <[email protected]>
-This commit allows direct calls to nrf_oberon (ocrypto_ prefixed APIs) without simultaneously requiring NORDIC_SECURITY_BACKEND being set. -This commit enables NRF_OBERON regardless if TF-M is enabled or not ref: NCSDK-29217 Signed-off-by: Frank Audun Kvamtrø <[email protected]>
921bdad
to
18c243e
Compare
This PR allows usage of nrf_oberon when TF-M is enabled without additionally selecting NORIDC_SECURITY_BACKEND
which would favour legacy API support (when it is unneeded)
ref: NCSDK-29217