Its best explained by this thread: https://mstdn.jp/@GrapheneOS@grapheneos.social/117645039420648634

TL:DR is that Google's business side is threatening to revoke android licenses from phones that support GOS and is likely planning to lock the bootloaders on Pixel phones going forward. Important to note is that in GOS own words, the actual Google Android team is seemingly not down with it and has helped GOS work on things like Vanadium. As it stands it seems like Graphene is trying to take legal action against Google.

Edit: apparently they're also on track to start making new Android feature updates exclusive to the Pixel line of phones. We're really in for a major shakeup in the phone market it seems.

you are viewing a single comment's thread
view the rest of the comments
[–] -2 points 3 hours ago (7 children)

I think it's fairer to say that Graphene OS makers AND Hardware makers are both being dicks.

If either side conceded I bet Graphene OS would be far more prevalent, even if it had to be "Graphene OS Basic" rather than the full maximum security version.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 5 points 3 hours ago (4 children)

    How is having hardware requirements being "dicks"? The whole point of GrapheneOS is privacy and security is important for strong privacy. Lowering our standards doesn't help the project or our users. Having a less secure version of the OS would effectively mean a lot more work for a worse OS. We'd need to hire a lot more people to support that additional OS as well as all the new devices we'd support. It just doesn't make sense.

  • source
  • parent
  • hideshow 4 child comments
  • [–] -3 points 3 hours ago (3 children)

    It only doesn't make sense if you're taking A SIDE.

    For anybody looking at it from the outside, the objective of smartphones freed of big-corporation controlled OS is being blocked BOTH by GrapheneOS refusing to have a version of their OS that works without very specific hardware that's only needed for highly hardenned security AND by phone makers being unwilling to make phones with that hardware.

    Either side conceding would solve the problem for the rest of us and any evidence-free claims that it's easier for one side than the other are just bullshit excuses from those taking sides rather than looking at the big picture.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 2 hours ago (1 child)

    That's not how security works though. There are hardware requirements in order for certain software features to work.

    To make a less secure phone in both OS and hardware is more marketable, but it defeats the purpose.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 1 hour ago* (last edited 1 hour ago)

    Funny your confident proclamations about how security works or not.

    Security isn't an absolute and in fact there is no such thing as absolutely secure - as smart-chip technology long ago showed when attackers started reverse engineering the keys stored in the supposedly secure smart-chip hardware by tracking energy consumption when the chips were using them for encryption or digital signing, even supposedly super secure hardware is only secure against certain kinds of attackers.

    (Also don't get me started on techniques involving liquid nitrogen and electron microscopes)

    Security is a range and IT Security design is done on the basis of answering the question "secure against which kind of attackers?", which is why banking system security is not the same as blog website security.

    So the question is, can GrapheneOS make a system which is secure against external attackers whilst not having specific cryptographic hardware?

    Because it would be a big fucking leap forward if your smartphones couldn't be remotely turned into surveillance devices or their contents accessed by Google or by those who can get Google's cryptographic keys for things like software updates (i.e. state actors), and generally the cryptographic hardware is only needed to secure systems against access by people with physical access to the hardware, not against remote access, especially not against the OS maker themselves.

    Sure, some people do worry about the likes of the TSU confiscating and cloning their phones at a border entry and latter hacking its contents - and those people should stick to GrapheneOS and whatever the hardware that team things is needed for it to be safe against that - but most people just want their private data to remain private in everyday life, and everyday life for most people does not involve their smartphone being confiscated by the authorities of authoritarian nations like the US.

  • source
  • parent
  • [–] 2 points 31 minutes ago

    I think you may be confused about the purpose of grapheneOS. If what you want is a phone OS that's free of big corporate control, even if it sacrifices some security, lineageOS is right there.

    The whole point of grapheneOS is highly hardened security without compromise. That comes with certain hardware requirements and so far only Google and Motorola meet them. It's not about corporate control or marketability or being an open source alternative for everyone or whatever. There are people who actually need the security provided by grapheneOS, where a compromise could be the difference between going to prison or not. Those people are graphene's core userbase and they count on the developers for their literal safety. So it's no surprise that the developers are not willing to compromise on the core of the product.

    I'm sure they would be very happy if pine64 or fair phone or some other less evil corporations started making cheaper phones that include the required hardware, but they aren't going to step back on security to support more phones because the security is the point.

  • source
  • parent