←back to thread

401 points Bluestein | 1 comments | | HN request time: 0.001s | source
Show context
stiray ◴[] No.44363735[source]
I am still waiting for Fairphone and Graphene OS collaboration. This is match made in heaven.

Any Fairphone/GrapheneOS developer reading this? Just do it, document if something is not secure enough for you, but do it. Nothing to think about, you fit together like hand and a glove and any seconds thoughts are depriving the planet of THE PHONE!

Pick the cash we will throw at you and make second generation with the cpu GrapheneOS wants, that will make the /r/GrapheneOS members eyes shine, drooling and crying of joy at the same time. +throw them in a few hardware switches for camera, mic, connectivity,... disabling. No need to wait to be perfect in first iteration (and due to that craziness and perfectionism will never happen), to gain the possibility to be perfect in second or third.

I would love so much to stop buying Google Pixel phones just to install Graphene OS and protect myself from Google and its ecosystem, it seems so counterproductive.

replies(4): >>44363775 #>>44363839 #>>44364179 #>>44364441 #
IlikeKitties ◴[] No.44363839[source]
Fairphones consistently doesn't support a quarter of what graphene os requires. See their FAQ:

https://grapheneos.org/faq#future-devices

Unless Fairphone becomes significantly better in their security and update policy and integrate a whole lot of new features it's not gonna happen.

replies(2): >>44363930 #>>44365029 #
cge ◴[] No.44365029[source]
>Fairphones consistently doesn't support a quarter of what graphene os requires

I expect it's not just a matter of feature support: Fairphone in general seems rather horrible on security, doing things like using test keys for production signatures [1].

[1]: https://forum.fairphone.com/t/bootloader-avb-keys-used-in-ro...

replies(1): >>44365045 #
1. IlikeKitties ◴[] No.44365045[source]
To be fair that's from 2022, I thought they fixed those issues on newer devices.