crypto: Move nrf_oberon base library out of BUILD_WITH_TFM filter #1520
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-This allows direct calls to nrf_oberon library regardless if
TF-M is set for the implementations that don't have a PSA crypto API
to call (for ocrypto_ prefixed calls)
Note: This addition is done to allow deprecating more legacy features by always allowing NRF_SECURITY being enabled by default. Previously the NORDIC_SECURITY_BACKEND and legacy Mbed TLS APIs was allowing for direct access to nrf_oberon and its proprietary APIs.
ref: NCSDK-29217