lowRISC
[sw] Flash secure erase and guidance
Description
There may be a software need to implement a "secure" erase. This is an erase that is multi-pass where after the data is erased a random value is then written.
It should also be well defined when such an erase should be used, since uncontrolled usage of such a feature may degrade flash endurance.
Some examples of when we would use this is when sensitive data is wiped, such as keys, owners data during ownership transfers.
There is no hardware change request with this, but it does need to be documented somewhere as guidance.
this does not need to be M3, but it's also not exactly "backlog". Do we need to create a milestone representing software items that can essentially be post silicon?
@moidx / @cfrantz - I think the priority should be bumped up for this. Please correct me if I'm wrong. @luismarques - for visibility also as this will probably need to be implemented in SW / referenced.
@moidx @johannheyszl @cfrantz we have several such "SW guidance" items for security that should be documented somewhere. what is the best milestone or label to collect these?
cc @jadephilipoom agree it would make sense to have a dedicated label.
