Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bpo-9216: Add usedforsecurity to hashlib constructors #16044

Merged
merged 5 commits into from Sep 13, 2019

Conversation

tiran
Copy link
Member

@tiran tiran commented Sep 12, 2019

@gpshead
Copy link
Member

gpshead commented Sep 12, 2019

The hashlib.rst documentation needs to be updated.

@gpshead gpshead self-assigned this Sep 12, 2019
@tiran
Copy link
Member Author

tiran commented Sep 12, 2019

I need to update documentation, PEP, and tests.

Signed-off-by: Christian Heimes <christian@python.org>
Signed-off-by: Christian Heimes <christian@python.org>
Signed-off-by: Christian Heimes <christian@python.org>
Signed-off-by: Christian Heimes <christian@python.org>
Signed-off-by: Christian Heimes <christian@python.org>
@gpshead gpshead added the sprint label Sep 13, 2019
@gpshead gpshead merged commit 7cad53e into python:master Sep 13, 2019
stratakis pushed a commit to stratakis/cpython that referenced this pull request Jan 2, 2020
The usedforsecurity keyword only argument added to the hash constructors is useful for FIPS builds and similar restrictive environment with non-technical requirements that legacy algorithms be forbidden by their implementations without being explicitly annotated as not being used for any security related purposes.  Linux distros with FIPS support benefit from this being standard rather than making up their own way(s) to do it.

Contributed and Signed-off-by: Christian Heimes christian@python.org
stratakis pushed a commit to stratakis/cpython that referenced this pull request Oct 5, 2020
The usedforsecurity keyword only argument added to the hash constructors is useful for FIPS builds and similar restrictive environment with non-technical requirements that legacy algorithms be forbidden by their implementations without being explicitly annotated as not being used for any security related purposes.  Linux distros with FIPS support benefit from this being standard rather than making up their own way(s) to do it.

Contributed and Signed-off-by: Christian Heimes christian@python.org
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint type-feature A feature request or enhancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants