3 ms·
Wow, this is pretty thorough but I never saw it address the simple question, why not use rdrand? Also: > the CPU Jitter random number generator returns roughl
by tedunangst 12y ago
Wow, this is pretty thorough but I never saw it address the simple question, why not use rdrand?
Also:
> the CPU Jitter random number generator returns roughly 10 kBytes per second on an Intel Core i7
OpenBSD requires at least 8 bytes of random data per TCP connection. Limiting a system to 1000 conn/sec (to say nothing of any other processing those connections may require) probably isn't going to fly.
As a comparison, I can read from /dev/random (and write to /dev/null) at over 300 MB/s.
- hurin 12y ago> OpenBSD requires at least 8 bytes of random data per TCP connection. Limiting a system to 1000 conn/sec (to say nothing of any other processing those connections may require) probably isn't going to fly. They can use the generated random values to seed a CSPRNG. I guess for containers or other virtual environments this has distinct advantages (at least that's one of the reasons given in the introduction). > As a comparison, I can read from /dev/random (and write to /dev/null) at over 300 MB/s. You can read from /dev/random only if there is enough entropy in it, and it's rarely very much, I don't know how you got that 300MB/s figure.