add pbkdf2 hash function for FIPS 140-2 support #20658
Open
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.
Description
Adding a new password hash function for use with FIPS 140-2 deployments.
Motivation and Context
If enabled through setting
user_password_default_algorithm
topbkdf2
the only hash function for user passwords isPBKDF2WithHmacSHA512
which is the recommend one to use.The iterations default to 10000, which is rather slow. This can be customized with
user_password_pbkdf2_iterations
.The stored hash remembers which iteration number was used, however old hashed passwords are no longer usable and must be reset (this is true for bcrypt as well, so there's no new behavior introduced).
How Has This Been Tested?
Unit test.
Screenshots (if appropriate):
Types of changes
Checklist: