News for hackers. Stuff that matters.

A comment on Some AMD CPU's RDRAND might not return random data after a suspend/resume. Parent comment

Re:Some AMD CPU's RDRAND might not return random data after ... by rwmj on Tuesday May 07, 2019 @03:15PM (#19852516)
There shouldn't be collisions. I mean that really: if you see a collision it's so much more likely that your computer / program / source of randomness is faulty [as in this case] than that the two random numbers collided that it's not worth considering the collision case.
[ Parent | on HN ]
Re:Some AMD CPU's RDRAND might not return random data after ... by lokedhs on Tuesday May 07, 2019 @09:36PM (#19855160)
But there can be collisions, at least in theory. And as we can see, in practice too.

Not checking for collisions because you trust that an RNG returns unique values is a fallacy and should be avoided. Especially since it's so easy to deal with the problem.

[ Parent | on HN ]
Re:Some AMD CPU's RDRAND might not return random data after ... by codedokode on Wednesday May 08, 2019 @07:07AM (#19857693)
It would be better to report the collision because most likely it means some error.
[ Parent | on HN ]
Re:Some AMD CPU's RDRAND might not return random data after ... by lokedhs on Wednesday May 08, 2019 @10:19AM (#19858998)
Yes, of course. As long as you do something. Just ignoring it because it's assumed it'll never happen is just bad design.
[ Parent | on HN ]