The Costs of Patching
prestidigital writes "vnunet has a brief but interesting article in which Craig Fiebig, general manager of Microsoft's security business unit, is quoted as saying "In dollar terms, patching is the most expensive security measures and keeping your antivirus descriptions up to date is the least." That seems like an important statement coming from a company who's patches are possibly responsible for 45% of traffic on some networks."
Rather than throwing away an otherwise perfectly good pair of pants, patches have allowed me to fix them and extend their life. In some cases, patches can even be fashionable. Sewing is a great skill that all geeks should learn.
This document was part of an interesting debate over the last year and a half between MS and Novell over whose product was more buggy (measured in terms of number of patches.)
(Google cache version in html.)
Why do I h8 apple?
Pff.. you lamers with your fancy-pants Windows or your free Linux or *BSDs are all clueless. I haven't patched my Apple ][+'s DOS3.3 for 20 years and it still has yet to be 0wned.
Trolling is a art,
Try to enter today's date in Appleworks.
And maybe I should spend more time proofreading my own posts so that I don't mangle words so much!
There's a growing sense that even if The Future comes,
most of us won't be able to afford it.
-- Lemmy
Yeah and? Today is Thursday, May 1 10003.
Trolling is a art,
responsible for 45% of traffic
But spam is responsible for, what was it Taco, 60% of traffic on networks?
I'm at 105% utilization already!
Didn't you see that the article was about Microsoft? I'm sure there is at least SOME overlap in the spam/patch metrics.
Man, I can attest to this... patches... especially ones that screw up systems not only cost time/money/bandwidth but they cost HAIR.. yes thats right... admins lose their hair b/c of the stress this makes them go through..... ::looks in the mirror::
arrhhggghh..
Hey, I know, maybe Microsoft could do these new things called DESIGN REVIEW and CODE REVIEW, rather than trying to test out bugs.
You must have missed it. After Bill declared a new focus on security, they did a code review -- one month of review for twenty years of code. The next code review is scheduled for 2022. :)