feat: add WORDPRESS68 hash algorithm for WordPress 6.8+ - #3145
Open
HotWaterFlask wants to merge 1 commit into
Open
HotWaterFlask wants to merge 1 commit into
HotWaterFlask wants to merge 1 commit into
Conversation
WordPress 6.8 switched password hashing to bcrypt with an HMAC-SHA384
pre-hash step and stores hashes with a "$wp" prefix (e.g. "$wp$2y$10$...").
The existing WORDPRESS algorithm only handles the legacy phpass format
("$P$"), so passwords written by current WordPress versions cannot be verified.
WORDPRESS68 implements the same scheme: "$wp" + bcrypt of
base64(HMAC-SHA384(password, "wp-sha384")) with cost 10.
comparePassword only accepts the "$wp" format; other formats are expected to be
configured via legacyHashes (WORDPRESS for "$P$", BCRYPT2Y for "$2y$"), which
AuthMe upgrades to WORDPRESS68 upon a successful login.
Adds Wordpress68Test (generated with the tools task) and regenerated docs.
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
1 participant
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.
WordPress 6.8 switched password hashing to bcrypt with an HMAC-SHA384 pre-hash step and stores hashes with a "$wp" prefix (e.g. "$wp$2y$10$..."). The existing WORDPRESS algorithm only handles the legacy phpass format ("$P$"), so passwords written by current WordPress versions cannot be verified.
WORDPRESS68 implements the same scheme: "$wp" + bcrypt of base64(HMAC-SHA384(password, "wp-sha384")) with cost 10.
comparePassword only accepts the "$wp" format; other formats are expected to be configured via legacyHashes (WORDPRESS for "$P$", BCRYPT2Y for "$2y$"), which AuthMe upgrades to WORDPRESS68 upon a successful login.
Adds Wordpress68Test (generated with the tools task) and regenerated docs.