3 ms·
But that is not how /dev/(u)random works and does not give U(255). Generally speaking, it gives some hash of some user/device activity, from these resources:
by yonixw 4y ago
But that is not how /dev/(u)random works and does not give U(255). Generally speaking, it gives some hash of some user/device activity, from these resources:
https://linuxhint.com/dev_random_vs_dev_urandom/ https://linuxhint.com/dev_random_vs_dev_urandom/
https://en.wikipedia.org/wiki//dev/random https://en.wikipedia.org/wiki//dev/random
- Retr0id 4y agoI know how urandom works (consider reading the articles you linked). The number between 0 and 255 is produced by the `od` command: https://man7.org/linux/man-pages/man1/od.1.html https://man7.org/linux/man-pages/man1/od.1.html
- deleted 4y ago[deleted]
- messe 4y ago> does not give U(255) What do you think each byte from /dev/(u)random is?
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- moyix 4y agoJust to be clear, cryptographic hashes and other outputs of cryptographic primitives are designed to be uniform random. If you find a detectable bias from uniform on the outputs of /dev/urandom then you should consider the underlying primitive (the ChaCha20 stream cipher, in the case of modern Linux urandom) to be broken.