-
Notifications
You must be signed in to change notification settings - Fork 6
Improved fixup for bcrypt >= 5.0.0, bcrypt version detection
#21
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
2648e24
Fix bcrypt wraparound bug test for bcrypt >= 5.0.0
chapmajs efa7aa2
Unpin bcrypt < 5.0.0
chapmajs f6d6523
Fixing bcrypt backend version detection
chapmajs d7f80d3
Fixing indent in bcrypt.py
chapmajs 10d51a2
Backing out version check change
chapmajs ea34c47
Removing empty line
chapmajs File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have to do this instead of using
packaging.metadata.version? 🤔P.S. The updated hash check looks fine though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only did the check that way as
metadata.version()failed on a random old install I tested on. The above works in both cases.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On what version specifically does it fail? 🤔 From what I know
metadata.version/distributionshould get the info from.dist-info, maybe that specific version is missing some metadata or isn't packaged "correctly".There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Old Slackware 14.2 i486 install, I'd have to start the machine up to check
passlib/bcryptversions. If it's guaranteed functionality/just some packaging aberration switch it back topackaging.metadata.version(or I can do it and amend the PR!)