Comments on: WordPress 2.0.6: CRITICAL Security Release http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/ Web Technology and Real Life Merge Thu, 18 Mar 2010 02:16:34 +0000 hourly 1 http://wordpress.org/?v=3.0-alpha By: Aaron Brazell http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45951 Aaron Brazell Sun, 07 Jan 2007 06:48:10 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45951 My upgrade script <a href="http://www.technosailor.com/how-we-mass-upgrade-blogs/">is posted</a>. My upgrade script is posted.

]]> By: Aaron Brazell http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45904 Aaron Brazell Sun, 07 Jan 2007 03:11:57 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45904 I did the upgrade again with the bugfix that failed to make it in to the original 2.0.6 and this time the upgrade took 6 minutes and 23 seconds. Oh well, you can't win 'em all. :) I did the upgrade again with the bugfix that failed to make it in to the original 2.0.6 and this time the upgrade took 6 minutes and 23 seconds. Oh well, you can’t win ‘em all. :)

]]> By: Aaron Brazell http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45760 Aaron Brazell Sat, 06 Jan 2007 14:38:14 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45760 Hi Matt! Perhaps I'll post the script I use to do this though it's nothing uber-magical. We have a central database that houses all kinds of info about our blogs and bloggers and so I get a list of URLs from it, do some matching against /etc/passwd where the comment field has the the domain and if it's a match, I copy in from a depot with the current "image" of WordPress. I then use cURL to run the upgrade script and it's off to the races. Additional bells and whistles include an array for plugins to remove and blogs that shouldn't be upgraded (such as mine since I run 2.1). Hi Matt!

Perhaps I’ll post the script I use to do this though it’s nothing uber-magical. We have a central database that houses all kinds of info about our blogs and bloggers and so I get a list of URLs from it, do some matching against /etc/passwd where the comment field has the the domain and if it’s a match, I copy in from a depot with the current “image” of WordPress. I then use cURL to run the upgrade script and it’s off to the races.

Additional bells and whistles include an array for plugins to remove and blogs that shouldn’t be upgraded (such as mine since I run 2.1).

]]> By: Matt http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45713 Matt Sat, 06 Jan 2007 07:58:27 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45713 "It took me 4 minutes and 15 seconds to upgrade all 181 blogs currently active or being prepped in our network." Whoa! That's sweet. “It took me 4 minutes and 15 seconds to upgrade all 181 blogs currently active or being prepped in our network.”

Whoa! That’s sweet.

]]> By: How to Handle Security Flaws » Technology, Blogging and New Media http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45665 How to Handle Security Flaws » Technology, Blogging and New Media Sat, 06 Jan 2007 03:04:32 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45665 [...] Yesterday, over at Blog Herald, the new management demonstrated the entirely wrong way of handling security flaws. (The flaw I detailed here) [...] [...] Yesterday, over at Blog Herald, the new management demonstrated the entirely wrong way of handling security flaws. (The flaw I detailed here) [...]

]]> By: Aaron Brazell http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45659 Aaron Brazell Sat, 06 Jan 2007 02:24:01 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45659 Hart: Before we can talk, all your blogs would have to be on the same version. Then my tips could be of use. ;) Hart: Before we can talk, all your blogs would have to be on the same version. Then my tips could be of use. ;)

]]> By: Brian Layman http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45635 Brian Layman Sat, 06 Jan 2007 00:37:32 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45635 Yeah, the plug in world has become soooo much better since 1.5 days but still there are some that require you to edit the core WP code. In that sort of a situation, scripts and automation aren't that helpful unless you also script the process of updating editing the files too, and THAT's tricky to do in a version generic way. The one good thing is that you won't have to do a multi step upgrade. Every WordPress release is a cumulative upgrade. They've really done a great job in this area... Yeah, the plug in world has become soooo much better since 1.5 days but still there are some that require you to edit the core WP code.

