Privacy

50658 readers

1227 users here now

A place to discuss privacy and freedom in the digital world.

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.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 6 years ago

MODERATORS

143

GrapheneOS not supporting Pixel 11s? (grapheneos.social)

submitted 1 day ago by soratoyuki@piefed.zip to c/privacy@lemmy.ml

51 comments fedilink hide all child comments

If GrapheneOS stops supporting future Pixels, and Motorola is only targeting the flagship market for their compatible phones, we're looking at truly dark days ahead.

you are viewing a single comment's thread
view the rest of the comments

[–] TrollAccount69@lemmy.ml 1 points 7 hours ago* (last edited 7 hours ago) (1 children)

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.

[–] grue@lemmy.world 1 points 4 hours ago (1 children)

cat /proc/cpuinfo gives me a bunch of copies of this (one per CPU core):

$ cat /proc/cpuinfo
processor       : 0                                                             
BogoMIPS        : 49.15                                                         
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdh
p cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm
 dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm sves
ha3 svesm4 flagm2 frint svei8mm svebf16 i8mm bti mte mte3                       
CPU implementer : 0x41                                                          
CPU architecture: 8                                                             
CPU variant     : 0x1                                                         
CPU part        : 0xd46                                                         
CPU revision    : 1

Not sure how "MTE3" relates to "EMTE"...

[–] TrollAccount69@lemmy.ml 2 points 3 hours ago

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).