TheButlah opened a new issue, #273: URL: https://github.com/apache/teaclave-trustzone-sdk/issues/273
[The docs say](https://teaclave.apache.org/api-docs/trustzone-sdk/optee_utee/struct.Parameter.html#method.as_memref): > The caller must ensure that the raw pointer is valid and points to a properly initialized TEE_Param. But how can we be sure the raw pointer is valid? An adversarial CA could be mutating the buffer concurrently to the TA reading it, and as such maybe this buffer should instead be considered as a volatile pointer. For that reason, constructing either a &[u8] or a &mut [u8] doesn't seem safe. I would assume that the *only* safe mechanism here is to copy the buffer into the TA's stack or heap. Please advise. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
