We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money.
GrapheneOS is an open-source fork of AOSP. Anyone could fork it again and provide kernel modules/drivers for their hardware.
To my knowledge, GrapheneOS is not standards-based. They take one operating system, and tweak it. I don’t know if there are relevant standards to contribute to, or even standards bodies to approve them.
Can other organizations replicate GrapheneOS’s principles in ways where THOSE organizations can maintain the burden?
Is GrapheneOS working towards industry wide standards on privacy-first operating systems from the hardware up?
Are they contributing to the field at large, or are they keeping to themselves out of self preservation (or selfishness)?
GrapheneOS is an open-source fork of AOSP. Anyone could fork it again and provide kernel modules/drivers for their hardware.
To my knowledge, GrapheneOS is not standards-based. They take one operating system, and tweak it. I don’t know if there are relevant standards to contribute to, or even standards bodies to approve them.