Microsoft today announced that it will be changing the way it handles patching. Basically, work is being done to beef up the Windows security perimeter. The majority of this work will be released soon in Windows XP Service Pack 2. I plan to detail these changes over the next few days, but for now, here's how it affects PatchDayReview:
- Microsoft is changing their patching from weekly to monthly unless critical flaws are discovered). That means that this site will not be as demanding on my daily schedule.
- Microsoft will be devoting more of their efforts to integrated security, and I will do my best to keep you informed in the same clear and simple terms that I use for my patches.
As I said, I will be detailing more of these changes within the next few days. For now, here are some links to this news on the web:
News.com
NewScientist.com
Your Friend In Security,
Robert “Patch” McLaws
Well, someone's done it! They've blown the cover on Microsoft's insistence that all information coming out of them has to be as complicated and un-user friendly as possible.
...This is good stuff, kids. Visit, Use, DO!
[Jason Ketterman]
Microsoft issues patches for vulnerabilities in its software at the rate of about one a week - the 40 weeks of 2003 have seen exactly the same number of advisories though some weeks have been more "patchy" than others - but the advisories are so jargon -heavy that few non-technical users can understand them.
This is the reasoning behind PatchDayReview, a site set up by Interscape Technologies, says its president and chief software architect, Robert McLaws.
[TheAge.com.au]
I just found a great little
site (via
techno weenie). It is called patch day review, and it basically keeps you up to date with all the latest patches released, and their importance.
This is very useful for me, because after the last bug I disabled all ActiveX controls in
IE, so to goto WindowsUpdate I have to re-enable ActiveX first. Now I can see whats going on before messing with ActiveX. Also he gives nice little explanations!
[
CodeMonkeyX.net]