.. i believe that article/column is completely ignorant -- if you want to wait for just one full service pack, then all you will be patching is an 0wned machine ..

maybe this could be easier: have updates/fixes for known security flaws available for d/l as soon as possible.. have a running list of new patches/fixes .. and then when they put out a new service pack for bugfixes/etc .. they can include the security fixes too (for lazy admins.. seems the author would prefer this option) -- but at least this way security fixes are available asap (but, as we all know, m$ just gives us fixes when they see fit)

another topic: have you ever pondered on how much the government works with microsoft/security vendors ? .. say a security flaw is found.. does the government have the ability to keep this underwraps for a period of 'monitoring' time (to see who else has discovered these flaws.. and who is using them actively on the internet) ? and then we see the vuln go up on cert/bugtrack ( .. then two months later microsoft releases sp2 - which is a few major bugfixes, and oh ya, we added a fix for the security vuln that was found 2 months ago)

- take a minute to think about what you are writing about

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/112/16727#16727