UUIDs in binary format have wrong endinanness #858
Labels
Comments
ghost
added
the
jenswi-linaro
added a commit
to jenswi-linaro/optee_os
that referenced
this issue
Dec 8, 2016
When encoding a UUID as a sequence of bytes, the spec (https://www.ietf.org/rfc/rfc4122.txt) says that the u32, and two u16s should be represented big endian. Before this patch OPTEE always treated them natively. With this patch UUIDs are always converted to/from big endian when communicating with normal world. Fixes: OP-TEE#858 Signed-off-by: Jens Wiklander <[email protected]>
jenswi-linaro
added a commit
to jenswi-linaro/optee_client
that referenced
this issue
Dec 8, 2016
When encoding a UUID as a sequence of bytes, the spec (https://www.ietf.org/rfc/rfc4122.txt) says that the u32, and two u16s should be represented big endian. Before this patch OPTEE always treated them natively. With this patch UUIDs are always converted to/from big endian when communicating with the kernel. Fixes: OP-TEE/optee_os#858 Signed-off-by: Jens Wiklander <[email protected]>
jenswi-linaro
added a commit
to jenswi-linaro/optee_client
that referenced
this issue
Dec 9, 2016
When encoding a UUID as a sequence of bytes, the spec (https://www.ietf.org/rfc/rfc4122.txt) says that the u32, and two u16s should be represented big endian. Before this patch OPTEE always treated them natively. With this patch UUIDs are always converted to/from big endian when communicating with the kernel. Reviewed-by: Jerome Forissier <[email protected]> Fixes: OP-TEE/optee_os#858 Signed-off-by: Jens Wiklander <[email protected]>
jenswi-linaro
added a commit
to jenswi-linaro/optee_os
that referenced
this issue
Dec 9, 2016
When encoding a UUID as a sequence of bytes, the spec (https://www.ietf.org/rfc/rfc4122.txt) says that the u32, and two u16s should be represented big endian. Before this patch OPTEE always treated them natively. With this patch UUIDs are always converted to/from big endian when communicating with normal world. Reviewed-by: Jerome Forissier <[email protected]> Fixes: OP-TEE#858 Signed-off-by: Jens Wiklander <[email protected]>
takuya-sakata
pushed a commit
to renesas-rcar/optee_os
that referenced
this issue
Dec 22, 2017
When encoding a UUID as a sequence of bytes, the spec (https://www.ietf.org/rfc/rfc4122.txt) says that the u32, and two u16s should be represented big endian. Before this patch OPTEE always treated them natively. With this patch UUIDs are always converted to/from big endian when communicating with normal world. Reviewed-by: Jerome Forissier <[email protected]> Fixes: OP-TEE/optee_os#858 Signed-off-by: Jens Wiklander <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When encoding a UUID as a sequence of bytes, the spec says that the u32, and two u16s should be represented big endian. OPTEE always treats them natively, which on all supported targets is little-endian.
For most use cases, such as the
ioctlinterface, it doesn't really matter, as long as both ends misinterpret the bytes the same way. This is more of a concern if they are being stored or communicated in this format however.The text was updated successfully, but these errors were encountered: