(no subject)
May. 2nd, 2004 07:15 pmAs most of you know, earlier this year I sold my soul to Satan and went to work for Microsoft.
Today was hell.
Some little good for nothing fucker has released another virus, much like the Blaster worm. I swear if I ever meet anyone who claims responsibility for any of these I'm going to tear them limb from limb with my bare hands.
For those of you dealing with the virus, here are some links for your clients or yourselves.
http://www.microsoft.com/security/incident/sasser.asp and see if you're infected. If you're running a firewall and are up to date on your critical updates, you should be fine.
Removal tool: http://www.microsoft.com/downloads/details.aspx?FamilyId=76C6DE7E-1B6B-4 FC3-90D4-9FA42D14CC17&displaylang=en
Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;841720
Today was hell.
Some little good for nothing fucker has released another virus, much like the Blaster worm. I swear if I ever meet anyone who claims responsibility for any of these I'm going to tear them limb from limb with my bare hands.
For those of you dealing with the virus, here are some links for your clients or yourselves.
http://www.microsoft.com/security/incident/sasser.asp and see if you're infected. If you're running a firewall and are up to date on your critical updates, you should be fine.
Removal tool: http://www.microsoft.com/downloads/details.aspx?FamilyId=76C6DE7E-1B6B-4 FC3-90D4-9FA42D14CC17&displaylang=en
Microsoft Knowledge Base article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;841720
But wait, there is more
Date: 2004-05-02 04:31 pm (UTC)Re: But wait, there is more
Date: 2004-05-02 06:12 pm (UTC)no subject
Date: 2004-05-02 04:41 pm (UTC)I don't support those that release the virus. Since the company I IT for is a Microsoft shop it is a pain when these worms are released. But an even bigger pain is having to go through dozens of servers and hundreds of work stations to make sure they are all updated with patches M$ finally got around to releasing after ignoring the exploits for so long.
no subject
Date: 2004-05-02 06:13 pm (UTC)no subject
Date: 2004-05-02 07:30 pm (UTC)no subject
Date: 2004-05-02 05:58 pm (UTC)no subject
Date: 2004-05-02 06:15 pm (UTC)no subject
Date: 2004-05-02 07:55 pm (UTC)no subject
Date: 2004-05-02 09:44 pm (UTC)It hit us pretty hard that day.
Got my machine too. Luckily I'd isolated the fucker at home before I got to work, warned my reps and we were on top of it.
I'd worked out how to stop it, then eventually we had references for it.
I'm not looking forward to going to work tomorrow. Luckily I don't have to speak to the customers front line. Heh.
no subject
Date: 2004-05-02 09:47 pm (UTC)no subject
Date: 2004-05-03 08:02 pm (UTC)no subject
Date: 2004-05-03 12:07 pm (UTC)This is after countless emails about the subject from me, my supervisor, and the district support person on that very subject.
Thanks for the links though. I'll be sure to use them when it pops up here.
no subject
Date: 2004-05-03 08:00 pm (UTC)SUS took care of the workstations and we took care of the servers on the weekend. Our IDS has yet to catch Sasser on our network.
Thank you
Date: 2004-05-04 06:12 pm (UTC)Thank you.
Re: Thank you
Date: 2004-05-04 06:29 pm (UTC)