143
GrapheneOS not supporting Pixel 11s?
(grapheneos.social)
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
much thanks to @gary_host_laptop for the logo design :)
There’s mte and emte (it’s actually way more complicated than that). Mte was shown to be vulnerable to some exploit which is partly why emte got released. The graphene os people were saying the whole time they need a new platform with emte not just mte.
Which is one reason why only the elite version of whatever qualcomm soc qualifies.
Your pixel 8 supports mte, not emte.
I don’t have a pixel 8 in front of me to perform this check on but you could easily disprove what I just said by checking proc/cpuinfo for ID_AA64PFR1_EL1.MTEX, ID_AA64PFR2_EL1.MTESTOREONLY and ID_AA64PFR2_EL1.MTEFAR or however cpuinfo reports them.
Those are the baseline implementation of enhanced memory tagging extensions, although there are more, and they’re completely optional silicon. Defined by a standard the tensor g3 processor in your pixel 8 adheres to but not required to be present.
E: I might be using some of the wrong language here for arm stuff. I spend more time in the esp world.
cat /proc/cpuinfogives me a bunch of copies of this (one per CPU core):Not sure how "MTE3" relates to "EMTE"...
Feat_mte4 is emte. You just have normal mte (it’s not just normal mte, mte3 means you also have mte2 and can do I think four different kinds of tagged memory management. It’s really powerful but it isn’t emte).
E: I just wanna toot my own horn here and congratulate me on correctly remembering details from someone else’s work while posting on the toilet. Not today cognitive decline, not today.