J
Jacka$$ Joe
Because I keep my computer up to date and have a good
firewall on my Windows XP Computer!
-Cheers!
firewall on my Windows XP Computer!
-Cheers!
Roger said:I agree. The patch that fixes this has been out for almost a month.
If people haven't downloaded it yet than they deserve to have every
virus in the internet. ANy computer with an internet connection
needs a good virus scanner and a firewall (even on a 56k dial-up),
and they need to be updated (once a week, at the very least).
Roger said:The patch has been out for quite some time. Yes, windows has more
holes than a swiss cheese at a firing squad, but if people don't have
enough sense to keep it up-to-date, the they deserve whatever
security exploit comes there way.
Jacka$$ Joe said:Because I keep my computer up to date and have a good
firewall on my Windows XP Computer!
kurttrail said:This patch hasn't even been out a month yet. And a lot a people also
got burned downloading flawed MS's patches recently too!
MS doesn't go looking for flaws, just waits till
others find them first, otherwise Windows Server 2003 wouldn't have
need to be patched for this too!
Apologize for MS, if that rocks your boat, but this buffer overrun has
been in Windows since NT4, and was released in MS's first OS that was
released under the banner of "Trustworthy Computing!"
Mike said:x-no-archive: yes
Kurttrail speaks the truth! Thank you for telling it like it is.
YES, you should keep on top of security updates. YES, you should run
AV utilities and firewalls. But NO, it's not the customer's fault
when hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
after hole after hole after hole after hole after hole after hole
comes up.
Jacka$$ Joe said:What's the matter...get nailed by this virus?...boo hoo
hoo :-(
Don't bitch at me - it's not my problem. If you can't
manage all your workstations, then get someone competent
to take your place!
And you manage HOW MANY WinNT/2K/XP workstations, idiot?
Have any idea what it's like to deal with one patch right after the
other, on an almost-daily basis?
T.G. Reaper said:Except in this particular case we're talking about a patch that was
issued almost a month ago.
If you're a month behind in updating the systems you're responsible
for, then you're incompetent, plain and simple. Quite frankly, I'd say
that appears to be the case.
Microsoft issued a patch, that successfully eliminates the
vulnerability, and doesn't break anything else. They provided the
patch, and an advisory, in plenty of time for all this to be easily
avoided. What exactly is it they were supposed to do beyond that?
EGMcCann said:Yeah, everyone should just put out software that's 100% perfect. Then
we'd be running...
um...
Nothing at all.
So that means that people deserve to get viruses?
Ron said:Nope.
But what it does mean is that if 50 million or so Windows users were
to suddenly switch to Linux there would be a flood of Linux viruses
and security exploits that would make the current problem look
minuscule by comparision.
kurttrail said:So that means that people deserve to get viruses?
Don said:Where the heck did you get that out of this post?
What a dumb question - seriously, are you still a pre-teen?
T.G. Reaper said:Except in this particular case we're talking about a patch that was
issued almost a month ago.
If you're a month behind in updating the systems you're responsible
for, then you're incompetent, plain and simple. Quite frankly, I'd say
that appears to be the case.
Microsoft issued a patch, that successfully eliminates the
vulnerability, and doesn't break anything else. They provided the
patch, and an advisory, in plenty of time for all this to be easily
avoided. What exactly is it they were supposed to do beyond that?
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.