GrapheneOS on nostr

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.

1013❤️20👀3🤙2🔥1😱1🚀1

Turiz · 1w

When Infinix support

Ziggy · 1w

pixel 10 -> Motorola?

Pana - The Network State of Refuge · 1w

Wouldn't be surprised because Surveillance stodtaeis struggling to break through GrapheneOS encryption. So they built themseves a Zio backdoor. As per usual. ¯\_(ツ)_/¯ This is why we never trust anything with a Joogle tag on it..

Sondre | satoshiconsult.com · 1w

Grateful for your note, nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43q0uc5de How about connecting a working LN-address, which will enable sovereigns to zap you freedom money? https://blossom.primal.net/01b01a9410e31476a266faad91edf1c4f47...

Tobias Muller · 1w

Hardware memory tagging is critical for security—if Google cut corners here, it’s a worrying trend. Reminds me of supply chain vulnerabilities like the Oman port drone strike: small cuts can have outsized risks when security is deprioritized. https://theboard.world/articles/oman-port-drone-st...