I'm considering the switch to GrapheneOS, so I watched this interview with one of the members of the GrapheneOS team, and honestly, I feel it was a great general introduction to it and touched on common features and misconceptions.

For those who don't know, it's one of the most secure and private mobile operating systems out there. Some things that I took away:

  1. They touched upon MAC randomization. I researched a bit on my own about what the need for it is. Apparently, it's standard practice to randomize MAC addresses when scanning WiFi connections. However, GrapheneOS (and Pixel firmware) are even better at this, as they make sure they don't leak any other identifiers when doing so. They also allow you to get a new random MAC for every connection that you make (not sure whether this is very useful, as this can cause problems). On a related note, even when WiFi/Bluetooth are "off," stock Android can still scan in the background to improve location accuracy (by matching visible networks/devices against Google's database). So basically, even with WiFi/Bluetooth off, Google still knows where you are. In GrapheneOS, this option is off by default.

  2. They have their own reverse proxies that they use to talk to Google on your behalf when needed.

  3. Apparently, in the USA you can be compelled to provide a fingerprint or Face ID. Courts have ruled this doesn't violate the 5th Amendment because it's physical, not testimonial. BUT you cannot be compelled to provide a password/PIN. That's considered testimonial evidence, protected by the 5th Amendment. GrapheneOS has a two-factor system where, after using your fingerprint, you still need to enter a PIN, so it helps with this. They also have a BFU state after reboot, which is the safest and requires you to enter your full passphrase.

all 23 comments

sorted by: hot top controversial new old
[+] 39 points 8 months ago* (last edited 8 months ago) (20 children)
  • [–] 20 points 8 months ago* (last edited 8 months ago) (4 children)

    They're working on that, I think they said next year or 2027 the OEM they're working with will be up to snuff. Currently only pixels support their hardware requirements for security reasons until then it seems. I also hate google, but a graphened pixel is still the best option in the meantime. I can't wait for their new phones either though!

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 8 months ago (3 children)

    Next year is when they'll release the OEM models, as far as I'm aware.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 17 points 8 months ago (2 children)

    The weird irony of android is that google's devices have given you more control over the hardware than other OEMs for a really long time. If you wanted to buy a phone and then immediately put a custom ROM or alternative OS on it, you'd usually have an easier time with Pixels than anything else.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 8 months ago*

    Yeah they touched on this in the interview. Basically:

    • Pixels allow unlocking the bootloader (most phones don't)
    • Pixels support alternate operating systems at the firmware level
    • Pixels get long-term security updates
    • The hardware meets GrapheneOS's security requirements

    In one part they mention Pixels Titan M2 chip, for example, which throttles how many unlock attempts you can make.

    That being said they were critical of Google's recent actions. Now Google gives OEM partners (Samsung, etc.) 4 months to implement security updates before publishing to AOSP. Prob one of the reasons why they wanted to seek an OEM partnership as they now get updates instantly with the caveat that for those 4 months they can't publish the source code publicly untill Google releases it to AOSP. So they release 2 builds for every update (One with the embargoed security patches (binary/compiled version) and one with only public AOSP code (open source version that lags behind).

    Also they had problems supporting Pixel 10 as Google removed device trees and didn't push Android 16 QPR1 to AOSP until months after the Pixel release.

  • source
  • parent
  • [–] 8 points 8 months ago (10 children)

    I can see some reasons to not want to get Google hardware, but I can I ask you to explain your reason (in case you have some good reason I didn't think of).

  • source
  • parent
  • hideshow 10 child comments
  • [+] -6 points 8 months ago (9 children)

    Google hardware might have backdoored firmware, some say.

  • source
  • parent
  • hideshow 9 child comments
  • [+] 16 points 8 months ago* (last edited 8 months ago) (2 children)
  • [–] 3 points 8 months ago (1 child)

    As far as I'm aware, they don't have Fairphone support for reasons they already explain. Despite the baggage of the Pixel hardware, it's the best hardware security wise, which is why the devs chose it (McCay firstly before someone else took over while that troll continued to be on the board).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 8 months ago* (5 children)

    Pretty impressive to have an OS that's "almost impossible to crack" with backdoored firmware.

  • source
  • parent
  • hideshow 5 child comments
  • [–] -3 points 8 months ago (4 children)

    They probably must've known, and disabled some of the nonsense. At least, that's how I see it.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 4 points 8 months ago (3 children)

    Must've... If only GOS was open source and the devs were incredibly outspoken about privacy, we could verify this speculation through their statements (or lack thereof). Alas...

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 8 months ago* (1 child)

    The thing is that GOS is open-source: https://github.com/GrapheneOS

    And more proof: https://grapheneos.org/source

    Fun fact: It turns out they're from Canada.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 8 months ago
    [+] -3 points 8 months ago*