this post was submitted on 07 Feb 2024
738 points (97.7% liked)

Technology

59534 readers
3195 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] xradeon@lemmy.one 8 points 9 months ago (3 children)

The private key would have to stored in clear text somewhere. Potentially if you had non volatile space on cpu that to store the private key, that might work. But if you’re going to do that, might as well just use an ftpm.

[–] laughterlaughter@lemmy.world 2 points 9 months ago (1 children)

Why not store it directly in the TPM, if that's the device that will do that initial decryption?

[–] xradeon@lemmy.one 1 points 9 months ago (2 children)

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

[–] laughterlaughter@lemmy.world 2 points 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.

[–] Lojcs@lemm.ee 2 points 9 months ago (1 children)

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 1 points 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.

[–] jet@hackertalks.com 2 points 9 months ago

Right and not to mention pairing the cpu and tpm for key exchange to avoid mitm attacks...

[–] Lojcs@lemm.ee 1 points 9 months ago (1 children)

Just generate one anew. You don't need to use the same one each time

[–] xradeon@lemmy.one 1 points 9 months ago (1 children)

What do you mean by that? Generate a new private/public key pair every time you setup a new TPM? Or when you boot the system or something?

[–] Lojcs@lemm.ee 1 points 9 months ago* (last edited 9 months ago)

On each connection. Or boot. Whenever you need

Edit: to be clear, this would still be vulnerable to mitm attacks without a user entered password on top but at least you can't just read the secrets from the bus. E2: And having a password wouldn't be fully secure without such a scheme neither