/explore
|
You are here 
|
words.filippo.io | ||
| | | | |
lists.openwall.net
|
|
| | | | | ||
| | | | |
www.thomas-huehn.com
|
|
| | | | | [AI summary] The article discusses the use of /dev/random and /dev/urandom in Linux systems for generating random numbers. It highlights that /dev/urandom is generally preferred over /dev/random due to its non-blocking nature and sufficient cryptographic security. The article also addresses misconceptions in the man pages and emphasizes that /dev/urandom is safe for most applications, including cryptographic uses, as long as the initial seeding is done properly. It mentions that while /dev/random is considered a legacy interface, it's not always necessary, and modern Linux distributions and syscalls like getrandom(2) provide better alternatives. | |
| | | | |
lwn.net
|
|
| | | | | [AI summary] This article discusses a recent Linux kernel patch series that aims to remove the blocking pool of /dev/random to prevent denial-of-service issues, while introducing new system call flags and interfaces for cryptographic random number generation. | |
| | | | |
cocomelonc.github.io
|
|
| | | [AI summary] The author presents a C programming proof-of-concept for collecting Linux system information via system calls and sending it to a Telegram bot, teaching necessary coding techniques like URL encoding while disclosing potential security pitfalls. | ||
