Post reply

Name
Email
Subject
Message icon

Other options

Return to this topic
Don't use smileys

Verification:

Please leave this box empty:

Shortcuts: ALT+S post or ALT+P preview

Topic summary

Posted by rept!

- Today at 12:06:29

Quote from: Opsec Followed on Yesterday at 19:38:00Great article! I was honestly too lazy to comb through that paper myself when I came across it so it's nice someone did lol, was all put together in a really concise yet explanatory way, thank you!

Only thing I would say is that you should specify that MTE is opt-in (per user app) on Android/iOS while Graphene forces it on, it's not explicitly clear they also used on non-system services in this article

Thanks for the suggestion!

Posted by Opsec Followed

- Yesterday at 19:38:00

Great article! I was honestly too lazy to comb through that paper myself when I came across it so it's nice someone did lol, was all put together in a really concise yet explanatory way, thank you!

Only thing I would say is that you should specify that MTE is opt-in (per user app) on Android/iOS while Graphene forces it on, it's not explicitly clear they also used on non-system services in this article

Posted by Redaktion

- Yesterday at 09:02:27

GrapheneOS says it will not support Google's Pixel 11 because the Tensor G6 chip lacks Memory Tagging Extension (MTE), a hardware security feature central to the privacy-focused operating system. Bootloader analysis and leaked Google documents suggest MTE was deliberately removed, prompting GrapheneOS to recommend older Pixels while exploring support for a forthcoming Motorola flagship.

https://www.notebookcheck.net/Leaked-documents-show-Google-planned-and-then-cut-a-key-Pixel-11-security-feature-for-GrapheneOS.1382732.0.html