Fix maximum password length enforcement#44
Merged
patrickfav merged 1 commit intopatrickfav:masterfrom Feb 9, 2023
quinot:quinot/fix-max-len
Merged
Fix maximum password length enforcement#44patrickfav merged 1 commit intopatrickfav:masterfrom quinot:quinot/fix-max-len
patrickfav merged 1 commit intopatrickfav:masterfrom
quinot:quinot/fix-max-len
Conversation
NUL terminators play a role in keying only if the password is shorter than 72 bytes. For a password that is exactly 72 bytes, no cyclic repetition occurs in the key expansion phase, and no NUL is needed: the password can be used as-is; in other words, the NUL terminator should not be counted against the 72 bytes limit. Adjust test cases accordingly. Test vectors in testReferenceValuesWithoutNullTerminator have been tested against the Python bcrypt module.
This was referenced Feb 6, 2023
Owner
|
Thank you for your PR! |
Merged
|
I suggest the public field My code currently uses |
Owner
|
@Andrew-Cottrell good point, I re-introduced it with 0.10.1, see #48 |
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.
NUL terminators play a role in keying only if the password is shorter than 72 bytes. For a password that is exactly 72 bytes, no cyclic repetition occurs in the key expansion phase, and no NUL is needed: the password can be used as-is; in other words, the NUL terminator should not be counted against the 72 bytes limit.
Adjust test cases accordingly.
Test vectors in testReferenceValuesWithoutNullTerminator have been tested against the Python bcrypt module.