|
|
Subscribe / Log in / New account

Pitchforks for RDSEED

Pitchforks for RDSEED

Posted Feb 9, 2024 13:28 UTC (Fri) by zx2c4 (subscriber, #82519)
In reply to: Pitchforks for RDSEED by spacefrogg
Parent article: Pitchforks for RDSEED

These are unprivileged CPU instructions. This isn't a kernel scheduler issue.


to post comments

Pitchforks for RDSEED

Posted Feb 9, 2024 14:31 UTC (Fri) by spacefrogg (subscriber, #119608) [Link]

Then the CPUs are actually broken. You must guard your entropy state or its useless to you.

Daniel J. Bernstein has an excellent write-up about how you could potentially mis-use an entropy source to force your encryption scheme to leak your private key alongside your ciphertext while making it look perfectly fine. I just fail to find it right now. (It was concentrating on why encryption schemes should not mindlessly access entropy)

The argument is quite simple: You do know how the encryption scheme distributes bits. If you control the entropy bits and the encryption scheme, you can hide the private key in the entropy bits and make the ciphertext partially predictable, enough to recover the private key and thus the original message.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds