When to expect Advanced Memory Tagging=on ?

ClownsDarkSoulPerps

The latest ARM CPUs have AMT feats, and Android 14 already shipped with software controls.

I'm not sure if AMT will be a full device feature or if app devs must include it in their app build in order to profit from the AMT/AME feats offered by the latest hardware

But what is the progress on this, what can we expect and when will it be available in Gos?

Also , would this affect the Gos hardened memory manager on software level (when used in interaction) or just provide additional security , but on the hardware level?

I'm no dev but looking for any info on Advanced Memory Tagging

GrapheneOS

ClownsDarkSoulPerps Memory tagging is not available on most devices. MTE is used by default on GrapheneOS and used for both the base OS and user installed apps known to be compatible. The toggle is only for force enabling it with apps that are not known to be compatible with it.

ClownsDarkSoulPerps There's no feature called Advanced Memory Tagging in Android or GrapheneOS. You're mixing up the name.

ClownsDarkSoulPerps

Right now on latest Android the advanced memory tagging is off by default on most Android

Not sure how it is on graphene?

Probably needs to undergo a period of field testing with many types of apps,no?

Markus

Croak3114

Not sure if you are referring to a different feature with "Advanced Memory Tagging" but GOS has had MTE enabled since Nov last year.

https://discuss.grapheneos.org/d/8439-mte-support-status-for-grapheneos/52

ClownsDarkSoulPerps

Croak3114

This is the info I was looking for! Thanks a lot!!

final

GrapheneOS uses MTE by default for the OS components on Pixel 8 and later and there is a per-app toggle to use MTE with apps you install. The GrapheneOS MTE implementation is far more stable and complete. The Vanadium web browser also uses MTE and is the only web browser that incorporates MTE in a production environment. It has been around for a while.

MTE is used in hardened_malloc and is a massive security benefit overall. It is a mandatory requirement for all newer devices to have MTE support now before GrapheneOS will support them.

ClownsDarkSoulPerps

final

Interesting

I see (in per app settings ):

"Exploit protection compatibility" (on/off)

And "Hardened memory allocator" which is a in/off toggle

I don't think any of these 2 are relating to MTE (Advanced Memory Tagging/ Memory Tag Extensions) but these are for the software malloc

I can't find the MTE settings (per app)

It seems MTE can be enabled in the system developer options, then every app must compile in MTE support around build time (dev's work)

The gos apps already have built in MTE but for other apps it depends if their devs even know about MTE and throw it in in Android Studio or whatever they use

Am I right?

Xtreix

ClownsDarkSoulPerps Your model is prior to the Google Pixel 8 / 8 Pro according to what you write, MTE is not available for Google Pixel released before the 8th generation due to ARM V8 which does not support MTE.

On Pixel 8, MTE is enabled by default for the operating system and system apps and you can't change it, you then have a toggle to enable it for any third-party apps you install.

Murcielago

ClownsDarkSoulPerps

Additional info on what Xtreix wrote: On a Pixel 8 under Long Press App Icon> App Info
you would see the following settings chronologically:

Exploit protection compatibility mode
Hardened memory allocator
Memory tagging
Native code debugging