Access the keystore via a path rather than the CoreContext #29
Conversation
This file contains 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
This syscall does the same as `delete` for a key. The only difference is that it is designed to allow re-import of the key if it was exported with `WrapKey`. With the core trussed backend this does not change anything, as nothing is needed to allow the re-import. However the same mechansim in the SE050 work differently, and being able to differenciate permanent deletion and deletion with intent to re-import is crucial.
Similar to 5af424e, this patch updates the `keystore` method to be able to create a keystore with a custom path. This can be useful for backends that want to have a keystore distinct from the core one.
This was referenced Aug 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Similar to 5af424e, this patch updates
the
keystoremethod to be able to create a keystore with a custom path.This can be useful for backends that want to have a keystore distinct from
the core one.
Built on top of #28