this post was submitted on 30 Aug 2026
133 points (99.3% liked)

Technology

87649 readers
3006 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
133
GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series (grapheneos.social)
submitted 14 hours ago by beep@piefed.world to c/technology@lemmy.world
19 comments fedilink hide all child comments
 

cross-posted from: https://piefed.world/c/tech/p/1368563/grapheneos-project-pixel-11-no-longer-supports-hardware-memory-tagging-mte

Bluesky.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] non_burglar@lemmy.world 5 points 4 hours ago (1 children)

It's not an on/off kind of thing, MTE is a set of ARM extensions. Either the api to use them is clearly documented or, as in the pixel 11's case, Google started to not document their implementation.

We know this matches their plan to obscure the AOSP code to eventually lock out anyone else from using their base.

GOS is not in a position to reverse-engineer api calls on what was formally documented hardware.

Instead, Google rewrote critical core Android system daemons using Rust. Like the keystore, Bluetooth stack, DNS resolver, and others. I believe using Rust essentially makes MTE unnecessary.

No. Rust being "memory safe" doesn't mean rust apps can't abuse speculation or buffer under/overruns.

The point is that the post makes it sound like using a Pixel 11 under Android results in less security than before, but for most people there is no change since they never used MTE anyway.

Read the BlueSky posts, Google didn't force app devs to opt into MTE, so no one did.

Google probably decided that since hardly anyone used MTE anyway on earlier Pixel devices, they could use the space in the chip for other uses.

"Space in the chips"? Again, see the Bluesky posts.

Google is very clearly shifting over to a completely walled garden, because, same as Apple, it isn't about the hardware performance and capabilities, it's about control.