Use pbkdf2-hmac-sha256 for password hash #495
Open
Conversation
This file contains 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
|
Is this backwards compatible with existing clients? |
|
We'll need to add backwards compatibility, maybe with a version or hash algo prefix on the hex, e.g. "sha256:<hex>" to signal the server. If it's not there, we just use the original algo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #494
I know,
golang.org/x/crypto/pbkdf2isn't in the standard library in Go 1.22 butx/cryptois maintained by the Go core devs and it is in the stdlib as of Go 1.24.While it is true 3rd party packages will have to update their code, I've seen it already wrong in the wild.