Warning: Some posts on this platform may contain adult material intended for mature audiences only. Viewer discretion is advised. By clicking ‘Continue’, you confirm that you are 18 years or older and consent to viewing explicit content.
I’ve always found it both weird and ironic that GrapheneOS is only available for Pixel phones when the whole principle of the project is basically “we don’t trust Google”.
Most brands allow relocking bootloader. But after that you with be only able to use stock rom. Pixel lets you lock the bootloader with a different signature, so in this example you are basically able to lock it to only boot grapheneos and nothing else.
Security. You’re caught with your pants down if you have any personal data on a phone with an unlocked bootloader. All data is effectively plaintext, all security is nullified with trivial difficulty. This is the actual worst-case scenario for journalists, whistleblowers, or anyone who is or may become under surveillance for any reason.
They still wouldn’t be able to do very much. All an unlocked bootloader does is let you flash things via fastboot.
Even with a locked bootloader, you could still get into recovery and cause mischief with physical access. You wouldn’t be able to access the storage partition without decrypting it, but you could still maybe flash stuff to the system partition to infect it for the next time the phone is booted up.
Remote access to the phone won’t be able to do much of anything with an unlocked bootloader. The far bigger hazard is app signature spoofing (eg Magisk and MicroG), which if successfully exploited can cause all sorts of havok - you can have apps pretending to be other apps that have root access.
Even then, though, I think it’s a fair trade of risk. The chances of any of this happening are very, very low, albeit the consequence is extreme. I personally prefer that to the absolutely certain risk that Google is spying on my phone, even if the consequences of that spying are relatively low.
This isn’t true at all. Daniel Micay has stated multiple times the goal isn’t to degoogle, it’s to provide a secure and private OS that’s actually usable. They worked tirelessly to integrate GMS compatibility layer and give users the choice to install sandboxed Google play for app compatability.
GrapheneOS has said countless times that by using Linux and other open source softwares that Google contributes massive amounts of code, you ARE inherently trusting them to not be malicious https://nitter.1d4.us/GrapheneOS/status/1672998518573740033#m
Google play does what it says and they are very open about what data they collect, which is obviously a lot. GrapheneOS stops much of this collection through sandboxing, where you can deny any permissions you desire.
G provides a phone that is incredibly friendly to developers (as friendly as it can get without free hookers and blow), in all aspects, which makes sense considering they want devs to adopt android as their platform for apps and stuff. This also goes into things like security vulnerabilies/research, and also alternative android-based systems. It’s humorous but not at all ironic. Be friendly to devs, and make money hand over fist because of it.
It’s logical for both, just for very different motives.
I’ve always found it both weird and ironic that GrapheneOS is only available for Pixel phones when the whole principle of the project is basically “we don’t trust Google”.
The pixel device is (as far as I’m aware) the only mainstream device that allows you to re-lock the boot loader.
Otherwise, once a phone is cracked, it remains cracked. I’m not entirely sure what that buys, but that’s why they do it
Most brands allow relocking bootloader. But after that you with be only able to use stock rom. Pixel lets you lock the bootloader with a different signature, so in this example you are basically able to lock it to only boot grapheneos and nothing else.
They also have an accessible secure element that graphene uses a lot. I’d recommend listening to the podcast interviews with graphene staff
Security. You’re caught with your pants down if you have any personal data on a phone with an unlocked bootloader. All data is effectively plaintext, all security is nullified with trivial difficulty. This is the actual worst-case scenario for journalists, whistleblowers, or anyone who is or may become under surveillance for any reason.
That’s wrong, data is still usually encrypted.
A locked bootloader ‘just’ prevents tampering with the OS. You’re only pwned when using the phone after it has been manipulated.
Yeah but if you have the phone with an unlocked bootloader and anyone gains access to it (physical or otherwise)…
They still wouldn’t be able to do very much. All an unlocked bootloader does is let you flash things via fastboot.
Even with a locked bootloader, you could still get into recovery and cause mischief with physical access. You wouldn’t be able to access the storage partition without decrypting it, but you could still maybe flash stuff to the system partition to infect it for the next time the phone is booted up.
Remote access to the phone won’t be able to do much of anything with an unlocked bootloader. The far bigger hazard is app signature spoofing (eg Magisk and MicroG), which if successfully exploited can cause all sorts of havok - you can have apps pretending to be other apps that have root access.
Even then, though, I think it’s a fair trade of risk. The chances of any of this happening are very, very low, albeit the consequence is extreme. I personally prefer that to the absolutely certain risk that Google is spying on my phone, even if the consequences of that spying are relatively low.
This isn’t true at all. Daniel Micay has stated multiple times the goal isn’t to degoogle, it’s to provide a secure and private OS that’s actually usable. They worked tirelessly to integrate GMS compatibility layer and give users the choice to install sandboxed Google play for app compatability.
GrapheneOS has said countless times that by using Linux and other open source softwares that Google contributes massive amounts of code, you ARE inherently trusting them to not be malicious https://nitter.1d4.us/GrapheneOS/status/1672998518573740033#m
Google play does what it says and they are very open about what data they collect, which is obviously a lot. GrapheneOS stops much of this collection through sandboxing, where you can deny any permissions you desire.
G provides a phone that is incredibly friendly to developers (as friendly as it can get without free hookers and blow), in all aspects, which makes sense considering they want devs to adopt android as their platform for apps and stuff. This also goes into things like security vulnerabilies/research, and also alternative android-based systems. It’s humorous but not at all ironic. Be friendly to devs, and make money hand over fist because of it.
It’s logical for both, just for very different motives.