Skip to content
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

Improve security key handling in pluggable.php #6588

Closed
wants to merge 1 commit into from
Closed

Conversation

spacedmonkey
Copy link
Member

Requires #61053.

Use wp_prime_site_option_caches to prime option / network option caches if not defined as const.

Trac ticket: https://core.trac.wordpress.org/ticket/59871


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.

This commit adds functionality to recognize undefined keys and salts in wp-includes/pluggable.php and to prime site options with them. This strengthens the security by addressing key and salt duplicates and ensuring unique identifiers for each.
Copy link

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 props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props spacedmonkey.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@hubot hubot deleted the fix/59871 branch May 20, 2024 22:20
Copy link

Test using WordPress Playground

The 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

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@peterwilsoncc
Copy link
Contributor

@spacedmonkey It looks like you accidentally pushed to the WordPress org's copy of the repo. Are you able to reopen from your fork so the branch doesn't get deleted when the bots sync every minute or so.

@spacedmonkey
Copy link
Member Author

@spacedmonkey It looks like you accidentally pushed to the WordPress org's copy of the repo. Are you able to reopen from your fork so the branch doesn't get deleted when the bots sync every minute or so.

Done #6597

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants