PEP 522: Rewrite accounting for Nathaniel's feedback#23
Merged
ncoghlan merged 1 commit intoJun 20, 2016
python:masterpython/peps:masterfrom
ncoghlan:security-sensitive-rngncoghlan/peps:security-sensitive-rngCopy head branch name to clipboard
Merged
PEP 522: Rewrite accounting for Nathaniel's feedback#23ncoghlan merged 1 commit intopython:masterpython/peps:masterfrom ncoghlan:security-sensitive-rngncoghlan/peps:security-sensitive-rngCopy head branch name to clipboard
ncoghlan merged 1 commit into
python:masterpython/peps:masterfrom
ncoghlan:security-sensitive-rngncoghlan/peps:security-sensitive-rngCopy head branch name to clipboard
Conversation
The core proposal (raising BlockingIOError) remains the same, but the rationale and background sections now go into much more depth for folks that want it. The PEP now also explicitly covers the related changes to interpreter and random module initialization, as well as providing references to most of the related bugs.python.org messages.
| and when it occurs then there is no direct way for userspace to tell it has | ||
| happened without querying operating system specific interfaces. | ||
|
|
||
| On \*BSD systems, encountering this situation means ``os.urandom()`` will block |
Contributor
There was a problem hiding this comment.
This is a minor nitpick, but AFAICT (could easily be misinformed on one piece of another but):
- OpenBSD: requires entropy be present before spawning the first userspace process
- FreeBSD: reads from
/dev/urandomand/dev/randomblock if the RNG is uninitialized, and never afterwards (as described here) - NetBSD: acts like Linux
This is why my draft avoided saying anything about *BSD :-)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The core proposal (raising BlockingIOError) remains the same,
but the rationale and background sections now go into much more
depth for folks that want it.
The PEP now also explicitly covers the related changes to interpreter
and random module initialization, as well as providing references
to most of the related bugs.python.org messages.