In that sort of a situation, scripts and automation aren’t that helpful unless you also script the process of updating editing the files too, and THAT’s tricky to do in a version generic way.

The one good thing is that you won’t have to do a multi step upgrade. Every WordPress release is a cumulative upgrade. They’ve really done a great job in this area…

]]> By: HART (1-800-HART) http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45632 HART (1-800-HART) Sat, 06 Jan 2007 00:22:03 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45632 uh .. thanks Brian, but I think I'll pass on your offer to delete some of my older archives :) I believe you! For now = I do plan to upgrade the older versions .. I have to figure this out once they are all on the same playing level for future upgrades. I also have many plugins activated that some need upgrading to. uh .. thanks Brian, but I think I’ll pass on your offer to delete some of my older archives :) I believe you!

For now = I do plan to upgrade the older versions .. I have to figure this out once they are all on the same playing level for future upgrades. I also have many plugins activated that some need upgrading to.

]]> By: Brian Layman http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45624 Brian Layman Fri, 05 Jan 2007 23:43:28 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45624 Thanks for the link Aaron and thanks for looking over the script! I really appreciate it. Hart: Yeah, I tried to make that post daunting. I guess it worked! The final process isn't bad. You download the script, edit the top lines to specify your 42 blog directories and their urls, and from then on it will take seconds to go to go through any upgrade. I just didn't want to release it, and suddenly have 200 people coming after me for wiping their blogs. Heck, I didn't want to have one person come after me... So I needed confident guru's like Aaron to put their toes in water first. In any case, you REALLY want to update those older sites ASAP. I could demonstrate why, for you, by deleting a few of your posts for you if you like and you wouldn't even be able to tell how it happenned. ;) Please see my <a href="http://www.thecodecave.com/article249">A few words about the RISKS of WordPress 1.2, 1.5, 2.0 or anything less than 2.0.4</a> post if you'd like a much more wordy recommendation... The holes plugged by 2.0.6 are just as bad. Thanks for the link Aaron and thanks for looking over the script! I really appreciate it.

Hart: Yeah, I tried to make that post daunting. I guess it worked! The final process isn’t bad. You download the script, edit the top lines to specify your 42 blog directories and their urls, and from then on it will take seconds to go to go through any upgrade. I just didn’t want to release it, and suddenly have 200 people coming after me for wiping their blogs. Heck, I didn’t want to have one person come after me… So I needed confident guru’s like Aaron to put their toes in water first.

In any case, you REALLY want to update those older sites ASAP. I could demonstrate why, for you, by deleting a few of your posts for you if you like and you wouldn’t even be able to tell how it happenned. ;) Please see my A few words about the RISKS of WordPress 1.2, 1.5, 2.0 or anything less than 2.0.4 post if you’d like a much more wordy recommendation… The holes plugged by 2.0.6 are just as bad.

]]> By: HART (1-800-HART) http://technosailor.com/2007/01/05/wordpress-206-critical-security-release/comment-page-1/#comment-45618 HART (1-800-HART) Fri, 05 Jan 2007 22:59:41 +0000 http://www.technosailor.com/wordpress-206-critical-security-release/#comment-45618 Whoooooooooooosh. Over my head. Do you have any plans to write a more detailed tutorial how 181 blogs in 4 minutes 15 seconds can be ugraded? I know I would grateful :) I still have a few blogs at 1.5.2 version .. the rest range between 2.0.2 and 2.0.5. I've got 42 sites .. which has been taunting me just to wait until 2.1 version comes out of beta. Whoooooooooooosh. Over my head. Do you have any plans to write a more detailed tutorial how 181 blogs in 4 minutes 15 seconds can be ugraded? I know I would grateful :)

I still have a few blogs at 1.5.2 version .. the rest range between 2.0.2 and 2.0.5. I’ve got 42 sites .. which has been taunting me just to wait until 2.1 version comes out of beta.

]]>