272
GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE); GrapheneOS might skip the the whole pixel 11 series (grapheneos.social)
submitted 2 weeks ago by to c/technology@lemmy.world
89 comments fedilink hide all child comments
 

cross-posted from: https://piefed.world/c/tech/p/1368563/grapheneos-project-pixel-11-no-longer-supports-hardware-memory-tagging-mte

Bluesky.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 2 weeks ago (11 children)

But why can't GrapheneOS work with those companies to ACQUIRE the right hardware requirements, rather than leaning on a corporation?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 11 child comments
    •
  • [–] 12 points 2 weeks ago (10 children)

    The hardware requirements are public. Those manufacturers have chosen not to implement supported hardware, which is step 0.

    There is also a maintenance burden for the GrapheneOS team. The ROM requires kernel patches and driver work that makes supporting additional phones intensive work.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 1 point 2 weeks ago (9 children)

    Why would manufacturers choose to meet GOS's extra requirements?

    There needs to be a give and take. It seems like GOS's mantra is their way or the high way, which isn't collaborative in the slightest.

    Can there not be discussions held between Linux and sustainable/repairable OEMs and GOS to start integrating each other's requirements? Diplomacy/negotiations/working groups are just completely neglected?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 1 point 2 weeks ago* (4 children)

    GOS is designed for maximum security at its base. It uses all the hardware features it requires to minimize its attack surface against adversaries that have infinite resources to attack the device and get at the infirmation inside.

    Lowering those standards means opening a vulnerability, which means someone with that vulnerability can have their data stolen from the device in particularly that way, since that vulnerability is well documented.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 2 weeks ago (3 children)

    How come other phones by Samsung, Apple, etc. seem to be doing alright despite not meeting the hyper restrictive requirements of GrapheneOS?

    I reject that GrapheneOS can't continue to do their work with Google Pixels and Motorola and NOT encourage open-source hardware developers to integrate GOS's so that one day we can have open-source, privacy-first, truly-secure, repairable, sustainable communications devices.

    It seems to me like GrapheneOS could lead the world in pushing this topic by creating cross-industry working groups to focus on fixing vulnerabilities in some of the most important intelligent devices existing today.

    There could be organizations like IEEE or IEC that GOS may or may not work with, but no one has given me an answer for that. GOS seems self-isolated and therefore self-serving, as an outsider. I don't understand why they can't do more outreach to build coalitions in the industry, if they aren't already.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 weeks ago* (2 children)

    There is a lot of government / intelligence agency interest in making sure devices can be hacked into... see the whole FBI vs. Apple thing from some time back.

    Most device manufacturers are trying to keep costs down... adding security features adds R&D money they have to spend and pass on to the devices as sold.

    Most people don't know or care their devices are easily hackable... until it affects them personally.

    Some people have to use GOS because enemy nations are targeting them and their devices in particular for hacking into, and normal devices are easy to break into... see Pegasus.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 weeks ago (1 child)

    I agree that GrapheneOS is useful for some and vital for many people in the world.

    What I'm asking (and demanding) is for GrapheneOS to not put all their eggs in one basket, and to develop alternatives. I don't think GOS investing in phone manufacturing with Motorola will last forever, just as Google didn't. Having non-corporate options is imperative as Big Tech ramps up more and more surveillance, walled off gardens, and enshittification

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 weeks ago (3 children)

    There needs to be a give and take

    If GrapheneOS can't handle the maintenance burden, there is nothing to negotiate.

    Presumably, maintaining software for a niche phone requires effort similar in magnitude to a larger, mainstream phone. Why, then, would a solely privacy-oriented org choose to cater to a smaller audience?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 2 weeks ago (2 children)

    Can other organizations replicate GrapheneOS's principles in ways where THOSE organizations can maintain the burden?

    Is GrapheneOS working towards industry wide standards on privacy-first operating systems from the hardware up?

    Are they contributing to the field at large, or are they keeping to themselves out of self preservation (or selfishness)?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 weeks ago (1 child)

    GrapheneOS is an open-source fork of AOSP. Anyone could fork it again and provide kernel modules/drivers for their hardware.

    To my knowledge, GrapheneOS is not standards-based. They take one operating system, and tweak it. I don't know if there are relevant standards to contribute to, or even standards bodies to approve them.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 2 weeks ago*

    Thanks for taking the time to educate someone that is STEM-studied but not necessarily in computer hardware/software.

    Given that GrapheneOS picked AOSP to be their canvas with which to tighten down the hatches and improve the base AOSP platform's privacy characteristics, this to me indicates that nothing is stopping GOS from doing the same and contributing to other major platforms intended for mobile devices. Unless of course bandwidth is an issue for them, then they can't contribute to more than just their AOSP fork.

    As someone who uses tech and doesn't really develop it, I would appreciate GrapheneOS expanding their vision to other software/hardware platforms like those being worked on by the Ubuntu Touch, SailfishOS, PostmarketOS, etc. teams.

    I'm not advocating that GOS work on all of these, but I am advocate for GOS to branch off from corporate dependence in the event Motorola goes the way of Google.

    If one thing capitalism has shown us over the last 100+ years, corporations that can enshittify will enshittify. It's only a matter of time, and it'd be better imo for GOS to start pivoting sooner rather than later.

    Unless GOS are ok with ceasing their entire project once Motorola drops them. Maybe they're confident in that bet. I wouldn't be, being a FOSS advocate myself nowadays.

  • permalink
  • fedilink
  • source
  • parent