2718.us blog » SECRET_KEY http://2718.us/blog Miscellaneous Technological Geekery Tue, 18 May 2010 02:42:55 +0000 en hourly 1 http://wordpress.org/?v=3.0.4 WordPress 2.5.1 http://2718.us/blog/2008/04/25/wordpress-251/ http://2718.us/blog/2008/04/25/wordpress-251/#comments Fri, 25 Apr 2008 18:16:45 +0000 2718.us http://2718.us/blog/?p=29 The .1 update that many people said they were waiting for is here. (And there are reminders all over every admin page on my blog, too.)

Version 2.5.1 of WordPress is now available. It includes a number of bug fixes, performance enhancements, and one very important security fix. We recommend everyone update immediately, particularly if your blog has open registration. The vulnerability is not public but it will be shortly.

The notice also mentioned the SECRET_KEY thing that I talked about yesterday and gave a link to auto-generate the line for wp-config.php:

Since 2.5 your wp-config.php file allows a new constant called SECRET_KEY which basically is meant to introduce a little permanent randomness into the cryptographic functions used for cookies in WordPress. You can visit this link we set up to get a unique secret key for your config file. (It’s unique and random on every page load.) Having this line in your config file helps secure your blog.

Upgrading took me about 15 seconds (as usual), mostly to find the svn command in the codex again and then a few seconds to run it and a few seconds in hitting the “database upgrade” page on the site before things were all done.

]]>
http://2718.us/blog/2008/04/25/wordpress-251/feed/ 0
The SECRET_KEY in WordPress http://2718.us/blog/2008/04/24/the-secret_key-in-wordpress/ http://2718.us/blog/2008/04/24/the-secret_key-in-wordpress/#comments Thu, 24 Apr 2008 22:20:59 +0000 2718.us http://2718.us/blog/?p=27 I’ve gotten into the habit of actually reading the various blogs to which there are links on my WordPress dashboard and I saw this today from boren.nu:

To make cookies secure against attacks where someone has managed to get into your database through an SQL injection exploit or other means, WordPress 2.5 introduced a user-definable constant called SECRET_KEY. If you look at the sample wp-config.php shipped with 2.5, you’ll see these lines.

// Change SECRET_KEY to a unique phrase. You won’t have to remember it later,
// so make it long and complicated. You can visit https://www.grc.com/passwords
.htm
// to get a phrase generated for you, or just make something up.
define(’SECRET_KEY’, ‘put your unique phrase here’); // Change this to a unique phrase

If you upgraded from a previous version of WordPress you probably won’t have these lines in your wp-config.php.

That last bit is, of course, the critical thing for me and had me going back and inserting SECRET_KEYs into all my older/upgraded WordPress installs.  Just remember that if you’re integrating with bbPress, you have to match the SECRET_KEYs in wp-config.php and bb-config.php.

]]>
http://2718.us/blog/2008/04/24/the-secret_key-in-wordpress/feed/ 2