-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix a few SecureStore issues (following preliminary security review) #8987
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
Conversation
@davidsaada, thank you for your changes. |
@jenia81 @shelib01 @evgenibo @TaniaMirzin @trianglee Please be aware of this change that is a result of a preliminary security review: REQUIRE_INTEGRITY_FLAG has been removed and authentication is now mandatory. Other security bugs solved. |
@AnotherButler This change will require changes in documentation. Will issue a PR |
4a7247c
to
b533f9d
Compare
@0xc0170 @adbridge @dannybenor |
@davidsaada Anyone else who should review? We can start CI in the meantime |
CI started |
Test run: FAILEDSummary: 1 of 11 test jobs failed Failed test jobs:
|
@davidsaada Please take a look at the |
- Remove require integrity flag (authentication) - always authenticate - Use RBP KV to store CMAC also in write once case - Allow removing a key if reading it failed on RBP authentication error - Disable SecureStore if user disables MBED TLS AES CTR or CMAC
b533f9d
to
cb7f68e
Compare
@cmonr Should be OK now. |
CI started |
Test run: SUCCESSSummary: 11 of 11 test jobs passed |
Description
This PR includes a few fixes to SecureStore, following a preliminary security review.
These include:
Design docs modified as well.
Resolves #8865
Pull request type