News for hackers. Stuff that matters.
Re:RDRAND on AMD Ryzen 9 5900X is flakey by Dylan16807 on Tuesday January 12, 2021 @10:52AM (#25748481)
No matter what, you could get hit with a cosmic ray or spark of static or a bug could corrupt your program's memory.

The state of "we somehow generated two identical UUIDs" cannot be prevented in the real world. You can only reduce the chance to acceptable levels.

Compared to the risks that are accepted in basically all devices, the danger from using big random numbers is negligible. Which makes it not crazy to do.

Re:RDRAND on AMD Ryzen 9 5900X is flakey by rasz on Wednesday January 13, 2021 @02:33AM (#25759272)
Did you just compare normal operation (true randomness allowing for a string of duplicate outputs) to a bug caused by stray cosmic ray in an effort to excuse brain dead decision by systemd?
Re:RDRAND on AMD Ryzen 9 5900X is flakey by Dylan16807 on Wednesday January 13, 2021 @11:53AM (#25764643)
If you choose to run on unreliable hardware, then bugs caused by that are normal too.

And everyone runs on unreliable hardware.

So yes, I did compare them. Do you have a reason I shouldn't?

If cosmic rays will cause one collision per decade, and "allowed" random collisions will cause one collision per million years, then why care about the increase in risk?

And let's be clear. This github issue is not happening because of using truly random numbers to generate full-size UUIDs. The problem is something else.