> Now the question is whether MTE will be enabled by Google as part of a future OS-upgrade, to which there is no definite answer AFAIK
replyStill means that currently the phone has no support for MTE.
I have bought too many things on vague promises that did not happen.
It's not there now -> it's not supported. EOL.
Why are we dependent on Google to enable MTE on the OS-side? If it's a hardware feature, why couldn't GrapheneOS enable it in GrapheneOS even if Google's OS wouldn't enable it?
reply> It still has at least bare minimum support for MTE at a hardware level. We think they removed most of the hardware acceleration from the CPU cache to save money. They ruined the performance so it ended up being fully disabled in firmware. It may still be usable.
replyMTE but slow
"We think", followed by a quite fueled accusation.
replyIt has no MTE right now, okay. Is there any evidence on the rest?
I wonder what the comms would have been without the Motorola partnership
replyThe comms have been like that for years now.
replyThey would have either sucked it up and supported the 11, or shut down the GrapheneOS project completely.
replyMTE support in itself says nothing as vendors usually obscure implementation details and also MTE is a perfect place to implant undocumented backdoors for security services to use.
replyAny evidence of those backsoors?
replyThis reads like “your front door lock is the perfect place for security services to have a master key.” True, but not strong as an argument against having a lock.
>This reads like “your front door lock is the perfect place for security services to have a master key
replyEven that analogy fails because MTE is in addition to existing countermeasures against memory corruption attacks. In the worst case, compromising MTE just means you don't have MTE, not that you get arbitrary code execution.