-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Deprecate broken TDB_EXTERNAL_NO_RBP and FILESYSTEM_NO_RBP in kv_config #14657
Conversation
NO_RBP (no rollback protection) is intended to not require an internal TDB, however, DeviceKey, which we use to derive SecureStore's encryption key, still does. Currently, no internal TDB is created with these two configurations, meaning there's no way to store the DeviceKey and SecureStore doesn't work.
The documentation previously referred to a weakly defined function `storage_configuration`, however, this function was replaced at some stage by `kv_init_storage_config`. Refactor the explanation on how to override the default configurations to reflect this. Also, remove the snippet which was used to show the implentation of `storage_configuration`.
@LDong-Arm, thank you for your changes. |
I would mark this as functionality change, although it could be patch. A reason: adding this to the release notes automatically. The changes look good to me. |
Now changed. |
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.
LGTM
@LDong-Arm as this is a functionality change please also fill in : |
Updated |
This pull request has automatically been marked as stale because it has had no recent activity. @ARMmbed/mbed-os-maintainers, please start CI to get the PR merged. |
Ci started |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Summary of changes
Replaces #14490: changed from removal to deprecation due to the Mbed OS release model.
NO_RBP (no rollback protection) is intended to not require an internal TDB, however, DeviceKey, which we use to derive SecureStore's encryption key, still does. Currently, no internal TDB is created with these two configurations, meaning there's no way to store the DeviceKey and SecureStore doesn't work. The configurations
TDB_EXTERNAL_NO_RBP
andFILESYSTEM_NO_RBP
are broken due to this design flaw.This PR deprecates the non-working configurations, with their documentations removed but code and configurations kept with deprecation warnings. They will be completely removed from the next major release.
Impact of changes
Existing applications that use
TDB_EXTERNAL_NO_RBP
andFILESYSTEM_NO_RBP
will still be able to compile for now, until we fully remove the two configurations in the future. But they have never been functional, so no application should have ever been able to use them.Migration actions required
Applications that have
storage.storage_type
set toTDB_EXTERNAL_NO_RBP
orFILESYSTEM_NO_RBP
should switch to useTDB_INTERNAL
,TDB_EXTERNAL
,FILESYSTEM
ordefault
depending on their use cases.Documentation
ARMmbed/mbed-os-5-docs#1440 raised to remove references to
TDB_EXTERNAL_NO_RBP
andFILESYSTEM_NO_RBP
from the online documentation.Pull request type
Test results
Reviewers
@ARMmbed/mbed-os-core