Google is sabotaging their OEM partners by making a growing number of features and updates exclusive to Pixels. At the same time, Google is trying to convince OEM partners not to support GrapheneOS or even bootloader unlocking. They're also trying to harm GrapheneOS directly.
@GrapheneOS
Dear @kimvsparrentak, I think this 👆 might be a relevant thread for you to read. Many citizens are concerned about this. The EU needs to take even stronger action in terms of anti-trust legislation against Google imho.
Are you able to be a bit more specific about the "trying to convince OEM partners" accusations?
Most of all, with OEM partners you mean Motorola, or you heard it happening towards other OEMs too?
Especially with regards to the bootloader unlocking, they pushed against it with Motorola or other OEMs you've contacted, or it seems to go beyond that?
Thank you
Google is trying to convince OEM partners not to support [...] bootloader unlocking
Do we have proofs for that? If we can have strong arguments that the bootloader is part of Android OS, then it's covered by the the (european) DMA and likely the other countries' equivalent.
We can then use the DMA to require them to implement the possibility to open and to relock the bootloader using non-factory keys. If that's part of Google requirements for their compatibility certification, then all OEM would need to follow
@S1m It's factual information and not speculation. It has been directly communicated to us by multiple OEMs. Don't follow the logic of what you're saying about it though and how it could be used to force doing those things. There's realistically no way to force making secure devices or proper alternate OS support. We aren't interested in that since it would never result in a device we could support in practice. Trying to force it to happen is just not going to work.
@GrapheneOS nearly bought a pixel 10 pro the other day just to put grapheneos on it to replace my aging OnePlus 6t running lineageos, glthink I'm gonna wait to see what happens here, I'm getting desperate to get a replacement phone but get so anxious when I see things like this happen, just thankful it happens before I bite the bullet and buy something lol.
@tuqueque GrapheneOS is Linux. AOSP is an open source Linux distribution and is a drastically better starting point for GrapheneOS than the desktop Linux software stack. Google could entirely stop releasing it and it would still remain a far better starting point. We aren't going to move to a drastically less private, secure and usable software stack without the necessary app compatibility. That software stack is far from even providing proper power management for mobile let alone the rest.
@tuqueque Linux isn't a secure foundation for an OS and must eventually be replaced. It has thousands of security vulnerabilities being found and fixed each month. The monolithic kernel architecture, memory unsafe programming language and other design choices are unsuitable for a reasonably secure OS. Android heavily mitigates that with a much more minimal kernel configuration and greatly reduced attack surface beyond that but it does need to be addressed beyond that in the medium and long term.
@tuqueque If we're going to switch to another base OS to run on bare metal, it wouldn't be a much less private and secure traditional desktop OS software stack.
If we switched to a much more modern and secure base with a microkernel, we would still need AOSP and our work on it. It would still be kept with either a Linux compatibility layer or running with the Linux kernel in virtual machines.
Our work on it is important in the long term. Claiming we're the ones wasting our time is backwards.
@tuqueque We're not only going to defend ourselves from the business people at Google engaging in illegal anti-competitive behavior. We're also going to defend ourselves from people who incessantly GrapheneOS to promote projects and products which aren't at all in the same space. Those do not provide the same things, do not work on the same things and largely do not share our goals or values. GrapheneOS doesn't exist to simply provide an alternative to GMS Android and iOS. It is not the point.
@GrapheneOS Even though I love and champion Linux, I can't disagree with this.
It's a long shot, but I hope something FOSS that's like Linux but without the monolithic architecture and memory unsafe programming language is popularized one day.
@raindrac @GrapheneOS that and also without the ensloppification that's happening to the kernel now 😔
@littlerao @raindrac A lot more bugs are being fixed in the Linux kernel than are being added but it's not a solution to massive security issues. It's not going to become secure due to relentless AI vulnerability discovery. It's not going to find everything important and plenty of new bugs will continue to be added. The reason it's in such bad shape isn't a skill issue or due to them using AI but rather the design and tool choices from the beginning to this day. It's set up to be insecure.
@littlerao @raindrac It has such an incredible level of complexity for the core components along with massive amounts of features and drivers. Everything runs with full privileges with no isolation. It's all written in a memory unsafe language without even following a modern code style and best practices which makes it even worse. There's not a lot of testing or careful review. It's extremely focused on making stuff appear to work and making it fast, not on robustness, correctness or security.
@GrapheneOS @raindrac yeah, but well... that's part of being this old. 30 years ago, alot of those things you mention weren't best practice and reworking all of it is a monsterous task.
also "AI" is also a tool choice... it is already controversial, event tho some may not see it as such.
Do you really want the future of your kernel depend on some mega corp providing their model? When they rais prices to become profitable? And the code base became humanly unmaintainable due to slop? I don't!
@littlerao @raindrac The codebase was already extraordinarily complex, convoluted and poorly understood. It isn't becoming that way due to their use of AI models. The code will now be less buggy overall due to being able to rapidly find so many of the issues but it's not going to become reasonably robust or secure.
AI models have actually heavily slowed down the churn and low quality code being shoved into the kernel by overwhelming Linux with a flood of discovered bugs to fix.
@littlerao @raindrac AI models speed up their development work but they have to spend so much of it fixing bugs now that they can't continue down the path they were before as easily. The illusion that things were relatively fine has been completely shattered.
It hasn't yet convinced them that there are massive systemic issues requiring a massive change in priorities and approach. The maintainers largely see it as an annoyance that so many bugs are being found without reconsidering fundamentals.
@littlerao @raindrac Linux has the extreme level of issues it does with bug density and security due to the priorities and design choices. It's unsurprising that them heavily using AI does not result in it becoming a robust and secure codebase. The priorities and design choices haven't changed. It has become less buggy overall due to the extreme level of bugs being found and fixed but a decent subset of the fixes are incomplete or incorrect. Plenty of new bugs are added too. It's not a solution.
@psyhackological @tuqueque It's a good example and does use both a microkernel design and memory safe language which we're advocating for using. Redox itself is not quite what we need for multiple reasons but it could be very useful as a reference or even a starting point to create it. It isn't clear if it will ever get broad adoption but it's already useful to build components which can be reused elsewhere and to do research which can be applied elsewhere.
@GrapheneOS @psyhackological @tuqueque I miss using Linux. Frig it. Frig windows 11. I'm getting that off my laptop when I get it back from the pawn shop, and putting a great Linux distro on it.
@tuqueque GrapheneOS is Linux. Android is a Linux operating system family.
GrapheneOS is an Android-based OS but isn't Android similarly to how Ubuntu is based on Debian but isn't Debian.
AOSP is open source and can be turned into whatever people want. GrapheneOS is near fully focused on privacy, security, usability and Android app compatibility. Our approach is steady progress with things done properly to meet high quality standards. We don't try to add much more UI customization, etc.
@lake2hill4robot @littlerao @raindrac Our information comes from years of experience doing security research and engineering including on GrapheneOS. macOS and especially iOS have a much more secure kernel than Linux. It's far smaller, far simpler and far lower attack surface. It's a real hybrid kernel keeping far more attack surface in isolated processes. It's not a modern microkernel with a tiny core TCB but it's a drastically more secure design and implementation than Linux.
@lake2hill4robot @littlerao @raindrac Linux is a kernel, not a whole operating system. You're nearly entirely talking about a specific userspace built on top of it which isn't what we're talking about.
AppArmor and SELinux are access control systems for userspace code. SELinux in particular can be used to greatly improve overall security but it's mostly not kernel self-protection but rather userspace access control. SELinux is near entirely used for only targeted policies in desktop distros.
@GrapheneOS "There Can Never Be Hope Under Big Tech" = Big Tech Official Motto
@lake2hill4robot @littlerao @raindrac Motorola was split into 2 companies in 2011. Motorola Mobility was acquired by Google in 2012 and sold to Lenovo in 2014. It's a completely different company from Motorola Solutions.
Motorola Mobility owns the Motorola trademark. Motorola Solutions has a historical limited license to use it for their historical product lines using it. It isn't part of the same company as Motorola Mobility, isn't their business partner and doesn't have the same ownership.
@lake2hill4robot @littlerao @raindrac The macOS and iOS kernel is quite clearly a lot more secure than Linux. Linux is a massive monolithic kernel. It has far greater complexity and attack surface even in a very minimal configuration far different from traditional desktop and server Linux distributions enabling nearly all the available features. macOS and iOS have far smaller kernel with much lower bug density, isolation for a growing number of components and far deeper hardening integrated.
@lake2hill4robot @littlerao @raindrac If you want to compare the whole OS then you need to specify the overall being compared against. AOSP userspace security compares far better to iOS than the kernel. Both AOSP and iOS are drastically more secure than a traditional desktop OS. iOS wins in more ways than it loses for userspace security but we make up for the difference and beyond it. Linux kernel is a different story. Linux has several RCE bugs being fixed weekly and hundreds of LPE bugs...
@lake2hill4robot @littlerao @raindrac Linux has very dense severe vulnerabilities. There are nowhere close to as many severe security bugs in the macOS and iOS kernel. It's also a lot easier to exploit the Linux kernel due to much weaker hardening. iOS in particular has heavily integrated hardware-based defenses including PAC, MTE and restrictions on what the kernel itself can do to preserve safety properties. The code has been overhauled for type-based allocation, read-only memory pools, etc.
@lake2hill4robot @littlerao @raindrac Linux has very severe security issues. It's going through a massive crisis from AI models exposing that's it's completely riddled with serious vulnerabilities. There have been several recent patches for remotely exploitable TCP vulnerabilities and hundreds of serious local privilege escalation patches per month. Building better exploit protections has been a top priority for us recently. We're in a far better position than a desktop distro but it's not good.
@lake2hill4robot @littlerao @raindrac AOSP uses a very minimal core kernel configuration compared to a desktop OS and has a huge amount of attack surface reduction for it in userspace via seccomp-bpf and advanced use of SELinux not done for desktop or server distributions. It covers the whole OS with it built around it. It has hardware-specific policies to permit the minimal access needed by distributions. It has a lot of driver complexity moved to userspace processes which are sandboxed.
@GrapheneOS @lake2hill4robot @littlerao @raindrac What are your thoughts on RedoxOS? Is your eventual plan to migrate GrapheneOS away from AOSP and Linux to a new kernel like RedoxOS that has compatibility with Android apps?
@GrapheneOS @lake2hill4robot @littlerao @raindrac
Yep, currently trying to hack a smart pdu that hasn't been updated for at least 25 years. And because of storage and memory constraints they basically stripped out every feature they didn't need.
That thing isn't vulnerable to anything I tried so far. Including the recent "catastrophic" Linux and openssh vulnerabilities.
@GrapheneOS I'm honestly done with Android. I've seen Google slowly but continuously cripple non-OEM distros and now it's just going fully mask off. I know it's not much of a better option but I'm leaving for iOS. I couldn't even get a budget Android phone with something like Lineage if I wanted to because every budget phone has gradually moved from Qualcomm to Mediatek processors.