zlacker

[return to "Experimental release of GrapheneOS for Pixel 9a"]
1. mystif+BY[view] [source] 2025-04-13 14:10:53
>>moelf+(OP)
I really wanted to like Graphene, but it feels more locked down than stock android. The primary reason I want a custom OS in the first place is that I want to control the device I own.

Graphene is just taking control of my phone from Google and giving it to whoever runs Graphene. I don't get any say in how my phone works.

Graphene thinks you can't be trusted with your own device. But don't worry, they definitely know what's best for you and it's a totally different kind of control from what Google has. Really, just trust them, it's totally fine, promise.

I switched to Lineage after a few months.

◧◩
2. gruez+t01[view] [source] 2025-04-13 14:28:15
>>mystif+BY
>I really wanted to like Graphene, but it feels more locked down than stock android. The primary reason I want a custom OS in the first place is that I want to control the device I own.

What specific ways do you feel are "more locked down" than stock? It's not recommended, but you can install magisk + root if you really wanted to. It won't try to prevent you.

>Graphene is just taking control of my phone from Google and giving it to whoever runs Graphene. I don't get any say in how my phone works.

That's fine. The homepage of grapheneos says:

"The private and secure mobile operating system with Android app compatibility"

Surely you must understand that "security" and "giving users a say in how their phone works" are diametrically opposed? A phone can't be secure if its sandbox can be bypassed in one tap by the user. You might have a lot of say in how your linux system works, but don't kid yourself into thinking it's secure. It's only one `bash -c "$(curl -fsSL http://...` from getting pwned.

◧◩◪
3. yjftsj+opa[view] [source] 2025-04-16 19:10:42
>>gruez+t01
> Surely you must understand that "security" and "giving users a say in how their phone works" are diametrically opposed?

Absolutely not.

> A phone can't be secure if its sandbox can be bypassed in one tap by the user. You might have a lot of say in how your linux system works, but don't kid yourself into thinking it's secure. It's only one `bash -c "$(curl -fsSL http://...` from getting pwned.

In both cases, yes, a user may choose to bypass a security measure. In most threat models, that's fine. If malware needs me to give it permission to compromise the system, I consider that a secure system.

[go to top]