GrapheneOS retweeted
We've already repeatedly talked to the EU. They haven't yet done anything substantial. The EU itself keeps putting out standards which encourage using the Play Integrity API and most of the implementations of EU digital wallet, etc. standards end up banning GrapheneOS with it.
GrapheneOS retweeted
Replying to @GrapheneOS @dewindells
We're very happy to help them pursue this case against Google in the right way. It should be nearly entirely focused on the bait and switch Google pulled with Android and their OEM partners. They lured them in, made them feel like equal partners and then gradually took control.
GrapheneOS retweeted
Replying to @GrapheneOS @dewindells
Google's management working in partner management, Android revenue sharing and the Play Integrity are criminals who should be prosecuted under US law. US DoJ has tried to go after Google for Android but they chose the wrong ways to do it due to lack of domain knowledge about it.
GrapheneOS retweeted
Replying to @GrapheneOS @dewindells
South Korea and the EU have found Google's GMS licensing to be a violation of the law. It's an objective legal fact to describe it as such in those jurisdictions. We aren't making a hyperbolic statement. It's also clearly illegal in the US, but not yet properly taken to court.
GrapheneOS retweeted
Replying to @GrapheneOS @dewindells
Play Integrity API exists to enforce Google's licensing system for Google Mobile Services. The device and strong integrity levels check for a device with a GMS license running the stock OS. Google's GMS licensing is a very clear violation of antitrust laws and this is the stick.
GrapheneOS retweeted
Replying to @GrapheneOS @dewindells
It's easy for attackers to spoof the Play Integrity device integrity level and leaked keys are available for low prices to bypass the strong integrity level. That doesn't help us since it requires awful hacks and is a lot easier without Google Play as a regular sandboxed app.
GrapheneOS retweeted
Replying to @dewindells
Play Integrity API isn't a legitimate security feature doesn't provide any serious checks for devices not being compromised. The strong integrity level permits devices which haven't received security updates since 2017 and the device integrity level supports even further back...
GrapheneOS retweeted
They're actively interrogating, influencing and outright threatening OEMs to try to stop us having more options than Pixels. They're specifically doing that about GrapheneOS. They benefited a lot from GrapheneOS existing and yet are doing underhanded things to try to harm us.
GrapheneOS retweeted
It was bad enough having Google's business side increasingly block any form of access, collaboration or even communication with Google engineers. It was bad enough having them remove Pixel support from AOSP and make an increasing amount of Android releases Pixel exclusive too.
GrapheneOS retweeted
We're on good terms with many of Google's engineers and have actively collaborated with them. Years ago, Google's security team gave us security access and the business side revoked it so we had to get it via another OEM before our Motorola partnership. It's downhill since then.
GrapheneOS retweeted
Google are the ones hostile towards us, not the other way around. We've contributed upstream to Android for years with vulnerability reports, suggestions and submitted improvements. We used Pixels because they were the most secure Android devices and they sold more because of it.
GrapheneOS retweeted
GrapheneOS has never specifically been an anti-Google project and still isn't. We handle Google apps/services in a similar way as others. They should be an equal playing field without special access or features. Google cannot tolerate that and wants to wipe out any OS doing it.
GrapheneOS retweeted
Replying to @StatsLime @Turret9999
Google's business side is actively pushing OEMs to avoid providing any support for alternatives to Google Mobile Services operating systems and to end support for bootloader unlocking. Google was hostile towards alternatives and especially GrapheneOS before we said anything.
GrapheneOS retweeted
Replying to @GrapheneOS @Turret9999
It can be clearly seen that there are a growing number of Pixel exclusive Android features. There are public reports on Google merging the Android and Pixel teams together. Android is now explicitly developed for Pixels as the first class platform and explicitly hindering others.
GrapheneOS retweeted
Replying to @Turret9999
It's public knowledge that Google made 2 out of 4 major releases of Android each year into Pixel exclusives. It's also public knowledge that they exclusively released Android 17 QPR2 for Pixels prior to it being available for others devices. That's the tip of the iceberg.
GrapheneOS retweeted
Considering the capability jump in cyber models that I have seen from July to September this year: all those people whining about how hard and expensive patching is for them will be in for a harsh awakening. The current stream of vulnerabilities will only get worse.
GrapheneOS retweeted
Infosec likes to forget its history. Everyone should remember Apache-nosejob and how experts considered an Apache overflow unexploitable and then Gobbles just dropped the working exploit. Just because you think X is hard or unexploitable doesn’t mean another mind/AI can’t do it.
GrapheneOS retweeted
On modern mobile devices, Hardware components such as radios and many others are isolated from the rest of the device. Code in any kernel driver is highly privileged and can control the whole device. HardMAC Wi-Fi has more isolated firmware code instead of privileged kernel code.
GrapheneOS retweeted
Moving drivers into the upstream kernel often means moving a lot more functionality into the kernel. We'd rather have out-of-tree drivers with most functionality in userspace than upstream drivers with more in the kernel. It's even similar with firmware due to the Linux design.

