• termaxima@slrpnk.net
    link
    fedilink
    English
    arrow-up
    20
    ·
    3 hours ago

    I want GrapheneOS more than repairability, personally. I hope the Fairphone + GrapheneOS combination is possible some day…

    • Routhinator@startrek.website
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      2 hours ago

      The Graphene devs explicitly only support Pixels. Sticking with Graphene means continuing to give Google the profits from your hardware.

      /e/OS is not bad as an alternative. The system wide ad and tracker blocking is nice.

      • mal3oon@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        34 minutes ago

        This is a big issue that the fairphone doesn’t have its dtb open yet. It’s not easy to build ROM for it. Despite their core claim of sustainability, without addressing the blobs, it remains just a tad more convenient for green minded people. We need a full Fairphone.

      • ozymandias117@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 hour ago

        Graphene modifies AOSP for much more security.

        E.g.

        • you can disable USB data at a hardware level
        • Receives Kernel updates even faster than Google’s phones
        • uses a different memory allocator, hardened_malloc
        • changes the way zygote launches apps, so ASLR actually works
        • doesn’t allow apps to ptrace themselves
        • disables JIT per-app
        • disable network access per-app

        I dont think e/OS is as security oriented, more privacy oriented

        • atcorebcor@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 hour ago

          Thanks for sharing. For someone who is not so well versed in these technicalities, what does that mean for the user? That you’re more susceptible to fraud and hacking and malware?

          • BurgerBaron@piefed.social
            link
            fedilink
            English
            arrow-up
            2
            ·
            52 minutes ago

            A big thing is gOS not using JIT compiling. So, app updates are pretty slow but this kills a lot of malware exploits.

              • zod000@lemmy.dbzer0.com
                link
                fedilink
                English
                arrow-up
                2
                ·
                20 minutes ago

                You would choose it for security hardening in general. E.g. it is harder for malware to infect, harder for unauthorized parties to gain access to data when the phone is locked, etc.

          • LedgeDrop@lemmy.zip
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            14 minutes ago

            From a user’s perspective, when you install an app, you can:

            1. Determine if that app is allowed to access the internet.
            2. If it needs access to your contacts, you can share which of your contacts, it can see (or none at all)
            3. If it needs access to your files, you can determine which files/photos/music it sees (or none at all, but the application still believes it has access to everything)

            There are a bunch of other, security features it provides, but from a “normal user” experience, the ability to take control of your data is probably one of the most impactful.

            It is possible to do similar things with other CFW, but AFAIK, graphene is the only one to cleanly integrate it as a polished feature of the ROM.

            edit: fix formatting