avb: add support for named persistent values
AVB 2.0 spec. revision 1.1 introduces support for named persistent values that must be tamper evident and allows AVB to store arbitrary key-value pairs [1]. Introduce implementation of two additional AVB operations read_persistent_value()/write_persistent_value() for retrieving/storing named persistent values. Correspondent pull request in the OP-TEE OS project repo [2]. [1]: https://android.googlesource.com/platform/external/avb/+/android-9.0.0_r22 [2]: https://github.com/OP-TEE/optee_os/pull/2699 Reviewed-by:Simon Glass <sjg@chromium.org> Reviewed-by:
Sam Protsenko <semen.protsenko@linaro.org> Signed-off-by:
Igor Opaniuk <igor.opaniuk@gmail.com>
Showing
- cmd/avb.c 78 additions, 0 deletionscmd/avb.c
- common/avb_verify.c 125 additions, 0 deletionscommon/avb_verify.c
- drivers/tee/sandbox.c 102 additions, 19 deletionsdrivers/tee/sandbox.c
- include/sandboxtee.h 12 additions, 3 deletionsinclude/sandboxtee.h
- include/tee.h 2 additions, 0 deletionsinclude/tee.h
- include/tee/optee_ta_avb.h 16 additions, 0 deletionsinclude/tee/optee_ta_avb.h
- test/py/tests/test_avb.py 16 additions, 0 deletionstest/py/tests/test_avb.py
Loading
Please register or sign in to comment