Set usedforsecurity=False
in hashlib methods (FIPS compliance)
#5790
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.
Related to huggingface/transformers#27034 and huggingface/huggingface_hub#1782.
TL;DR:
hashlib
is not a secure library for cryptography-related stuff. We are only usinghashlib
for non-security-related purposes indiffusers
so it's fine. From Python 3.9 we can setusedforsecurity=False
in anyhashlib
method which is mandatory for companies that forbid the use ofhashlib
for security purposes. This PR fixes that.Note: before merging this we need to release a new tokenizers version that would allow the newest
huggingface_hub
version (see huggingface/tokenizers#1385). Otherwise it might create friction to users that want to installdiffusers
+tokenizers
at the same time.