There isn't currently a usable open hardware SoC, Wi-Fi radio, cellular radio, SSD, touchscreen, etc.
Running an open source OS doesn't make hardware open. Using an open source late stage boot chain (coreboot, etc.) doesn't make the firmware open, as that's a tiny part of it and it still begins from closed source hardware/firmware.
Having the sources for an open hardware SoC doesn't mean you can simply build it yourself. You need a manufacturer to build it for you, and their manufacturing process will be closed source. The end result is not really open, and even if it was, individuals in the main couldn't verify that it is.
Pixel phones uses their open source Trusty OS for the TEE (TrustZone) and secure core (core in SoC which talks to secure element). Pixel-specific variants of Trusty OS are not published yet, as far as we know, but we may just be missing where they publish it (unlikely though).
Secure element has https://opentitan.org as an open source project. Titan M2 is a RISC-V core sharing a lot with this, but similarly the Pixel-specific code isn't published yet. They said they'd publish it but it's takign a long time to do it. ARM NDA likely blocked it before.
GrapheneOS goes a long way toward not having to trust the hardware, any compromise of it, would then also require a further OS based exploit to compromise your data. There does not exist any disclosed exploits for GrapheneOS and we are a high value target.
MetropleX [GrapheneOS] ⚡🟣
npub1gd…7cn8c
2023-08-09 19:47:30
in reply to nevent1q…90mu
Author Public Key
npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8cPublished at
2023-08-09 19:47:30Event JSON
{
"id": "e5ad57478e1da472c19ef05cbaf9cc1abd8093257003ae65fbd5b478d645f6b3",
"pubkey": "43637a311a15f1c253b5d60778ab7544ac639b88e168e7224a900d4a41283183",
"created_at": 1691610450,
"kind": 1,
"tags": [
[
"e",
"2af20a4fe388a933ba6d4cf41090a5c4ba2cc9c0b23de6c9ae3927593b54b9d3",
"",
"reply"
],
[
"p",
"04c915daefee38317fa734444acee390a8269fe5810b2241e5e6dd343dfbecc9"
],
[
"p",
"4aa4d22440770429fa745b674fab7e46ed267f36a1abae6ff4e8d26eb65b7f52"
],
[
"r",
"https://opentitan.org"
]
],
"content": "There isn't currently a usable open hardware SoC, Wi-Fi radio, cellular radio, SSD, touchscreen, etc. \n\nRunning an open source OS doesn't make hardware open. Using an open source late stage boot chain (coreboot, etc.) doesn't make the firmware open, as that's a tiny part of it and it still begins from closed source hardware/firmware.\n\nHaving the sources for an open hardware SoC doesn't mean you can simply build it yourself. You need a manufacturer to build it for you, and their manufacturing process will be closed source. The end result is not really open, and even if it was, individuals in the main couldn't verify that it is.\n\nPixel phones uses their open source Trusty OS for the TEE (TrustZone) and secure core (core in SoC which talks to secure element). Pixel-specific variants of Trusty OS are not published yet, as far as we know, but we may just be missing where they publish it (unlikely though).\n\nSecure element has https://opentitan.org as an open source project. Titan M2 is a RISC-V core sharing a lot with this, but similarly the Pixel-specific code isn't published yet. They said they'd publish it but it's takign a long time to do it. ARM NDA likely blocked it before.\n\nGrapheneOS goes a long way toward not having to trust the hardware, any compromise of it, would then also require a further OS based exploit to compromise your data. There does not exist any disclosed exploits for GrapheneOS and we are a high value target.",
"sig": "4abbde3af6d6103d09c07d778f1abbfb83e81efcd7e3e3af3419bcccc8e7e5b38799b41b11f0d3fda1cdf3ffd5de4de12b7afd1d30155855aea3b8fae1ff8129"
}