AMD security bulletin disclosed for hardware RNG flaw
2 Sep 22 7:03 AM · 1d ago · 5 comments · 1 source · development 2 of 4
An AMD security bulletin (SB-7055) is cited as official acknowledgment of the RDRAND16 issue.
“I always wonder how hardware bugs like this happen with the sheer amount of hardware validation that's done. It'd be fascinating to know how it slipped through the cracks, though I know almost nothing about this side of the industry sadly”
20k, HN commenter · hn ↗jstanley Zen 2 CPU owner, bug reproducer0x000xca0xfe Hardware/cryptography developerAMD CPU manufacturer
The whole story articlespostscomments the bright band is this development · numbered dots are the others · click one to jump
What people said 4 voices · best of 5 · verbatim
-
This is why I use, in security critical contents of my software (where the numbers have to be computationally infeasible to produce), a type of random number generator called an XOF (extendable-output function).It takes entropy from multiple different sources, makes it all input to the XOF, then the XOF uses cryptography to output a stream that…
-
I always wonder how hardware bugs like this happen with the sheer amount of hardware validation that's done. It'd be fascinating to know how it slipped through the cracks, though I know almost nothing about this side of the industry sadly
-
Does rdrand32 and then taking the lowest 16 bits of its result yield any zeroes?Basically I'm wondering if it's a bug in the version of the instruction that writes to a 16-bit reg, or a bug in the underlying RNG
-
Chased a similar bug in a KDF once and only caught it by histogramming the 16 bit draws, statistical suites never flagged it.
All 4 developments of AMD's RDRAND16 instruction can't generate zero on some Zen… →
Hacker NewsNewswiresMastodon