Do any decent single-board computers implement Arm MTE, e.g. the latest Raspberry Pi?
Guess not, the RasPi5 is quad A76 which have v8.2 extensions, MTE is v8.5.
GrapheneOS finds Bluetooth memory corruption via ARM MTE
61–70 of 228 posts
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#62Earlier quoted context omitted.
Do things such as Gcam and Google Pay work? The two major things I need from my phone is good camera quality and being able to use Google Pay which is useful where I'm at.
Google Camera works fine, but is not included out-the-box Google Pay will not work as GrapheneOS makes no attempt to masquerade as a Google-Certified device [0] [0] https://grapheneos.org/usage#banking-apps
It does not work on the phone, but I was able to use NFC payments with Google Wallet through my Pixel Watch.
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#63Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#64Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#65> Pixels shipped a massive hardware security feature (MTE) they aren't enabling for the OS to save 3.125% memory/cache usage. It's silly. Heap MTE has near 0% perf overhead in async mode and is cheaper than increasingly ineffective legacy mitigations like SSP in asymmetric mode. I really want to see someone from the Pixel team justifying the decision here. I really wonder what the thought process is for someone to di…
AOSP engineer here; I don't have a deep knowledge of the issue at hand as I don't work on the bluetooth part of the OS, but I did just want to call out that GrapheneOS (while a really cool project!) supports ~11 total device types, and changes in AOSP have to keep a much larger context in mind.
I'm always looking for ways to implement cool stuff and make things in android better, but it's a little myopic to ignore the larger OEM ecosystem when complaining about specific feature roll outs.
I highly doubt the reason this isn't enabled is the 3% memory/cache usage, and there's some other consideration that's informing the decision.
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#66Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#67Earlier quoted context omitted.
I don't know what Gcam is, but it comes with a camera app. I've never used Google Pay so I don't know.
The Google Camera app can be made to work fairly easily. Google Pay's NFC payment will not work in a useful way because the environment signature differs.
> The Google Camera app can be made to work fairly easily.
In fact, it's as easy as installing it through Play Store.
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#68Earlier quoted context omitted.
1. No, it was very easy. I used a normal USB cable and adb on the Linux command line, but the recommended method involves using Web USB in Chromium which is meant to be easier for non-technical people but I couldn't get it to work. 2. No, it is very convenient. It has a sandbox for Google Play Services, which IMO is the best of both worlds as it means you can install all the proprietary crapware apps that make modern…
FWIW, I've used the Web USB installer probably a dozen times without issue, so I would definitely recommend that route if adb is intimidating. I've done it both ways, but the web installer is so easy it feels magical. As for it not working, were you running a Flatpak/Snap version of the browser? Apparently those are problematic with Web USB. I personally haven't tried on Linux yet (just Mac O's) but now that I've swi…
Tip: The GrapheneOS Web installer doesn't work for me with the Chromium in Debian Stable.
I always try the Web installer, to see whether it works now, but then end up doing the command line method (which is also pretty easy, compared to historically how Android phone flashing used to work).
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#69I can hardly wait until mainstream hardware catches up to Solaris SPARC in 2015, or previous memory tagged architectures, to finally tame all those memory corruption issues, only written by bad skilled developers.
Re: GrapheneOS finds Bluetooth memory corruption via ARM MTE
#70Hope somebody using Graphene OS could answer: 1. Is it very challenging to install Graphene OS? Need special cables and to know a lot about jailbreaking Android devices, or will I be fine just following instructions? 2. Is it very inconvenient to use as a daily driver? How often phone just crashes and requires a few days of debugging? Will my bank app work on it?
> Is it very inconvenient to use as a daily driver? No but it is not the most convenient thing either. The Security Additions, Sandboxing Setup and a bit of slowness due to the hardened memory allocator are more annoying than just using plain android and clicking ok for whatever data it wants from you. Initial Setup and understanding what makes grapheneos different and how to use it's security features takes a bit th…
I guess there's also a chance that a banking app will initially work but then fail after a forced update at a very inconvenient time. Is there a possibility that some use of "integrity signals" (in SafetyNet Attestation API and Play Integrity API) will be banned in the EU out of antitrust concerns? https://developer.android.com/privacy-and-security/safetynet...