D
djs
http://news.zdnet.co.uk/0,39020330,39115732,00.htm
"A flaw in Windows Update -- Microsoft's online tool that lets customers
update their operating system with patches and fixes -- enabled the
MSBlast worm to infect computers that appeared to have already been
patched, according to a security expert."
"Windows Update works by adding an entry into the system registry every
time it installs a patch. When users log on to the update tool, it scans
their registry and offers them list of patches that have not yet been
installed. Cooper said that this mechanism was found to be flawed."
"'We found that people had got the registry key for the patch, but not
the file,' he said, explaining that the error could be triggered by a
number of reasons -- from an incomplete installation to a lack of system
resources."
*****
What was all that blather about how "easy" it is to make sure you're
patched?
Ah, don't worry, Ed--I'm sure you can find an illogical defense of
Microsoft again, and pin this on their poor users like everything else.
My advice would be to start by claiming that this was an isolated
incident. Yeah, I think I'd go that route. I'd try to play down the
fact that a U.S. Army server was one of the systems this problem
occurred on. That might look too bad. Another thing you might try is
claiming that they "didn't turn their AV off", or some other desperate
move (SHHHHHHHH! No, it doesn't matter that Microsoft doesn't recommend
doing that). Hey, I'm trying to think outside the box here for ya,
buddy.
Sorry for having lied about that "last tug" thing.
"A flaw in Windows Update -- Microsoft's online tool that lets customers
update their operating system with patches and fixes -- enabled the
MSBlast worm to infect computers that appeared to have already been
patched, according to a security expert."
"Windows Update works by adding an entry into the system registry every
time it installs a patch. When users log on to the update tool, it scans
their registry and offers them list of patches that have not yet been
installed. Cooper said that this mechanism was found to be flawed."
"'We found that people had got the registry key for the patch, but not
the file,' he said, explaining that the error could be triggered by a
number of reasons -- from an incomplete installation to a lack of system
resources."
*****
What was all that blather about how "easy" it is to make sure you're
patched?
Ah, don't worry, Ed--I'm sure you can find an illogical defense of
Microsoft again, and pin this on their poor users like everything else.
My advice would be to start by claiming that this was an isolated
incident. Yeah, I think I'd go that route. I'd try to play down the
fact that a U.S. Army server was one of the systems this problem
occurred on. That might look too bad. Another thing you might try is
claiming that they "didn't turn their AV off", or some other desperate
move (SHHHHHHHH! No, it doesn't matter that Microsoft doesn't recommend
doing that). Hey, I'm trying to think outside the box here for ya,
buddy.
Sorry for having lied about that "last tug" thing.