←back to thread

Leaker reveals which Pixels are vulnerable to Cellebrite phone hacking

(arstechnica.com)
446 points akyuu | 4 comments | 30 Oct 25 23:12 UTC | HN request time: 0.639s | source
Show context
aussieguy1234 ◴[31 Oct 25 03:49 UTC] No.45768219[source]▶
I've set up GrapheneOS on my Pixel with 2FA fingerprint + PIN unlock. No way will anyone be getting into it without my cooperation.

My only issue was less compatibility with my local emergency services, since they can't see me on a map for some reason if I call from a GOS phone.

My solution to that was a second Pixel as an emergency phone - one with the stock OS, that I'll swap sims with and take with me when hiking, stand up paddle bording and doing other activities that carry risk. This phone has no sensitive information in it. I also have a PLB for added protection.

replies(5): >>45770609 #>>45776669 #>>45776670 #>>45776947 #>>45778083 #
fluidcruft ◴[31 Oct 25 10:54 UTC] No.45770609[source]▶
Is there anything actually preventing Samsung or another vendor from adopting GrapheneOS's security innovations?
replies(4): >>45776786 #>>45777068 #>>45777093 #>>45777842 #
1. russianGuy83829 ◴[31 Oct 25 21:50 UTC] No.45777093[source]▶
GrapheneOS is seemingly working with an OEM to make a GrapheneOS smartphone. Its probably not samsung, but would still be an established vendor
replies(2): >>45777825 #>>45784439 #
2. DANmode ◴[31 Oct 25 23:25 UTC] No.45777825[source]▶
It better not be Samsung...
replies(1): >>45782715 #
3. Andromxda ◴[01 Nov 25 16:02 UTC] No.45782715[source]▶
It isn't Samsung
4. preisschild ◴[01 Nov 25 19:12 UTC] No.45784439[source]▶
They are not making a "GrapheneOS smartphone", they are just helping providers make their new devices compatible with the security requirements, so GrapheneOS can be installed on it. But GrapheneOS will not come by default AFAIK.