Talk:Entropy-supplying system calls

Computing: Software / CompSci / Security Low‑importance

This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles

Low

This article has been rated as Low-importance on the project's importance scale.

This article is supported by WikiProject Software (assessed as Low-importance).

This article is supported by WikiProject Computer science (assessed as Low-importance).

This article is supported by WikiProject Computer Security (assessed as Low-importance).

Things you can help WikiProject Computer science with:

Here are some tasks awaiting attention:

Article requests :
- Requested articles/Applied arts and sciences/Computer science, computing, and Internet
Cleanup :
- Computer science articles needing attention
- Computer science articles needing expert attention
Copyedit :
- Computing
Expand :
- Computer science
Infobox :
- Computer science articles without infoboxes
Maintain :
- Timeline of computing 2020–present
Photo :
- Find pictures for the biographies of computer scientists (see List of computer scientists)
- Computing articles needing images
Stubs :
- Computer science stubs
Unreferenced :
- WikiProject Computer science/Unreferenced BLPs
Project-related :
- Tag all relevant articles in Category:Computer science and sub-categories with {{WikiProject Computer science}}

Linux Low‑importance

	Linux portal This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.LinuxWikipedia:WikiProject LinuxTemplate:WikiProject LinuxLinux articles
Low	This article has been rated as Low-importance on the project's importance scale.

Talk

This page is pretty sloppy, and it may be impacting code quality. When judging a function in this area, the characteristics of concern include: 1. cryptographic-use acceptable output 2. gauranteed output, no error cases to worry about (error prone) 3. does not block (forever?), no retry cases to worry about (again, error prone) 4. The comparison with rand()-style functions is embarrasing. What next, a comparison against

  getpid() ^ time(NULL)?  Bad practices don't need flaunting unless mention raises the bar.

Can someone with word skills try to write this page from a different perspective? Like maybe, state-of-the-art gets mention as the main-line primitive, and everything else is given a description as a subset?

The state of the art is: always_returns [buffer] gauranteed_random_value() no_matter_what, including early as possible during bootstrap. Anything else has missed the mark -- a significant trap for programmers who suddenly tries to do cryptography "too early". Most of the designs which don't do this right are concessions to the past. Hopefully the python-near-systemd bug is educational, ie. take general purpose code and put it earlier, and it fails unexpectedly. I'm guess I am saying some people anticipated problems like this and build a better system, and some other people didn't anticipate this or the next 100 problems and failed to build right.