I want to mainly use it for privacy over its “security”. I don’t know what makes everyone fine with running it on fucking google pixels. Is there some kind of “low security” version or something for other phones? I’m so tired of certain organizations infiltrating privacy communities and making people believe in improving “security” by voluntarily giving up on privacy and using even non free software like that insecurities blog and other people.

  • onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    37
    arrow-down
    3
    ·
    10 months ago

    I believe the devs of GrapheneOS have tailored their requirements to target Google Pixel phones for one simple reason: there aren’t enough devs to help them support other phones. They probably owned Pixels and started development on them, got specialized in them and didn’t want to branch out as that costs lots of time.

    There’s nothing wrong with that. The only issue I find with their reasoning is all the claims they make of Google Pixels being the only secure Android phones in existence. It’s detrimental because non-techies will just repeat that to death because they don’t know better - just like Appholes repeating that iPhones are the most secure phones out there and Apple cares about privacy. It’s free advertisement for Google. So people head out and give Google more money than their data would ever be worth and they do it repeatedly every few years because it’s “common knowledge” that Google Pixels are the most secure phones out there.

    The worst thing about that is that Google didn’t have to do anything. Had Google made those claims, people would be wary, but this is an independent group and because of that, people give it credence.

    Not saying GrapheneOS is a shit project - it definitely isn’t, just the claims and free advertisement these devs are giving Google is bad.

    CC BY-NC-SA 4.0

    • ArcaneSlime@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      19
      arrow-down
      2
      ·
      edit-2
      10 months ago

      The issue is that Pixels are one of the only manufacturers that lets you install a custom ROM and re-lock your bootloader, which is an important security feature. Afaik only pixels and xaomi can do that, so they could expand it a bit, but tbh if those are my two options I’ll take the pixel.

      If you don’t care about relocking your bootloader just use lineageOS or eOS, they aren’t as secure, but if you don’t want/need it to be as secure they do exist as options.

      Edit: Relocking and https://grapheneos.org/faq#future-devices my mistake

        • Max-P@lemmy.max-p.me
          link
          fedilink
          arrow-up
          3
          ·
          10 months ago

          Google’s phones have always supported the full spec. OnePlus used to also do that, but quietly removed support for it. OnePlus 8T on Android 11 (last OxygenOS version) you could, but when they switched it to Oppo’s ColorOS that got removed, that’d be 2021-2022 ish so that fits your experience.

          For Samsungs, I don’t know. They let you relock the bootloader with a custom ROM on it, not just after flashing back a stock image? And it does the whole verified boot dance, TPM works and everything?

          The key feature here is relocking with your own keys and retain all the security features as if it was a manufacturer’s build. Rollback protection and everything.

        • ArcaneSlime@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          2
          ·
          10 months ago

          Good to know for sure. I confuse the fairs/librems/pines sometimes, are the fairphones the ones that are hard to get in the US? Iirc the librem is the expensive one and the pine is the kinda not as good one, but I can’t remember if it was the fairs or the librems that were hard to get in US.

          Hopefully they get graphene working on it soon, that’d be awesome. Turns out it’s a bit more than just the bootloader that they consider however: https://grapheneos.org/faq#future-devices so looks like I was only partially correct lol.

            • ArcaneSlime@lemmy.dbzer0.com
              link
              fedilink
              arrow-up
              1
              ·
              10 months ago

              Ah yeah well that’d def be an issue for US people. They look good though if we could get them lol, hopefully they’ll make it to the US and get graphene soon!

    • THE MASTERMIND@lemmy.today
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      10 months ago

      I have to agree that i too hate the devs saying pixel is the most secure but i disgree that google gets more money from pixels than our data .

      • onlinepersona@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        3
        ·
        10 months ago

        Hmm… is your data worth 300€ every 3-4 years? This would indicate not. There are probably other sources, but 100€/year for your data = ~8€/month for your data. I’d find that hard to believe, but will gladly be proven otherwise.

        In any case, even if it were > 100€/year, giving them that amount is like a present despite trying to degoogle yourself.

        CC BY-NC-SA 4.0

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      10 months ago

      What phone hardware to you suggest as a replacement from a security perspective?

      • onlinepersona@programming.dev
        link
        fedilink
        English
        arrow-up
        7
        ·
        10 months ago

        TL;DR Unless you’re being persecuted, I’d say the most important criteria is picking a modern phone actively supported by a ROM. Samsung, OnePlus, LG, FairPhone, … they’re all fine.

        What’s your threat model? Most likely, if you’re just a normal dude, the most you’ll have to fear is someone stealing your phone and trying to replace the OS on the phone. Probably every modern Android phone protects against that with secure boot. If somebody wants to read your data, IINM every modern Android phone has encryption activated by default meaning so do modern ROMs.

        If you have somebody knowledgeable enough to start attacking your phone by opening it and messing with hardware, you’ve got an entirely different problem and if they want to get in, they will. Either physically through you (a wrench can reveal your password), a 0-day (iPhones were hacked through iMessage by text messages the user never saw aka zero click), or through some yet unrevealed vulnerability if you’re that important.