I’m currently using GrapheneOS and I quite like it, but I would like to switch to something else. Will I lose much privacy if I switch to e/OS? Can I lock bootloader after flashing it like on GrapheneOS? I’m using Pixel 7 btw

  • jacktherippah@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    7 months ago

    I recommend sticking to GOS. If you’d like to use something else, I’d recommend DivestOS. CalyxOS, LineageOS, /e/OS and iodéOS are all significant downgrades in usability, privacy and security and therefore not worth using on a Pixel.

  • Unsafe@lemmy.today
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    You won’t lose anything. Both options are 100% private. However, it’s worth noting that Graphene is generally considered to be more secure.

    • Undertaker@feddit.de
      link
      fedilink
      arrow-up
      2
      ·
      7 months ago

      What? Please stop spreading misinformation.

      /e/ includes microG per default and thus calls google servers. /e/ includes unique identifyer per update call tracking its users. Graphene uses several proxy servers to hide user information, /e/ does not in similar way. And so on…

  • Atemu@lemmy.ml
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    7 months ago

    Were you using the Google espionage services on GOS? If so, you’d likely gain a little privacy because of µG.

    Some devices can lock the bootloader but that’s not a generally supported feature on /e/OS.

    • driveway@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Ah yes, gaining privacy by running microG as root which already has Google code in it instead of running GSF in a sandbox as user.

      • Atemu@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        6 months ago
        • µG is not running as root
        • It does not “already have google code in it”. That’s an optional, tightly scoped feature with one specific blob that is required to implement the SafetyNet feature in any implementation
        • I see no reason why you couldn’t run µG inside a sandbox too; the differentiating factor for security is the sandbox, not the GMS implementation. Also has nothing to do with privacy as, contrary to the original GMS, µG doesn’t spy on you to begin with.
  • random65837@lemmy.world
    link
    fedilink
    arrow-up
    3
    arrow-down
    4
    ·
    7 months ago

    It literally makes less than zero sense to go from Graphene to e, Graphene is the most hardened privacy tweaked OS available, e would be a huge step backwards on many fronts, what’s your reason for wanting to switch? No, you can’t lock your bootloader with e, verified boot won’t be there, you’ll lose the hardened kernel , the improved sandboxing, the memory protection. It’s a fail from every angle.