• ChaoticNeutralCzech@feddit.org
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      A HW manufacturer (aka OEM) will share specs and interfaces with the GrapheneOS team, who will develop an official port for the hardware, with support and everything. The OEM will allow bootloader unlocking and maybe even ship some of these phones with Graphene preinstalled, depending on what their contract with Google allows. To this day, only Pixels have officially received GrapheneOS releases because Google has documented their hardware interfaces in AOSP. Now, AOSP is no longer developed with the Pixel as a target but a virtual device, putting the future of GrapheneOS on Pixels into question (the team refuses to use reverse-engineered hardware interfaces, which may result in bugs).

  • 𝕸𝖔𝖘𝖘@infosec.pub
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    But if google goes on with locking out the app store with the developer verification bs, how would would this play into that? If Aurora won’t install the app or the app won’t run, then we’ve accomplished little in that area. I’m really hoping I’m missing something.

    • kuhli@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      Custom ROMs should be able to disable the checks. My bigger concern is what it does to the open app ecosystem as a whole.

      • cmhe@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        TBH I would actually expect GrapheneOS not to disable these checks. GrapheneOS devs pride themselves to have the best implementation of the official Android security model, and enforcing signature checks is likely part of that…

        They might add additional certificates I guess, to allow their own apps, and maybe a selected few others.

        • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          2 days ago

          This is incorrect. The sideloading checks are implemented in Play Protect, which needs elevated privileges to function. On GrapheneOS, Google Play services run with normal privileges, just like any other user-installed app. This means, there are no Play Protect checks in GrapheneOS, and there will never be. It would only be possible on ROMs, such as LineageOS with Gapps, where Play services are installed as system apps, running with higher privileges than all other apps.

          • cmhe@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 days ago

            Well, good to know.

            I was thinking more about the way of Android security models, and that it would make sense for GOS to restrict available storefronts to stay consistent with their way to implement them. But good to know that it will not automatically happen just by updating the google services.

            And I would also think that people would likely complain if they where to implement it in a different way.

        • Fiery@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          Except this ‘signing’ is more of a control feature than a security feature. Just because Google markets it as a security feature doesn’t mean it is.

          • cmhe@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 days ago

            Well… The Android security model, as it is implemented in stock android and GOS, is about top down control, the full trust is given to the system vendors, not the end users. No rooting for instance. From this perspective not allowing installation of apps that cannot be blocked by the system vendor, fits well with that model.

            TBH, I am not a fan of that security model. And this is my critique of GOS. It doesn’t allow the user full access to their device, so that they can check and control what each application is storing or sending to third-party servers. Instead it is on full security and allows apps to store and transfer information to which the user has no access to.

            But the system vendor/developers would have that access, because they control the whole base system.

            The focus of the Android security model and in turn of GOS is on security, at the cost of privacy or freedom.

  • rezad@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    my hot take: while this is good for users in short term, in long term it just prolongs non-copyleft android OS hold for google.

    my only hope for grapheneos is that they pointed that they may move from android too.

    • Lev@europe.pub
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      That’s the long-term plan, yeah. Moving from Linux entirely actually, as they mentioned a future microkernel project

      • rezad@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        as I said in last post, I only see copyleft as a viable alternative. too many dev efforts forked and privatized. android should have been a warning. but many devs just think open source is enough. and they still think getting adapted by big corporation will not change the direction of projects.

        I am personally going in the direction of testing and helping only copyleft projects. so I skipped RedoxOS. even-though I like rust and new microkernel OSes.

        If I am going to give my time to a project (small as it is) I don’t want it to end up like android.

        • Lev@europe.pub
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          I completely agree, and a strong copyleft licence is something that GPLv3 does much better than its predecessor, which is unfortunately why it has not been adopted by the Linux kernel. I foolishly assumed that GrapheneOS, given the values it professes, would be distributed under the GPLv3 licence, but I have now discovered that this is not the case, in a move that I frankly cannot understand. Hope that changes in the near future, but it’s not very likely to happen I guess

  • commander@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 days ago

    I’ll hold off on a new phone to watch for this. Android could be great without Google’s nonsense. An OS that has high end hardware support and continues to work on convergence with desktop Linux both by the communities development and Google’s

    • Lka1988@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      3 days ago

      I don’t know… Part of me thinks that someone overruled Daniel on this decision. He stepped down as the main dev years ago, but is still a director… maybe the other directors overruled Daniel?

      But again, I don’t know. I’m just shooting from the hip.

      • 3ch0_Archit3ct@lemmy.zip
        link
        fedilink
        English
        arrow-up
        0
        ·
        3 days ago

        In all the time i looked online Ive never found a legitimate basis for these vague claims of drama around Graphene. See a lot of it in Louis Rossman circles (nothing against him, but he made a dramatic video on YT about leaving GrapheneOS) it’s reactionary at best. Someone got blocked people got mad, full story only the ones directly involved know.

        • Lka1988@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          3 days ago

          Louis was directly involved, and he brought receipts.

          Daniel is extremely paranoid (arguably part of why GOS is as secure as it is), but that paranoia can also lead to anxiety and assuming everyone is “out to get you”.

  • fodor@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 days ago

    Every cell phone manufacturer has some interest in diversifying the operating systems. Because Google develops Android and sells its own cell phones, it has an unfair market edge. And now Google is threatening to filter out apps that it doesn’t like which makes the risk even higher.

    So we can be sure all of the other major manufacturers of Android phones have considered if they’d like to support other distributions.

    • Axolotl_cpp@feddit.it
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      Maybe they will make deal with other distributors to ship their exclusive app stores and so that would be a good economic move for them

  • Seefra 1@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 days ago

    manufacturer will offer GrapheneOS support on future versions of their existing models, priced similarly to Pixels.

    Great, so I still won’t afford it…

    • Onomatopoeia@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 days ago

      I paid $120 for each Pixel I own.

      I refuse to pay a premium to have the “latest and greatest gadget”