Repository navigation
qemu_v8: update Teaclave SDK revision - #356
Merged
Merged
Conversation
Contributor
|
|
Update the pinned revision to include the secure storage fix from Teaclave TrustZone SDK PR OP-TEE#318. The new revision reads persistent object data into TA-private memory before copying it to the client output buffer. This avoids passing client shared memory directly to TEE_ReadObjectData. Signed-off-by: ivila <390810839@qq.com> Acked-by: Jens Wiklander <jens.wiklander@oss.qualcomm.com>
Contributor
Author
Tag Applied. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the pinned Teaclave TrustZone SDK revision to include apache/teaclave-trustzone-sdk#318.
The secure storage example incorrectly passed client shared memory directly to
TEE_ReadObjectData. Persistent object data must first be read into TA-private memory and then copied to the client output buffer.OP-TEE/optee_os#7983 exposed this existing bug by correctly validating the destination buffer.