925
Google is working on essentially putting DRM on the web (github.com)
submitted 3 years ago by to c/technology@beehaw.org
266 comments fedilink hide all child comments
 

The much maligned "Trusted Computing" idea requires that the party you are supposed to trust deserves to be trusted, and Google is DEFINITELY NOT worthy of being trusted, this is a naked power grab to destroy the open web for Google's ad profits no matter the consequences, this would put heavy surveillance in Google's hands, this would eliminate ad-blocking, this would break any and all accessibility features, this would obliterate any competing platform, this is very much opposed to what the web is.

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

I'm afraid you are sorely mistaken. Here's an RCE vulnerability in the TPM 2.0 reference implementation.

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

    Your own article says it’s VMs. The tpm itself can be bricked. Ok that sucks. Still not persistent like you describe.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago*

    The vulnerability is not specific to VMs. Malicious code running with privileges on the host operating system can also exploit it.

    But yes, this can also be used to escape the VM sandbox, and since the TPM has full access to the entire system, exploit code can then gain full privileges on the host.

    Can the TPM firmware not write to the flash where it's stored? If it can, then an RCE exploit can do so too, and thereby make itself persistent.

    Basically, any successful RCE exploit in a TPM equals total and permanent compromise of the entire physical machine. That's why the TPM is a security threat rather than a security feature.

  • permalink
  • fedilink
  • source
  • parent