[nrf fromtree] secure_storage: improve expandability and other minor improvements #2906
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomi-font
force-pushed
the
secure_storage_backward_compatibility
branch
from
bcfd99e to
49f2019
Compare
tomi-font
force-pushed
the
secure_storage_backward_compatibility
branch
2 times, most recently
from
29ddec6 to
9648b40
Compare
bjarki-andreasen
approved these changes
May 28, 2025
tomi-font
force-pushed
the
secure_storage_backward_compatibility
branch
from
9648b40 to
ee9413c
Compare
tomi-font
changed the title
nordicjm
approved these changes
May 29, 2025
tomi-font
force-pushed
the
secure_storage_backward_compatibility
branch
3 times, most recently
from
8db77ff to
51fd6af
Compare
Some minor improvements. Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit b87befb)
…ility Instead of checking for CONFIG_SECURE_STORAGE_ITS_TRANSFORM_AEAD_*_CUSTOM, check for any of the existing providers. This allows downstream users to expand the choices with more options Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit 9379678)
…e of transform.h Some ITS store module implementations may make use of them. This is the case of the custom one in the secure_storage.psa.its.secure_storage.custom.store test. Instead of making transform.h conditionally available, move the definitions to common.h and simply make them available whenever the ITS transform module is enabled. At the same time, remove unneeded/redundant includes/build asserts. Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit 001d054)
Instead of checking whether a custom implementation is present, check whether the AEAD one is used. This allows downstream users to expand the implementation choice with more options. Signed-off-by: Tomi Fontanilles <[email protected]> (cherry picked from commit 18b14e7)
tomi-font
force-pushed
the
secure_storage_backward_compatibility
branch
from
51fd6af to
a50439d
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Cherry pick changes for downstream integration and expansion.