GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series

cross-posted from: https://piefed.world/c/tech/p/1368563/grapheneos-project-pixel-11-no-longer-supports-hardware-memory-tagging-mte

Bluesky.

Wish they’d focus on phones NOT made by major corporations like Google and Motorola, and instead focus on small companies’ phones like Fairphone, Pine64, Purism, Jolla, etc.

Those also don’t meet the hardware requirements

But why can’t GrapheneOS work with those companies to ACQUIRE the right hardware requirements, rather than leaning on a corporation?

The hardware requirements are public. Those manufacturers have chosen not to implement supported hardware, which is step 0.

There is also a maintenance burden for the GrapheneOS team. The ROM requires kernel patches and driver work that makes supporting additional phones intensive work.

Why would manufacturers choose to meet GOS’s extra requirements?

There needs to be a give and take. It seems like GOS’s mantra is their way or the high way, which isn’t collaborative in the slightest.

Can there not be discussions held between Linux and sustainable/repairable OEMs and GOS to start integrating each other’s requirements? Diplomacy/negotiations/working groups are just completely neglected?

GOS is designed for maximum security at its base. It uses all the hardware features it requires to minimize its attack surface against adversaries that have infinite resources to attack the device and get at the infirmation inside.

Lowering those standards means opening a vulnerability, which means someone with that vulnerability can have their data stolen from the device in particularly that way, since that vulnerability is well documented.