Enhance wp_hash function to support custom hashing algorithms#7306
Enhance wp_hash function to support custom hashing algorithms#7306PushpenderIndia wants to merge 11 commits intoWordPress:trunkfrom
Conversation
|
Hi @PushpenderIndia! 👋 Thank you for your contribution to WordPress! 💖 It looks like this is your first pull request to No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making. More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook. Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook. If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook. The Developer Hub also documents the various coding standards that are followed:
Thank you, |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Fix: Unit test and sprintf placeholders
|
Committed in https://core.trac.wordpress.org/changeset/59578 |
Trac ticket: https://core.trac.wordpress.org/ticket/62005
Summary
This PR updates the
wp_hashfunction to allow users to specify a custom hashing algorithm, enhancing the security and flexibility of the function. Previously, the function hardcoded themd5algorithm, which is vulnerable to collision attacks.Changes:
$algoto thewp_hashfunction, allowing users to specify the hashing algorithm. The default remainsmd5for backward compatibility.hash_hmac_algos()to ensure the provided algorithm is supported. If not, the function will fall back tomd5.Benefits:
sha256.Backward Compatibility:
md5as the default algorithm, ensuring backward compatibility with existing code.Testing:
md5,sha256,sha512) to confirm correct functionality.md5when an unsupported algorithm is provided.This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.