Skip to content
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

Secure storage (SQL FS and REE FS): blocks not tied to current meta header #1188

Closed
jenswi-linaro opened this issue Nov 17, 2016 · 2 comments

Comments

@jenswi-linaro
Copy link
Contributor

The blocks of a secure storage file aren't tied properly to the meta header. Even if there's no rollback protection for the meta header one can expect that given a certain version of the meta header only one combination of file blocks should be valid. Currently any block of a specific file can be rolled back and also supplied in a different order.

@jbech-linaro
Copy link
Contributor

For users of OP-TEE not working directly with Linaro, I can just mention that we have started to look into this issue and if everything goes as planned there will be a fix implemented in OP-TEE 2.4.0, that is about to happen in April 2017. (Internally in Linaro this is handled in SWG-141).

@ghost ghost added the enhancement label Feb 15, 2017
@ghost
Copy link

ghost commented Oct 6, 2017

Issue has been resolved, see SFO17-309 (video)

@ghost ghost closed this as completed Oct 6, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants