Live data from Hacker News

Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

outflux.net

31–40 of 61 posts

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#31
post #22

Earlier quoted context omitted.

Writing this from a Pixel running GrapheneOS. I've been away from Graphene (using Lineage) since the CopperheadOS days. Coming back I can safely say I will be buying Pixels as long as GrapheneOS is around. The robustness a finish is just amazing. To anyone using a Pixel: install and donate (if you can)! The web installer[1] is basically a few clicks on a web page. So damned impressed. [1] https://grapheneos.org/insta…

Do you lose the whole play store? Does it even make sense if I use gmail? I like the idea at least. And my 4a isn't getting updates now(on graphene either apparently) which is a shame because I still like it. I used to ise lineage on Samsung devices.

One of GrapheneOS's absolute best features is the sandboxed Google Play Services.

Basically, where other privacy AOSP forks typically offer up to three choices...

- no Google at all

- root and install an extremely fragile FOSS alternative GPS implementation (MicroG)

- root and install the full Google Play Services binary blobs

... GrapheneOS offers option #4: you can install Google Play Services in a sandbox so that they still run, but they don't get root-level access to your system, instead they are treated the same as any other app (so e.g. you get to manage their access to location/storage/contacts etc.).

Note that you don't have to, it's just an option in the built-in Apps menu. I personally run GrapheneOS with no GPS at all in my main profile, and occasionally access my old Gmail/Gdrive accounts via web browser.

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#32
post #30
post #28

Earlier quoted context omitted.

[flagged]

> What I'd hope to hear is that Daniel Micay is in better mental health, but they made the almost-certainly wise choice to stop engaging with social media, and I can't find much information about what actually went down, so I guess it's a question mark. I mean, it sounds like you have pretty much all the relevant information already? strcat's technical chops were AFAIK never in question, but he had a tendency to pick…

I was curious if that actually happened or not. However, I didn't actually see anything about GrapheneOS's leadership structure, or any kind of blog or anything where news like this would be announced.

So if it happened, who replaced them? Are they trustworthy? At least in my cursory searching, I didn't figure out an answer to that.

I assume the answer is actually out there, but I don't have it.

> Whether he still lurks the GrapheneOS discussion threads or not, or whether he is currently undergoing therapy or just chilling with a good book isn't really anyone else's business.

Sure, whatever. But failing any information about whether or not anything happened, I assume they still have root access to critical infrastructure. If so... I mean, naturally, the problem of trust hasn't changed much. If that's the case, then you still need to trust them to trust GrapheneOS. Can you? Don't know.

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#34

Arm memory tagging whitepaper (2019), https://developer.arm.com/-/media/Arm%20Developer%20Communit... > MTE provides a mechanism to detect both [spatial, temporal] categories of memory safety violation. MTE assists the detection of potential vulnerabilities before deployment by increasing the effectiveness of testing and fuzzing. MTE also assists detection of vulnerabilities at scale after deployment ... Memory locat…

And Googles announcement from 2019...

https://security.googleblog.com/2019/08/adopting-arm-memory-...

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#35

Wait, is this the first ARMv9 chip? (Apple M3 is ARMv8.x, with X being 4 or 6 depending on who you ask)

Tensor G3 uses Cortex-X3/Cortex-A715/Cortex-510 from ARM, which are all ARMv9 cores. That said, there are other, earlier cores that also implement the ISA: Cortex-X2/Cortex-A710, for example.

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#36

Earlier quoted context omitted.

Memory Tagging Extension, an arm v9 hardware feature for mitigating some memory safety bugs.

Is this the outcome of the Morello project? Honestly sounds nice.

MTE is somewhat like an in-band, weak version of Morello, but the project is independent of MTE.

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#38
post #28
post #10

Consider using GrapheneOS instead of stock Android for an improved version of MTE (and extra security and privacy as a bonus): https://discuss.grapheneos.org/d/8439-mte-support-status-for... > Stock Pixel OS has it as a developer option which isn't usable in practice since it breaks far too much. The implementation is also much less powerful than hardened_malloc. > We integrated it into hardened_malloc where it's abl…

[flagged]

It sickens me that this tabloid blathering is the 2nd thing after the story link and about 1/2 the page after load. The disclaimer that it's important because it's an OS, OS' are important, thus people who work on OS' are important, and you are discussing their mental health because you need to know if they'd "abuse their position" is ham-fisted.

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#39
post #28

Earlier quoted context omitted.

[flagged]

It sickens me that this tabloid blathering is the 2nd thing after the story link and about 1/2 the page after load. The disclaimer that it's important because it's an OS, OS' are important, thus people who work on OS' are important, and you are discussing their mental health because you need to know if they'd "abuse their position" is ham-fisted.

What?

Re: Enable ARMv9 Memory Tagging Extension (MTE) on Pixel 8

#40

Sounds very useful. Even just for testing. Does x86 have something comparable?

They did, MPX, however the design was buggy and eventually removed.

Currently x86 is the only mainstrem architecture without a plan for hardware memory tagging.

Even RISC-V has an ongoing discussion for hardware memory tagging extensions.

Post reply on HN