Okay, not the thing I feared the most, but one thing I was concerned would happen: WordPress was hacked.
Some time during the last week of February, someone hacked the most current version of WordPress (2.1.1). WordPress has the details:
It was determined that a cracker had gained user-level access to one of the servers that powers wordpress.org, and had used that access to modify the download file. We have locked down that server for further forensics, but at this time it appears that the 2.1.1 download was the only thing touched by the attack. They modified two files in WP to include code that would allow for remote PHP execution.
Which means that blogs using the latest version of WordPress were vulnerable.
Including this little blog.
So, when I found out about the WordPress vulnerability, I had to update.
And with the issues I've had with my computer recently, it's not been easy to update.
You see, with Network Solutions hosting, I have to upload WordPress to the site and manually perform the update. With Dreamhost -- where this little blog used to reside -- it was really easy to update: just click a link and it was done.
Updating is a pain, to be sure. But it needed to be done.
And all because someone hacked WordPress' servers.
I'm not about to call for the death penalty for hackers. But beating with a large stick sounds in order.