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. |
|
@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_RBPandFILESYSTEM_NO_RBPare 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_RBPandFILESYSTEM_NO_RBPwill 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_typeset toTDB_EXTERNAL_NO_RBPorFILESYSTEM_NO_RBPshould switch to useTDB_INTERNAL,TDB_EXTERNAL,FILESYSTEMordefaultdepending on their use cases.Documentation
ARMmbed/mbed-os-5-docs#1440 raised to remove references to
TDB_EXTERNAL_NO_RBPandFILESYSTEM_NO_RBPfrom the online documentation.Pull request type
Test results
Reviewers
@ARMmbed/mbed-os-core