I decided to boycott my computer yesterday as I can't take how inane April 1 has become. It's probably nothing new, but it's really started to annoy me these last few years, so today the Security Week in Review comes to you +1 day.
Last week saw the end to the
Month of PHP Bugs. As a whole is was mostly unexciting. I'm not a fan of any month of "something" projects. I think they're just people pandering to the press, but it doesn't really seem to work. Every month of something project has pretty much just fizzled out at the end with nobody really noticing. I suspect if they really wanted to pimp themselves to the press, releasing thirty advisories at once to a mailing list would gain far more attention (please note I don't think this is a good idea either).
So I've come to a crossroads with this weekly column again. I'm wondering if listing last week's security updates is of use given there are other places once can find this information without much effort. I'm thinking it may be more worthwhile to just comment on the various updates and flaws that deserve comment. I find that the hardest thing about writing a blurb each week is how to keep it interesting. I'm not going to list any security updates in this week's column. If anyone likes seeing them here, please leave a comment, and I'll bring them back. Additionally, if there is something you like or dislike about what you see, I'd love to hear from you.
