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
[–] 11 points 2 weeks ago* (7 children)

They can't. They require extremely up to date firmware and very short update cycles. Only large corporations with huge phone platforms are able to do satisfy that.

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

    Can Graphene OS achieve their privacy targets and principles in different ways that encourage collaboration with non-corporations?

    I refuse to believe that GOS can't agree to graduated privacy provisions according to the capabilities of Linux and sustainable/repairable non-corpo companies and their phones.

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

    Well, than you should read what GOS developers have to say about that, they are pretty clear on it. They absolutely do not accept any compromise on that, even if that means being forced to rely on cooperation by big corporations for hardware and firmware. I don't even judge that, it is just merely how it is.

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

    I am judging that.

    I want them to keep their principles, and at the same time partner with some Linux group or some other working group representing Open-Source Hardware (OSH) so that one day we don't HAVE to rely on corporations for true privacy with our smartphones.

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

    I can't see how that is possible without compromising on their security requirements. The hardware isn't the problem here, that could be overcome, the extremely rapid firmware updating reqirement is. That needs huge resources, hence they are using so far a device from the huge comoany behind the Android ecosystem. Already Motorola, another huge compaby is stretchung that requirement, as tgey are not sitting at the source of that ecosystem.

    Again, I am not defending GrapheneOS' choice, just describing their dilemma

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

    They don't want to, which is fine for their goal of having the absolutely most secure phone possible.

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

    Short-sighted goal in my opinion. They could be the leader in privacy for smartphones from the bottom up, including hardware and software.

    GOS's work with Motorola might just lead Motorola to be that group as they always have for decades, so my issues might go away anyways.

    Just getting arrogant, self-isolating vibes when they have soooo much good will with the tech community on building privacy from the ground up in some of the most important intelligent devices in our lives.

    Why can't GOS join a working group with ISO or IEC or IEEE or other groups to create roadmaps and tiers of compliance so that other manufacturers have means and methods of approaching GOS's lofty goals.

  • permalink
  • fedilink
  • source
  • parent