• xradeon@lemmy.one
    link
    fedilink
    English
    arrow-up
    1
    ·
    9 months ago

    You can’t do that since vulnerability is the connection between the TPM and the CPU, you need to encrypt that path.

    • Lojcs@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Pretty sure they meant if you need to keep a persistent public/private pair you can keep them in the tpm and initiate the exchange from there

      • laughterlaughter@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 months ago

        That’s correct. I’m guessing if it hasn’t been implemented yet, then there is some technical roadblock I’m currently missing.

    • laughterlaughter@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      The TPM comes out from the factory with a private key stored in it. The CPU has the public key.

      You turn on the laptop for the first time, and the communication between the CPU and the TPM is encrypted from the start.

      That’s what I’m referring to. Can’t this be done? I’m guessing it’s not that easy because I’m sure computer designers have already considered this idea.