233
Volkswagen Bans Security-Focused GrapheneOS Citing Security Reasons, Continues To Support Android 10 (www.autoevolution.com)
submitted 2 months ago by to c/android@lemmy.world
55 comments fedilink hide all child comments
 

cross-posted from : https://lemmy.zip/post/67481084

you are viewing a single comment's thread
view the rest of the comments
[–] 136 points 2 months ago (1 child)

updated its mobile apps to no longer support GrapheneOS

This is not accurate. They updated the app to actively block GrapheneOS and other third-party Android builds.

The distinction is critical; unsupported combinations often work.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 25 points 2 months ago (3 children)

    They updated the app to use the Play Integrity API, which GOS does not meet.

    Not that it means anything, of course. GOS is far more secure than Google's laughable excuse of a certification.

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

    They updated the app to use the "Play Integrity[sic] API," which actively blocks GOS.

    "Does not meet" implies there is something reasonable GOS could do to "fix" it, which untrue and misleading. The malice on Google's and Volkswagen's part is an important part of the story.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -7 points 2 months ago* (last edited 2 months ago) (1 child)

    Requiring a valid Play Integrity API response is a blanket enforcement on all custom ROMs, regardless of security measures.

    This was not a targeted attack on Graphene. GOS users just tend to be more vocal and....paranoid.

    “Does not meet” implies there is something reasonable GOS could do to “fix” it

    "Does not meet" has more than one meaning. Don't play dumb.

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

    I didn't say the attack was "targeted" only on GOS; you made that up yourself. But it is an attack, as opposed to something with a valid excuse.

    Also: it's only paranoia if they aren't actually out to get you.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 2 months ago

    Big companies have been trying to lock out custom ROMs for years, it's a giant cat and mouse game. The integrity bullshit thing is just another move. And the fascists in charge have been stripping regulations which is allowing these companies to make such bold moves.

    I think we're on the same page here. I apologize for coming off so harsh.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 10 points 2 months ago (2 children)

    That is until the official Motorola partnership happens with GoS and Motorola. It's the missing piece for integrity verification as of current listed requirements on Google's documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.

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

    That is until the official Motorola partnership happens with GoS and Motorola. It’s the missing piece for integrity verification as of current listed requirements on Google’s documentation. They needed to have first class support from a major OEM. Looking forward to seeing how Google will change that maliciously. This includes attestation.

    Good point, I didn't think about that. It will be very interesting to see what happens.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •