Slashdot Mirror


Sasser Worm Disruption Growing

thebra writes "Yet another virus is causing problems with Internet Explorer. "Sasser, unlike a virus which travels through e-mails and attachments, spreads directly from the internet."A removal tool can be found here."

999 comments

  1. Yeah..you're telling me... by hookedup · · Score: 5, Interesting

    Here at work, none of our employees can connect to the VPN, hence nobody can get work done, hence I'm sitting here with my phone ringing off the goddamn hook.

    Capital punishment for worm writers!

    1. Re:Yeah..you're telling me... by VC · · Score: 1, Troll

      Capital punishment for monopolistic, insecure bloatware publishers.
      Or atleast a class action lawsuit..

      Anyone? Oh what everyone here uses linux anyway right? *snickers*

    2. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 5, Funny

      It's not fair. I sometimes wish I used windows.

      All the windows folks in the place are sat around talking and drinking coffee because everythings broken, but us unlucky users of openbsd servers and linux desktops are having to work hard as usual.

      It seems there are hidden benefits to choosing Microsoft products.

    3. Re:Yeah..you're telling me... by FrYGuY101 · · Score: 4, Insightful

      Yes. Because Linux IS inherently secure?

      Or maybe, just maybe, computers are inherently insecure?

      --
      "If we let things terrify us, life will not be worth living."

      - Seneca
    4. Re:Yeah..you're telling me... by Mysticalfruit · · Score: 4, Insightful

      More like capitalism punishment.

      If after all the bullshit that companies went through with Blaster, they didn't sit down, get a team of smart IT people together and implement solutions to stop worms, then they don't deserve customers business.

      Darwanism at work. Those who don't grow immune to the poison, die from it.

      --
      Yes Francis, the world has gone crazy.
    5. Re:Yeah..you're telling me... by AllUsernamesAreGone · · Score: 1

      Computers aren't inherantly insecure, people are. I propose the Bender Security Solution!

    6. Re:Yeah..you're telling me... by clifyt · · Score: 1

      Would you really punish someone for doing something as simple as what they have done?

      Capital punishment is for someone that breaks into a bank, shoots a few people and rapes a woman before taking off with the cash.

      This is a misdemeanor -- break into a candy store that someone left the door open, flip the lights a few times and tell the local kids that it would be funny to run to neighboring towns and repeat this process. It deserves a slap on the wrist.

      Trust me, I'm no happier about this worm than you are. I found out of 100 computers, 3 work stations were not set up for automatic updates -- the users always canceled when it wanted to update manually. Those 3 were infected and I got hit on Saturday and called out of a wedding. One of my former employees was in charge of making these all automatic updates earlier in the year (as well as changing the virus protection to daily updates instead of weekly -- noticed half were still updating weeking from this weekends audit).

      So I had my life interuupted for a bit because of this crap. Its not a big deal. I blame Microsoft more than I do the virus writters.

      Wheres my new powerbook?

    7. Re:Yeah..you're telling me... by hookedup · · Score: 1

      What I failed to mention, is these employees are police officers. At this time, they are all unable to connect to the VPN which allows them to view/enter reports, which in turn, does not allow them to their job, and in turn, puts the public at risk.

    8. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 1, Informative

      Maybe capital punishment for the IT support team that doesn't keep the PCs that they are responsible for patched would be more appropriate???

      The patch came out weeks ago... if you had applied it, you wouldn't be having problems.

      SUS server is free and actually works quite well.

    9. Re:Yeah..you're telling me... by kin_korn_karn · · Score: 2, Insightful

      Somehow I don't think they're going to ignore a guy mugging an old lady because they won't be able to write a report about it afterward.

    10. Re:Yeah..you're telling me... by hookedup · · Score: 1

      All our patches are up to date.
      We run a SUS server.
      All our definitions are up to date.
      Sadly.. it's the people in control of our VPN that are the incompetent ones.

    11. Re:Yeah..you're telling me... by Pig+Hogger · · Score: 0, Flamebait
      What I failed to mention, is these employees are police officers. At this time, they are all unable to connect to the VPN which allows them to view/enter reports, which in turn, does not allow them to their job, and in turn, puts the public at risk.
      Any police chief who supplies his force with inferior, useless tools deserves to be shot.
    12. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      If this worm would have nuked all attached drives, how many billions of dollars would have been lost? Or would it even be that high?

    13. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 5, Funny

      Typical *nix admin, thinking that posting on Slashdot is 'working hard as usual'.

    14. Re:Yeah..you're telling me... by Paulrothrock · · Score: 4, Funny

      Darwan: A large network in which selection determines node connectivity.

      --
      I'm in the hole of the broadband donut.
    15. Re:Yeah..you're telling me... by JWW · · Score: 4, Insightful

      I'm sorry, but even companies that aren't getting hit by this still paid the price.

      We ran around frantically patching every $#%@#^ windows box at the company after the patches came out. Installing patches wastes users time, administrators time, everyones time. I know it can be automated, but its still a pain and you have to check every system anyway.

      And whether or not you get a worm on your systems should not be the deciding factor of whether you deserve the customers business. Are you really saying that a record company that effectively blocked this worm deserves my business? Please don't start an oftopic rant about the RIAA, its just an example.

    16. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0
      get a team of smart IT people together

      First, you'd have to find smart IT people. They exist, but are preciously few and far between.

    17. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0
      Please don't start an oftopic rant about the RIAA, its just an example.

      Offtopic, I know, but the RIAA really are a bunch of dinosaurs that deserve to perish after systematically screwing both their customers and artists for decades.

    18. Re:Yeah..you're telling me... by halaloszto · · Score: 4, Insightful

      All this really resembles me to the Y2K problem.

      The difference is, that we could sit down, make a plan, inspect all PCs, have stickers for OK machines, etc.

      And there were far less problems than with an average worm nowadays. Imagine if the Y2K problem would have been as big as a usual worm hit. (several middle to large companies affected for a couple of days)

      Vajk

    19. Re:Yeah..you're telling me... by TheSpoom · · Score: 2, Interesting

      Yes, but customers don't know that. Witness a news story I heard about the Sasser worm after a day of doing tech support for it... it ended with "...a patch is now available to protect against the worm from Microsoft." Customers think "oooh, thanks Microsoft!", not knowing that it was a huge hole in their product that allowed the worm in the first place. Subtle misdirection and Microsoft didn't even have to pay for it. Thanks, CBC!

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    20. Re:Yeah..you're telling me... by ultrasound · · Score: 0, Offtopic

      And reading /. instead of answering it?

    21. Re:Yeah..you're telling me... by teh*fink · · Score: 2, Interesting

      Somehow I don't think they're going to ignore a guy mugging an old lady because they won't be able to write a report about it afterward.

      or vice versa

      --
      "I DARE you to make less sense!"
    22. Re:Yeah..you're telling me... by Mysticalfruit · · Score: 2, Insightful

      I know it's a pain, but the question is.

      Is the one time pain of deploying an automated patching system greater or less than the 3 or 4 times a year that even if your networkd doesn't come to a grinding halt, you've got to spend 4 hours going cube to cube and deploying patches.

      Our solution was to deploy a centeralized controlled distributed firewall system inside our internal network. The best defense is a good offense.

      This allows us to from C&C (command and control) to proactively block ports and sample traffic from any machine on any subnet.

      Hense, even if sasser were to come in from some laptop and that person plugged their laptop into our general purpose subnet, 99 percent of the machines on all the subnet have the offending incoming ports blocked and as soon as it sees traffic for that port it'll send me a report.

      Also, this combined with an agent that lets us push out patches and auto updating virus software allows us to stay ahead of the curve.

      --
      Yes Francis, the world has gone crazy.
    23. Re:Yeah..you're telling me... by Smidge204 · · Score: 4, Informative

      No, but if the cops can't run a plate or license number check during a routine traffic stop, you won't know if there's a warrent out on the guy for a series of violent crimes.

      Just an example. The ability for the police to do thier job in any capacity relies on the ability to get and share information. It's pretty rare that the cop actually witnesses the mugging, but a witness description, cross referenced with other reports from the head office, might lead to the ID of a suspect.
      =Smidge=

    24. Re:Yeah..you're telling me... by Enucite · · Score: 1

      Are you really saying that a record company that effectively blocked this worm deserves my business?

      Well, yeah. If they don't care enough to keep their business up and running, what makes you think they're going to put any more than the bare minimum into the product they produce?

      Yeah, I'm sure there are some exceptions, but he has a point. If they don't care enough to make sure they can do business, they don't deserve to do business.

    25. Re:Yeah..you're telling me... by kin_korn_karn · · Score: 1

      Both of those are good points. Still, they can radio in for plate checks and other cross-referencing. That's what they did before the advent of wireless networks in the cars.

    26. Re:Yeah..you're telling me... by surprise_audit · · Score: 1

      Yeah, but if the precint network is fucked by the same vulnerability, they still don't get the data they need...

    27. Re:Yeah..you're telling me... by vortexlrd · · Score: 0

      Similar thing with smoking, it has at least one "benefit" in the workplace: people get to go outside a couple of times per day "because they have to".

    28. Re:Yeah..you're telling me... by GMFTatsujin · · Score: 1

      protect against the worm from Microsoft.

      I want to see this phrase employed more often. It's good advice.

    29. Re:Yeah..you're telling me... by Starlet+Monroe · · Score: 2, Funny

      Any police chief who supplies his force with inferior, useless tools deserves to be shot... ...with a weapon borrowed from a different precinct.

      --
      ++
    30. Re:Yeah..you're telling me... by phasm42 · · Score: 1

      This is a slippery slope... stretch the chain of events out, and maybe that cop that pulled you over for speeding was delayed just long enough that he wasn't able to respond in time to a home invasion and now the murder is blamed on you. I think that the worm deserves more than a misdemeanor, but not capital punishment.

      --
      "No one likes working in a hamster wheel, and your shop smells of cedar shavings from here." - TaleSpinner
    31. Re:Yeah..you're telling me... by DGregory · · Score: 1

      Odd but we're a 100% microsoft shop and our firewall blocked out the worm from coming in. Only had a problem on one laptop that had left the office the previous evening.

      I say yell at the network admin who should've had those ports closed!

    32. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      Still a bit better than MS admins, who think that posting misinformed bullshit on Slashdot is 'working hard as usual'...

    33. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      DarWAN

    34. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0
      Typical *nix admin, thinking that posting on Slashdot is 'working hard as usual'.

      Never underestimate the difficulty of bypassing logic and drinking the Kool-Aid every day.
      Also, its not easy coming up with new and different ways of saying "Mikro$l0th W1nd0ze is teh suxx0rz!!!!11"

    35. Re:Yeah..you're telling me... by System.out.println() · · Score: 1

      Darwanism at work.

      funny you should mention the kernel that runs Mac OS X.... ;)

    36. Re:Yeah..you're telling me... by jrockway · · Score: 1

      Well the police department bought the wrong product. They fucked up. They could have read some reports and decided that *NIX would have been a better choice.

      This is the fault of people who buy M$ products. M$ has every right to make a shitty product. Nobody's holding a gun to your head forcing you to buy it (and if you say "well I need interoperability" i say that OO.org works fine AND i also say that that's too bad. which do you want? stability or more apps?)

      --
      My other car is first.
    37. Re:Yeah..you're telling me... by System.out.println() · · Score: 2, Funny

      Some of us use Mac OS X.

      ....

      ....

      ....you insensitive clod! XD

    38. Re:Yeah..you're telling me... by cayenne8 · · Score: 1
      "No, but if the cops can't run a plate or license number check during a routine traffic stop, you won't know if there's a warrent out on the guy for a series of violent crimes....It's pretty rare that the cop actually witnesses the mugging..."

      Well, maybe if the cops weren't out trying to "collect money" by 'routine traffic stops'...speed traps, etc...and WERE driving around neighborhoods, especially the more crime ridden ones...they would observe the muggings, murders, drug deals and rapes...or at least their presence would help prevent them.

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    39. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      Never underestimate the difficulty of bypassing logic and drinking the Kool-Aid every day.

      If you're talking about living and working in the US, then I'm in total agreement.

      Those of you not in the US, we have the shiniest, most efficient treadmills on the planet. They suck the energy from your body faster than anywhere else. Before you know it, you'll be dead. And you'll die happy, believing that your children might have the life you never did.

    40. Re:Yeah..you're telling me... by System.out.println() · · Score: 2, Funny

      Wheres my new powerbook?

      Probably still waiting to come back from getting fixed. :P

    41. Re:Yeah..you're telling me... by Shimmer · · Score: 1

      Our solution was to deploy a centeralized controlled distributed firewall system inside our internal network.

      Aren't "centralized" and "distributed" opposites?

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    42. Re:Yeah..you're telling me... by Mark+Bainter · · Score: 1
      The difference is, that we could sit down, make a plan, inspect all PCs, have stickers for OK machines, etc.

      Oooh, that's a good one. I just about fell out of my chair laughing at that one. Can't you just imagine a windows PC with a sticker for every time it had to have a patch applied to the OS? That's hilarious.

      Sadly, I don't think it's a feasible concept. The whole reason we have patch rollout mechanisms is so that we don't have to go to /every/ pc to do the patch update. This would sorta defeat the purpose. And the stickers would only be amusing, since the tools are out there to do checks on your local net for patchlevels. (even free ones).

      However, I still found your post hilarious. If I had mod points I'd mod you up funny.

      --
      "No nation could preserve its freedom in the midst of continual warfare."
      --James Madison
    43. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      30 years ago cops couldn't instantly run plates and we did just fine back then. Don't give me that bullshit.

    44. Re:Yeah..you're telling me... by psyberjedi · · Score: 1

      ... and now, as the head samurai of my clan, i kneel before you, sword in hand, to commit seppuku and atone for the loss of my honor at the ignorant hand of my master ...

      for i have knelt before her and announced the coming of the Sasser threat, and from my master's lips the response ..."huh? we can not have any server downtime. no matter what... "

      both our preparation and our systems are woefully inadequate. to the gods of /. i beg forgiveness.

      --
      He who confuses his religion with his science knows neither.
    45. Re:Yeah..you're telling me... by bl8n8r · · Score: 1

      > Capital punishment for worm writers!

      Capital punishment for those run^H^H^H not keeping up with win^H^H^H OS patches!

      Wake up people. If you're 700 1337 to figure out how to protect/secure your box(es), then unplug them and go back to using dial-up. The rest of us need the bandwidth for pr0n and UT.

      --
      boycott slashdot February 10th - 17th check out: altSlashdot.org
    46. Re:Yeah..you're telling me... by KrisCowboy · · Score: 1

      Same here. But the hidden benifits of Micro$oft products come with a cost. I use windows for an average of one hour per day and 15 minutes of it goes to updating Norton and "protecting my PC against viruses". Crap. If Microsoft builds their own anti-virus, Gates can get much richer. Oh yeah, you got to buy the anti-virus seperately at a mind-blowing price, but hey, the virus comes for free!!!

    47. Re:Yeah..you're telling me... by metamatic · · Score: 1

      Naah, the VPN was down, so the fact that I don't run Windows didn't help.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    48. Re:Yeah..you're telling me... by Mysticalfruit · · Score: 1

      I suppose they are... let me clarify...

      Each PC has it's own piece of firewall software running on it.

      All those individual firewalls feed their info into a central console.

      That console gives an overview of the activity and does some trend analysis.

      So, it's a centerally managed distributed system.

      --
      Yes Francis, the world has gone crazy.
    49. Re:Yeah..you're telling me... by CmdrGravy · · Score: 1

      If this kind of problem is putting the public at risk then shouldn't they have an alternative backup system in place which can function independently of any technology likely to suffer from outages ?

    50. Re:Yeah..you're telling me... by Anonym0us+Cow+Herd · · Score: 4, Funny

      Still a bit better than MS admins, who think that posting misinformed bullshit on Slashdot is 'working hard as usual'...

      It may actually be working hard if one is being paid to post misinformed bovine feces on slashdot.

      --
      The price of freedom is eternal litigation.
    51. Re:Yeah..you're telling me... by Anonym0us+Cow+Herd · · Score: 1

      Typical *nix admin, thinking that posting on Slashdot is 'working hard as usual'.

      Maybe the *nix admin's server isn't broken.

      --
      The price of freedom is eternal litigation.
    52. Re:Yeah..you're telling me... by Doesn't_Comment_Code · · Score: 1

      Capital punishment for worm writers!

      You're not far off base there. While it would be difficult to convince a jury beyond a reasonable doubt that someone was responsible for writing a virus, it wouldn't be hard to fit the punishment to the crime.

      Among the few crimes that warrant death are murder and treason. Considering how much infrastructure is computer dependant, it isn't hard to beleive that devastating worms cause death and degrade national security. People die indirectly from power outages and similar semi-natural disasters. If someone had purposely cut the power, I think you could make a case that whoever cut the power was responsible for the murder of anyone who died as a result. The worm/virus issue is no different.

      --

      Slashdot Syndrome: the sudden, extreme urge to correct someone in order to validate one's self.
    53. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      This is why I like my MAc Os-X. The only reason I would use a WinBlows system, would be to use it as a honeypot. So I stick an unpatched version on an Open Commercial T1 line, sit back and say "Come on in...." Said the spyder to the fly... hoping that some scanner will byte the bait.... Then, once infected I sniff the shit out of it, grabbing the TCP protocols, then analysing the captured packets to write some snort rulz to detect it... BRING IT ON!!!! I have yet to get a nybble...

    54. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 2, Informative
      Some of us use Mac OS X.
      Better get QuickTime and iTunes patched then:

      Apple QuickTime (QuickTime.qts) Heap Overflow

      :o)
    55. Re:Yeah..you're telling me... by RichardX · · Score: 1, Insightful

      Capital punishment for anyone who hasn't already installed the windows update which closes the security hole and has been avaliable for sodding ages

      --
      Curiosity was framed. Ignorance killed the cat.
    56. Re:Yeah..you're telling me... by JWW · · Score: 1

      Nice sounding setup.

      Centrally managed distributed systems can be great at providing secure configurations, without sacrificing the performance of systems by running them centrally from distributed sites.

      Could you convince corporate IT at my company why this is a good thing, they've got it backwards. ;-)

    57. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      Um, the parent was referring to a Y2K patching strategy. In that case there would be, lemme think, one sticker each. But I'm glad your misinterpretation brought you such amusement.

    58. Re:Yeah..you're telling me... by Snaller · · Score: 1

      Capital punishment for worm writers!

      Capital punishment for lazy programmers - how many of them are bad? 90% ? How often do they NOT check return values to see if they actually allocated something, check bounds values to see if this piece of data actually can find in this buffer etc. The amount of shit that has happned because some idiot lame programmer didn't bother to check the size of his buffer is incredible.

      --
      If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
    59. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      Witness a news story I heard about the Sasser worm after a day of doing tech support for it... it ended with "...a patch is now available to protect against the worm from Microsoft."

      Maybe news orgs should be saying the truth... "A patch has been available for a few weeks, you lazy ass network admins".

      I run SUS on my LAN for the few Windows workstations I need to keep updated. Between SUS, SMS, Automatic Updates, and Windows Update, there should be almost no reason why people don't have their systems patched already.

      The only reason I can think of is either A) Patches must be tested with applications in a corporate environment, or B) Invalid Product Keys (even though I know friends who use automatic updates with their pirated copy of XP all the time).

    60. Re:Yeah..you're telling me... by Dr+Caleb · · Score: 2, Interesting
      Strange this in the logs for my firewall I keep getting "portsentry[]: attackalert: connect from host slashdot.org/66.35.250.150 to TCP port 1080".

      Several times during the last couple days. Seems someone at Slashdot hasn't patched their two year old RPC hole.

      And recent patches for XP actually break SSL connections - so patching right away isn't always the best thing to do.

      --
      "History doesn't repeat itself, but it does rhyme." Mark Twain
    61. Re:Yeah..you're telling me... by fire-eyes · · Score: 1

      I've some advice for you.

      Set up a 2003 terminal server.

      Investigate Linux thin clients which run in as little as 16MB ram. Of course, no hard drives needed, no cdrom, no floppy. These are pulled down from the newtork from a TFTP server. They connect to the terminal server.

      Think of how much time will be saved.

      I recommend PXES for the thin clients.

      Do investigate this, if we hadn't done it, we would have had to spend thousands on newer machines to even run windows, and a few more people to even begin to deal with maintaining them.

      --
      -- Note: If you don't agree with me, don't bother replying. I won't read it.
    62. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      Dude, I think it is time for a vacation...a long one.

    63. Re:Yeah..you're telling me... by jonadab · · Score: 1

      > Aren't "centralized" and "distributed" opposites?

      Well, that just depends how much holistic synergy you've got. HTH.HAND.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    64. Re:Yeah..you're telling me... by Tony-A · · Score: 1

      Typical *nix admin, thinking that posting on Slashdot is 'working hard as usual'.

      Actually not far from the truth. Once set up, *nix tends to pretty much take care of itself. I don't think Microsoft has factored this into their TCO studies.

    65. Re:Yeah..you're telling me... by Anonymous Coward · · Score: 0

      I didn't know the OSX kernel was called 'darwanism' or even 'darwan'.

    66. Re:Yeah..you're telling me... by halaloszto · · Score: 1

      You are right, stickers would be a pain. I just wanted to show, that if a case is taken seriously, (even by management) a workable solution can be implemented, and the catastrophe simply does not happen. I still see a huge contrast between the way companies handlet the y2k issue and are handling the current worm issues. There were news about the worm on saturday, still i have not heard of any company, that would have pulled the IT staff in the office for sunday to prepare for the workday. vajk

    67. Re:Yeah..you're telling me... by msborg · · Score: 1

      People who still choose to smoke today, knowing full well the deadly qualities of the product, have no one but themselves to blame when they get lung cancer.

      People who still choose to use Windows to run their businesses, knowing full well the security track record of Microsoft, have no one but themselves to blame when they get the latest virus/worm infecting their systems.

    68. Re:Yeah..you're telling me... by hurtta · · Score: 1
      Strange this in the logs for my firewall I keep getting "portsentry[]: attackalert: connect from host slashdot.org/66.35.250.150 to TCP port 1080".

      What is source port?
      If source port looks like 80, then your firewall is just blocking some return packed from your http connection, when you surf on slashdot.org. It is just 'mistaken' direction of connection.

  2. Another removal tool by BlackHawk-666 · · Score: 2, Funny

    Can be found here.

    --
    All those moments will be lost in time, like tears in rain.
    1. Re:Another removal tool by BlackHawk-666 · · Score: 3, Informative

      Oh stupid me for typing the wrong slashes...try here instead. Oh well, a dose of humiliation before your peers is good for the humility gland.

      --
      All those moments will be lost in time, like tears in rain.
    2. Re:Another removal tool by Anonymous Coward · · Score: 0

      Idiot. Mozilla does not have any effect on the LSASS. What, do you just read the category icons and not the stories?

    3. Re:Another removal tool by azzy · · Score: 1, Funny

      Sure sure.. it was just deliberate to get /two/ posts modded funny as opposed to one!!

      </sourgrapes>

    4. Re:Another removal tool by Anonymous Coward · · Score: 0

      BlackHawk down.

    5. Re:Another removal tool by Anonymous Coward · · Score: 0

      You used backslashes? I guess that goes to show *you're* still on Windows!

    6. Re:Another removal tool by Geoffreyerffoeg · · Score: 1

      Or maybe he programs in C, C++, Java, PHP, etc.

    7. Re:Another removal tool by Anonymous Coward · · Score: 0

      Hey!! Your "removal tool" deleted my hard drive! NOW how am I supposed to log into AOL to surf for kiddie porn?!

  3. YAME by SpaceLifeForm · · Score: 0, Funny

    Yet Another Microsoft Exploit.

    --
    You are being MICROattacked, from various angles, in a SOFT manner.
    1. Re:YAME by Ymiris · · Score: 1

      How in the hell is that a funny post?!?! He made a comment that has been made at least a million other times on slashdot. I would Mod Troll, give me my damn mod points :)

      --
      **It runs through my veins like radioactive rubber pants! Do not deny my veins!**
    2. Re:YAME by Anonymous Coward · · Score: 0

      It's not just "another" exploit. Since this one records the successful infections (In C:\Win.log), it's creating a ready made P2P network for launching a much nastier attack.

      A worm which piggy-backs Sasser doesn't need to search for other infected peers to spread to - there's a handy list of them sitting there...

    3. Re:YAME by chris_mahan · · Score: 1

      Note that the funniest things in life are the ones that repeat over and over, no matter what you do to try to fix them.

      I think it's superior humor in view of the focus on security at MS in the past 2 years (has it been that long already?).

      Also, it is obvious in the posting that this is not new. Yet Another means there has been umpteeth before...

      --

      "Piter, too, is dead."

  4. Re:Windows only by mahdi13 · · Score: 1
    What does this tell us about MSFT products?
    That it must suck to be running Windows?
    --
    "Some things have to be believed to be seen." - Ralph Hodgson
  5. Late... by tirenours · · Score: 2, Informative

    Even the news on the tv talked about it before /.

    1. re: Late... by c0defiant · · Score: 3, Informative

      Nope, this one was on /. first

    2. Re:Late... by Anonymous Coward · · Score: 0

      But if you had been a subscriber, you would have seen the story the same time as the news on TV!

  6. Dupe? by Anonymous Coward · · Score: 0

    Uh oh, did not we have this already?

    1. Re:Dupe? by Anonymous Coward · · Score: 0

      Yep: http://slashdot.org/article.pl?sid=04/05/01/161822 4&mode=thread&tid=126&tid=172&tid=185&tid=190&tid= 201

  7. Internet Explorer? by Anonymous Coward · · Score: 5, Informative

    Sasser doesn't affect IE.

    1. Re:Internet Explorer? by gl4ss · · Score: 0

      yeah talk about slashdot going downhill.

      the words "internet explorer" doesn't even appear in the bbc article linked..

      --
      world was created 5 seconds before this post as it is.
    2. Re:Internet Explorer? by Anonymous Coward · · Score: 2, Insightful

      Yeah, but blaming stuff on IE is really good for Slashdot's parent company, VA Systems, or whatever they've called themselves now to grope for profitability.

    3. Re:Internet Explorer? by Anonymous Coward · · Score: 0

      Here's an idea. Since this site is so distasteful to you go somewhere else. Maybe they'll appreciate your whining there.

      It amazes me how many people trash this site but keep coming back for more. If it hurts don't do it. Doh!

    4. Re:Internet Explorer? by ameoba · · Score: 2, Insightful

      It depends on how you look at it. From the perspective of the average user, if the network is down then "IE is broken".

      --
      my sig's at the bottom of the page.
    5. Re:Internet Explorer? by Jugalator · · Score: 1

      Yes, but I hope Slashdot hasn't fallen to the levels of "the average user" now. :-(

      --
      Beware: In C++, your friends can see your privates!
    6. Re:Internet Explorer? by BKoT · · Score: 1

      Even the BBC article implies that IE (and any other browser) is in the mix.

      "Unlike more recent viruses, Sasser does not travel by e-mail instead it makes its way around the web unaided."

      I grew tired long ago of the terms "web" and "internet" being interchangeable.

  8. I have a question by Progman3K · · Score: 5, Interesting

    What does Sasser actually DO?

    Usually, viruses have a goal, like collecting your personal information, DDOSing SCO, or SOMETHING...

    What does this one actually do?

    My theory is that someone wrote it to disable all the spamware-infested computers out there.

    They can't be spamming us if they're rebooting constantly, can they?

    And if the owner doesn't disinfect them and protect them from future attacks, they'll just start rebooting again...

    --
    I don't know the meaning of the word 'don't' - J
    1. Re:I have a question by manavendra · · Score: 5, Informative

      You mean other than scanning random IP addresses on successive TCP ports starting at 1068 and making copies of itself?

      Well, it also acts as an FTP server on TCP port 5554, and creates a remote shell on TCP port 9996.

      It further makes copies of itself in the %Windows% directory.

      Oh and finally, it causes LSASS.EXE to crash, and by default this causes your system to reboot. Repeatedly.

      --
      http://efil.blogspot.com/
    2. Re:I have a question by joeykiller · · Score: 4, Insightful

      Sasser is mostly annoying. It causes your computer to restart repeatedly, while scanning nearby ip adresses and spreading itself to them (if they're not patched). Doesn't sound too bad does it?

      Well, even though it's "just annoying" and "poorly written" according to F.Secure, it caused Sampo (a large bank in Finland) to shut down yesterday. Both computer networks and telephony systems were hurt. The same happened to If, a Norwegian / Swedish insurance company, and today another Norwegian insurance company had to halt operations (Vesta).

      So even annoyances can stop entire operations, and thus we can say that it's a pretty serious problem until most (Windows) computers are patched.

    3. Re:I have a question by nordicfrost · · Score: 4, Informative

      Well, for one, it bogs down your network to a mush of syrup. All that looking for other hosts to infect really takes up a lot of capacity on the network. And the Sasser.D version is up to 1024 threads pr. CPU, up from 128 in the Sasser.B version...

    4. Re:I have a question by Progman3K · · Score: 1

      Right, but let's look at each of those;

      Scanning random IP addresses on port 1068, to make copies of itself. OK, a virus needs to reproduce to have any effect, so that makes sense.

      It acts as an FTP server, to copy itself, again...

      I don't know the purpose of the remote shell... That one is a mystery.

      --
      I don't know the meaning of the word 'don't' - J
    5. Re:I have a question by Anonymous Coward · · Score: 2, Interesting

      The purpose seems to be simple propogation (no destructive payload, mass-mailer, etc.). The crash of LSASS seems to just be a side effect of the exploit used.
      Of course the patch to fix the LSASS hole has been reported to render systems unusable as well.

    6. Re:I have a question by Anonymous Coward · · Score: 1, Interesting

      You mean other than scanning random IP addresses on successive TCP ports starting at 1068 and making copies of itself?

      It actually scans on port 445, not 1068.

    7. Re:I have a question by ianturton · · Score: 1
      apparently it also took out the UK coastguard .

      Ian

    8. Re:I have a question by Progman3K · · Score: 4, Interesting

      Right...
      But have you noticed, it can only infect computers that are not properly patched and up-to-date...

      I read a while ago that 0-day exploits on Windows are mostly unheard of, while most viruses seem to come out a few weeks AFTER Microsoft has issued a patch, because the virus-writers wait for a patch to disassemble it and learn how to exploit the weakness, which is easier to do that figuring out how to exploit the vulnerability.

      This hole was patched by Microsoft, when? A few weeks ago...

      So other than annoying people with improperly-maintained machines, Sasser doesn't really seem to be more than a proof-of-concept, or as I believe, a virus crafted to SPECIFICALLY annoy people who's machines are not properly patched.

      And let's face it; if your machine is not properly patched, it's probably already being used as a spam relay, so it's not the spammers who would want this.

      Rather it feels like someone waging war ON THE SPAMMERS!

      --
      I don't know the meaning of the word 'don't' - J
    9. Re:I have a question by manavendra · · Score: 1

      It acts as an FTP server, to copy itself, again...

      FTP server - can then be used to copy files onto the infected server as well.

      The remote shell is presumably to allow access to the infected machines and execute copied programs for further alterations/destruction?

      --
      http://efil.blogspot.com/
    10. Re:I have a question by spellraiser · · Score: 2, Interesting

      Usually, viruses have a goal, like collecting your personal information, DDOSing SCO, or SOMETHING...

      Sorry, but that's not all that accurate. Most often, the virus/worm is a goal in itself (and by the way, Sasser is a worm, not a virus). Viruses and worms that are tools to carry out some separate agenda are the exception, not the rule. Although recent worms such as Bagle, Netsky and MyDoom (and their numerous variants) were crafted to be 'useful' in some way, this is a fairly recent phenomenon, and still a fairly uncommon one, if one looks at everything that's being released these days. It might become the norm in the future, but that hasn't happened just yet.

      My theory is that someone wrote it to disable all the spamware-infested computers out there.

      They can't be spamming us if they're rebooting constantly, can they?

      Interesting theory, but there's one problem. Whoever wrote Sasser did not intend for it to crash systems. This is a side effect of sloppy coding; it's not intentional.

      --
      I hear there's rumors on the Slashdots
    11. Re:I have a question by Progman3K · · Score: 4, Interesting

      >Interesting theory, but there's one problem. Whoever wrote Sasser did not intend for it to crash systems. This is a side effect of sloppy coding; it's not intentional.

      You know what?
      I think that yesterday, I received a LOT LESS spam than usual. I'm talking a fraction; instead of 200-300, I only received about 20.

      So even if taking down all those spam-relays was just a side-effect, I'LL TAKE IT! :-)

      --
      I don't know the meaning of the word 'don't' - J
    12. Re:I have a question by Anonymous Coward · · Score: 2, Insightful

      Well, even though it's "just annoying" and "poorly written" according to F.Secure, it caused Sampo (a large bank in Finland) to shut down yesterday. Both computer networks and telephony systems were hurt.

      I'm concerned about what'll happen when some more competently written worms get written, with some highly destructive payloads triggered at a certain time, or by some certain network event.

      At the moment, most of the disruption is directly as a result of the worms spreading, with network connections being swamped. If worms were to actively trash filesystems, or (more dangerously) subtly mess about with data in spreadsheets, databases etc, it could be horribly expensive to sort everything out, and genuine, lasting damage could be done to businesses.

      You'd think the current worm and trojan problems were enough to jolt people into a more security-aware frame of mind, but it seems we're fighting a losing battle to educate people before some polymorphic, ultra-subtle worm with no (initial) obvious effects will strike.

      If such a thing were to wreak havoc, there'd probably going to be a major backlash against Microsoft, even though computer security is partly the responsibility of the user, too.

    13. Re:I have a question by psavo · · Score: 1

      Next step version applies same 'fix' to rebooting computer as what f-secure recommends. (creating some debug log file in some directory)

      --
      fucktard is a tenderhearted description
    14. Re:I have a question by WormholeFiend · · Score: 1

      "The same happened to If, a Norwegian / Swedish insurance company"

      that has to be a joke-name, right?

    15. Re:I have a question by 4string · · Score: 1

      Actually I got it on Apr 3rd on a rare occasion that I dialed in, I was away on a trip. I dialed in and then rebooted, immediately got the LSASS error ten a minute or so later the shutdown window.
      My PC is spyware and spam free, I know this because I just re-formatted and reinstalled XP
      Maybe the problem was using XP in the first place?

    16. Re:I have a question by interiot · · Score: 4, Informative

      Just a note regarding 0-day exploits: SysInternals (the people who brought you filemon, regmon, etc) write BGInfo, a low-CPU no-memory way of displaying important system properties. If you do have it installed, you can tell it to display the timestamp of the file C:\Program Files\WindowsUpdate\V4\iuhist.xml, which should be the last time WindowsUpdate was run, helping remind you to run it frequently.

    17. Re:I have a question by WormholeFiend · · Score: 4, Funny

      I've always been a virus-writer-hater, but reading your comments, I'd say you're doing a pretty good job at convincing me that viruses are good...

      the enemy [virus writer] of my enemy [spammer], while being useful, is he still my enemy or my friend?

      I'm confused.

    18. Re:I have a question by mwilliamson · · Score: 1

      Well, our network is 100% switched on Cisco gear. Every time when our network turns to syrup, we know it's due to hardware failure. ;-)

    19. Re:I have a question by Progman3K · · Score: 1

      >Maybe the problem was using XP in the first place? ;-) Maybe.

      It's not to be sanctimonious, or to laugh at you, but you got infected because you hadn't patched your system recently, right?

      Of course, infecting you is LOW, of course it's mean, of course it's underhanded, and I empathize with you, because it's a pain-in-the-ass...

      So while a lot of innocent people will get caught by this too, I'm sure an even greater number of delinquent users will get caught.

      Sorry about your troubles though. Good luck sorting it out.

      --
      I don't know the meaning of the word 'don't' - J
    20. Re:I have a question by C_nemo · · Score: 1

      nope, its called "if". name sucks, I know, but still they call themselves "if". They are also apparently quite prod about it.

    21. Re:I have a question by Ashtead · · Score: 2, Informative

      No joke, this company is for for real. And yes, I do not think they chose that good of a name either. But this is the result of the fusion of several insurance companies, including some with names like "Storebrand" and "Norges Brannkasse" names which reveal the focus on fire insurance (Brann == fire) in a country where most houses are made of wood.

      --
      SIGBUS @ NO-07.308
    22. Re:I have a question by JWW · · Score: 1

      You know I love all this its the users' fault crap. Microsoft has everyone buying that line. Of course they always seem to get the patch out before the virus appears. What happens one day when they don't, when the virus comes first? Who will you blame then?

      Also, if GM recalled my car every month, I think I'd be getting a little pissed off as a customer. But with Microsoft not only do they report defects almost monthly, you have to fix it yourself!

    23. Re:I have a question by Anonymous Coward · · Score: 0

      That is not necessarily true. The company I work for was activly testing this fix for several weeks after Microsoft released it. In a company with 60000 employee's you can't just automatically patch every release M$ pushes out there. In fact, this release was delayed (within my comany) last week because of fears that it would cause more system instability. We were in the process of releasing the patch worldwide when the virus hit. Don't assume that because a major company was hit with the virus that the company has an incompentent IT department. Most major companies are going to spend quite a bit of their time testing, before they release a security fix like the one released by microsoft.

    24. Re:I have a question by Anonymous Coward · · Score: 0
      Ah, the Microsoft party line - it's the dumb users, they didn't patch their boxes they had a whole two weeks (good for MSFT, some time it's months).

      Reminds me of the post about backing up your computer frequently a while back and the problems with the short life of CDROMS. A poster asked what happens when the life of the cdrom is shorter than the time it takes you to back up all your stuff. I'll steal that idea and ask "What if, as virus spread faster and faster, the time it takes you to download and install the fix is greater than the time it take _the next_ virus to hit your 'puter? Hmmm...)

    25. Re:I have a question by kasparov · · Score: 2

      Anything that opens a remote shell has a destructive payload. It basically gives a remote user full control of your pc. That means at a whim, they (or someone else who figures out that it is there) can delete files, format drives, or store kiddy porn on your pc--whatever they want. I would argue that that is a destructive payload...

      --
      There's no place I can be, since I found Serenity.
    26. Re:I have a question by Progman3K · · Score: 1

      Non, no, no.
      I DON'T blame the users.

      At the heart of all this is a terrible product - Windows, that has got all its users caught-up in this maelstrom of problems.

      But zero-day exploits are VERY rare, if not non-existant.

      Even more dangerous is releasing a patch!

      Read this
      http://www.computerworld.com/printthis/2004/ 0,4814 ,92037,00.html

      --
      I don't know the meaning of the word 'don't' - J
    27. Re:I have a question by Naffer · · Score: 1

      You know, back in my day viruses used to do nasty things like write data into the bios or randomly delete data on the HD. I think we should all just thank our lucky stars that the writers of Blaster and Sasser decided not to add a malicious payload. In fact, I'm pretty sure that there isn't anything Microsoft fears more then a widely spread destructive worm.

    28. Re:I have a question by bogie · · Score: 2, Interesting

      "I read a while ago that 0-day exploits on Windows are mostly unheard of, while most viruses seem to come out a few weeks AFTER Microsoft has issued a patch, because the virus-writers wait for a patch to disassemble it and learn how to exploit the weakness, which is easier to do that figuring out how to exploit the vulnerability."

      Actually your probably not doing it intentionally but your just repeating Microsoft marketing-speak. http://slashdot.org/article.pl?sid=04/02/26/155520 8

      There is little evidence that hackers are actuallly reverse engineers patches. In fact as people pointed out in that thread if that theory was true then MS could just stop releasing patches and Windows would become invulnerable.

      Most exploits are based on proof of concept code that floats around the net way before MS gets around to fixing patches. In fact there are more than a few sites out there that have lists of MS security flaws which have yet to be patched. I think your right that patches may increase the visibility of MS flaws to some of the dumbiest script kiddies and common people but the damage was already done way before then. MS is just trying to plug a hole that was already known. So no, patches are Not the reason why worms happen.

      Finally as proof of at least one virus or 0-day exploit that took advantage before MS issued a patch, look at the Melissa virus. See that thread for other examples.

      When MS's security cheif said "We have never had vulnerabilities exploited before the patch was known", he lied.

      --
      If you wanna get rich, you know that payback is a bitch
    29. Re:I have a question by wvitXpert · · Score: 1

      So other than annoying people with improperly-maintained machines, Sasser doesn't really seem to be more than a proof-of-concept, or as I believe, a virus crafted to SPECIFICALLY annoy people who's machines are not properly patched. Unfortunately my University is one of those "people" with improperly-maintained machines. The workstations that allow us to print are periodically rebooting. And I work help desk... fun, fun, fun. I couldnt believe it when I walked into work this morning and found out that our entire network is still vulnerable to an exploit that was patched last month.

    30. Re:I have a question by Anonymous Coward · · Score: 0

      Well if you read his post you'll note that he dialed in - that might be the only connection he has. Updating is pretty tough through dialup.

    31. Re:I have a question by dasmegabyte · · Score: 1

      Or you could just use Automatic Updates. They've been around since Windows 2000 service pack 3. You can set it to run Windows Update automatically, to download in the background and let you know when it's ready, or to notify you when new updates are available so you can get them yourself.

      It's an astoudingly good piece of software. Easily on par, if not better than, Apple's Software Update.

      --
      Hey freaks: now you're ju
    32. Re:I have a question by Pii · · Score: 1

      Well, it's not like the Coast Guard is important... to an Island nation... Ok, maybe it is.

      --
      For those that would die defending it, Freedom
      has a sweet taste that the protected will never know.
    33. Re:I have a question by Progman3K · · Score: 3, Insightful

      >Actually your probably not doing it intentionally but your just repeating Microsoft marketing-speak

      So someone at Microsoft wrote this article and invented all the facts in it?

      http://www.computerworld.com/printthis/2004/0,48 14 ,92037,00.html

      And you should know that I am NOT a Microsoft shill.
      I'm not excusing Microsoft, I just think someone out there has an agenda that is different that the typical worm-writer's.

      --
      I don't know the meaning of the word 'don't' - J
    34. Re:I have a question by Pii · · Score: 1
      Actually, this shouldn't happen, because any clueful network/firewall guys are already doing egress filtering of outbound TCP/UDP 135-139, and 445, as a result of some other worms from the last couple years...

      Oh, your company isn't, you say?

      I said "Clueful."

      --
      For those that would die defending it, Freedom
      has a sweet taste that the protected will never know.
    35. Re:I have a question by Anonymous Coward · · Score: 0

      Thank you for this most excellent tip. I had used BGInfo, but didn't know it could do this.

      A small problem, however, is that it only tells when Windows Update last CHANGED something, not when it was last run.

    36. Re:I have a question by BokLM · · Score: 1

      I read a while ago that 0-day exploits on Windows are mostly unheard of, while most viruses seem to come out a few weeks AFTER Microsoft has issued a patch, because the virus-writers wait for a patch to disassemble it and learn how to exploit the weakness, which is easier to do that figuring out how to exploit the vulnerability.

      I think that enought details about the vulnerability help more than a patch do disassemble.
      MS say this to give a reason why they take so much time to release their patchs.

      This hole was patched by Microsoft, when? A few weeks ago...

      Yes, it was patched a few weeks ago. But if you look on this page, you'll see that eeye reported this problem to MS on October 8, 2003.
      However they waited for MS to release a patch to give more details about it.
      But there was people aware of this for a very long time ...

    37. Re:I have a question by Anonymous Coward · · Score: 0

      Thats just stupid. Just enable windows updates. You can have it notify you to update when you are out of date, or download the updates and notify you they are ready to install, or -better yet for these corporate idiots- auto install updates.

    38. Re:I have a question by p_trekkie · · Score: 1

      Actually, there's something funny about the LSASS crashing.

      It crashed LSASS on a computer I was maintaining, but when I went to look for the virus executable in running processes and windows directory, there was no sign of it. Furthermore, activating Microsoft's firewall stopped the LSASS crashes and let me patch the system.

      Maybe the crashing was accidental (i.e. a poorly written virus) and the rebooting computers don't actually get infected?

    39. Re:I have a question by Anonymous Coward · · Score: 0

      if I had a bank account with that bank, I'd close the account immediately.

    40. Re:I have a question by Anonymous Coward · · Score: 1, Insightful

      Well, yeah, frankly ComputerWorld has been known to take a pro-Microsoft stance. As has been reported elsewhere in this thread, this was reported to Microsoft in Oct of 2003 by eeye. It was almost certainly exploited before this by people smart enough not to use 100% of computer resources or cause the machine to crash.

    41. Re:I have a question by mindriot · · Score: 1

      Well, Sasser is not a virus, it's a worm. Worms usually want to simply spread, not necessarily actively wreak havoc. (Sasser does of course wreak havoc, but that's more of a collateral damage type thing.) Viruses, on the other hand, may (but not always do) deliberately destroy stuff. The Jargon file has some more complete explanations on worms and viruses.

    42. Re:I have a question by Dave419 · · Score: 0

      Actually Sasser only reboots machines it is not able to infect, but are not properly patched. Infected machines are not constantly rebooting.

      --
      ~ there are 10 types of people in this world, those that can read binary and those that can't
    43. Re:I have a question by megarich · · Score: 0

      I don't patch my windows system. Call it what you wan't but my personal experience, patches hurt my computer more than it helped it. Thus far a hardware firewall, not searching for porn in windows, and an up to date virus protector is doing the trick for me....

    44. Re:I have a question by manavendra · · Score: 1

      It actually scans on port 445, not 1068.

      Not really. Again to clarify the confusion, its the darned LSASS.EXE that listens on 445, while the worm scans 1068 upwards.

      Oh and it exploits a vulnerability in LSASS.EXE causing a buffer overflow and thus crashing it and XP is fused to reboot if LSASS.EXE crashes!

      --
      http://efil.blogspot.com/
    45. Re:I have a question by Anonymous Coward · · Score: 0

      "But have you noticed, it can only infect computers that are not properly patched and up-to-date..."

      From BUGTRAQ:

      I've been following this thread and the stated instabilities of the
      MS04-011 security update, I had determined to delay deployment of this
      patch until it was stabilized but it seems it wasnt stabilized fast enough
      to beat the worms to market.

      Now of course this same LSASS vuln addressed by MS04-011 is the target of
      the Sasser worm....

      undeployable/unstable patch + critical vulnerability = the even greater
      threat of the sasser worm(s)... good job.

      I read in a article on this patch that the instability is only present if
      the "Nortel Networks VPN client is installed and the IPSec Policy Agent is
      set to manual or automatic startup type", does anyone have any further
      input on MS04-011? Stable on a standard Win2k server install or not?

    46. Re:I have a question by Zarquil · · Score: 1

      What an exceptional tip!

      Now I don't have to read Slashdot any more. I've only been coming in to check for the latest Windows exploits anyhow.

      - Zarq

    47. Re:I have a question by Anonymous Coward · · Score: 0

      Except that Automatic Updates sends a lot more data back to MS than Apple's Software Update sends back to Apple.

      </tin-foil hat>

    48. Re:I have a question by swb · · Score: 1

      We saw a similar behavior with Welchia/Nachi; some systems only got partially infected. When rebooted, they lacked the .exe to continue infection.

    49. Re:I have a question by Progman3K · · Score: 1

      >Actually, this shouldn't happen, because any clueful network/firewall guys are already doing egress filtering of outbound TCP/UDP 135-139, and 445, as a result of some other worms from the last couple years...

      Probably a case of someone who brought their laptop home and has DSL/Cable.

      I believe it was mentioned somewhere that sasser ACTIVATED friday or saturday, but that would mean that there had been a period of dormance before?

      So you could have had an infected laptop brought into work, and when the virus activated, every machine on the LAN became a target.

      I think the solution is to firewall EACH MACHINE, like Linux. :-)

      --
      I don't know the meaning of the word 'don't' - J
    50. Re:I have a question by gnuman99 · · Score: 1
      I don't know the purpose of the remote shell... That one is a mystery.

      The infected machines are SOLD to spammers and others to relay spam. Well, most of the time.

      It can be also used in other things, like DDOS attacks, or delete your HD when you sleep!

    51. Re:I have a question by jrockway · · Score: 1

      > xcurs [iki.fi] -- XCursor editor for XFree86 4.3 out now.

      Forbidden
      You don't have permission to access /~ptikka/decurs.html on this server.
      ------------------
      Apache/1.3.29 Server at www.hut.fi Port 80

      --
      My other car is first.
    52. Re:I have a question by Progman3K · · Score: 1

      OMG
      I mean I *know* I suggested something straight out of the tinfoil-hat brigade's greatest-hits, but your post makes me wonder if I'm paranoid ENOUGH.

      LOL

      --
      I don't know the meaning of the word 'don't' - J
    53. Re:I have a question by homer_ca · · Score: 1

      "And let's face it; if your machine is not properly patched, it's probably already being used as a spam relay, so it's not the spammers who would want this."

      The spammers use worms like Netsky which are user executed email attachments. One version of it did exploit an IE bug to autoexecute from the preview pane, but most of them were social engineering attacks ("Hey look at this file!"). OS patching won't fix that, but updated antivirus software can. Of course, nothing is stopping someone from writing an RPC exploit worm with a spam proxy payload, but I think email worms are just more effective at creating spam zombies because they're less intrusive. RPC worms like Blaster and Sasser are impossible to ignore just because all the network traffic from scanning.

    54. Re:I have a question by System.out.println() · · Score: 1

      I agree.... especially since this worm doesn't affect my OS. :)

    55. Re:I have a question by Progman3K · · Score: 1

      >RPC worms like Blaster and Sasser are impossible to ignore [...]

      Yes, that's why I think that this is a Good Thing (TM), because those constantly-rebooting machines will have to be dealt with now.

      Up until now, if those machines were part of a spam relay or what have you, they might have been easy to ignore if the infection didn't do anything to hinder the user too much.

      Now though, there will be now way for the administrator of the machine to ignore it any longer.

      And if the admin DOESN'T take care of it, well the machine can't be used to spam because it's constantly rebooting.

      So, cool.

      --
      I don't know the meaning of the word 'don't' - J
    56. Re:I have a question by MrHanky · · Score: 1
      the enemy [virus writer] of my enemy [spammer], while being useful, is he still my enemy or my friend?

      I'm confused.

      Hmmm... The enemy of my enemies is confused.
    57. Re:I have a question by interiot · · Score: 1
      Yes. There's also the caveat that if there are updates that are installed in other ways (my company pushes updates out via SMS), those don't update that file either, I don't believe. I was sort of hoping someone would post an improvement to this, but alas.

      BGInfo does take output from VBScripts as well, so it's possible to do some complicated procedure if someone would take the time to figure out the proper solution and code it up.

    58. Re:I have a question by interiot · · Score: 1

      Windows Update may itself be astoundingly good, but the patches sent out over it are sometimes less so. So it's really recommended that everyone spend at least a small bit of time checking community postings to make sure microsoft's fixes are good.

    59. Re:I have a question by Anonymous Coward · · Score: 0

      You wrote:

      >My theory is that someone wrote it to disable all the spamware-infested computers out there.

      DREAM ON!!! I wish that were true.... SPAMMERS- eat shit ahd die... But I DID shut down more then 2500 spam trojans last week... but (sigh), it's kinda like swatting flies... One down, and 99,999,999,999,998 to go.

      >They can't be spamming us if they're rebooting constantly, can they?

      Don't get your hopes up dude.... There are just way too many Russian or E European programmers out there that like to drive Porshces, I'm sure they will figure out a way.

      >And if the owner doesn't disinfect them and protect them from future attacks, they'll just start rebooting again...

      Yea - well perhaps people will wize up and conder the fact that there IS life after Bill Gates, and there ARE people out there that THINK DIFFERENT... The "migration" is already starting to happen.

    60. Re:I have a question by Anonymous Coward · · Score: 0

      Program3K has a very good point. The release of the Sasser virus will indeed wipe out a LOT of infected hosts as the news gets out, because people would then be forced to clean out all their other spam trojans.

      Look what happened when the MSBlaster worm got released. Within days of the initial infection, my spam went down significantly. Then, about 4 days later, SOBIG was released... Ever figure out why? Think about it.... Spammers were loosing their spam proxies... They had to do something really fast... so they hired this programmer to write the SOBIG virus, and using their (still large) huge spam network, started sending them out.... people (still being clueless and stupid) would of course open them.... thus continuing the perpetuate their spam empire..

      I've already noticed a significant decrease in spam...

      Last week, I was getting about 2500 spams a day. But we also started field testing our new auto-reporting system (which - by the way if you use Comcast, your service would get hosed). Yes, massive spam reporting is NOT POSSIBLE of you use consumer grade broadband... ISP's think your spamming when you sent out your spam complaints.

      Anyway - my average spam count went from 2500 down to about 900 - 1000, and I don't think it's from our massive spam reporting efforts.

      What does this mean? Well, figure it out!!! I mean all you slashdotters can make the connection...

      In a few days from now, there might be a repeat of what happened when the MSBlaster worm was released... IE: another one of the likes of Sobig... might be released soon... After all, those spammers can't lose those infected zombies, right?

      Sheesh - the war goes on....

      Remember - IBM = I buy Mac

    61. Re:I have a question by Anonymous Coward · · Score: 0

      Hahahaha! You noticed that also? So did I - I posted something about that earlier. Mine went down from 2500 to about 900.

    62. Re:I have a question by Anonymous Coward · · Score: 0

      There is no %Windows% environment variable in a fresh install. Perhaps you meant %windir%?

    63. Re:I have a question by psavo · · Score: 1

      Nice. That piece of link has been there for quite a long time and you're first who've told me about that. Thanks!

      --
      fucktard is a tenderhearted description
    64. Re:I have a question by Anonymous Coward · · Score: 0

      Oh, good idea, I'll just tell my mother and grandmother that they need to "check community postings" for information about the patches coming from Windows Update. Screw that, I'm doing the automatic update thing that's available in newer copies (SP1?) of Windows XP.

    65. Re:I have a question by 4string · · Score: 1

      You are absolutely correct, my point was that my infection was not due to spam (email) or spyware.

      My theory is that someone wrote it to disable all the spamware-infested computers out there.

      I had a newly installed machine and since I was on a trip I had to dial in and was immediately infected, granted had I been on the corporate network I would have been OK. My servers are constantly patched, but my laptop I usually just service pack.
      Anyway...it was an easy fix. The Clean Tool and the MS patch did the trick!

    66. Re:I have a question by fyeles · · Score: 1


      How can one configure BGinfo to display updates info when one is using LSASS?

      --
      Curiosity killed a cat, but for a while I was a suspect.
  9. Microsoft's "fixes" by JosKarith · · Score: 4, Funny

    We tried installing MS04-014. It totally secured our network - it shut down out ADSL link until we removed it.
    Thanks guys...

    --
    'Don't worry' said the trees when they saw the axe coming, 'The handle is one of us.'
    1. Re:Microsoft's "fixes" by getling · · Score: 5, Informative

      Umm...why did you install MS04-014 instead of MS04-011? Maybe you got confused, like /. about what in the world this "poorly written" worm is attacking....

      --
      "Life is tough but we're tougher. You only get what you give, so give all that you've got." --Tony LaRussa
    2. Re:Microsoft's "fixes" by rabs · · Score: 2, Funny


      Reminds me of a quote I saw on bash.org:

      "The most secure computer in the world is one not connected to the internet. Thats why I recommend Telstra ADSL."

      - rabs

    3. Re:Microsoft's "fixes" by Anonymous Coward · · Score: 2, Insightful

      Perhaps if you people stopped referring to patches and vulnerabilities as hard-to-decypher combinations of uppercase letters and numbers, and started calling them by short explanatory titles, others would be less confused. Sheesh! You'd think we're back to the mainframe days. In this century, you people are absolute fucking idiots if you're still running around using irrelevant numbers to refer to anything.

      STOP THROWING AROUND FUCKING NUMBERS AND JUST SAY WHAT THE PROBLEM IS. ELITIST JACKASS!

    4. Re:Microsoft's "fixes" by Anonymous Coward · · Score: 0

      translation: it reenabled the built in firewall and u forgot about it so u just uninstalled it and blame Microsoft.

    5. Re:Microsoft's "fixes" by Anonymous Coward · · Score: 0

      STOP THROWING AROUND FUCKING NUMBERS AND JUST SAY WHAT THE PROBLEM IS. ELITIST JACKASS!

      You mean like they did for the MS04-013 patch? That ended up causing even more confusion in the long run!

  10. once again by aixou · · Score: 1

    Once again, those "other" OS'es prove that security through obscurity is the wya to go. :D

    1. Re:once again by iainl · · Score: 1

      Absolutely - those "other" OSes aren't really any more secure by design, its just that they are too obscure to bother writing a virus for.

      That _is_ what you mean by "security through obscurity", isn't is?

      --
      "I Know You Are But What Am I?"
  11. Re:Windows only by Anonymous Coward · · Score: 0

    That it's the most popular even amongs hackers.

  12. Removal tool by Mindtoy · · Score: 5, Informative

    Another removal tool made by Network ASSociates can be found at: http://vil.nai.com/vil/stinger/ I've used it on a number of a machines with no problem. It only scans files (no registry). It fits on a floppy and it's free. It'll even run on machines that already have virus protection, good if someone hasn't updated their definitions and can't get on the internet. It's updated anytime a new baddy comes out, but you have to redownload the EXE file since it doesn't check for updates.

    1. Re:Removal tool by Anonymous Coward · · Score: 0

      How would someone get the Sasser worm if they were not connected to the internet in the first place??

    2. Re:Removal tool by The+Step+Child · · Score: 1

      "Stinger" huh? I'm not falling for that again...

    3. Re:Removal tool by Mindtoy · · Score: 1

      It was either that or "Shocker" I guess :)

    4. Re:Removal tool by Mindtoy · · Score: 1

      Never said in the first place. If you've ever worked on a corporate LAN with one of these things running wild you'd see how quickly a you can bring down your whole network if you don't start simply unplugging machines.

    5. Re:Removal tool by vgaphil · · Score: 1

      Your right it does a great job but beware. I ran it on a users PC and it found the Netsky virus in an email and decided to delete her entire inbox. The virus should have never made it through, we use Postini for email filtering. Damn laptop users, oh well that's a different story....

      BTW, Postini kicks ass.

      --
      A clever person solves a problem. A wise person avoids it. -- Einstein
    6. Re:Removal tool by periol · · Score: 1

      Uh, NO!!! Unless you want the registry keys that Sasser installs sitting around, or you plan on cleaning the registry yourself, you might want to get a tool that cleans the registry.

  13. Re:Windows only by Anonymous Coward · · Score: 0

    That crackers like to attack them because they are widely deployed.

  14. Re:Windows only by Anonymous Coward · · Score: 0

    What does this tell us about MSFT products?

    that they have the largest market share so are targeted by hackers?

  15. Re:M$ - First Post? by Oxy+the+moron · · Score: 5, Insightful

    I still am of the opinion that it doesn't matter how many patches M$ releases. The fact is, we need an educated user base. So many people continue to use computers without knowing the full risks associated with them.

    The Internet is great, broadband is great, computers are great. But as long as people are willing to give up their passwords for chocolate and have no clue what a firewall is or what it does, this problem will continue to plague everyone.

    Nothing beats a good educated user.

    --

    Proudly supporting the Libertarian Party.

  16. If Im totally up to date with my MS Security stuff by Anonymous Coward · · Score: 0

    then Am I okay?

    This is an honest question. Noone ever posts "users that have been keeping up with microsoft windows security updates are (still/not) under threat by this worm."

    Its just a tiny little bit of information that could be extremely valuable.

    So, Im totally up to day.. Am I safe?

  17. Decent firewall, regular updates & common sens by Dark+Lord+Seth · · Score: 3, Informative

    These are the three secret ingredients to a relatively secure system. Read them. Learn them. Understand them.

  18. Re:Windows only by cyborch · · Score: 2, Insightful

    You forgot to mention that "sasser" only infects windows machines.

    It should be the default assumption that since it is a worm then it only infects windows (the same goes for virii of course). I would think that it would be worth mentioning if it infected anything besides windows boxes...

  19. Don't blame Internet Explorer this time by joeykiller · · Score: 5, Informative

    The original poster is not correct when claiming Internet Explorer has a problem. This time it's a hole in the so called "Local Security Authority Subsystem Service" that's causing problems.

    See this and this for more details.

    1. Re:Don't blame Internet Explorer this time by penguinbrat · · Score: 0, Funny

      ...so called "Local Security Authority Subsystem Service"...

      Goes to show you that Microsoft + security = oxymoron

    2. Re:Don't blame Internet Explorer this time by Tackhead · · Score: 5, Interesting
      > This time it's a hole in the so called "Local Security Authority Subsystem Service" that's causing problems.

      One of my first questions when I laid hands on an XP box: "OK, so now that I've un-dumbed-down the thing as much as I can... WTF's this LSASS.EXE process running as SYSTEM, and WhyTF is it listening to port 445, and HowTF do I shut it down?"

      Answer: "Some sort of weird Microsoft shit, I don't know, and there's no way to kill it - in that order."

      Me: "Fuck it, then. Let's block inbound 445 at the router, and on my personal box, I'll try setting my third-party software 'Firewall' to deny all inbound and outbound traffic to it. If anything blows up, I can always permit my box to talk to whatever machines it needs to talk to".

      Nothing blows up. Yet another Microsoft unnecessary service running with SYSTEM privs is forgotten about.

      A year or two later: w00t!

      Win9x may have been an unstable piece of shit masquerading as a graphical DOS shell, but as long as you didn't use Internet Exploiter and Outbreak Excess, you couldn't get pwn3d, because desktops that don't run any listening services are pretty fucking hard to compromise remotely.

    3. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      You're a fucking idiot.

    4. Re:Don't blame Internet Explorer this time by shlomo · · Score: 1
      wrongo!

      dont forget bad packets which causes win9x to die! :) and a handfull of other bad os stuff.

      The users are always blamed for microsoft's bad software, why cant they just ship a good product (hard) instead of blaming the users for not patching (easy)?

      hmmmm

      --
      sorry officer, left my sig in my other computer.
    5. Re:Don't blame Internet Explorer this time by Oriumpor · · Score: 0

      And then the accountant goes Clickety-Clickety on his laptop at the coffee shop then plugs it in at the office and you're pwned anyways.

    6. Re:Don't blame Internet Explorer this time by Asprin · · Score: 1


      Win9x may have been an unstable piece of shit masquerading as a graphical DOS shell, but as long as you didn't use Internet Exploiter and Outbreak Excess, you couldn't get pwn3d, because desktops that don't run any listening services are pretty fucking hard to compromise remotely.

      IIRC, unlike the NT based versions, the TCP/IP stack in the Win9xs don't support raw sockets, either, so they're harder to turn into attack zombies.

      --
      "Lawyers are for sucks."
      - Doug McKenzie
    7. Re:Don't blame Internet Explorer this time by DR+SoB · · Score: 1

      Actually there were other ports, that _were_ important to anyone running a network, such as, say... Netbios, or Windns (or whatever the fuc* they called it I can't even remember)..

      IMHO _ALL_ inbound traffic should be blocked, if someone tries to make an inbound connection, it should be prompted (Allow Inbound to: xxx port xxx application - yes/no/always/only_from_that_host -> as most firewalls will allow set up of). For the average Windows Home Edition OS that would solve many problems.. Especially worms..

      --
      Mod +5 Drunk
    8. Re:Don't blame Internet Explorer this time by schon · · Score: 1

      IIRC, unlike the NT based versions, the TCP/IP stack in the Win9xs don't support raw sockets, either, so they're harder to turn into attack zombies.

      No. It's true that 9x doesn't support raw sockets, but that has no bearing on how hard it is to turn them into zombies.

      All it does is make it harder to mask the source IP address (which most zombie writers don't care too much about.)

    9. Re:Don't blame Internet Explorer this time by jjares · · Score: 3, Informative

      Actually, LSASS is the security validation services that SMB uses to validate a user when he is trying to request a resource, and that validates your user in a network that doesn't use Kerberos... I think login in most unixes runs as root too, so I don't see where microsoft went wront here.

    10. Re:Don't blame Internet Explorer this time by Oriumpor · · Score: 1

      Oh well, not that people really care about ring based security models. /. seems like the place where firewalls=bliss, since 90% of the posting for every new patch is "Blocked on the firewall for X years anyways" when in reality this is only the first step towards a secure model. IPSec or maybe some radius at your site to make sure you don't get any hassling noobs plugging into your net w/blaster/sasser etc bringing down your infrastructure just by plugging in.

    11. Re:Don't blame Internet Explorer this time by AstynaxX · · Score: 1

      I'd agree with you, except I noticed something odd about this worm. My roomates and I use my Win2K box, and while I use Mozilla nigh unto religiously, they stick with IE. Oddly enough, when this little worm tuned, they got the NT AUTHORITY shutdown messages, and I didn't. Considering that the only real difference here is browser of choice, I have to suspect that even if the vulnerability isn't -in- IE, it is somehow facilitated by IE.

      --
      -={(Astynax)}=-
      "Darkness beyond Twilight"
    12. Re:Don't blame Internet Explorer this time by Tackhead · · Score: 1
      > Actually, LSASS is the security validation services that SMB uses to validate a user when he is trying to request a resource, and that validates your user in a network that doesn't use Kerberos... I think login in most unixes runs as root too, so I don't see where microsoft went wrong here.

      How about where /bin/login doesn't bind to a port and listen to inbound traffic 24/7/365?

      Yes, there was a hole /bin/login too, but if you're running a desktop that you don't expect to log into from anything other than the console, you can turn off crap like telnetd.

    13. Re:Don't blame Internet Explorer this time by ealar+dlanvuli · · Score: 1

      Well, login doesn't get remote rooted often does it?

      There's a difference there.

      --
      I live in a giant bucket.
    14. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Unix is so secure the phrase "remote rooted" was coined just for that OS and has since made its way into the lingo as a generic term for an exploit that takes over the machine, kind of like "kleenex" or "linoleum".

      Good testiment to the inherent security of Linux there.

      Face it, Linux doesn't get pwned because it's not worth the bother. If a significant number of people really used it, there's be attacks for it as well. We see enough of them even considering Slashdot's reporting bias and the limited user base as it is.

    15. Re:Don't blame Internet Explorer this time by Dahan · · Score: 1
      Yes, there was a hole /bin/login too, but if you're running a desktop that you don't expect to log into from anything other than the console, you can turn off crap like telnetd.

      How's that any different from Windows? If you don't expect to log into a NT/2K/XP box from anything other than the console, you can turn off the Server service. Either use the Services applet, or completely uninstall "File and Printer Sharing for Microsoft Networks" from your network connection.

      Just because you don't know how to do something doesn't mean it can't be done :P

    16. Re:Don't blame Internet Explorer this time by Lemmeoutada+Collecti · · Score: 1

      Theoretically, a good idea. Until the user sees this:

      "61593428.adelphia.net is attempting to connect to your pc (3459876.adelphia.net) on port 455 and initiate a TCP connection to strcruft.exe. Do you wish to allow this connection?"

      *click no*

      Starcraft caused a general protection fault...

      Guess it's yes from now on.

      --

      You can have it fast, accurate, or pretty. Pick any 2.
    17. Re:Don't blame Internet Explorer this time by jonfelder · · Score: 2, Insightful

      Except that most people will just click yes because they have no idea what they are doing.

      All they know is that "clicking yes" makes their IM client work or game work.

      Asking if it's ok to do something hasn't stopped websites that install spyware, "comet cursor...sure sounds good...spyware crap toolbar, wow that sounds useful!"

      What makes you think it'll work with firewalls?

      Finally, clicking "always" makes the notices stop comming up. Imagine the machine is being pummeled by Sasser and notices keep popping up constantly asking to allow inbound traffic.

      Unfortunately the only real solution is also the most impractical...cutting the luser's network cable.

    18. Re:Don't blame Internet Explorer this time by Chester+K · · Score: 1

      WTF's this LSASS.EXE process running as SYSTEM, and WhyTF is it listening to port 445, and HowTF do I shut it down?

      Answer: "Some sort of weird Microsoft shit, I don't know, and there's no way to kill it - in that order."


      NT is a microkernel. The various APIs that applications use are implemented by regular processes running under it (CSRSS, for example, implements the Win32 API). LSASS implements most of the security infrastructure of the system. The reason you can't kill it through the Task Manager is because it's providing services to every other process running. (Actually, if you use a third-party process monitor, you can easily kill it, but your machine will hit a STOP error as soon as you do).

      In many ways, this design is regarded as superior to the Linux kernel's design; unintended bugs notwithstanding.

      --

      NO CARRIER
    19. Re:Don't blame Internet Explorer this time by DR+SoB · · Score: 1

      True, but if your launching a game of star craft, and expecting someone to join your game, wouldn't you click YES knowing this was an expecting incoming connection?!

      --
      Mod +5 Drunk
    20. Re:Don't blame Internet Explorer this time by DR+SoB · · Score: 1

      Well, if your launching IM, then you would click YES (It could easily tell you this is a normal port used by IM, or FTP, or StarCraft, or whatever you are expecting)

      And if your getting pummelled without even doing anything (i.e. you sit down on the 'puter after work and there is already a warning msg up), you could always put an option "always NO" :)

      I think that there is no 100% solution, but I certainly think microsoft could be doing a better job, as far as the average "dumb homeuser" is concerned..

      --
      Mod +5 Drunk
    21. Re:Don't blame Internet Explorer this time by jonfelder · · Score: 1

      That's just it...you, I, or someone else who knows things about computers would click yes and feel confident that we were doing the right thing. In reality people who are knowledgable configure the firewall properly such that it works for the things they need to do and blocks everything else. For us there's no need to even have popup notifiers. What you are failing to understand is that most people have no idea how computers or networks work nor do they want to.

      Most people do not know what a port is...they don't know what FTP is...some don't even know what IM is. Ask the majority of people what program they use to browse the web and they say, "I don't know...the e thing...or windows". Try it sometime. Ask people what version of windows they have, what their mail client is, what IM client they use, what the difference between a worm a virus and a trojan is and watch the blank stares.

      In short, they simply have no idea what they are clicking yes and no to. The only things they know are that sometimes if they click no things do not work and that the constant popping up of firewall messages is annoying.

      I agree that Microsoft could be doing a better job, and they are working on it. The ICF is a good first step. Enabling it by default (which they will do with Service Pack 2) is a good second step. A good third step would be forcing the user to enable a lot of the worthless services that are now currently turned on by default when windows is installed.

      Other than that there isn't much they can do...people choose not to install patches. People choose not to install/update antivirus software. People choose to launch harmful email attachments.

    22. Re:Don't blame Internet Explorer this time by Lemmeoutada+Collecti · · Score: 1

      You, me, most likely. Joe Twopack (already 4 down) probably not. They just like the simple it says click no if I don't know what's goin' on, so I click no style. Witness e-mail virii and worms, spam, etc.

      The only problem is if everything is written for the lowest common denominator, we might as well just plug in at birth so no one can possibly get hurt.

      I'd rant about it, but I'm so tired and inured of it that all I have left is a feeble kick or two before I join them...

      Ooh... shiny!

      --

      You can have it fast, accurate, or pretty. Pick any 2.
    23. Re:Don't blame Internet Explorer this time by caluml · · Score: 1
      I think login in most unixes runs as root too, so I don't see where microsoft went wront here.

      /bin/login doesn't listen on network ports.

    24. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0


      Are you trolling or just dumb? I challenge you to back up your troll with facts.

    25. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Except that unkillable mandatory processes shouldn't listen to network ports by default.

    26. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Just because you don't know how to do something doesn't mean it can't be done :P

      But its Microsoft's fault! They don't provide a command-line option for me to complete my task, so the task cannot be completed!

    27. Re:Don't blame Internet Explorer this time by KJKHyperion · · Score: 1

      445 is CIFS over direct TCP/IP (as opposed to 138/UDP and 139/TCP, which reach the CIFS server indirectly, through NetBIOS emulation over TCP/IP - also known as NetBT). The CIFS server, in other words, is both a NetBIOS and (since Windows 2000) a TCP/IP server. I hope this answers what port 445 is for.

      What's LSASS for? LSASS is the center of Windows authentication. Logging on on a Windows system always involves LSASS. Single sign-on is all about LSASS - when the CIFS client needs to authenticate on a file server, it asks LSASS for the credentials the requestor provided. The opposite is also true: when the CIFS server receives a request on the network, it must validate the credentials and resolve them to a SID (Security ID, variable length identifiers for users, groups and domains). This is probably what happens here - CIFS is used to deliver malformed credentials to LSASS.

      --

      Make a difference - use Windows! (open source clone of Windows NT)

    28. Re:Don't blame Internet Explorer this time by TheRealSlimShady · · Score: 1

      Neither does lsass. What listens on port 445 is SMB - SMB requires authentication, so the worm connects and overflows the authentication mechanism.

    29. Re:Don't blame Internet Explorer this time by Frizzle+Fry · · Score: 1
      IMHO _ALL_ inbound traffic should be blocked, if someone tries to make an inbound connection, it should be prompted (Allow Inbound to: xxx port xxx application - yes/no/always/only_from_that_host -> as most firewalls will allow set up of).

      You mean exactly like it works in xp sp2?
      --
      I'd rather be lucky than good.
    30. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Too much Steve Gibson for you. Someone ought to invent an innoculation for the hysterical crap that guy writes.

    31. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Shit, I wonder who provided "net stop server" then?

    32. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Actually, lsass DOES listen on a network port, just not 445 (like Tackhead claimed - the number one reason I think he's talking out his ass, trying to score geek points by making up something plausible-sounding from reading some sasser details). On my system, LSASS is listening for UDP packets on port 1027.

      Port 445 is grabbed directly by the "System" process, which always makes me wonder what the hell MS are doing with MY hardware.

    33. Re:Don't blame Internet Explorer this time by Anonymous Coward · · Score: 0

      Yes, Winnuke was cool, wasn't it?

    34. Re:Don't blame Internet Explorer this time by Tokerat · · Score: 1


      You use Mozilla and they use IE...

      ...you installed the patch that fixes this 3 weeks ago and they didn't?

      /just asking

      --
      CAn'T CompreHend SARcaSm?
  20. Please wake up... by MSFanBoi · · Score: 3, Insightful

    What it tells us about Microsoft, is there are people out there who cannot take care of systems.

    This includes Linux boxes and Mac boxes as well.

    Wake up and smell the damn coffee, it's not a problem exclusive to Microsoft, as much as some of the Linux rah-rah club would like to think.

    Why is it OK for Linux to patch the hell outta itself but a damn near capital crime if Microsoft has to?

    Grow up.

    Microsoft released a patch, people did not install the patch. Who's fault is that? None of the 1000+ systems in my office were infected because I'm intelligent enough to have policies in place to prevent stuff like this from happening.

    1. Re:Please wake up... by Anonytroll · · Score: 4, Insightful

      Yeah, but the problem in this case was that the patch that closed the hole made other systems unusable (iirc most of them couldn't have any network connection anymore), so it couldn't be used.

    2. Re:Please wake up... by Compholio · · Score: 2, Informative

      Because when the Linux Rah-Rah Club provides a patch for a security vulnerability it usually doesn't provide a new three vulnerabilities for the one it fixed. Even if the LRRC did provide such a patch someone would see the problems immediately and provide another one to fix them.

    3. Re:Please wake up... by Anonymous Coward · · Score: 1, Insightful

      if damages are significant, common and appear every three months, then it's not enough that patches are released.

      if i had to change my car's engine oil every 500 miles and the car without fail broke down unless i did so, then i have a genuine gripe about the inconveniences incurred and the inherent design flaw with the car.

      to M$: fix the design. fix the base. longhorn better deliver because most of us are far past the point of willing to accept their "blame" for people not patching - do your part in making less patches necessary.

    4. Re:Please wake up... by Ruie · · Score: 5, Insightful
      Linux distributions do not have major security problems as often as Microsoft (I can remember a single occasion when a hole was found in SSL libraries and I had to upgrade fast).

      Also, on a Linux system there is no problem finding out what exactly runs, what it does and one can check the code quality.

      In contrast, I have never even heard of the "subsystem" that is being used by this worm.

      On a free system no one *has* to fix bugs for you, but you have the freedom to do it yourself (and configure the system anyway you like, so that, if you are not comfortable running sendmail, you use other software like exim or postfix).

      On a black box system like Windows the company that makes it is responsible for getting each and every detail right because they do not let anyone else touch the contents.

    5. Re:Please wake up... by bluntos · · Score: 0

      its still damn funny

      --
      Fnord Fnord Fnord
    6. Re:Please wake up... by Lumpy · · Score: 4, Interesting

      Microsoft released a patch, people did not install the patch. Who's fault is that? None of the 1000+ systems in my office were infected because I'm intelligent enough to have policies in place to prevent stuff like this from happening.

      I find that comment funny and sad. Obviousally you run in a very tiny shop. we are still TESTING that patch because we are not stupid enough to trust microsoft. we have had many times a patch completely hose several of our critical apps. and when you are looking at around 500,000 desktops/ servers/ etc.. you can't do foolish things like installing patches willy nilly.

      now let's add the fact that the company is too damned stupid to staff the security and virus team properly. we have 2 people... 2! and maybe 6 machines to test on... we really need about 5 and 20 machines and 2 servers to test on so we can roll this crap out in a timely manner.

      So buddy, Grow Up.

      --
      Do not look at laser with remaining good eye.
    7. Re:Please wake up... by G27+Radio · · Score: 1

      I think the big deal is that when it's a Microsoft exploit it spreads like wildfire, causes outages, and generally wreaks havoc across the Internet.

      When it's a Linux exploit maybe a couple machines get compromised and it doesn't even make the news. And it's not as if there aren't tons of Linux servers out there that are constantly connected to the Internet.

      And what's this "Grow up" crap? If it upsets you so much stick your head in the sand and don't read about it.

    8. Re:Please wake up... by southpolesammy · · Score: 1

      Perhaps the problem is that since Microsoft OS's seem to have critical security patches far more often than other OS's, people just can't keep up. I know there are alternatives to having to do it yourself, but what does it say about Microsoft's coding practices when you have so many exploits against the codebase appearing so regularly?

      Now this could just be a law of numbers issue, in that the installed base of systems with one of MS OS's is far larger than any other and therefore it gets the most scrutiny. However, the simple fact is that it does happen more often, and given the absence of an educated userbase (BTW -- this is a pipe dream and you know it), Microsoft should be doing more and better code reviews and testing of their products. Microsoft is quickly becoming the Ford Pinto of the IT world.

      --
      Rule #1 -- Politics always trumps technology.
    9. Re:Please wake up... by Dogers · · Score: 1

      LSASS is the whole authentication subsystem in Windows - without it, its, well, Windows :)

      Seriously though, this is the system that sets and maintains the execution levels (SYSTEM, UserX, Guest, Admin, etc) so is a very very important one.

      The reason the system reboots when being hit by this worm is that the worm causes the exe to exit, which the services system then has "Reboot on failure" set for. System restarts, gets hit again, round and round the mulberry bush we go!

      --
      I am a viral sig. Please copy me and help me spread. Thank you.
    10. Re:Please wake up... by Havokmon · · Score: 1
      Microsoft released a patch, people did not install the patch. Who's fault is that? None of the 1000+ systems in my office were infected because I'm intelligent enough to have policies in place to prevent stuff like this from happening.

      Ahh You must run Netware and Win98. Good lad. ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    11. Re:Please wake up... by RoLi · · Score: 2, Insightful
      When do you Winlots start to realize that there is a HUGE difference between remote and local exploits?

      The former is likely to hit a lot of people through worms, the latter is (and I'll get flamed for saying that) mostly irrelevant unless you really need ultra-high security or have untrusted users on your machines (both cases are pretty rare in real life, sorry Winlots.)

      And that's exacly why Linux' TCO is a lot lower than Window's. That's why webhosters usually charge about 30$ more for Windows than for Linux. (Every Windows machine is a much larger risk than a Linux machine.).

      Also while in the Windows-world old bugs are constantly re-introduced into the network (because if you have some Win2K license you will use that when you reinstall) while in the Linux-world you usually use the newest version when you install a new machine. Actually Netcraft reported that after the CodeRed epidemy, the number of vulnerable machines was on the rise again!

      To sum up (and to prevent somebody purposely misunderstanding), sure OSS isn't the silver bullet - but it indeed is much more secure than Microsoft. Also a halfway recent (let's say about 1-2 years old) unpatched Linux installation does not provide 100% security, but adequate (or "good enough") security for most users.

    12. Re:Please wake up... by MSFanBoi · · Score: 0, Insightful

      So lemme get this right, this wouldn't ever happen if you were a linux shop? 1000 systems and 25 servers isn't so small. We have a test lab, I tested the patch, it worked, and I deployed it to all the systems via SUS. Quick and painless. I forgot to mention, there is only ONE person on the IS team (other than the 2 person help desk) and thats ME. If your company is too stupid to care about security, and using the right tools, maybe you should be looking for another job, because apparently you cannot handle the one you got.

    13. Re:Please wake up... by dmomo · · Score: 1
      Another problem that Microsoft has, is the fact that it has a more or less predictable installation. One writing a worm knows what common apps and services are likely to be running on a Windows machine. Linux, as it's desktops becomes more standardized may be vulnerable in such a way too. This isn't to say that Microsoft isn't MORE vulnerable, but Linux users are far from invincible. This will become more apparent when "the average Joe" starts using Linux. The "average Joe" tends to go with the defaults. One might find an exploit in one of the defaults, and take advantage of it.


      Though there will likely not be as many exploit opportunities as we see for Windows, I am sure they will arise.
      From A Letter from the Editor of Linux Journal (4/04):

      As I write this, yet another e-mail worm is spreading among non-Linux computers and incidentally filling my mailbox with "YOU HAVE A VIRUS" bounces from dumb software that somehow doesn't yet get the concept that worms forge mail. There's nothing like a worm attack that spares Linux to bring out the smug superiority in Linux users.


      Cut it out. The attack path here is one step long. All that's keeping us safe is that most programs for Linux don't make it easy to run attachments from incoming mail. But combine the right vulnerability in a common desktop app with a little social engineering, and you've got a Linux worm.

    14. Re:Please wake up... by StrawberryFrog · · Score: 1

      nd when you are looking at around 500,000 desktops/ servers/ etc.. you can't do foolish things like installing patches willy nilly.

      No, you can't. However with that many machines you naturally must have a firewall (right?). So you'll be all right for this one.

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    15. Re:Please wake up... by pesc · · Score: 3, Insightful

      No, the truth is that Windows is not ready for the internet. Do you need more proof?

      1) All windows boxes use the same software and services which creates a good monoculture for viruses to spread in.

      2) Why the fuck is that port turned on by default? What the heck is the service doing? Most users don't use that service so it should be turned off by default. sheesh!

      3) When I last used Windows (a couple of years ago) it actively made it difficult for me to remove services I didn't want to use, like IE, IM, M$-media player, etc. There were many services that I didn't understand what they were doing, but I couldn't remove them. On Linux I do the opposite. I install a slim minimal server, and then add the services I want to use and understand. This is how it should be done.

      Why all the talk about how Linux is not ready for the desktop (it is, it's what I use all the time) when the truth is that Windows is not ready for the internet. This is demonstrated monthly.

      --

      )9TSS
    16. Re:Please wake up... by Anonymous Coward · · Score: 0

      to M$: fix the design. fix the base

      Specifically what needs fixing? What part of Windows' design needs fixing? What part of the base needs fixing? What would *you* do to fix Windows?
    17. Re:Please wake up... by presarioD · · Score: 1


      Grow up

      What is it with these comments anyway? Whenever somebody has a different opinion the "infected" party has to "grow up to adulthood", "get over him/herself" or what else!

      Grow up and get over yourselves!

      --
      Yam, yam, uga booga, yam, yam, yade, yade, uga booga, yam, yam, yade, yade
    18. Re:Please wake up... by Anonymous Coward · · Score: 0

      You'll be allright as long as an employee with an infected computer doesn't VPN into your LAN, wich will transfer the worm straight into the network bypassing your firewall. The only way to protect a LAN against this one is to install patches and/or firewalls on each computer and avoid any remote connections.

    19. Re:Please wake up... by Anonymous Coward · · Score: 0

      Specifically what needs fixing? What part of Windows' design needs fixing? What part of the base needs fixing? What would *you* do to fix Windows?

      um, whatever it takes to make less patches necessary?

      i don't know what i would (personally) do to fix Windows - it's not my problem. M$ gets paid for Windows - not me.

    20. Re:Please wake up... by Carty · · Score: 1

      You would also not be alright if any of those 500,000 machines were portable (pretty likely, no?. They could (and will) be infected while at home or on the road, for which an enterprise's perimeter firewall is useless. Once the machine comes back to work the worm freely propagates inside the enterprise network.

    21. Re:Please wake up... by Anonymous Coward · · Score: 0

      and when you are looking at around 500,000 desktops/ servers/ etc..

      This is somewhat of a cop-out. It's understandable that you'd want to thoroughly test server systems. But the desktops don't require nearly the same level of testing. A day or two of testing should be sufficient for workstations (I would envision that with 500K systems that you have a reasonably standard build for them).

      The company I work for faces this same problem. We've found that with situations like this it's easier to fix one off workstations that break due to patching instead of trying to disinfect 500K workstations because they weren't patched.
    22. Re:Please wake up... by Beer_Smurf · · Score: 1

      I hear you.
      How many real remote exploits are there for OSX?
      In asking that I mean actual ones that have infected users computers and don't require local or physical access.
      Seriously, am I looking in the wrong places?

      Thanks
      Trying not to be clueless.

    23. Re:Please wake up... by Anonymous Coward · · Score: 0

      Well, I dunno... Apple's OS X machines are *extremely* predictable, but they're not more vulnerable thereby -- they're typically more secure simply because most stuff is turned off by default. If you turn things on, you at least are more likely to be someone who knows what they're doing.

      It's really puzzling why MS doesn't do this. Is it that hard?

    24. Re:Please wake up... by mi · · Score: 1
      because we are not stupid enough to trust microsoft.[...] around 500,000 desktops/ servers

      I'd say, trusting Microsoft to run half a million computers in a company (even if the real number is a thousand times smaller) is stupid.

      --
      In Soviet Washington the swamp drains you.
    25. Re:Please wake up... by NatasRevol · · Score: 2, Interesting

      Specifically what needs fixing?
      Security.
      What part of Windows' design needs fixing?
      Security issues.
      What part of the base needs fixing?
      All the remote exploits.
      What would *you* do to fix Windows?
      sudo rm -rf /

      Hope that clears it up for you!

      --
      There are two types of people in the world: Those who crave closure
    26. Re:Please wake up... by RickHunter · · Score: 1

      You must admit, however, that killing the network connection DOES close the hole quite effectively!

    27. Re:Please wake up... by RobertB-DC · · Score: 4, Funny

      we have 2 people... 2! and maybe 6 machines to test on... we really need about 5 and 20 machines and 2 servers to test on so we can roll this crap out in a timely manner.

      I get it now. Microsoft isn't the bad guy after all! They're trying like mad to increase your company's staffing by 150%, not to mention the trickle-down effect of quadrupling your machine count.

      Microsoft Windows: It's not a virus portal, it's an employment generator!

      I'm glad Microsoft's doing something about the outsourcing issue.

      (Caution: the above comment contains satire, an element determined by the State of California to cause cognitive dissonance in affected individuals)

      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    28. Re:Please wake up... by goldspider · · Score: 1
      "we are still TESTING that patch because we are not stupid enough to trust microsoft."

      Are you saying then that you don't test Linux patches prior to implementation?

      If you don't, you shouldn't be a sysadmin.

      This is (once again) a non-MS issue, since you should be testing ALL patches. Grandparent is right on. If your company can't adequately roll out patches, that's their fault, not Microsoft's.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    29. Re:Please wake up... by necrotic · · Score: 1

      VPN or not, you should still firewall unwanted traffic coming in via the VPN. If all a user needs is Citrix or RDP traffic to/from their VPN connection, thats all the BOFH should give them...

    30. Re:Please wake up... by Anonymous Coward · · Score: 1, Interesting

      2) Why the fuck is that port turned on by default? What the heck is the service doing? Most users don't use that service so it should be turned off by default. sheesh!

      It's used for filesharing. Chances are that you have used this service. The latest version of Samba even supports sharing files on this port. It's not some obscure port. Best learn what you're talking about before finding fault.
    31. Re:Please wake up... by Cally · · Score: 0, Troll
      we are still TESTING that patch because we are not stupid enough to trust microsoft.
      And yet you are stupid enough to install their software throughout your organisation. So you're stupid AND arrogant. Nice try...

      --
      "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
    32. Re:Please wake up... by Anonymous Coward · · Score: 0

      onghorn better deliver...

      Or what? You going to switch Operating systems? Yeah right. Good luck getting your software and games to run.

    33. Re:Please wake up... by dmomo · · Score: 2, Insightful

      Agreed. This is yet ANOTHER thing that I never understood with MS. Why aren't certain things off by default? I am weary to guess that it is merely oversight. I thought of it, and you thought of it. My boss who knows little of OS security thought of it, I am sure Microsoft has thought of it. But, why aren't they doing it? The must have some reason. It's exactly this that makes me trust them less. What are their reasons?

    34. Re:Please wake up... by slackerboy · · Score: 4, Interesting

      "1000+ systems"
      "Obviousally you run in a very tiny shop."
      " 500,000 desktops/ servers/ etc."

      Something about this exchange just struck me as really odd. So let's be generous and assume that the companies in question have 2 computers for every employee (unlikely). According to this page, that would place the first company in the top 0.306% of businesses in the U.S. and and the second company in the very elite 0.016% of businesses in the U.S.! Tiny shop, my ass.

      --
      Things to do today: See list of things to do yesterday
    35. Re:Please wake up... by Dr.+Evil · · Score: 1

      Those mobile people with their infected machines do occasionally come into the office and plug-in.

      Firewalling all client workstations is pretty new, but with the number of notebooks out there, it is becoming absolutely necessary.

      Wireless technology has already done a good job describing the problem of untrustworthy business-only networks.

    36. Re:Please wake up... by Politburo · · Score: 0, Troll

      we have 2 people... 2!

      Ponderous.. fuckin' ponderous!

    37. Re:Please wake up... by imroy · · Score: 1

      Ok, IHBT:

      Why is it OK for Linux to patch the hell outta itself but a damn near capital crime if Microsoft has to?

      Because patch is the unix/linux tool used to apply a file generated by diff. All our updates are therefore "patches". You non-Unix people latch onto this word and think that Linux programmers and/or users must be constantly running around fixing problems. In reality only a few critical problems with Linux come up each year. Most of the "patches" you refer to are for new drivers or functionality, or more mundane bugs that *don't* open the system up to a remote exploit.

    38. Re:Please wake up... by Anonymous Coward · · Score: 0

      Troll? It's a brilliant reference and I'm sorry that you do not get it. Search for Casey Kasem outtakes..

    39. Re:Please wake up... by Anonymous Coward · · Score: 1, Insightful

      i'm already on a Mac. my work place is 50/50 windows/Mac. where i did my Ph.D. was running UNIX/Linux.

      slowly but steadily, corporations will almost be forced to at least consider non-M$ alternatives if Longhorn tanks. there's only so much they will tolerate. if corporations move away from M$, then so will software developers.

      i'm pretty sure M$ doesn't want to become just a gaming OS...

      if M$ wants to sit and continue to milk $$$ off of their inferior products - that's their decision. however, i'm personally sick and tired of their attitude and practice. get out a product that's worth something. i've decided not to just sit still and accept that there are no alternatives. and i believe others will do the same.

    40. Re:Please wake up... by sangdrax · · Score: 1

      Sounds like you run critical apps on a platform, both made by companies either of which you do not trust to make their software work correctly? If the apps can't stand patching OS security holes, the app doesn't function correctly. If you do not trust MS to make a proper OS or patches to their own software, you shouldn't use their software either.

      Maybe Windows isn't the ideal platform to use, especially if it can be brought down quite easily by such a worm?

      What will you do when the next vulnerability comes out and a patch arrives, say, within the hour? Test for weeks and see your system go down by the next worm? This question seems quite independant of the number of employees in the security and virus teams.

      How does management think about all this? The company is basically a sitting duck.

    41. Re:Please wake up... by Eklypz · · Score: 1

      Our systems admins just tell us to goto the microsoft webpage to download the patches. We are not a small operation either (140,000+ employees). But then again our sysadmin had to ask me how to set up dial-up networking on an unnetworked pc so can't comment too much on their professionalism (I am a lowly business specs writer)

      --
      Life is everything but nothing.
    42. Re:Please wake up... by Alioth · · Score: 1

      If you think local exploits are pretty irrelevant, you're just waiting to be pwn3d. A trivial non-privileged user exploit in say, a CGI or PHP script can be used to attack the local root exploit, especially in a general-purpose webhosting environment. I've had it happen - fortunately, I treat all local root exploits with the seriousness of remote ones, and so the attempt to own my server failed.

    43. Re:Please wake up... by Anonymous Coward · · Score: 0

      You have 500,000 machines and 2 people securing them?

      That is an operation!

    44. Re:Please wake up... by Anonymous Coward · · Score: 0

      If something is one time smaller than a positive number, it's zero.

    45. Re:Please wake up... by Anonymous Coward · · Score: 0

      all it takes is one asshat CTO or CEO or regional VP that ignores the rules and DEMANDS he runs as administrator on his local machine to get infected to hose the whole company.

    46. Re:Please wake up... by Anonymous Coward · · Score: 0

      Sorry, BZZZZT... you lose. most of our machines dont run office and that is it.. we have lots of apps that are specific to our business as we have major problems when a patch screws up an app across the company...

      remember Nt4Sp6 and it hosing lotus notes? so you are fine with taking down ALL email in the company?

      lumpy is right, you really need to learn about large enterprise computing environments... it is VERY different in the big corperate world.

    47. Re:Please wake up... by Anonymous Coward · · Score: 0

      what kind of drugs are you on?

      where the hell do you see linux anywhere in the parent post?? or are you a frothing at the mouth MS lover looking for where opression lives at every turn???

      Microsoft, Linus, Sun, silicon graphics, Hell IBM... trust noone as they did not test on your environment.

    48. Re:Please wake up... by mi · · Score: 1

      5 is two times smaller than 10. 7 is one time smaller than 7. No?

      --
      In Soviet Washington the swamp drains you.
    49. Re:Please wake up... by Anonymous Coward · · Score: 0

      we are not stupid enough to trust microsoft.

      You're running Windows? Then you're trusting M$ to write secure code. That sounds pretty stupid to me.

      we have had many times a patch completely hose several of our critical apps.

      And by not installing this patch, you've now ended up in the same place... what was the advantage of not installing?

    50. Re:Please wake up... by Creepy · · Score: 1

      We have a limited subset of developers/QA/etc get the latest patches and verify none of their tools are affected, so only a few people would need rollbacks, if necessary, not everybody.

      Fortunately for me, I am one of those people - my company was hit by Sasser before 4AM on Friday and I had the patch, unlike most of my coworkers. I had a 6AM meeting that day (one of the "perks" of working with India... groan), and was greeted by a mail system that was shut down and ops people frantically pulling network cables (we had no idea how it spread at the time). The only reason they caught it so early was one of the ops people came in to upgrade our mail server at 4, knowing some employees start at around 6 and found the machine (and others) in the error/reboot state.

      We do that because every once in a while, one of these patches breaks an app or the system. Like the Win 2K Service pack that broke Win 2K when all patches had already been installed. Glad I wasn't the one to find that one out!

    51. Re:Please wake up... by goldspider · · Score: 1
      Quoth the grandparent: "we are still TESTING that patch because we are not stupid enough to trust microsoft", implying that only Microsoft patches need testing.

      So either he is a bad sysadmin who doesn't test ALL patches before implementation, or is simply an intellectually dishonest "frothing at the mouth" Microsoft hater.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    52. Re:Please wake up... by Anonymous Coward · · Score: 0

      And should it be turned on by default? ...

      Silence.

    53. Re:Please wake up... by BigBlockMopar · · Score: 1

      Wake up and smell the damn coffee, it's not a problem exclusive to Microsoft, as much as some of the Linux rah-rah club would like to think. Why is it OK for Linux to patch the hell outta itself but a damn near capital crime if Microsoft has to?

      No, that's right. Linux and *BSD have had root exploits before. But the problem is that Microsoft insists on shipping Windows with all sorts of daemons (ahem... services) running. Each one is a potential exploit; the Microsoft philosophy of run-everything-for-convenience is a lot more dangerous than the Unix philosophy of run-only-what's-necessary. Bugs in code don't get exploited in services which aren't running.

      Microsoft released a patch, people did not install the patch. Who's fault is that? None of the 1000+ systems in my office were infected because I'm intelligent enough to have policies in place to prevent stuff like this from happening.

      You rolled out a patch in 1000+ systems without testing it extensively? Sooner or later, one of those patches will break your 1000+ systems.

      Behind a firewall, thinking you're safe without patching? Sooner or later, someone is going to release a worm which also propagates by e-mail or web browsing (IIRC, Nimda did it) and infects a machine behind your firewall. In a matter of minutes, your entire network will be compromised.

      Either way - when a patch fails and takes out the machines, or when a worm gets into your LAN and takes out the machines - I'd love to be the fly on the wall while you explain to your boss why 1000+ users are out of work for a day or two.

      Your ass would be fired faster than you can say Control-Alt-Delete.

      --
      Fire and Meat. Yummy.
    54. Re:Please wake up... by Phragmen-Lindelof · · Score: 1

      "What would *you* do to fix Windows?"
      Delete it? Open source it but keep the "humor rights" to the source code? Hire virus writers to make Windows a "big league" virus? Make M$ employees rewrite it in APL (one LONG line of code)?

    55. Re:Please wake up... by j4k3 · · Score: 1

      So your saying in your monolithic 500K+ user shop, your running systems on the outer edge with port 445 open? Does that break your 1989 dos app? Or do you just let people randomly connect their laptops to your network?

    56. Re:Please wake up... by Anonymous Coward · · Score: 0

      Yes, why not? It is, however only turned on default for LANs, not for remote connections, dial-up, DSL etc.

      But if you are worried then turn file sharing off. It is very simple. You can also enable the firewall and block traffic too (which you should have done in the first place).

    57. Re:Please wake up... by Anonymous Coward · · Score: 0

      In a matter of minutes, your entire network will be compromised.

      This is why you use internal firewalls and security measures too...

      There is really no need for UserX to have SMB, RPC, Registry or any other access to UserY. That is plain stupid and silly.

      Fix your LANs before you complain to others to fix your problems.

    58. Re:Please wake up... by jack_csk · · Score: 1

      Also, on a Linux system there is no problem finding out what exactly runs,

      Not if your machine has some sort of LKM rootkit installed

    59. Re:Please wake up... by AK+Marc · · Score: 1

      Microsoft released a patch, people did not install the patch. Who's fault is that?

      Microsoft's. The patch had not been out long enough for proper testing before wide-spread deployment by corporations by the time the hole was exploited. Those that did install or test it found that it did crash systems and cause problems. The vulnerability was in Microsoft's code (their fault) over a port that doesn't need to be open in most cases, but is open by default (again, their fault).

      If they were as security conscious as they claim, they would set the OS defaults to more conservative values and have Help let users know how to fix communications problems caused by blocking the incoming ports.

      But is saves them support time (and therefore money) to leave everything wide open and blame exploits on the virus writers, the firewalls, the sys admins, and everyone else.

  21. Re:Windows only by bungley · · Score: 2, Insightful

    Perhaps that MS products are more widely used than anything else?

  22. Interesting way of talking about it. by ActiveSX · · Score: 3, Insightful

    The poster called Sasser a virus, then proceeded to give a definition that said it was not a virus. No offense, but was the poster actually reading what he wrote?

    1. Re:Interesting way of talking about it. by nmg196 · · Score: 1

      No - YOU are not reading what he wrote.

      He said "Sasser, unlike a virus which travels through e-mails and attachments"...

      He did not say "Sasser is unlike a virus."

      It's as though you'd never read past the word virus. There was no comma after the word virus. Perhaps you should read the post properly before flaming it...

    2. Re:Interesting way of talking about it. by br0ck · · Score: 1

      I agree with the grandparent because in the first line that the article poster clearly states that "Yet another virus is causing problems with Internet Explorer". But then then he quotes the sentence from Mcafee that you posted which directly contradicts his lead in sentence.

    3. Re:Interesting way of talking about it. by ultrasound · · Score: 1
      The story poster wrote

      Yet another virus is causing problems with Internet Explorer. "Sasser, unlike a virus which travels through e-mails and attachments, spreads directly from the internet."A removal tool can be found here."

      So (1), I think the grand parent is correct, the poster is refering to Sasser as a virus, but not one that travels through e-mail and attachments. And (2) The story poster is talking absolute bollocks, doesn't seem to have actually RTFA'd anything before posting the story. In particular Internet Explorer plays absolutely no part what so ever.

      And (3) It's you who is posting flamebait and who should read the post properly.

    4. Re:Interesting way of talking about it. by Anonymous Coward · · Score: 0

      It depends how you read this statement:

      "Sasser, unlike a virus which travels through e-mails and attachments, spreads directly from the internet."

      Is "which travels through e-mails and attachments" an unnecessary clause? Strictly speaking, I think that a comma after the word "virus" would indicate that it was unnecessary, but there isn't one there. To me, that implies that the sentence could be reworded like this:

      "Sasser is unlike other viruses because it spreads directly from the internet rather than travel through e-mails and attachments."

      Then again, commas are a lost art these days, so who knows what the original writer was thinking. I'm not a grammarian, so please forgive me if I used any incorrect terms.

  23. Re:Windows only by AriesGeek · · Score: 1, Troll
    What does this tell us about MSFT products?

    It tells us that since Windows is the most widely-used (and since there are a lot of anti-Microsoft zealots), it is the favorite target of script kiddies. If Linux were the most widely-used OS, it would be the one attacked all the time.

    Read CERT. There are just as many linux-related vulnerabilities as Windows. (think: OpenSSL).

    --
    Insert offensive troll-style sig here. Please mod or respond appropriately.
  24. It's not a virus by Anonymous Coward · · Score: 0

    Sasser is not a virus as the poster stated, it's a worm.

  25. Could Sasser possibly affect Linux? by Debian+Troll's+Best · · Score: 4, Interesting

    From my understanding of the Sasser worm, it infects vulnerable Windows PCs by probing and connecting through a specific open port, and then launching some Windows specific code designed to infect and propagate the worm. My question is of a largely theoretical, yet insightful nature: if a Linux machine is running a Windows emulation environment, such as WINE, and the Sasser specific port is open, is it possible that Sasser could attack and infect the Linux PC? After all, if WINE is at a level of compatibility which allows Linux users to run complex Win32 apps such as Microsoft Office, is it also not inconceivable that some Windows vulnerabilities have been emulated also? I look forward to the community's response.

    1. Re:Could Sasser possibly affect Linux? by Aliencow · · Score: 5, Informative

      You would have to run the LSASS Service under Wine...and I don't know why you would want to do that !

    2. Re:Could Sasser possibly affect Linux? by Lumpy · · Score: 1

      a VMWARE machine CAN get infected if the host machine is not properly configured.

      in fact we use VMWARE on linux machines here to test , poke and prod virii on a test lan here... it's kinda neat to be able to easily sniff the traffic coming into that virtual windows PC and watch the bugger do it's job.

      --
      Do not look at laser with remaining good eye.
    3. Re:Could Sasser possibly affect Linux? by Anonymous Coward · · Score: 0

      You'd just mess up WINE, if anything, which I highly doubt to begin with. You aren't going to see your linux machine rebooting.

    4. Re:Could Sasser possibly affect Linux? by penguinbrat · · Score: 1

      First - in a since all ports on Linux are open by default. However, apparently unlike M$ - an application (server,daemon,etc..) needs to be listening on that specific port - otherwise you get the infamous message "Unable to connect to remote host: Connection refused" I'm sure that M$ has the same type of basic structrure but it seems like they have many more open and insecure ports (something listening on them). Linux by default doesn't have that many, IE - mine only has sshd and cupsd (no I have not "secured" my box), hence the only way to get into the box is through one of those two server daemons.

      Second - While using Wine, the application and environment is executed by a specific user - likewise the application will inherit the user's environment (permissions, umask, etc..) so even if the app was written for Linux (modifying pam or something) the executing environment (via the offending user) would HAVE to have to the apropriate permisions - unless explicitly modified, only ROOT has such permisions usually. (note - that vmware is still vulnerable because it runs the actual OS, but it will NOT effect Linux)

    5. Re:Could Sasser possibly affect Linux? by necrotic · · Score: 2, Interesting

      I have sucessfully had a virus run under Wine. It was not sasser, and was not tcp port based however. Launched an infected exe from Thunderbird to see what would happen, Wine took over and ran it. THe virus scanned my networks SMB shares, and collected email addresses. It also spawned its own SMTP engine and proceeded to send itself to the collected addresses.

      When you think about it, Wine should have no trouble running simple applications such as this. It only seems to bawk when applications use non conformant GUI methods or non-standard network operations / file access methods...

      No patches for this one, just kill -9 :)

    6. Re:Could Sasser possibly affect Linux? by Naffer · · Score: 1

      So I fire up my properly patched WinXP box and run "netstat -a." Ports 59, 1025, 1034, 1035, 1039, 1379, 3366, 4361, 5000, and 30515 are all listening. Port 59 is my mirc client, but why good are the rest of those to me? Rather then shipping with everything on, XP should ship with everything off and ask the user. Unfortunatly, most users wouldn't know what to do if windows presented the option "Would you like to enable the LSASS.EXE Local Security Authority Service?"

    7. Re:Could Sasser possibly affect Linux? by 13Echo · · Score: 2, Interesting

      I've actually attempted to run a few viruses on my Slackware machine, through WINE, without any success. This was simply for testing purposes. In many cases, the environments are just too different for the virus to function properly. WINE often crashes in this case. Even then, Linux doesn't automatically load any of the the WINE "emulation layer" code on system startup, and only loads it when you run WINE. Still, WINE is not run as root (unless you are stupid), and anything that could possibly damage the machine would be restricted to a user's home directory, unable to affect the actual Linux OS and libraries, or the critical WINE stuff.

      Sasser is a worm that requires access to port 445 and needs to hit a machine that runs the LSASS authentication code on Windows machines (which WINE doesn't use). As someone mentioned, it might be possible to run LSASS in some form or fashion, but there would be no reason to do it.

    8. Re:Could Sasser possibly affect Linux? by spitzak · · Score: 2, Interesting

      Wine is not listening to that port without a lot of elaborate setup.

      However there certainly are examples of Wine successfully running .exe files imbedded in virus email and actually emailing copies out. And even doing this without the user knowing (they clicked on the exe just like a Windows user).

      Probably more of a concern is that I know that a Linux machine's disk can be trashed by a Windows virus. It wrote over the files right over NFS (or perhaps over Samba to a server that then went to this machine via NFS).

    9. Re:Could Sasser possibly affect Linux? by Anonymous Coward · · Score: 0

      Great, so Windows takes it up the LSASS?

    10. Re:Could Sasser possibly affect Linux? by jack_csk · · Score: 1

      Nothing is funnier than running these old DOS viruses such as walker and ambulance using vmware or virtual pc.

  26. The UK Coastguard has been hit. by levell · · Score: 3, Interesting

    All the computers the UK Coastguard use have beeen affected according to this BBC story

    --
    Struggling to find a day everyone can make? WhenShallWe.com
    1. Re:The UK Coastguard has been hit. by Theresa1 · · Score: 1

      Oh dear! there goes my afternoon swimming session then.

      --
      This is a manual signature virus. Copy to your signiture file and help me spread.
    2. Re:The UK Coastguard has been hit. by CPlusPlusOwnsYou · · Score: 0

      What the heck are the doing running Windows boxen anyway? And how about firewall? All you have to do is block port 445.

      --
      "Software is like sex: it's better when it's free."
    3. Re:The UK Coastguard has been hit. by archen · · Score: 1

      Pirates run wild. CD burner sales on the rise. News at 11.

    4. Re:The UK Coastguard has been hit. by real_smiff · · Score: 1

      oh great. so far from having no effect "other than rebooting machines", as some were saying/assuming, this is potentially costing lives (like flight controllers, they are trained to use paper backup systems, but this has got to be less efficient, or of course, they wouldn't use computers). The coastguards are great people, highly stretched, with less resources than many companies. Do we need a better demonstration of why these things are serious? (Note i'm not attributing blame here).

      --

      This is my Sig, this is my Gun. One is for Slashdot and one is for Fun.

  27. Another reason to click..... by Tangwei · · Score: 0

    Can't wait to get the phone call from my mom... "So now that I can get a virus/worm from doing nothing... can I click on that screen saver that nice man from Nigeria sent me?"

  28. Gentlemen... by mattgreen · · Score: 0, Redundant

    Let the condescending remarks about operating systems begin!

  29. Sass back by PriceIke · · Score: 1, Funny

    > Poor programming by Sasser's creator makes > infected machines shut down. I love it .. dissing the worm's creator IN THE NEWS STORY. I'm sure whoever it is was happy to read that.

    --
    It's not a lie. It's the truth with lossy compression.
    1. Re:Sass back by Anonymous Coward · · Score: 0

      I can't be all that bad, considering. I mean, how do you rate virus success?

    2. Re:Sass back by surprise_audit · · Score: 1

      I think that trend started at least as far back as the Morris worm in 1988. Several teams of researchers began converting the worm code back into compilable source form. They found a number of bugs and, IIRC, even posted bug fixes.

  30. Not exactly a 0-day exploit by Zog+The+Undeniable · · Score: 4, Informative
    If you applied last month's critical patches OR you have a working firewall - even the basic XP one - you won't get it.

    Everyone with a Windows machine should sign up for MS's monthly security e-mail or religiously check Windows Update on the second Tuesday of each month. I won't go as far as recommending automatic updates, though.

    --
    When I am king, you will be first against the wall.
    1. Re:Not exactly a 0-day exploit by Paulrothrock · · Score: 1
      Everyone with a Windows machine should sign up for MS's monthly security e-mail or religiously check Windows Update on the second Tuesday of each month. I won't go as far as recommending automatic updates, though.
      Or switch to a better OS. But I don't think the corporate masters would like that.
      --
      I'm in the hole of the broadband donut.
    2. Re:Not exactly a 0-day exploit by Proaxiom · · Score: 4, Informative
      An unfortunate factor of this worm is that the patch that fixes the exploited vulnerability - MS04-011, has been found to have stability problems and other issues in the field.

      This has caused many administrators to be hesitant to install it. Bugtraq had a discussion of the problems in April.

    3. Re:Not exactly a 0-day exploit by ConceptJunkie · · Score: 2, Insightful

      Yeah, but Joe Twelve-pack won't have his XP firewall turned on if he doesn't know to enable it... at least not until XP service pack 2.

      Could all virus and worm writers just lay off for a couple months? Thank you.

      Forget bad coding for a minute... Microsoft wouldn't have half the problems they have if they would simply not choose the most perversely stupid default settings.

      --
      You are in a maze of twisty little passages, all alike.
    4. Re:Not exactly a 0-day exploit by Drunken_Jackass · · Score: 1

      Too right. We patch all of our machines using our own window update server - it's really the best way we've found to handle this type of situation. We've got it set up to synchronize with the Windows Update servers every night, and Group Policies make sure that everyone's machine checks our update server every day at noon to make sure they have the appropriate patches (BTW - Windows 2000 has had over 1800 patches and security fixed put out for it!!).

      Now, having said that, I still get many, many hits every day on my SuSE box at home from people infected with Code Red.

      Just because we may be secure, doesn't mean that half of the corporations and 99% of home users are.

      --
      There are 01 types of people in this world. Those that understand binary, and me.
    5. Re:Not exactly a 0-day exploit by watermodem · · Score: 1

      I have seen viral spam mail that forges Microsoft headers and subject lines of their security e-mail. My spam blocking in mozilla, now ... after training ... , properly identifies MS mail as SPAM!

    6. Re:Not exactly a 0-day exploit by SlashDread · · Score: 1

      Mr Patch Nazi.

      Not zero day no, more like a whole week. By the way, the patch just BSOD my NT 4 TS server.

      We were hit, 4 laptops XP infected, TS, and we DO autoupdate patches vis SUS.

      How do you suppose your commentrs help me?

      "/Dread"

    7. Re:Not exactly a 0-day exploit by BokLM · · Score: 1

      I wonder how MS create their patch. Do they add new features in their patchs ?

      What I like with Debian GNU/Linux and most others Linux distributions is that when there is a security vulnerability found in a program, they provide updated packages. But the new packages do not upgrade the program to a newer version, but instead they backported the fix to the same version in order to avoid any problem. The update does not give you any new feature but only correct the vulnerability.

      If you're running à Debian Stable you can even put automatics updates every day whithout too much risk (it's still better if you can check that everything is ok, but problems are very rare).

      The other good thing is that _any_ program installed using the package system will be updated if some day a vulnerability is found.

    8. Re:Not exactly a 0-day exploit by TheZax · · Score: 1


      If you applied last month's critical patches OR you have a working firewall - even the basic XP one - you won't get it.

      That's an oversimplification. There are plenty of ways that it could slip behind a corporate firewall: laptops that go home and come back, VPNs, dial in users, etc. If you just have a firewall and nothing else, you have a false sense of security.

      --

      JWall: GUI client for IPTables
    9. Re:Not exactly a 0-day exploit by teridon · · Score: 1
      ... or religiously check Windows Update on the second Tuesday of each month.

      The problem with Windows Update, is, well, it doesn't always work! For example, a local system admin ran WU two weeks ago (April 15th and 16th, to be exact) on all the Windows machines in my office. On Friday the 30th, two of them were found to be infected with something that exploited the vulnerability in ms-its patched by MS04-013.

      When I checked, I found that it had not been installed, because Windows Update did not report it as a needed update.

      In other words, Windows Update is practically useless.

      --
      I hold it, that a little rebellion, now and then, is a good thing. -- Thomas Jefferson
    10. Re:Not exactly a 0-day exploit by mangastudent · · Score: 1
      If you applied last month's critical patches OR you have a working firewall - even the basic XP one - you won't get it.

      Until someone brings in an infected laptop....

      Unfortunately a basic firewall setup is a "crust" defense; get past the one layer of protection and it's all over. That's why "defense in depth" is such a big deal.

      (In this case, applying patches as fast as practical to the machines you haven't been able to switch to something other than Windows, per-machine firewalls if you can deal with the hassle, multiple internal firewalls if you're big enough, and of course business continuity plans (can't emphasize that enough, so many things can take out e.g. your server room; e.g. is there a bathroom above it, kitchen below it? etc.)

    11. Re:Not exactly a 0-day exploit by Anonymous Coward · · Score: 0

      Everyone with a Windows machine should sign up for MS's monthly security e-mail or religiously check Windows Update on the second Tuesday of each month.

      Personally, I just religiously sit back and let these things bounce off of my OpenBSD firewall.

    12. Re:Not exactly a 0-day exploit by CowboyBob500 · · Score: 1

      See this is what I don't understand. You're patching to fix a bug in LSASS and the consequence is "You cannot view enhanced metafile format graphics files (or EMF image files) that were created in Adobe Illustrator".

      How the hell does that happen? This is dependencies gone mad.

      Bob

    13. Re:Not exactly a 0-day exploit by Sj0 · · Score: 1

      I'm no computer scientist, but if one OS is used by 90% of the world, and gets 99% of viruses, perhaps the discerning computer user should look into alternatives, rather than spending every waking moment hammering boards over the windows(metaphorically speaking, of course)?

      Not every alternative OS to Windows is made by a large group of volunteer CS students either.

      --
      It's been a long time.
  31. IE? by BenBenBen · · Score: 5, Insightful

    What the hell has a worm that attacks through non-HTTP traffic and downloads its body through a built-in FTP client got to do with Internet Explorer?

    If you're going to bash Microsoft, at least bash the right frickin' part...

    --
    The Slashdot Paradox: "100% Overrated"
    1. Re:IE? by Anonymous Coward · · Score: 0

      My thoughts, exactly.

    2. Re:IE? by Rick.C · · Score: 1
      If you're going to bash Microsoft, at least bash the right frickin' part...

      Microsoft is like the Sta-Puff Marshmallow monster from Ghostbusters -- it's huge and it's hard to know where the right frickin' part is located.

      So we always aim for the eyes.
      --
      You were 80% angel, 10% demon. The rest was hard to explain. - Over The Rhine
      "Math in a song is good."-Linford
    3. Re:IE? by phyruxus · · Score: 1
      >> If you're going to bash Microsoft, at least bash the right frickin' part...

      Marketing?

      --
      "A witty saying proves nothing." ~Voltaire
      "d'Oh!" ~Homer
  32. UK Coastguard Effected by Anonymous Coward · · Score: 0

    The UK coastguard is severly effected. Shouldn't this be an easy sell for Linux.

    Thinking about emailing them, but they probably have their hands full.

    1. Re:UK Coastguard Effected by Anonymous Coward · · Score: 0

      The UK coastguard is severly effected. Shouldn't this be an easy sell for Linux.

      I only have 5 words for you right now; NO!

  33. Nothing to do with IE by Anonymous Coward · · Score: 0

    The /. item is wrong in associating this worm with Internet Explorer. It's a direct attack on Windows, not a flaw in IE (or Outlook Express). And, for once, it doesn't seem to have an email vector.

  34. Took out a coast guard station by Anonymous Coward · · Score: 0

    mapping systems. Luckly those people still knew how to use old fashioned maps for emergencies.

    I wounder how people will survive in a few decades when everything is dependent upon the computers; then out of knowwhere a virus takes out systems. Can people still know how to go old skool to fix problems?

  35. quick and cheap fix by Anonymous Coward · · Score: 1, Insightful

    Here is a fast, cheap and reliable way to fix this problem:

    * Buy a hub/router with builtin firewall for about $40 to $80.
    * plug it in.

    There you go.

    1. Re:quick and cheap fix by Paulrothrock · · Score: 1

      Forgot one step

      * Change the default admin password.

      --
      I'm in the hole of the broadband donut.
    2. Re:quick and cheap fix by Anonymous Coward · · Score: 0

      Hehehehe. I stand appended :P

    3. Re:quick and cheap fix by Anonymous Coward · · Score: 0

      * Wonder why no one can connect to you, so you forward all ports to your box...

    4. Re:quick and cheap fix by Haydn+Fenton · · Score: 1

      ..and here's an even cheaper, more reliable fix.

    5. Re:quick and cheap fix by schon · · Score: 1

      .. which works great until someone connects their infected laptop to the network.

      And then the person who though that a $40 'firewall' wonders how the hell it got through their '1337' security system.

      Your solution isn't a fix, it's (at best) a temporary workaround.

    6. Re:quick and cheap fix by thogard · · Score: 1

      You buy one $40 firewall for all the lusers.

    7. Re:quick and cheap fix by Anonymous Coward · · Score: 0

      I plugged it in, but still got infected!

      Do you think maybe I need to run the network connection through it or something?

      Thanks.

  36. Re:Windows only by Paulrothrock · · Score: 2, Informative

    Wrong again. Apache has the largest market share in HTTP servers, and it's not the most hacked.

    --
    I'm in the hole of the broadband donut.
  37. Re:Windows only by Anonymous Coward · · Score: 0

    I think it is a given that most worms and such now are windows, and mac and linux (all other unix's included) are worm free by nature.

    Note the word worm....

  38. Re:Direct? by orbit0r · · Score: 5, Informative

    What could be more "directly from the Internet" than email?

    An exploit connecting directly to port 445 of a host and not requiring any user-intervention to become infected.

  39. How Long by tacocat · · Score: 1

    I was reading the article from the BBC. How many key services of the society must be crippled before those in charge start to realize that Microsoft, while pleasing to the eyes and well marketed, just isn't suitable for anything that matters.

    When someone can crash a railroad system from a virus, we have a problem. What would Benito Mussolini have said when his trains were running late because of yet another worm? How many railroad operators would have died?

    1. Re:How Long by Tangwei · · Score: 0

      And just think, if Microsoft wasn't around we'd still be able to buy the new Prince of Persia on 5.25 for our Commadore 90's.

    2. Re:How Long by steve.m · · Score: 1

      How many key services of the society must be crippled before those in charge start to realize that Microsoft, while pleasing to the eyes and well marketed, just isn't suitable for anything that matters.

      It's not just the software (It ceartinly doesn't help that it's full of holes), it's bad implementation - if you're stupid enough to connect a box directly to the internet, you deserve everything that's coming to you.

      Linux & *BSD users can be smug here, as they are secure out of the box. Windows 2K & XP include a no-frills firewall, it's just not enabled by default...

    3. Re:How Long by Anonymous Coward · · Score: 0

      What would Benito Mussolini have said when his trains were running late because of yet another worm?

      He would have said, "Last week, you said it was leaves on the track; the week before because you had to go to your cousin's wedding; the week before that because your Grandma was ill; the week before that, you lost the timetable; the week before that...."

    4. Re:How Long by tacocat · · Score: 1

      Not quite. He got the trains on time by executing the engineers if they were late.

  40. Re:M$ - First Post? by basil+montreal · · Score: 4, Insightful

    It's a strange problem, security. Educated users are key, but because Microsoft has the largest market share, they also get the largest number of uneducated users. What will happen if Linux eventually completely replaces MS products on the desktop? Will they have the same security problems?

  41. Re:Direct? by kunudo · · Score: 1

    Port knocking?

  42. Re:Windows only by YellowElf · · Score: 1

    That they're more popular than Linux and Mac machines, and make a better dispersion vector?

    --
    Insert witty saying or aphorism here.
  43. firewall to the rescue by steve.m · · Score: 4, Informative

    It looks like it exploits LSASS.EXE by scanning for a listening port 445. Good job I've got all incoming blocked by default.

    Roll on XP SP2 with the firewall on by default for everyone, then hopefully things like this will go away....

    1. Re:firewall to the rescue by Scutter · · Score: 1


      Roll on XP SP2 with the firewall on by default for everyone


      Yeah, what could possibly go wrong? ;-)

      --

      "Tell me doctor, with all of your defenses, are there any provisions for an attack by killer bees?"
    2. Re:firewall to the rescue by Gaima · · Score: 1

      You can hope until the cows come home my friend.
      But Service Pack or not, update or not, these problems aren't going to go away.

      A person can be smart, intelligent, and logical.
      People are stupid.

      For exploits like this it's mom and pop who are the biggest problem, and they are highly unlikely to even know what Windows is! Let alone give the slightest thought to computer security.

      Until we have some cataclysmic event, and humanity has to start over, Microsoft will be the bane of the internet :)

    3. Re:firewall to the rescue by NatasRevol · · Score: 1

      Why do WE have to have a cataclysmic event?

      Why can't Microsoft? And, in a perfect world, it should involve all of their production machines being wiped clean by the latest virus.

      That way, humanity (including me!) is still around and the internet is a much nicer place to be.

      --
      There are two types of people in the world: Those who crave closure
    4. Re:firewall to the rescue by isorox · · Score: 1

      You're assuming people will install SP2

    5. Re:firewall to the rescue by bryhhh · · Score: 1

      A firewall is a poor substitute for patching.

      If users would simply run windows update and download a ~1Mb patch, then this worm would not be a problem.

      If these users can't be bothered to download and install a 1Mb hotfix, what are the chances of them downloading and installing a service pack that is > 250Mb?

    6. Re:firewall to the rescue by Spoing · · Score: 1
      1. Roll on XP SP2 with the firewall on by default for everyone, then hopefully things like this will go away....

      Stop relying on firewalls. Remove the services entirely!

      Nessus, Dependency Walker, and a dozen other tools to examine your machines are much more effective.

      If it's not running it can not be exploited!

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    7. Re:firewall to the rescue by Mesaeus · · Score: 1

      That's why the smart thing to do is to use as many security approaches at the same time as possible. Get a virus scanner, making sure it's updated as fast as possible. Get a firewall, a hardware one preferably but a software one is better than nothing. Make sure the hardware firewall is also up to date in firmware/patches, and get regular updates for the software one too. Install a spyware scanner to deal with that kind of dirt accumulating, because the sheer number of badly programmed spyware can bring an otherwise clean box to its knees. Finally, try to keep up to date with Windows patches, even if you have to unroll the occasional unstable patch.

      This is what I use for any of my clients, and it does work since I usually spend my time during "major" virus/worms outbreaks by reading/posting on slashdot, instead of trying to dam a tidal wave of computer and network troubles. When a worm like this hits, I have the time to check on all my clients, in my own tempo, in order to make sure their patches are still up to date. Because the firewall is temporarily protecting them from the exploits, I can do this without them even noticing there is some kind of worm epidemic going on (until they read the papers and call me asking why they don't have problems while the firm next door had to close, some of them even think it's suspicious that they're not getting hammered :D).

      I still have to get out once in a while, but instead of racing to limit the damage to my clients, I can keep myself to merely maintenance, and they don't lose time and money while I do it.

      Sure, someday something will come out which bypasses all my security measures, but I can rest safe in the knowledge that at that point I can immediately deal with that (hopefully rare) situation, instead of having to first make time between cleanup rounds of previous virusses/worms.

      You cannot expect to be forever free of these kinds of threats, but you sure can limit the amount of work by taking some preventive measures and trying to approach the problems from as many angles as possible. There is a huge difference between one major virus incident in three years an one every tree months.

    8. Re:firewall to the rescue by maximilln · · Score: 1

      -----
      Get a virus scanner, making sure it's updated as fast as possible
      -----
      Autoupdate features are just as likely to provide a route of entry.

      -----
      Get a firewall, a hardware one preferably but a software one is better than nothing
      -----
      Hardware firewalls are pretty nice. They suck if someone ever does figure out a hardware exploit. Software firewalls can give a false sense of security unless it's iptables--You just have to learn something of the way connections are made and tracked to use it. I'm not saying that ZA and Norton and the others are worthless but, in order to be usable by a typical customer, they're not very secure. It'd be easy for a virus to tell the firewall "hey! I'm telnet.exe. Give me an outgoing port and an incoming port!" Most firewalls, on Windows, automagically scan the machine for potential network apps to minimize headaches for the user. Compound that with all the apps that want autoupdate or network play. So many potential holes.

      -----
      Install a spyware scanner
      -----
      I agree in principle. Something in the back of my head makes me think about radar companies and radar detectors. They're all owned by the same people who have patents on the same technology.

      -----
      even if you have to unroll the occasional unstable patch
      -----
      This is why I distrust the Windows registry. How can one guarantee that it doesn't leave reg keys behind which may open possibilities for future exploits? On my *nix, if I kill an app, I know that it hasn't left junk around which may compromise the function of other things. As Mozilla, Gnome, and KDE get larger, though, this will soon become a problem for Linux as well.

      --
      +++ATHZ 99:5:80
    9. Re:firewall to the rescue by Anonymous Coward · · Score: 0

      A firewall is a poor substitute for patching.

      A real admin knows that one is not any kind of substitute for the other. When most effective, they work hand-in-hand. You can't expect to get every single patch or block every single packet of traffic you want, but when you are proactive on keeping up with both of those (in addition to other daily admin duties) then it is not that difficult.

    10. Re:firewall to the rescue by Your+Average+Joe · · Score: 1

      you moron, sp2 is not out yet. pull your head out.

      --
      Your Average Joe
    11. Re:firewall to the rescue by jack_csk · · Score: 1

      Since most ./ers are using high speed internet connections, they forget that most people out there are still using dialups.

      I recalled at the time when I was using dialup, I didn't do windows update as often as I am right now. Someone may suggested to config windows to download updates automatically on schedule, but most people are gonna to think that it will slows their internet connection down.

  44. Yay... by Anonymous Coward · · Score: 0

    Just added another virus removal tool to my startup folder! Its starting to get big and unmanagable, I am thinking of putting it on a seperate partition...

  45. Re:M$ - First Post? by Anonymous Coward · · Score: 1

    one thing about that chocolate ... how do we know the password is legit? If someone came up to me offering chocolate for a password, I could easily make up some random sequence of alphanumerics and get the candy.

    example: when i was at university, there were frequently marketers out pushing credit cards to students by offering up a free gift (eg, a hat, t-shirt, some other corny thingy) in exchange for filing an application. many students got the gift by filling in dummy info for the credit card application.

  46. Heard of a firewall? by Anonymous Coward · · Score: 0

    Any site that gets slammed by this needs to fire their network admin.

    1. Re:Heard of a firewall? by SiggyRadiation · · Score: 5, Insightful

      A. Guy takes home corporate laptop.
      B. Plugs laptop into phone-line / uses internet
      C. Gets infected
      D. Takes his laptop back to the job
      E. Infects the entire LAN *FROM THE INSIDE* while the firewall hapilly keeps the fire "IN" (instead of out).

      If you fire anyone, please fire the laptop-owner.

      --
      This unique sig is intended to make this user more recognisable.
    2. Re:Heard of a firewall? by abb3w · · Score: 1

      If you fire anyone, please fire the laptop-owner.

      You might consider firing the person whose responsibility it was to make sure Critical Updates got applied to that laptop.

      --
      //Information does not want to be free; it wants to breed.
    3. Re:Heard of a firewall? by StrawberryFrog · · Score: 4, Insightful


      A. Guy takes home corporate laptop.
      B. Plugs laptop into phone-line / uses internet
      C. Gets infected
      D. Takes his laptop back to the job
      E. Infects the entire LAN *FROM THE INSIDE* while the firewall hapilly keeps the fire "IN" (instead of out).

      This actually happend to us last year.

      If you fire anyone, please fire the laptop-owner.

      Uh, problem being that it's good odds that the laptop owner is the boss of the people wanting to fire someone.

      --

      My Karma: ran over your Dogma
      StrawberryFrog

    4. Re:Heard of a firewall? by MCraigW · · Score: 2, Interesting

      The company for which I work requires anything that ever connects to the internal network to have a personal fire wall installed.

      We also require the installation of a service that installs various updates (Microsoft and others) after they have been approved by a team that installs and tests them.

      We have around 36,000 employees world wide, and this virus hasn't affected us.

    5. Re:Heard of a firewall? by Anonymous Coward · · Score: 0

      fire the laptop-owner?... being the company that owns the laptop. Ookay.. lets keep going.

      1) The IT support team must have left all internal computers vulnerable by not patching them.. which may be understandable since sometimes patching BREAKS systems, especially custom systems. Fire them.

      2) The managers who decided to use Microsoft products, and/or ensure their entire corporation uses Microsoft products exclusively, ie no computer left standing. Fire them.

      3) The worker/s, who decides to do more work for the company in their own time, and by mistake introducing the worm. Fire them.

      Therefore, fire the corporation.

      Great! and get new 'green' staff.. their inexperience and eagerness to work will ensure they all take the laptops home.

      You must be a manager if you want to fire the worker for working hard. I bet you're the same guy who decided to 'retire' the patching guy, and 'get a discount by exclusively using Microsoft'..

    6. Re:Heard of a firewall? by Anonymous Coward · · Score: 0
      If you fire anyone, please fire the laptop-owner. [Disclaimer]: I work for managed security services supplier. We sell lots of firewalls and consultancy. [/disclaimer]

      No, you should fire the network manager or IT director for failing to anticipate this perfectly well-known and understood scenario. Either don't allow laptops to be plugged into your internal network or use some technology to extend your administrative control over those laptops wherever they happen to be. Hint to the iptables fans: Checkpoint SecuRemote VPN client allows you to tell it to (amongst other things) check the local client a/v software is up-to-date, block any traffic to the machine except that via the VPN, check a very large and granular subset of local system configuration knobs and lots of other stuff. We have remote workers all over the place, connecting over DSL, cable broadband, dialup etc from many different NSPs. They are all fine, as are all our customers who asked for and then took our advice on this issue.

      I'd still recommend using Linux personally cos you can then save all the money you spend trying to plug the leaky dyke of WIndows, but that's just me ;)

    7. Re:Heard of a firewall? by Anonymous Coward · · Score: 0

      9. sysadmin installs firewalls on all laptops.

    8. Re:Heard of a firewall? by Anonymous Coward · · Score: 0

      You might fire the "security professional" who didn't take the A.-E. scenario into account when designing the firewall, which, we remember, is the POLICY and the SYSTEM(S) required to implement the policy. Geez, this hoo-ha is the result of incompetent dolts, Microsoft and others. It's also a cheap-shot attack. What if someone clever actually starts looking at how to attack layer one, two, three in an organized manner, eh?

      And what eediot allows employees to extend their security perimeter to the local coffee shop, phone line, Internet at large, ...? Fire everybody.

    9. Re:Heard of a firewall? by KevinKnSC · · Score: 2, Insightful
      If you fire anyone, please fire the laptop-owner.

      How about firing the genius who lets laptops connect directly to the internal network? It's a laptop, the whole point is that it's portable. It should be assumed that it will be taken somewhere else and connected to untrusted networks. At your facility, you should connect laptops to a purgatorial network between firewalls, so that they're protected from the outside world but don't have unrestricted access to everything on the inside. It's just common sense.

    10. Re:Heard of a firewall? by avandesande · · Score: 1

      This is how that nuclear reactor network was infected from the inside.

      --
      love is just extroverted narcissism
    11. Re:Heard of a firewall? by dcam · · Score: 1
      --
      meh
    12. Re:Heard of a firewall? by Anonymous Coward · · Score: 0

      Uh, problem being that it's good odds that the laptop owner is the boss of the people wanting to fire someone.

      Then SET him on fire damnit!

  47. Microsoft: crime-ridden slums of computing by kherr · · Score: 2, Insightful

    It is very apparent that using Windows is like living in a high-crime, blighted neighborhood. You try and try to live a normal life but at any moment something bad could come along.

    Why people continue to choose Windows is beyond me. Linux and Mac OS X are more secure and more powerful. And oh yeah, cheaper. Sure you get Windows when you buy a new machine. But that's like offering a poke in the eye with a pointed stick with every purchase.

    1. Re:Microsoft: crime-ridden slums of computing by Jaeph · · Score: 1

      Because City of Heroes doesn't run on *nix.

      Until the games I play are both available on *nix and run as well, I'll always have a windows box.

      -Jeff

      --
      Please learn the difference between a dissenting opinion and a troll before you moderate.
    2. Re:Microsoft: crime-ridden slums of computing by Frizzle+Fry · · Score: 1
      It is very apparent that using Windows is like living in a high-crime, blighted neighborhood... Why people continue to choose Windows is beyond me

      For the same reason that many of us choose to live in the city where the other people are and where there are things to do, rather than in a bunker in the middle of the desert many, many miles from civilization, where we could feel secure because we are far away from everyone else (and thus the crime).
      --
      I'd rather be lucky than good.
  48. Re:Direct? by gunnk · · Score: 5, Informative

    Email gets picked up by your email client. An email virus must then be run from the message either by opening the attachment or (for some Outlook versions) by having Outlook open it for you. Even just receiving a copy of an email virus requires that you run your email client.

    In the case of the Sasser worm, it is using an open port to crawl directly into your computer when you connect to the internet. There is no action required on the part of the user and no infected file to load. Windows simple accepts the connection and installs the worm.

    That's why worms are "more directly from the internet" than email-based viruses.

    --
    Life is short: void the warranty.
  49. Re:Windows only by Anonymous Coward · · Score: 0

    what kind of idiots marked the parent "flamebait"? Seems like a pretty honest, straightforward, reasonable comment to me???

  50. Correct attribution by Anonymous Coward · · Score: 1, Informative

    I think it's important that we all recognize Microsoft's role in this and always refer to these worms as "Microsoft(R) Windows(TM) $(wormname)", in this case the worm is called the Microsoft(R) Windows(TM) Sasser Worm.

    This way people won't get confused as for which platforms are compatible. Thank you.

  51. Re:Windows only by Anonymous Coward · · Score: 0

    It tells us that a lot more people uses Windows that Linux. It's just showing a lack of understanding for the whole problem, to say that this shows that Linux is better than Windows.

  52. Re:Internet Explorer ? by Anonymous Coward · · Score: 0

    I thought the same thing... Has nothing to do with IE. Read the articles to double check. Has nothing at all to do with IE.

  53. Yeah, I'll run that removal tool. by pschmied · · Score: 5, Insightful

    I'm not sure why everyone is so hopped up on these removal tools. It seems to me that after being infected with a worm that installs a back door, more people ought to look at reinstallation from known good media.

    Biggest Windows vulnerability ever, again. How many times have we said that this year? At work, it's begining to feel a bit like a duck and cover drill.

    -Peter

    1. Re:Yeah, I'll run that removal tool. by the+grace+of+R'hllor · · Score: 2, Interesting

      Of course, why don't we all just toss out our E-mail, address books, bookmarks and 'special files' three times a month?

      While all those things can be backed up, practically noone actually does this, and so keeping a system running is top priority.

      Besides which, 'known good media' means 'unpatched windows'. A pre-SP1 WinXP takes about 15-30 seconds from first connect to infection with MSBlaster, even nowadays. What you want people to have is a during-install-service-pack-update.

    2. Re:Yeah, I'll run that removal tool. by nevets · · Score: 1

      OK, its been a long time since I used Windows, but I would assume that you can partition it like you can in *nix. I have a /home partition and a /usr/local that has stuff independent from the OS. This is where I keep all personal data and the like. Sometimes I get tired of the distribution I'm using and decide to change (SuSE to RedHat to Debian), and I have no problems in installing. I just blow away the OS partitions and start again, keeping all of my person stuff from one distro to the next.

      I'd be shocked if the same can't be done with Windows. So if I had a Windows box that was infected, I'd just reinstall, if it is possible to keep my personal stuff. But like I said, I don't use MS Windows.

      --
      Steven Rostedt
      -- Nevermind
    3. Re:Yeah, I'll run that removal tool. by happyfrogcow · · Score: 1

      any way to do a remote BSD install after saying over the phone, "hey mom, put that CD marked BSD into your CDROM tray and reboot the computer. What? Satan? Oh, the little daemon. Yeah, just ignore all demonic references... No mom, i'm not worshipping Satan. No mom, I havn't been outside all week."

      i kid, i kid!

    4. Re:Yeah, I'll run that removal tool. by Ytsejam-03 · · Score: 1
      Biggest Windows vulnerability ever, again. How many times have we said that this year? At work, it's begining to feel a bit like a duck and cover drill.
      IMO, this vulnerability is a big deal. We're talking about a remotely exploitable hole in a service running as LocalSystem, which is running on every WinXP box out there. (Granted, some of these will have port 445 blocked, but anyone smart enough to do that has likely installed the patch already.)

      IIRC, the last Windows vulnerability of this magnitude was the RPC hole that MSBlaster exploited. You may recall that there was widespread speculation that this worm was responsible for last year's power failure.

      IMHO, the LSASS vulnerability is equal in severity to the RPC vulnerability that Blaster took advantage of. Both vulnerabilities allow LocalSystem access, are remotely exploitable, and are present in components that are part of the base Windows OS, and therefore these components cannot be deselected at install time. However, the LSASS vulnerability would make it easier for a worm to grab sensitive information (password hashes) out of the SAM.
    5. Re:Yeah, I'll run that removal tool. by periol · · Score: 1

      I'm not sure why everyone is so hopped up on these removal tools. It seems to me that after being infected with a worm that installs a back door, more people ought to look at reinstallation from known good media. Because it's not that difficult to figure out what is installed. Any antivirus program can find the 2-20 instances of the virus in \windows or \windows\system32, and then you just have to get rid of the registry key. Oh, and guess what! A removal tool can do both at once.

    6. Re:Yeah, I'll run that removal tool. by AnyoneEB · · Score: 1

      I think this is possible under XP, but it would require manually doing the partitions or registry editing (or maybe both, I've never actually done it). On the other hand, a lot of Windows programs put their data in either the program directory, the windows directory, or the registry, making it difficult or at least annoying to transfer program settings.

      --
      Centralization breaks the internet.
    7. Re:Yeah, I'll run that removal tool. by RexxFiend · · Score: 1

      You can create a new partition, call it d: and set your home directory to d:\ using user mangler. Then you can trash c: (system part) as much as you want and your docs and settings stuff should be ok.

      --

      A crash reduces
      Your expensive computer
      to a simple stone.
  54. From an IT guy by bigjnsa500 · · Score: 5, Funny
    From a *nix IT guy, I am sitting here this morning, drinking my coffee and posting on /.
    Down the hall are the MCSE's. I can hear them shouting at each other about why this and that system wasn't patched.
    Even the network big wigs are in the room with them.

    Ahhhh... the joys of *nix....

    Back to my wonderful coffee....

    --
    This is a test. This is a test of the emergency sig system. This has been only a test.
    1. Re:From an IT guy by Anonymous Coward · · Score: 1, Funny

      re: Back to my wonderful coffee....

      don't worry. one of the windows guys dipped his pecker in it.

    2. Re:From an IT guy by Kenja · · Score: 1, Insightful

      As a *NIX and Windows admin I'm sitting at home without a care in the world. You see I use a "firewall" to "secure" our "network". Let me know if you need help with the big words.

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    3. Re:From an IT guy by Finuvir · · Score: 1

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"

      I'm sure I've seen/heard that before (maybe from your sig in the past). Is it a quote from something?

      --
      Why is anything anything?
    4. Re:From an IT guy by Kenja · · Score: 0, Offtopic

      Off topic, but what the hell. Its from the Futurama episode "Bender should not be allowed on TV".

      --

      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"
    5. Re:From an IT guy by Finuvir · · Score: 0, Offtopic

      Gah! Futurama? I didn't think one of those could have slipped passed me. I guess it's time to watch them all again...

      --
      Why is anything anything?
    6. Re:From an IT guy by 19thNervousBreakdown · · Score: 0

      It's from a Futurama episode.

      --
      <xml><I><am><so><damn>Web 2.0</damn></so></am></I></xml>
    7. Re:From an IT guy by rufus+t+firefly · · Score: 1
      "Have you ever thought about just turning off the TV, sitting down with your kids, and hitting them?"

      I'm sure I've seen/heard that before (maybe from your sig in the past). Is it a quote from something?
      According to http://c2.com/cgi/wiki?FunnyEmailSig, it is attributed to Bender, from Futurama.

      What would we all do without the superior searching power of The Google?

      --
      "He may look like an idiot, and talk like an idiot, but don't let that fool you. He really is an idiot." - Duck Soup
    8. Re:From an IT guy by Mysticode · · Score: 5, Insightful

      A firewall is all well and good until someone brings an unsecured laptop in and plugs it into the network. Are you tell me that no one in your organization has a laptop that they take home with them. What's the chance that they may plug it directly into a high-speed net connection at home without a firewall?

    9. Re:From an IT guy by kent_eh · · Score: 1

      Yeah, that happens all too often.

      We had one guy bring in a laptop (beacuse it was running "slow") which had a ton of spyware, a keylogger and an FTP server running on it. He had no idea how any of it got there.

      I shudder to think what is on some of the other laptops that are floating around here.

      --

      ---
      "I can't complain, but sometimes still do..." Joe Walsh
    10. Re:From an IT guy by painandgreed · · Score: 1

      More important than the subnet firewall are host based firewalls. We had three laptops come in yesterday and pick up the virus almost as fast as they could be plugged in. We were slack with updates and only had about half our comptuers updated at the time. Most had proper host based firewall and virus protection and faired all day without catching any virus. Only a few that were really old, non-standard builds got infected besides the laptops.

    11. Re:From an IT guy by surprise_audit · · Score: 1
      Where I work, the policy is that old desktops are upgraded to new laptops, and you are required to take the damn thing home... Mmmm, Dell M60 - poor me... :) Policy also mandates a virus checker and personal firewall software, which are also supplied and enabled by default. I think the plan is that if some maniac manages to "anthrax" the office building, we all dial in from home.

      There is a threat of dire consequences for anyone NOT using the supplied firewall and virus checker.

    12. Re:From an IT guy by Anonymous Coward · · Score: 0

      Very true. That's exactly why it's a good idea to have a definite policy for laptops (same goes for VPN/teleworker machines). We run NOD32 antivirus here (v. fast with an impeccable track record. Set to autoupdate upon logon + daily; both to our local servers and direct to the NOD updaters) as well as Kerio Personal Firewall to tighten stuff up. Lock down the laptops with Group Policy (inc. disabling unused services), make sure they've got a dial-up ISP connection for when they need to use a modem (plus a VPN connection if required) and you're laughing.

      As well as that it may be worth putting all the lappies that are connected to the local net behind a sep. firewall and filtering the appropriate ports (OpenBSD + spare old hardware + NICs = joy). I'd recommend using netstat, the inbuilt port viewer of Kerio, or TCPView from sysinternals.com to build up the list of appropriate ports needed to connect to your servers. Though an infection shouldn't spread past the Personal Firewalls it always helps to layer things a bit.

      Yeah, I know it's a pain to sort all this out but it'll save your ass in the event of one of the portables or teleworkers becoming infected...

    13. Re:From an IT guy by ameoba · · Score: 1

      Segment the network, force laptops onto another vlan & don't allow them to DHCP on the main network.

      --
      my sig's at the bottom of the page.
    14. Re:From an IT guy by Anonymous Coward · · Score: 0

      Wouldn't it be conceivable to force all traffic through a router at the first sign of an outbreak so it can be contained? I don't understand what is so difficult about containing these worms.

    15. Re:From an IT guy by HermanZA · · Score: 1

      So, how about enabling Port to Port security on your switches??? If you do that, this kind of shit can't spread.

    16. Re:From an IT guy by lordrich · · Score: 1

      How do you know what is a laptop and what is a desktop though?
      No, the only way you can combat this is to only allow machines to connect to the main network if they are running uptodate antivirus and firewall. And to date, Cisco appears the only way to enforce that.

    17. Re:From an IT guy by Anonymous Coward · · Score: 0

      There IS a solution to this problem... not only do we have to write detection rules to detect the presence of a trojan or virus, but we also have to be able to "detect" when a virus or trojan makes a TCP connection. It is possible, through the use of honeynets (a network of honeypots) to leave them open and sniff the network for TCP protocols. Using this sniffed data, one just writes some Snort rules, to detect when they make any connections (incoming or outgoing), and an IPS system and shut the door as soon as the infected machine tries to make a "phone call", or when someone tried to call it.

      We've been testing such a system, with excellent and very encouraging results...

    18. Re:From an IT guy by Conor+Turton · · Score: 1
      A firewall is all well and good until someone brings an unsecured laptop in and plugs it into the network.

      So what? If all the computers on the LAN are configured properly it still shouldn't be an issue.

      Perhaps if administrators stopped being lazy lard arses and actually configures every desktop properly then the fact someone brings in an infected machine to the LAN shouldn't make a difference.

      XP is pretty much the default OS on all new Windows boxes being bought in the corporate sector. It has a built in firewall. Its firewall would've stopped this BUT yet again, lazy fat arse administrators can't be arsed to tick the firewall box in the Advanced section of the NIC properties.

      I put a completely unpatched XP pre SP1 machine on the net yesterday. It didn't get Sasser or MSBlast etc etc. Why? Because I ticked the box to enable the built in firewall in the advanced tab for the NIC.

      --
      Conor "You're not married,you haven't got a girlfriend and you've never seen Star Trek? Good Lord!" - Patrick Stewart
    19. Re:From an IT guy by Slashamatic · · Score: 1

      You have the MACs of 'safe' machines which are on the enterprise virus scan. You then setup the switch so that only the recognised MACs get put directly onto the corporate LAN, the rest get isolated into quarantine segments until they can be checked, cleaned and patched.

    20. Re:From an IT guy by Anonymous Coward · · Score: 0

      Tell you a funnier story.
      My girl's company (it was just like that when she came) runs the network with windows xp, each one shares the whole harddrive (besides the default c$) out freely to others on the network, and spywares (ya know, those weather bug, gator, etc) run everywhere.
      I was asked by my girl to help on debugging a network issue one time (they had p2p networking problem), and the computer is so slow that browsing the workgroup takes 2 minutes, even when there are within 5 computers connected to the router. I could never finished downloading firebird or spybot s&d until I reboot to the safe mode.
      Ya know how the system admin detects the network down? She (the admin, not my girl) uses MSN and Yahoo Messenger for that purpose!.
      Now, that's the funniest scene I ever saw. Idiots handling idiotic network.

  55. Re:Windows only by Paulrothrock · · Score: 1

    Dude, it's Mac OS X, not OSX. It is not an acronym. And it's pronounced "oh ess ten."

    --
    I'm in the hole of the broadband donut.
  56. "sasser" in northern Europe by akaiONE · · Score: 2, Informative
    The Sasser-worm had its fair amount of success yesterday as it crashed the networks of insurance-giant 'If' and their competitor in Norway, 'Vesta'. Both companies blame corporate users with laptops for the glitches in the security system and media all over Norway reported the whole thing as "unavoidable".

    I have been giving this some thought, and quite frankly, even laptops can be locked down so that users are patched against this kind of attacks. The main issue in the IT-depts' of the companies mentioned above must surely have been giving it some thought yesterday; -Why did we not apply that patch from MS?

    The answers for many sysadmins is to apply patches in batches on a regular basis, unless there is something *mission critical* on the radar. Ofcourse such things as the patch available to stop "sasser"-worm may have slipped by the eyes of even expirienced sysadmins, especially when its not flagged with whistles and trumpets by Microsoft.

    Other sysadmins have choosen not to patch the vuln. due to its effect on VPN-connectivity as mentioned in other posts. The big question here is why Microsoft released a patch that disabled VPN in such a way. I realise it may have been the lesser of two evils, but hey, atleast they could have released the VPN-aware patch a little earlier than yesterday morning..

    Just my 0.02 Norwegian Kroner

    --

    "-Who said sit down?!"
    -- S. Ballmer @ MSDC 2003.

    1. Re:"sasser" in northern Europe by Anonymous Coward · · Score: 0
      Ofcourse such things as the patch available to stop "sasser"-worm may have slipped by the eyes of even expirienced sysadmins, especially when its not flagged with whistles and trumpets by Microsoft.
      It was announced as a "Critical" vulnerability, the highest rating Microsoft give. How many "whistles and trumpets" do you need?
    2. Re:"sasser" in northern Europe by akaiONE · · Score: 1

      I Myself, a Linux Sysadmin, had no problems with this worm :-) For the MS-people here the case was also the same as they patched this vuln. last week. Having an agressive policy on antivirus also helps, along with some network monitoring of traffic peaks :)

      What kind of whistles and trumpets the IT-droids in 'If' need I would not know, but the issue may be the VPN-access that their smaller offices and homeoffice users rely on.

      --

      "-Who said sit down?!"
      -- S. Ballmer @ MSDC 2003.

    3. Re:"sasser" in northern Europe by 10Ghz · · Score: 1

      In Finland a major banking/insurance-company closed all their retail-outlets for several hours due to this virus. I wonder that are these kinds of things included to the TCO-calculations of Windows? I wonder how many million did they lose when they had to turn the customers away?

      --
      Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
  57. evolution? by qqqqarl · · Score: 5, Interesting

    i'd like to know:

    when is someone going to put a genetic algorithm into their virus/worm?

    something that mutates the worm's parameters (ports, timing delays, ip-search stratgy, etc.) so that the most virulent parameters are found by "natural selection"?

    seems like an ideal application for genetic algorithms.

    K.

    1. Re:evolution? by Flyboy+Connor · · Score: 1

      Because a genetic algorithm is something different than you think. A genetic algorithm optimises a solution by applying genetic operators to a population of potential solutions and calculating a fitness function for each solution to compare it with the others. Other than that, since the worm is so ubiquitous, having two successful worms that meet procreate and deliver new, partially mutated children could be a fun and challenging exercise. But I assume script kiddies don't read slashdot, at least not posts this far down.

    2. Re:evolution? by qqqqarl · · Score: 1

      gosh Flyboy - thanks for that lesson. if you ever take my course on genetic algorithms at washington university, i'll make sure to flunk you.

      you know Flyboy, biological virus's don't have sex either, and yet they somehow manage to evolve.

      K.

    3. Re:evolution? by ultrasound · · Score: 2, Insightful

      A genetic algorithm is also something different to what YOU think. What qqqqarl is suggesting is actually quite possible and intriguing.

      The very existence of multiple instances of the code, with the ability to mutate by altering parameters or even parts of the worms algorithm automatically leads to the conditions for evolution of an improved worm. The very survival of the worm long enough to transmit itself to produce duplicate or mutated instances _is_ the selection process and a measure of its 'fitness'. 'Natural' selection at work. How effective this is is dependent on a number of things, particularly whether the infection of a host will block future infection by another instance of the worm, and how the worm affects the host. The parallel with natural viruses comes to mind, a virus has no purpose other than to reproduce. It does this by subverting a host. If it is too effective and kills the host rapidly, then its virulence is limited if it relies on the hosts continual operation to be transmitted. Hence Ebola is far less widespread than AIDS because the former zaps the host too fast, whereas the latter gives the host plenty of time to spread it around.

      Evolution without sex appears to be less effective (and less fun) but is still a valid method of a searching a parameter space for local and global optima. I also recall doing some experiments that seemed to indicate that certain problems are easier to solve without introducing cross-over through mating of selected pairs, but just relying on parameter mutation. Something to do with the particular fitness function over the parameter space selecting against large jumps.

      Dont forget that your predecessors had to do without sex but still managed to get along and produce you in the end.

      The idea is interesting and one could imagine extending it to include sex by allowing worms to meet up and share some of their parameters in order to produce offspring. The chances of them finding each other on compromised machines would be improved using irc, and maybe even turning every N'th machine into a 'worm' speed dating platform. The possibilities are endless.

      Wouldn't it be fun if it was actually something that wasn't destructive. I wonder if there is actually a 'good' application for this type of evolving distributed algorithm? What ever happened to the idea of Intelligent Agents that was all the rage a few years ago? Using the parallel with nature, I can't think of any symbiotic viruses, but there are many instances of symbiotic relationships between hosts and bacteria. Are we going to see a white hat virus one day(other than simple patching viruses that naturally die out), or is any foriegn code naturally excised out of principle? Probably.

    4. Re:evolution? by Flyboy+Connor · · Score: 3, Informative
      Funny, I give such a university course too.

      Anyway, by DEFINITION a genetic algorithm uses a population, and also by DEFINITION it uses sexual reproduction (see Thomas Bäck's excellent book comparing several evolutionary techniques, "Evolutionary Algorithms in Theory and Practice", 1996).

      If you use pure mutation on a single solution, the term to use would be "Evolution Strategy".

      If you want to exclude sexual reproduction, or use any evolutionary technique without bothering about definitions, use the term "evolutionary algorithm", which is an umbrella-name covering all evolutionary techniques.

      I know that people are often a bit loose about what terms to use, but since this is one of my particular subjects of research, I am a bit anal about it.

      Finally, AFAIK, there are already virusses and worms that mutate themselves. I don't have any definite examples, though.

    5. Re:evolution? by Flyboy+Connor · · Score: 1
      I quite agree with you. Since evolutionary algorithms are a specialty of mine, I have experience both with systems that use asexual reproduction and sexual reproduction. I didn't want to suggest qqqqarl's idea is not possible, just that he used the wrong terminology. The term he should use is "evolution strategy".

      AFAIK there are already worms and virusses that use mutation to change (I don't have any definite examples, though). However, virus scanners can still pick them up, because the mutation code itself does not change.

    6. Re:evolution? by qqqqarl · · Score: 2, Interesting

      i apologize for being loose with the jargon. i tend to use terms people have already heard, so that the root ideas can be more easily digested by the masses.

      it would have been nice, in your original post, if you had been more clear: "i'm harping on jargon" rather than "your idea is unsound."

      K.

    7. Re:evolution? by dasunt · · Score: 2, Interesting

      when is someone going to put a genetic algorithm into their virus/worm?

      something that mutates the worm's parameters (ports, timing delays, ip-search stratgy, etc.) so that the most virulent parameters are found by "natural selection"?

      I don't think the number of infected machines in the world is high enough for successful genetic evolution. Viruses and worms are not like living organisms -- the chance of non-fatal mutation is lower. If a mutation creates an organism with a 1/2" longer neck, that organism will probably not die because of it. If a virus mutates so that an exploit code attacks a slightly different bit of memory, that virus is probably toast.

      What we need for a successful 'evolution' virus it two-fold. First, their should be a different tendency to mutate different parts of its code. It should have a low chance to mutate most of its code, but a higher chance to mutate code that is least likely to result it damage. (Think "I love you!")

      Second, it should act like some bacteria and find other organisms (viruses) and steal its code. Let the walking bags of mostly dirty water and their wetware develop the code. Exploit it. In this manner, its more likely that a new working exploit will be found.

      Can the above be done in a viral payload? I don't know. I'm guessing that the difficulty factor is pretty large, but if someone wants to, someone will probably pull it off.

    8. Re:evolution? by qqqqarl · · Score: 1

      well - i'm not suggesting we mutate the entire binary code. (although that would be truly interesting - if successful the virus could discover completely new and unannounced exploits.)

      rather - just mutate important parameters. my understanding is that current worms use a variety of strategies for searching ip-addresses to attack (local network vs. world-wide) or which port-numbers to use for virus-virus communication. that sort of thing.

      K.

    9. Re:evolution? by Anonymous Coward · · Score: 0

      True sexual reproduction would also be possible to implement. When the sasser arrives on the computer it allready searches for a special file on the harddisk. This file tells the sasser if the computer is allready infected. If the computer is allready infected, sasser terminates itself. It would be quite easy to add a few parameters to this file and add a sexual reproduction mechanism. However I am not sure if the number of sensible tunable parameters justifies sexual reproduction.

    10. Re:evolution? by Flyboy+Connor · · Score: 1
      You're right, I'm sorry.

      It's probably due to the fact that I'm not a native English speaker. I tend to come over a little brazen.

      Also, since I am currently deep in writing my Ph.D. thesis, I am fanatically occupied by what is the correct term for which mechanism. I tend to forget that other people are a bit more flexible in their use of these terms.

    11. Re:evolution? by Anonymous Coward · · Score: 0

      A virus could steal the subject line from a random post in the mail archive.

  58. Re:If Im totally up to date with my MS Security st by JustDisGuy · · Score: 2, Insightful

    That depends on whether the Microsoft patches you have installed don't actually do more harm than good.

    For other than this particular exploit, it also depends on whether another exploit is made available before a working patch is made available for a publicized (or not!) vulnerability.

    In short, no. You may be safer, but you're not safe.

    --
    Hanlon's Razor - Never attribute to malice that which is adequately explained by stupidity.

    --
    "Never attribute to malice that which is adequately explained by stupidity." - Hanlon's Razor
  59. Re:Windows only by Hrothgar+The+Great · · Score: 5, Informative

    People have short memories. There was an Apache worm about two years ago (in mod_ssl).

    Here is a link

    Of course, worms like that are few and far between, especially when compared to the number of Windows worms going about lately, but to claim a system is "worm free by nature"? I think that's more than a little premature.

  60. Zonealarm Failure by doneagain · · Score: 3, Interesting

    I have zonealarm setup on a home PC and it failed to keep Sasser out. So much for a personal firewall.
    And yes there is AV on it, but it was infected before the updates had even come down.

    --
    Same s**t, different day
    1. Re:Zonealarm Failure by Jarnis · · Score: 5, Insightful

      Correction; You had a zonealarm that was set up wrong.

      Blocking port 445 from inbound traffic secures the computer against this worm.

      Also the failure to install a critical patch that has been out for two weeks is called 'stupidity'. Using a windows box connected to the net is already something close to extreme sports. Doing so without regular windowsupdate visits is like extreme sports blindfolded without a helmet. You are *bound* to get hurt.

    2. Re:Zonealarm Failure by LDoggg_ · · Score: 1

      Just curious, why would you use software for this, when you could use a 30 dollar piece of hardware?
      Are there other benifits to zonealarm other than just blocking incoming traffic?
      With a little hardware router, you get that plus the ability to use NAT if you want to connect other machines, and port forwarding if you want to let certain ports through that you think are safe enough.

      --

      "If they have both, tell them we use Linux. And if they have that, tell them the computers are down." -Dave Chapelle
    3. Re:Zonealarm Failure by Anonymous Coward · · Score: 1, Insightful

      ZoneAlarm and other personal firewall products are good, but can only provide so much protection from things like this, since they are running on the machine that is targeted, the attack has to reach the box in order for them to react to it. A separate firewall box (PIX, SmoothWall, etc.) can stop the attack before it even reaches the internal network.
      A physical security analogy would be the guard at the main lobby desk vs. the guard at the front gate.

    4. Re:Zonealarm Failure by doneagain · · Score: 1

      Updates like that take a different priority when the computer is in the back-end of no-where and connects to net once a week at 14000bps to check mail. Even download AV updates is a feat

      And although I can't check at the moment, Zonealarm was set at high security for untrusted connections which Dialup is part of. Personal doesn't give give all that many options for exactly what ports it closes.

      --
      Same s**t, different day
    5. Re:Zonealarm Failure by CPlusPlusOwnsYou · · Score: 0

      If you read any of the reports, Microsoft's patch for sassar causes more problems then it fixes.

      --
      "Software is like sex: it's better when it's free."
    6. Re:Zonealarm Failure by Anonymous Coward · · Score: 0

      I would think the advantages of zonealarm over a piece of hardware would be obvious:

      - easier & cheaper to upgrade
      - easier & cheaper to deploy to many computers (Granddad in Utah, Uncle Bill in Maine, ...)
      - much more accessible alerts (no having to monitor some remote router log)

    7. Re:Zonealarm Failure by doneagain · · Score: 1

      Honest Answear: laziness.
      It's a home PC used by my parents, which has never been infected by anything in 4 years of operation. I don't even use it anymore as 14000bps is unusable when used to a University connection.

      --
      Same s**t, different day
    8. Re:Zonealarm Failure by Deideldorfer · · Score: 1, Insightful

      You probably said Yes when ZoneAlarm asked if it was OK to let LSASS access the Internet.

      --

      Power off before disconnecting connecting connector. Seen on a cash register
    9. Re:Zonealarm Failure by MCraigW · · Score: 1


      In my opinion, you should use both a hardware firewall, and a software firewall, espcially on systems that may be moved, like laptops. The hardware firewall and software firewall provide differing features, which in combination result in greater security against intrusion, as well as locally installed mal-ware.

    10. Re:Zonealarm Failure by Firehawke · · Score: 1

      Zone Alarm is also particularly good at blocking outgoing connections at an application level, like those from a virus or spyware.

    11. Re:Zonealarm Failure by BokLM · · Score: 1

      Also the failure to install a critical patch that has been out for two weeks is called 'stupidity'.

      Most users are not stupid, they are simply not interested in computers and don't understand a lot about them. Microsoft told them that anyone could use a computer without any problem, but it is not true.

      Using a windows box connected to the net is already something close to extreme sports.

      True. But too much things at locked with Microsoft at the moment (giving them no choice about the OS), I hope that will change in the futur.

    12. Re:Zonealarm Failure by Mesaeus · · Score: 1

      Actually, I hate this "functionality". It's great in theory, but in practice it's nigh on impossible for "ordinary" users to know which program should be allowed access and which not. If "IEXPLORE.EXE" wants access, you can sorta guess it's Internet Explorer. But what's "MSIMN.EXE" ? (Answer : Outlook Express). "SVCHOST.EXE" ? Services under 2000/XP. "CCAPP.EXE" ? Part of Norton Antivirus. "SVCHOST32.EXE" ? Mimail worm. Oops.

      I tend to install the free ZoneAlarm version for other people, but I always tell them to click "Yes" and "Remember my choice" on any dialogs that ZoneAlarm pops up. Why ? Because otherwise they WILL at some point inadvertantly block Internet Explorer or Messenger and call me to complain that these apps don't work. I simply cannot expect these people to succesfully find out for each of these cryptic 8.3 DOS style names which program they really are.

      So I concentrate on preventing and removing spyware/virusses in the first place. I still use Zonealarm for blocking incoming connections, but they sure have to provide more usefull information if they want ordinary people to decide what's a good program and what's a bad program trying to connect.

    13. Re:Zonealarm Failure by poot_rootbeer · · Score: 1

      Blocking port 445 from inbound traffic secures the computer against this worm.

      Does anyone know if the built-in NT Personal Firewall blocks this port, or does it secretly leave it open "for my convenience"?

    14. Re:Zonealarm Failure by dwillden · · Score: 1

      I find that interesting because I also run ZA and have found it amusing to count the sasser hits it has been blocking since they started hitting last friday
      . Check your setup

      --
      I'm too lazy to compose a creative sig.
  61. Re:If Im totally up to date with my MS Security st by Anonymous Coward · · Score: 2, Interesting

    Up to date with patches, a proper firewall, and common sense and my Windows machine has never had a virus. I am convinced that in the end Windows users will end up better off. It is like security boot camp with live ammunition. Each time the number of people infected gets just a little bit smaller.

    I picture a day when most users have migrated to Linux and the first serious threat comes out and they are all prepared and the l33t get destroyed because their systems can't possibly get a virus because it is open-source.

    I patch both my Slackware box and my Microsoft box regularly - do you?

  62. Our server's protected by AC-x · · Score: 3, Informative

    A few days ago I saw a message from our firewall asking if I wanted to allow Security Authority Subsystem to be contacted by a remote host.

    A simple click on the "No" button stopped this worm in its tracks.

    If more admins just installed firewalls and made sure all unnecessary services were blocked there'd be a lot less worm infections. (sure it won't protect people who need to use the Security Authority Subsystem, but I'm willing to bet a lot of the infected machines don't use it at all)

    1. Re:Our server's protected by FictionPimp · · Score: 2, Funny

      Yea, I run software firewalls on all my windows machines as well as using NAT. Never had a problem.

      Although just the other day I had some "windows expert" recommend instead of trying to find and open the ports for a video game I was trying to play, that I just put my computer on the DMZ (even after I told him I needed to get 3 computers working and needed to use port triggering). I told him putting your computer as DMZ was just as good as putting a kickme sign up. He argued with me and told me windows is 100% secure, that I just didn't know how to secure it.

      So there, guys, windows is 100% secure. Get off it. :-)

    2. Re:Our server's protected by DavittJPotter · · Score: 1

      It is, actually... just unplug the Ethernet cable, remove the drive, and carry it in the steel briefcase shackled to your wrist.

      --
      "If there's hope, it lies in the proles..."
  63. Kill the AVSERVT.EXE process! by denis-The-menace · · Score: 2, Informative

    AVSERVT.EXE is the FTP server that Sasser uses.
    It will show up as a very hungry process (77%+ CPU)

    Kill it and then you'll be able to patch the box.

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
    1. Re:Kill the AVSERVT.EXE process! by CPlusPlusOwnsYou · · Score: 2, Informative

      Of course its located in the registry in the startup location and will be restarted everytime you reboot.

      Check the startup registry path for "Avservt.exe":
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run

      --
      "Software is like sex: it's better when it's free."
  64. Re:If Im totally up to date with my MS Security st by shoaler · · Score: 0, Offtopic

    "noone" is not a word. It is not in the dictionary. You've made an excellent point in your post, but it's tarnished, at least to my eye, when I see you use things like "noone." Look it up and use "No one" next time. Two words. Thank you.

  65. uh uh by WormholeFiend · · Score: 2, Insightful

    "I'm sitting here with my phone ringing off the goddamn hook"

    so are you telling us you'd rather let the phone ring and read slashdot and post comments instead?

    1. Re:uh uh by Anonymous Coward · · Score: 0

      so are you telling us you'd rather let the phone ring and read slashdot and post comments instead?

      Sure. But some of us are able to multitask, especially when dealing with lusers.

    2. Re:uh uh by ramzak2k · · Score: 1

      Note that there was a removal utility posted here. This was the first place i looked when someone talked about a worm.

      --

      Siggy Say, Siggy Do
    3. Re:uh uh by NatasRevol · · Score: 0, Flamebait

      Really?

      The first place I look is to an OS that doesn't have such horrible security breaches, especially ones that occur on such a regular basis.

      But that's just me.

      --
      There are two types of people in the world: Those who crave closure
    4. Re:uh uh by Daniel_Staal · · Score: 1

      Maybe he has a job where he has to support an system he has no (or little) say in designing.

      He didn't say his computer needed the patch. Maybe he just has to install it on other computers...

      --
      'Sensible' is a curse word.
  66. Read CERT by Anonymous Coward · · Score: 0

    OpenSSL is not turned on by default in every install, and *very few* of the vulnerabilities in Linux, or OS X would have affected a standard system install. For example the recently reported vulnerability in OS X doesn't affect most people because that service (AFS) is off by default. People who have turned it on should know they have, and are more likely to patch.

    Windows has a lot of holes, and has historically been very lax in leaving services open (uhm, netsend, RPC) that no normal user needs. Thankfully they're *starting* to address this, though the attempt to embrace and extend the internet with .NET doesn't leave me hopeful about their future security priorities.

    I think you should admit that things are not all rosy before/whilst jumping to the defence of Microsoft. It is time people wake up and start to question what system they use, rather than use Windows with the justification that 'everyone else does'.

  67. Directly from the Internet? by Phidoux · · Score: 1

    Yes! This a router borne worm that even has it's own IP address.

  68. Patch by MNJavaGuy · · Score: 1

    MS has issued a patch for this. Why it's not a critical update is beyond me...

    1. Re:Patch by reverendslappy · · Score: 1, Funny

      It was released two weeks ago, rated "critical". From the 10th line of your link: "Maximum Severity Rating: Critical"

      How you didn't see that is beyond me.

    2. Re:Patch by MNJavaGuy · · Score: 2, Interesting

      I was referring to how it's not showing up on some of my unpatched machines in Windows Update as a critical update (not at all).

    3. Re:Patch by CPlusPlusOwnsYou · · Score: 0

      Because the patch is shoddy and causes more problems then it fixes. Please refer to: here

      SYMPTOMS
      After you install the security update that is described in Microsoft Security Bulletin MS04-011 on a Microsoft Windows 2000-based computer, you may experience any one of the following symptoms:

      * Your computer appears to stop responding at startup.
      * You cannot log on to Windows.
      * Your CPU usage for the System process approaches 100 percent.

      --
      "Software is like sex: it's better when it's free."
    4. Re:Patch by MNJavaGuy · · Score: 1

      Ok...ignore that comment. It was released as a security update a couple weeks ago as was pointed out.
      I need to remember to have my coffee before posting in the morning :)

    5. Re:Patch by llzackll · · Score: 1

      If you are running Win9x (95, 98, or Millenium), then it is not going to show up as a critical update. It only affects NT machines, like 2000 or XP.

    6. Re:Patch by MCraigW · · Score: 1


      Perhaps it has already been installed on those systems. Or... if you are running Windows 98, 98 SE, or ME, the correction is "Not Critical".

    7. Re:Patch by Anonymous Coward · · Score: 0

      You have unpatched machines?

      What chance do we have of containing this worm when even /. readers aren't patching the fscking holes?

  69. Problems are with windows, not IE by T.Hobbes · · Score: 5, Informative
    A few things:
    • It's a worm, not a virus
    • It's attacks Windows, not IE (despite Microsoft's efforts, there is still a distinction)
    • For the user, the main damage is that the infected computer will shut down; I have no reference, but shutdown loops have been reported
    • For the admin, the main damage is the flood of trafic sent out by the worm in search of new hosts
    • The worm can use Win98/WinME boxes to propegate but cannot infect those same computers

    Google cache of McAfee's page on the worm
    One of symantec's pages

    1. Re:Problems are with windows, not IE by penguinbrat · · Score: 1
      Addendum...

      For the admin, the secondary damage is stopping the end users PC from rebooting it self constantly, quickly moving to the main problem when the single end user turns into the whole company.

    2. Re:Problems are with windows, not IE by Peyna · · Score: 1

      it's easy to abort the shut down, just run "shutdown -a". (The shut down only occurs when the user is connected to the Internet.)

      The best way to fix it would be to connect to the Internet, abort any pending shutdown, then download the removal tool. You'll have to reboot after downloading, because the reason you needed to shut down was the worm killed some system process which you will need to run the removal tool as well. Once the machine comes back up, make sure you are not connected to the Internet (i.e. unplug your ethernet cable). Then proceed to run the removal tool.

      Of course, most users won't be able to figure out how to get it to not shutdown, or have never seen the windows shutdown message before and assume that that is an actual part of the virus, and therefore find themselves helpless and will pay upwards of $60 for someone else to fix it for them.

      --
      What?
    3. Re:Problems are with windows, not IE by BokLM · · Score: 1

      The worm can use Win98/WinME boxes to propegate but cannot infect those same computers

      How does it work ?

    4. Re:Problems are with windows, not IE by EddWo · · Score: 1

      You also need to install the patch to stop the shutdown from happening. Or block access to the LSASS port, or change the service properties for LSASS so it doesn't shut down when the service crashes.

      --
      "Taligent is still pure vapor. Maybe they'll be the last who jumps up on Openstep... "
    5. Re:Problems are with windows, not IE by Anonymous Coward · · Score: 0

      For the user, the main damage is that the infected computer will shut down; I have no reference, but shutdown loops have been reported

      This is true. On Sunday I was trying to fix a friends computer who kept doing this shit. Of course the machine couldn't get on the network either (once linked up to any kind of network, the machine gets the LSASS.EXE errors and shuts down in 60 seconds). At that time, I didn't hear shit about any worms (my machines at home are all either already-patched Windows machines or Unix) so was wondering what the hell was going on. I knew it was a worm, but just figured it was some old one still making its way around the net. Of course this was on a Windows XP Home Edition (Service Pack 1) machine that was connected directly to a DSL modem. Oh, and my friend disabled his antivirus Auto-Protection as well beforehand (very smart).

      Very easy target.

    6. Re:Problems are with windows, not IE by LordLucless · · Score: 1

      The worm also runs a remote terminal server (on port 9997 I think). I don't know if you want it to go to the user or the admin, but somebody should do something about that too ;p

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  70. BEWARE NT4 TS + Citrix admins!! by SlashDread · · Score: 4, Informative

    The patch from MS : http://www.microsoft.com/technet/security/bulletin /MS04-011.mspx

    just BSOD'ed my Citrix server.

    YMMV

    "/Dread"

    1. Re:BEWARE NT4 TS + Citrix admins!! by gregarican · · Score: 1

      Did you install the NT 4.0 TS service pack that was required to be performed before patching? I think I read something to that effect.

    2. Re:BEWARE NT4 TS + Citrix admins!! by Rick.C · · Score: 4, Informative
      There's a Terminal-Server-specific security rollup patch (SRP) that must be applied first. Check the MS MS04-011 page.

      I would hope that MS04-011 would check for the presence of the SRP, but who knows?

      --
      You were 80% angel, 10% demon. The rest was hard to explain. - Over The Rhine
      "Math in a song is good."-Linford
    3. Re:BEWARE NT4 TS + Citrix admins!! by SlashDread · · Score: 1

      The service pack 6 was there, parts of the security roll up were there. (We followed the individual patches) Previoulsy TS patches refused, if the system not up-to-date.

      Maybe this didnt. maybe bad karma.

      "/Dread"

  71. The BBC's Magical Worm by donnacha · · Score: 1, Interesting


    Imagine my shock this morning when I read the BBC's article on Sasser which claimed:

    Unlike more recent viruses, Sasser does not travel by e-mail instead it makes its way around the internet unaided.
    Now that's what I call a superior worm!
    1. Re:The BBC's Magical Worm by randomencounter · · Score: 1

      That _is_ what we call a worm. The e-mail "viruses" out there are mostly more properly called trojans, as they require user intervention to infect the system.

      --
      Forget diamonds, copyright is forever.
    2. Re:The BBC's Magical Worm by Anonymous Coward · · Score: 0

      Dont blame them - they are journalists, TCP is well beyond them.

      Besides when has accuracy got anything to do with news reporting?

  72. Nasty little bug costing a lot of money. by Anonymous Coward · · Score: 1, Interesting

    This bastard hit Cummins Inc. , Sunday morning, shutting down manufacturing and corporate operations at every facility in the world till early Monday morning.

  73. Re:If Im totally up to date with my MS Security st by Anonymous Coward · · Score: 0

    You obviously weren't a fan of Herman's Hermits. Peter Noone rocked.

  74. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0

    Sure, my parents know what a firewall is.

    Dumbass.

  75. Re:have i missed something? by Anonymous Coward · · Score: 0

    false.
    remember, IE is an integral part of the Windows OS.

  76. old news by Anonymous Coward · · Score: 0

    This news is a couple of days old....why is it just now /.ed??

  77. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0

    In that case, your parents need some education instead of a computer. Education, you know... The thing they failed to give their offspring.

    Fuckface.

  78. Re:Windows only by Anonymous Coward · · Score: 1, Interesting

    like apache is the most popular web server?

  79. Re:Direct? by UnknowingFool · · Score: 1
    What could be more "directly from the Internet" than email?

    Bloody hell, man!
    This is /.! How dare you ask that question here?!

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  80. Re:If Im totally up to date with my MS Security st by Macgruder · · Score: 2, Insightful

    Well in this case, yes.

    Sasser exploits a hole in Windows. A patch for this hole has been out for about three weeks.

    Moral of the story: Keep aware of the Critical Updates. You may not need to apply every single one of them, but at least be aware of what they are, and what problems they are designed to fix.

    --
    I'm not crazy,I'm actively irresponsible.
  81. Heh, viruses don't worry me by Anonymous Coward · · Score: 0

    As I sit here working on my PowerBook, I look at news links and slashdotters frantically trying to apply patches and download the newest virus updates to combat yet another virus. And I continue to work, without even having a virus scanning program on Mac OS X. Never had a virus on my Mac, and never plan on getting one.

  82. Re:Windows only by Anonymous Coward · · Score: 4, Interesting

    Apache has the largest market share in HTTP servers, and it's not the most hacked.

    I always see this posted and I think people get this mixed up. More web sites are hosted on Apache servers, but there are more physical boxes running Windows.

    Example:

    I just left a job working at one of the largest internet hosting companies. We hosted close to 300,000 web sites; both Windows and Linux. Our customer base was roughly 60% Linux and 40% Windows; hosted on a little over 5,000 servers.
    If you were to know the number of servers we have and looked at a Netcraft scan you would assume the following:

    3,000 servers running Linux web sites
    2,000 servers running Windows web sites

    But that would be incorrect. Most of our Linux sites are cheep little geek home pages where we have a couple hundred sites hosted on a server. Our dedicated sites, big e-commerce sites, are mostly running on Windows boxes. So we have some servers running hundreds of sites and others running 1+ sites.

    What's my point? In reality it's more like 1,500 servers running Linux (Apache) and 3,500 running Windows (IIS). I've worked at a couple large hosting companies and it's the same at all of them. So when you see the Netcraft report stating that 65% of the web is running on Apache, that doesn't mean there's more physical servers out there running Apache than IIS; just Apache servers are hosting more sites due to the small, cheap nature of a lot of Linux hosted sites. So, in reality, there is a larger install base of IIS machines. Of course Apache is pretty secure, because if they attacked an Apache box at a hosting company they could take down a lot more sites, causing more havok.

  83. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0

    That's why I am in favor of licensing computer use. You obviously can't be bothered to educate your parents so somebody else will have to.

  84. Re:Windows only by qasimzaidi · · Score: 5, Interesting

    Mine was probably the only PC left infected in the office. Funnily however when i tried to download the patch for Sasser from Microsoft ( I unfortunately have to dual boot), Here is what i got Thank you for your interest in Windows Update Windows Update is the online extension of Windows that helps you get the most out of your computer. You must be running a Microsoft Windows operating system in order to use Windows Update. From what i have heard from my colleagues, this worm attacks when you connect to net, and microsoft forces you to connect with a vulnerable system. But then, windows is a product for dummies from the dummies. PS: Tried fooling the script at windows update site by changing browser identification, but this only prevented the thank you message, didn't allowed to download the patch

  85. Australian politician weighs in on the topic by Anonymous Coward · · Score: 0

    One aussie politician points out that not all computer systems are affected.

    1. Re:Australian politician weighs in on the topic by MCraigW · · Score: 3, Funny


      In interesting quote from that article: "Experts agree that Linux computers are not as susceptible for a number of reasons including clear separation of functions like email and applications so that hostile code cannot be run without significant user intervention;"

      It seems to me that non-hostile code cannot be run without significant user intervention either.

  86. Re:M$ - First Post? by Anonymous Coward · · Score: 2, Interesting

    Just to comment on the "educated user" bit. My father works at the EU Commission. The news reports were not overstated. Almost ALL (at least 90%+) Of the computers on the Commission intranet (around 25,000 if I remember correctly) were infected with this virus on the 3rd of may. In the end he went home arly (like most people) and the admins sorted it out overnight.

    These are computers which are automatically updated from a local mirror when an admin tells them to.

    Sod educated users, lets have some educated admins.

  87. Did I say I run Windows? by AriesGeek · · Score: 1

    Because I don't. I use Macintosh. However, I see the advantages of Windows, *nix, Mac, etc. Each has their own place. Take a look at the Linux notes on CERT (Just in one month alone, if you wish).

    --
    Insert offensive troll-style sig here. Please mod or respond appropriately.
  88. Once again, the writing is on the wall.... by innerweb · · Score: 3, Insightful
    ...Security, stability and safety are the primary concerns of any computing platform. When you ignore any of the three, you are at risk. Just like risk in the real world, risk in the digital world can have serious impact.

    Microsoft, Linux, Apple - all platforms need to have this drilled into their brains, coding, and documentation repeatedly with much force! Microsoft is a target because they have angered so many with their *business* activities and sloppy coding. How long before Linux joins them?

    I am an avid Linux user - The only windows machines I have are for client applications that I can not run on Linux.

    Most of us (yes, me included) when we scratch an itch, make it work for ourselves, not for the world in general. If we are to produce Secure, Stable and Safe programs, then we need to have a tool set that allows us to build them without thinking about it, or we need to all think about it with each app released into the wild. Asking Joe User to know enough to run a secure platform is like asking all people to be able to self serve everything in their own cars, appliances and bodies (i.e., no mechanics, repairmen or doctors needed).

    'It aint gonna happen!' All of these are way to complex and most are changing faster than most people can keep up with. So, it needs to fall back on our shoulders (the developers) to make this happen. The question today (as in so many other days past) is what can we Linux developers learn from Microsoft's mud? What are the issues that are allowing these things to happen and how can we prevent them? I hope everyone has heard this before.

    And, more importantly, how do we get qualified people to itch this scratch to completion? It seems to me that the world in general would benefit most from a programming tool set that built these solutions in, and that is not going to be an easy task. Microsoft is trying to address that with .net, and is still not on target (or anywhere close from what I have seen). Java tried to answer that, but it has fallen far short of what is needed.

    I really do not have any answers to this. One of my bet friends has explained to me the complexities of building compiler systems and writing your own languages. Those complexities alone are big issues. I would love to read what other /.ers have to say on this issue.

    InnerWeb

    --
    Freud might say that Intelligent Design is religion's ID.
    1. Re:Once again, the writing is on the wall.... by ciggieposeur · · Score: 1

      The question today (as in so many other days past) is what can we Linux developers learn from Microsoft's mud?

      I wish I could say there's lots to learn from Sasser, but there really isn't. We learned about insecure root-level networks daemons in 1988 with the Internet Worm: fingerd and sendmail were the culprits then. Since 1988 the common Unix daemons have been audited hundreds of times, and after a long rash of compromises through the early 90's they've gotten "reasonably" secure.

      What we learned in 1988 was that most daemons should NOT run as root, and that those which do should be very very small and selective with what they do AS root. We created tools to carefully control root access (chroot and sudo), we've implemented kernel-level firewalls to restrict inbound network access to insecure applications, and we've implemented other system controls to prevent non-root local users from seeing sensitive data (shadow passwords).

      All these steps don't work ALL the time, but they've increased the bar considerably since 1988 for unauthorized penetration.

      Then add the new security software we've written: intrusion detection systems, tripwire monitoring, weak password scanners, and dedicated honeypot systems. Some of these tools have been ported/duplicated for Windows, but they aren't used nearly so frequently in my limited server shop experience. Security has just always been an afterthought in the Windows market, and now Windows is undergoing the painful growing experience Unix went through fifteen years ago.

      What are the issues that are allowing these things to happen and how can we prevent them? I hope everyone has heard this before.

      Well, mostly we've got distros that set up the system to use lots of different user IDs to restrict access on listening ports. So very few network daemons are running with superuser privileges at all, generally only sshd, named, and RPC, plus a few others that are "unusual" on most systems. Most of these daemons have had their share of troubles, but that was many years ago and they have undergone a security beating far more severe than any version of Windows, so they can generally be "trusted". Furthermore, when holes DO pop up (as they have), we've got very mature systems for patching those holes without requiring major disruption. (In my case it's simply "apt-get upgrade".)

      Finally, even when a worm compromises a typical non-root network daemon such as Apache, its scope is limited to damaging whatever Apache's user (typically 'nobody') has access to. This point doesn't go very far in typical business use cases -- mostly those non-root users ARE the critical business data.

      The difference with Windows is that Microsoft started with dozens of services on that all have superuser access that they don't really need. So a hole in any one of these leads to an entirely compromised system that (important part) the user sitting at the desktop cannot fix. When apache goes down, I just type "apachectl stop" or "kill -9 [apache's PID]" and the worm is dead in its tracks. On Windows 2000/XP, I pull up taskmgr.exe and try to kill the service and I'm told it cannot be terminated.

      I used to think the Windows ACL's would provide better security than Unix group IDs (GIDs). But after migrating to a modern distro, I see that there's very little I can't control with GIDs. For example, my regular user is part of the cdrom, audio, and scanner groups, so I can rip and burn CDs, play music, and scan images, but I can't do anything else that would screw up the system. I'm sure Windows can be secured the same way, but (important point) it isn't ever shipped that way. Many Windows apps require Administrator rights just to *run* correctly, and I've encountered no professional apps that can install without Administrator rights. So IMHO those ACLs are providing only theoretical security. Unix distros are providing practical security.

      It seems to me that the world in general would benefit most from a pro

    2. Re:Once again, the writing is on the wall.... by DrVomact · · Score: 1
      It so happens that Unix IS a true multi-user system, while Windows is just barely getting there with Windows 2000.

      You were making good sense until that last part. What do mean "just barely getting there" with Windows 2000? Windows 2K is nowhere near anything that resembles a multi-user OS, and neither is XP. I've heard lots of hype about Longhorn, but the words, "true multi-user operating system" didn't come up.

      I've been working in a Windows shop for nearly a year now, since I was cast out of Heaven as the result of a RIF. Everyone here has their own little "personal computer" on their desk, and it's administered by a bunch of fascists called the "IT Department" that tries to make sure all the little boxes stay exactly the same. So they're personal...and each one is just like all the others...in theory.

      Of course, they're never really the same, because everyone tries to outwit IT to do something they're not allowed to, or because they don't have a clue about how to run a computer. So what we have is utter unmanageable chaos--and the poor IT devils regularly electrocute themselves to ease the pain. How sweet and sensible it would be to have some mainframes with a true multi-user OS--like *IX. If we had that instead of these stupid "personal computers" with single-user operating systems, it would be easy to share files and applications securely, and I.T. could spend their time managing something that was designed from the ground up to be a multi-user system, and was designed to be managed.

      But like I said, I was cast out of Heaven, so I know where I am now, and why we use Windows.

      --
      Great men are almost always bad men--Lord Acton's Corollary
  89. Correction by CPlusPlusOwnsYou · · Score: 2, Informative

    The problem isn't with internet explorer. It's with a program called lsass.exe or the "Local Security Authority System Service".

    It takes advantage of the open ports in Windows (as if microsoft didnt learn from NetBios).

    In Windows 2000/XP/2003, Microsoft added the possibility to run SMB directly over TCP/IP, without the extra layer of NetBT. For this they use TCP port 445.

    Check if port 445 is open on your system (you have to do a regedit hack to close it)

    http://www.petri.co.il/what_is_port_445_in_w2kxp .h tm

    The above site has a detailed information on howto use regedit.exe to disable port 445 in Win2k/XP.

    --
    "Software is like sex: it's better when it's free."
    1. Re:Correction by Anonymous Coward · · Score: 0

      Sorry man. I don't trust websites with the .il TLD.

  90. interesting thoughts for the future by Anonymous Coward · · Score: 2, Interesting

    At first linux's traction on the desktop was because "windows isn't stable". Then there came windows XP, where most instability is from third party drivers.

    Then alot of linux's traction has been "windows is insecure". But when windows XP SP2 comes out, the worms will die away a bit, and it will only be social engineering attachment trojans in outlook.

    Then what will linux's attraction be? A better the desktop right? Better browser etc. But when Longhorn finally comes, that might be gone too.

    Linux, to my mind will always be better for myriad reasons, but it has to be alot better to make people change. And winXP stability, firewalls cutting the worms down, and a better GUI... will it be *that* much better to get people to change?
    This makes the "linux on the desktop" window of opportunity quite finite.

    I, for one, believe we can best microsoft on the home desktop but we need the corporate desktop for the following reason; hardware compatability.

    "Why?" you ask, well I'll tell you. We need the corporate desktop for hardware support. OSX has a hardware rendered desktop, longhorn will have it too. No linux will be able to have a hardware rendered desktop without GPLed drivers. To get GPLed drivers for most graphics cards, we are going to need the slugging power of at least a 30% stake in business desktops. This makes Ximian/MS intergration type projects, mozilla/firefox/thunderbird and openoffice some of the most important battlegrounds you will see in the next few years. Once we have the hardware, we can take them - but don't fire until you see the whites of their CGI rendered eyes.

    And here are some thoughts on that matter, my head's in the clouds for some of it - but we can dream right?;

    Convince XGI to GPL Volari drivers. Standard tactic of an underdog is to use open-source to sling-shot ahead of the competition through features and performance. Directx9 is heavily shader based, but I prefer opengl myself and if you look at these performance statistics http://www.tomshardware.com/graphic/20031107/index .html
    the only thing a volari needs is GPLed drivers and a linux following.

    GPLed Nvidia and ATI drivers might follow. Who knows.

    The other thing is, put some weight behind an "opensource hardware" movement to get an openGL performance beast that can be manufactured and sold by anyone, as it is an open design. I think with DRM we are going to see the ground ripe for open source hardware configurations. And don't think electrical engineers won't be able to do what software engineers have done with linux.

    Anyway, that's just some memes I wanted to spread around, AC because I don't care about authorship. Just mull them over, because we need all the ideas we can get for the battle to gain a foothold. I am not saying I want to destroy MS, I just want enough market share to be able to have hardware compat and make sure things like DRM don't make their way into hardware (or make sure there is an alternative). from minix to now we have only seen the end of the begining business and home desktops, DRM and the very nature of hardware await.

    1. Re:interesting thoughts for the future by gnu-generation-one · · Score: 1

      "Then what will linux's attraction be?"

      Freedom

  91. Sasser prevention tips by Anonymous Coward · · Score: 2, Interesting

    1) Enable ICF (Internet Connection Firewall) if using XP or Server 2003. This blocks all unsolicited incoming traffic.

    2) Block the following at the firewall:
    * UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and 593
    * All unsolicited inbound traffic on ports greater than 1024
    * Any other specifically configured RPC port

    (Personal note here: I block *all* ports except 80, 443 (web), 25, 110 (mail).)

    3) Enable advanced TCP/IP filtering to block all unsolicited inbound traffic. See Microsoft Knowledge Base Article 309798.

    4) Block the affected ports by using IPSec on the affected systems.
    (Personal note here: I run a couple of machines over VPN exclusively, and so only the VPN ports need to be open on the firewall for them. Any attack will have to come from within the VPN.)

    These tips are straight from M$, see:
    http://www.microsoft.com/technet/security/bu lletin /MS04-011.mspx

    1. Re:Sasser prevention tips by cocotoni · · Score: 1

      Not to pick nits, but you can only block/allow INBOUND connections in ICF. So what you said means that people can connect to your machine on said ports. And if you are running a web server, or worse yet a mail server on a windows machine with only protection of ICF, boy you have more problems then the simple sasser worm...

  92. Don't keep your money there by Anonymous Coward · · Score: 0

    These people never heard of *FIREWALLS*?

    Honestly, the IT department should be fired.

  93. Sassier *is* a virus by cr@ckwhore · · Score: 2, Interesting

    Sasser, unlike a virus which travels through e-mails and attachments, spreads directly from the internet.

    Are you kidding me? By this definition, Sasser *IS* a virus, unlike everything else, which are Worms.

    It seems that we've been living in the land of email worms for so long that most people don't know how to deal with a real virus. Yeah, that's what they do... they spread without your help. Geez!

    --
    Skiers and Riders -- http://www.snowjournal.com
    1. Re:Sassier *is* a virus by Nrlll9 · · Score: 1

      nah, sasser is a worm, it doesnt attach itself to a file. viruses are called viruses cuz they infect files and programs.

    2. Re:Sassier *is* a virus by BCoates · · Score: 1

      I think you've got it backwards, worms propogate without assistance, viruses require user action.

    3. Re:Sassier *is* a virus by Tore+S+B · · Score: 1

      THE ORIGINAL 1988 RTM WORM that lead to the original term being coined, spread via telnetting to the listening sendmail demon.

      --
      toresbe
    4. Re:Sassier *is* a virus by American+AC+in+Paris · · Score: 5, Informative
      It seems that we've been living in the land of email worms for so long that most people don't know how to deal with a real virus. Yeah, that's what they do... they spread without your help. Geez!

      No, that's inaccurate.

      Worms can spread to other machines on their own. Viruses require some external intervention (such as file sharing or e-mail) to spread to other machines. See this entry in the Jargon File for a more verbose answer.

      Now, many of the latest e-mail "worms" would be better classified as viruses or trojan horses, as they are incapable of infecting other hosts without direct user intervention (i.e., opening an attachment.) They've been (IMHO) mis-labeled as worms because they display worm-like behavior once they've infected a machine--that is, they mail copies of themselves as trojan-style attachments to other users.

      So yes, the Sasser worm is a bona-fide worm. It transmits itself to other systems without any external help.

      --

      Obliteracy: Words with explosions

    5. Re:Sassier *is* a virus by b100dian · · Score: 1

      What you call "worms" because they spread with someone's help would rather be "trojan horses".
      And you're right, this *is* a virus.

      I'm afraid that even after this (and after codered, Nimbda, after msblast) nobody understood that IT should be taken more serious by the employer that finds it cheaper to have an "i'll click here" "specialist".
      The total cost of ownership that is worshiped everywhere should include a +infinitum for pairs of systems/administrators that can take you out of business!

      To be short, a smart Windows admin gets over this, a Linux admin too but the not-so-knowledgeable ones fail. The point is to know what the hell's making your OS tick. (and evidence is that open source reveils this faster:)

      --
      gtkaml.org
    6. Re:Sassier *is* a virus by Anonymous Coward · · Score: 0

      I think if you read that sentence carefully, paying close attention to the commas, you will agree that nowhere does it state Sasser is not a virus. If it were written as: "Sasser, unlike a virus, travels through emails and attachments, spreads directly ..." it would be stating that Sasser was unlike a virus. But as written, I believe it is only stating that it is not like other viruses.

    7. Re:Sassier *is* a virus by MCraigW · · Score: 1


      I prefer symantec's definitions and explanation, from http://service1.symantec.com/SUPPORT/nav.nsf/docid /1999041209131106 :

      "Worms are programs that replicate themselves from system to system without the use of a host file. This is in contrast to viruses, which requires the spreading of an infected host file."

  94. Re:Windows only by Anonymous Coward · · Score: 2, Insightful

    And now compare the number of users using apache and mod_ssl against those using windows and the number of windows outbreaks there have been over that two year period.

  95. "Patches" by Anonymous Coward · · Score: 0

    Every time a MS vulnerability story comes out with a link to the patch or a removal tool or something of the sort, does everybody honestly still have to post "funny" or "insightful" comments with links to Linux distros? Honestly, I think everybody on /. knows where to get them, and there's no need for everybody to jump on the bandwagon and try to get points. Jeez.

  96. Re:If Im totally up to date with my MS Security st by Anonymous Coward · · Score: 0

    Same thing with alright... should be all right.

  97. Re:I love my Mac by Paulrothrock · · Score: 1

    I would also like to say that I love my Mac.

    *Crosses fingers and hopes the virus crashes his work machine, so he can go home early.*

    --
    I'm in the hole of the broadband donut.
  98. Spring cleaning by josea · · Score: 0

    When my computer was infected last weekend I tried all the removal tools, manual removal instructions, and even sacrifices to the evil M$ gods. Did no good, spent yesterday reloading my computer... Oh well, I think of it as my computer telling me it was time for spring cleaning.

    --
    I blog, they blog, do you
  99. Re:If Im totally up to date with my MS Security st by DaHat · · Score: 2, Interesting

    Moral of the story: Keep aware of the Critical Updates.
    That... or don't have unrestricted port access to your machine. Because of my efforts, no one in my extended family is permitted to plug their PC directly into their cable modem, all go through NAT routers because of the inherit security benefit of them.

    I admit it, I don't keep up to date on windows updates, simply because my PC is several levels removed from the internet that a slew of cataclysmic events would have to occur for me to become infected with anything more then disk fragmentation.

  100. it does make one wonder by WormholeFiend · · Score: 1

    it does make one wonder if there are people out there working on anti-spammer viruses and worms...

    are such virus and worms even within the realm of the possible, or are spammers using systems that are by default impervious to cyber-attacks?

    1. Re:it does make one wonder by Progman3K · · Score: 1

      The whole spam-relay network is made up of apathetic users who run an infected machine, but other than being inconvenienced a little by their machine being a bit slower, either don't care, are too lazy or are clueless to address the problem.

      The rationale that I've seen among those users is "well, I haven't lost any data, and other than the pop-ups, it doesn't really get in my way or bug me that much, so, meh..."

      Kinda hard to ignore now though, what with your computer rebooting all the time, isn't it?

      --
      I don't know the meaning of the word 'don't' - J
  101. Swedish Network Administrator Chef Comments... by Chagatai · · Score: 1
    A netvurk prublem veet oooor systems? Impusseeble-a. Thees is oone-a ooff zee lergest bunks in Scundeenefia. Furst ve-a petched oooor systems, zeen ve-a rebuuted, und noo ve're-a sooffffereeng prublems. Um gesh dee bork, bork!

    --
    --Chag
  102. Re:Windows only by ThePiMan2003 · · Score: 1

    I hate it when people keep posting this drek. Just because Linux doesn't have the market share does not explain why it has fewer viruses. Look at Apache and IIS. Apache outnumbers IIS but IIS is what viruses target.

  103. Re:M$ - First Post? by Anonymous Coward · · Score: 1, Funny

    I think you are being rude and inconsiderate with your concept of an educated user base. Get off your high horse. I am a MS "power user" and I would never consider giving up my password for chocolate. Furthermore, I feel that... Mmm, licorice? Administrator/IBL33t

  104. Re:Windows only by Anonymous Coward · · Score: 0

    Mac OS X, not OSX. It is not an acronym.

    Not an acronym?

    OS X = Operating System Ten

    pretty much an acronym

  105. Windows machines directly on public networks by Peter+Cooper · · Score: 2, Insightful

    I'm no Windows hater, but these exploits reinforce my opinion that no Windows machine should have a publicly accessible IP address.

    We run Windows on our network here, but we have a Linux box with IP masquerading enabled connected to the Net, so the only exploits that could possibly work would be 'stupid enough to open the attachment' types, as you can't target any of our Windows PCs from the outside world, only our Linux box.

    Sure, some of the ports Windows leaves open are useful for things you might do on a corporate LAN (Active Directory, RPC, and such) but these things are next to useless for the larger Internet. If they don't want to fix the holes before someone has exploited them, or code their systems properly, then Microsoft could at least make it so that Windows leaves NO generic ports open on public/WAN interfaces.

    1. Re:Windows machines directly on public networks by BokLM · · Score: 1

      We run Windows on our network here, but we have a Linux box with IP masquerading enabled connected to the Net, so the only exploits that could possibly work would be 'stupid enough to open the attachment' types, as you can't target any of our Windows PCs from the outside world, only our Linux box.

      And what is your web browser ?
      If you're using Internet Explorer or Outlook Express you can very easily be infected reading a webpage or a mail you received.
      Mozilla is a good choise :)

    2. Re:Windows machines directly on public networks by Peter+Cooper · · Score: 1

      And what is your web browser ?

      Firebird across all machines. Also all on Outlook Express though.. but have had no problems as the zone is set to high security, and no-one is stupid enough to say 'OK' when it pops up a Run or Save box ;-) Haven't stumbled across any viruses which can run arbitrary code without you having to say OK to that box as of yet..

      Will probably check out Thunderbird once again now it's another revision down the road.

    3. Re:Windows machines directly on public networks by Anonymous Coward · · Score: 0

      I'm no Windows hater, but these exploits reinforce my opinion that no Windows machine should have a publicly accessible IP address.

      Psst, thats what firewalls are for! And I mean real firewalls, i.e. Cisco, etc. You can do wonderful things such as only allow the ports in that you want, but deny the rest. Its a great new feature!

  106. cataclysmic event by Gaima · · Score: 1

    Why do WE have to have a cataclysmic event?

    I just like the idea of a cataclysmic event, that way we can get on with the cool Star Trek stuff :)

  107. Re:Windows only by Tore+S+B · · Score: 1

    This doesn't mean anything. Remember, the share of ecucated users running a HTTP server is larger than the share of educated users running a Word processor or something.

    --
    toresbe
  108. That's only part of it by Anonymous Coward · · Score: 0

    If port xxxxx-whatever is being hacked, why is that allowed to pass into the corporate intranet to begin with.

    Then, you have machines that are weeks, if not months behind in patches...

    This points to an IT issue, not an end use issue.

    1. Re:That's only part of it by Progman3K · · Score: 2, Interesting

      Again, right!

      Net effect?
      These machines will keep crashing until they are DEALT WITH!

      That means brought up to date.
      And that means -
      No more vulnerabilities, no more infections, no more spam-relays...

      I think it's WONDERFUL that this worm causes the computer to reboot constantly; that's SURE to get the system the attention it requires, and in the meantime, it effectively takes it out of commission. :-)

      --
      I don't know the meaning of the word 'don't' - J
    2. Re:That's only part of it by GMC-jimmy · · Score: 1
      That means brought up to date.
      And that means -
      No more vulnerabilities, no more infections, no more spam-relays...

      FAT CHANCE !

      MS been combatting things like this for over a decade now and it's not likely to change much during the next decade.
      --
      __________________________________
      Free your mind - Flush your toilet
    3. Re:That's only part of it by Smidge204 · · Score: 1

      That means brought up to date. And that means - No more vulnerabilities, no more infections, no more spam-relays...

      Correction:
      That means brought up to date.
      And that means -
      The particular vulnerability is fixed, only the infected machines are patched, and none of the articles I've read say anything about spam relays. While it may be true that if a machine is vulnerable to this worm it may also be vulnerable to becomming a spam relay, there is no real correlation.

      In short, the virus writer probably just wanted to be a dick and screw with everyone's infastructure, as opposed to having some kind of altruistic "I'll make the world see the error of their ways" agenda.
      =Smidge=

  109. Here's my favorite bit... by qtone42 · · Score: 4, Insightful

    Poor programming by Sasser's creator makes infected machines shut down.

    That should make the writers happy... that their ineptitude made global news.

    I am not impressed with the foo of these cut-and-paste virus coders. There was a time when it was actually difficult to code one of these things, but come on... they are open-source now.

    No-kung-foo-required.

  110. Interesting? by sameerdesai · · Score: 2, Interesting

    Is this why the IRS computers were down yesterday? I had called them up regarding my return and they said all computers were down. Hmmmm...

  111. Dupe.. by shird · · Score: 2, Interesting

    Not only highly inaccurate (IE?), but also covered by Slashdot two days ago.

    New Windows Worm on the Loose

    Stupidest...story...ever...

    --
    I.O.U One Sig.
  112. Difference between a virus and a worm ? by Anonymous Coward · · Score: 0

    for those of us who are not that knowledge about these things, could someone explain what is the actual difference between a virus and a worm ?

  113. Minor Correction by Anonymous Coward · · Score: 1, Insightful

    Sasser is a WORM not a virus.
    Worm - Independent program that replicates from machine to machine.
    Virus - A program that can "infect" other programs by modifying them to include a, possibly evolved, copy of itself.

  114. Re:M$ - First Post? by Finuvir · · Score: 1
    What will happen if Linux eventually completely replaces MS products on the desktop? Will they have the same security problems?

    Not to the same extent, but certainly if someone is willing to tell you their password there's not much that can be done to secure their system. We won't see as many worms and viruses but I think that security, even in Windows, is at a point now that trojans are the easiest attack to have propogated.

    The security focus of Linux is such that I would expect every effort to be made to make any attack less effective than it would be in Windows, but there's no defence against "Run me!" in an email where regular users are concerned.

    --
    Why is anything anything?
  115. Re:If Im totally up to date with my MS Security st by Macgruder · · Score: 1

    Good practice, btu I don't see that it would stop the spread of Sasser.

    It starts at port 1068, and works it's way upwards. At somepoint, it'll probably find an open port that's not tied to another process. Unless you have it so locked down, that EVERY port above 1024 is blocked, or restricted in some way.

    With the various chat and P2P clients out there, that's tough to do.

    --
    I'm not crazy,I'm actively irresponsible.
  116. Had to share this... by Anonymous Coward · · Score: 1, Informative

    This image compares Microsoft and Apple's home pages recently. Note how Microsoft's webpage is dominated by security warnings, while Apple's is dominated by news about new features and products.

  117. Re:Windows only by Anonymous Coward · · Score: 0

    "Windows" is also Microsoft Windows XP Home. "Linux" is GNU/Linux. Do you say those two like that also?

    My point was that the OP used the hardware name, not the OS name. So sit down, fucktard.

  118. Built in XP firewall not effective by Anonymous Coward · · Score: 5, Interesting

    The built in WinXP firewall does NOT protect against the Sasser worm. I ghosted an XP box three times to confirm this-- not until after applying MS04-014 and/or using an alternative firewall (zB. ZoneAlarm) did I see protection from Sasser or its variants (if they exist... although I did see LSASS crash a few times without the presence of avserveX.exe on the system).

    I don't know about you guys, but the SASSER worm turned an otherwise boring Sunday into wickedly exciting day! Thankyou worm-guy!

    -s

    1. Re:Built in XP firewall not effective by Trogre · · Score: 1

      Really? Did you tell the inbuilt firewall to explicitly block port 445?

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  119. Re:Windows only by AriesGeek · · Score: 1

    My point exactly... What OS does IIS run on?

    --
    Insert offensive troll-style sig here. Please mod or respond appropriately.
  120. Re:If Im totally up to date with my MS Security st by Urkki · · Score: 1
    • Each time the number of people infected gets just a little bit smaller.

    You wish. That'd mean that people actually learn. They don't. Or let's say "we don't", though the things I "don't learn" are mostly not computer related.
  121. Re:If Im totally up to date with my MS Security st by peragrin · · Score: 1

    Patching works wonders for all systems

    MS allows open ports and worms to get through with out much probelms. There hasn't been a major *nix worm since 1988. MS gets one every 3-6 months.

    --
    i thought once I was found, but it was only a dream.
  122. Re:M$ - First Post? by JustDisGuy · · Score: 2, Insightful

    So many people continue to use computers without knowing the full risks associated with them.

    You're mad. I know this is /. but the fact is that most people don't give a shit about how computers work - they just want them to work like an appliance. That's why we have jobs.

    An educated user base? Hah. AIDS is still spreading and you're worried about a computer virus?!?!?

    --
    "Never attribute to malice that which is adequately explained by stupidity." - Hanlon's Razor
  123. Proxy scanning by Slashdot? by AndroidCat · · Score: 1
    With all the fuss about Sasser, I figured that I'd check the logs and see what was knocking. I didn't expect to find Slashdot in there. Wazzup? (66.35.250.150 is slashdot.org for those that haven't memorized it.)
    2004/05/04,07:50:02 -4:00 GMT,66.35.250.150:38047,207.112.91.239:80,TCP (flags:S)
    2004/05/04,07:50:04 -4:00 GMT,66.35.250.150:38082,207.112.91.239:1080,TCP (flags:S)
    2004/05/04,07:50:08 -4:00 GMT,66.35.250.150:38121,207.112.91.239:3128,TCP (flags:S)
    2004/05/04,07:50:10 -4:00 GMT,66.35.250.150:38243,207.112.91.239:8000,TCP (flags:S)
    2004/05/04,07:50:14 -4:00 GMT,66.35.250.150:38287,207.112.91.239:8080,TCP (flags:S)
    Guys, you got some 'splaining to do...?
    --
    One line blog. I hear that they're called Twitters now.
    1. Re:Proxy scanning by Slashdot? by spacefight · · Score: 1

      Looks like someone is enhancing the troll filter in order to prevent people posting via open proxies. So what...

    2. Re:Proxy scanning by Slashdot? by dnixon112 · · Score: 1

      Makes sense. In an earlier Mars rover thread I was linked to a pbs NOVA video about the rovers. PBS for some strange reason allows only US residents to watch these videos (I'm in Canada). After using a public US based proxy to circumvent PBS's useless attempt at control, I tried to login to Slashdot only to find that it doesn't recognize my userid/pw combo. Needless to say, after removing the proxy I could login as normal.

    3. Re:Proxy scanning by Slashdot? by Anonymous Coward · · Score: 0

      I get those same scans after I get banned for my regularly scheduled troll rampage.

  124. Infected here by AppyPappy · · Score: 1

    I was setting up a new machine. I turned it on, it set up XP. Before I could get the firewall installed, it was infected.

    Luckily, we are all firewalled to the hilt so we haven't been hit anywhere else.

    --

    If you aren't part of the solution, there is good money to be made prolonging the problem

  125. Re:M$ - First Post? by RoLi · · Score: 2, Interesting
    But as long as people are willing to give up their passwords for chocolate

    I think you don't understand the problem.

    People giving away passwords are not a problem except for themselves.

    Windows is a problem for everybody because a worm can exploit millions of machines automatically.

  126. Actually related to Internet Explorer? by Junks+Jerzey · · Score: 2, Informative

    Yet another virus is causing problems with Internet Explorer

    Does it have anything to do with Internet Explorer? Neither of the links provided mentioned anything at all about IE.

    1. Re:Actually related to Internet Explorer? by prshaw · · Score: 1

      Quit trying to confuse the issue with facts! We are technical here, we don't need to be accurate here.

  127. Slashdot Jumped the Shark by Fubar411 · · Score: 4, Funny

    Wow, I'm witness to Slashdot jumping the shark. An article summary bore no resemblence to the actual article. This hasn't happened before.

    1. Re:Slashdot Jumped the Shark by Anonymous Coward · · Score: 0

      Hey, I think you've mislaid something:

      <sarcasm> & </sarcasm>

      There we go, much better.

  128. Re:Decent firewall, regular updates & common s by wwwillem · · Score: 2, Insightful

    Pick two out of three :-).

    Nearly all my systems are Linux based or updated with the latest patches from Redmond. But I have here one box running Windows 95, daily used for email and browsing, behind a firewall that's as locked down as possible. On the other hand, the last security update or virus definition download happened at least three years ago. And yes, the common sense topic also applies, because I've trained my wife (the main user of that box) from day one to mistrust any attachment.

    So, this box, without being updated, has over the years always been virus free. And probably its chances are getting better by the day, because who is writing virusses for Win95, or IE4 or even WordPad....

    Colleage of mine is already working a week to install XP on a new notebook. While connected to the net (only sw firewall, no hw router) to get the Windows Updates, she got hit already. Of course I told here she was stupid not to buy a firewall box first, but oh well, who listens to me :).

    Conclusion: get that firewall and use common sense!!

    --
    Browsers shouldn't have a back button!! It's all about going forward...
  129. So very true!!! by Anonymous Coward · · Score: 0

    Happens here all the time. The firewall only delays the infection. Usually a MBA type as they are all given laptops.

  130. Dual boot works for me... by gillbates · · Score: 3, Interesting

    I've found that the best solution to the problem of Microsoft's constant and ever more serious security holes is simple:

    Dual boot with Linux. Linux for the network; Windows for the games.

    Just use Linux as your network-enabled OS, and Windows for everything else. Log off the internet or disconnect your DSL or broadband before you reboot into Windows, and you'll be fine.

    It is really that simple - I just disconnect my network connection when I'm running Windows. Let's face reality here:

    • The majority of PC users run Windows. So you need Windows to communicate with the rest of the world. If you want to write free software that benefits the average PC user, you have to target Windows. There are a lot of "average" users who couldn't use Linux, but not many geeks that can't use Windows.
    • Linux is far more secure when exposed to a network than Windows.
    • Yes, there are patches available for Windows, but some of us have better things to do than constantly patch our machines and spending hours trying to figure out why the latest Microsoft patch "broke" something that worked previously. And...
    • Neither I nor my professional colleagues have the time to constantly patch our desktop machines. We have work to do. We shouldn't have to deal with security holes that shouldn't be present in a commercial operating system.
    • Even should you put forth the effort to stay fully up to date, your boxes still contain a plethora of security holes; 6 months from now, Microsoft will be issuing patches for today's vulnerabilities that have yet to be discovered. Considering that more Windows security holes are discovered in the average month than have been discovered in all 10+ years of Linux's history, I feel a little safer running Linux.

    So the solution is simple: Linux is your network OS, and Windows is your "friends and family" OS.

    --
    The society for a thought-free internet welcomes you.
    1. Re:Dual boot works for me... by RzUpAnmsCwrds · · Score: 1

      "Neither I nor my professional colleagues have the time to constantly patch our desktop machines. We have work to do. We shouldn't have to deal with security holes that shouldn't be present in a commercial operating system."

      I sure hope you don't use SSH. Or the Linux kernel. Because both of those have had root exploits in the last year.

      Patching your system is something you have to do on *any* system.

      If you are "too busy" to patch your system, then you shouldn't be getting on the Internet at all.

    2. Re:Dual boot works for me... by GMFTatsujin · · Score: 1

      Neither I nor my professional colleagues have the time to constantly patch our desktop machines. We have work to do. We shouldn't have to deal with security holes that shouldn't be present in a commercial operating system.

      It's been said by smarter folks than me: Security is a process, not a product.

      I assume you still look both ways before crossing the street -- why? It's the same street, you're walking the same route, with the same feet... You're telling me that you can't just figure out when a car will be driving down the street without looking?

      Keep looking both ways to cross the street, and keep patching your operating system. Same damn thing.

    3. Re:Dual boot works for me... by ndege · · Score: 1

      Simple question: How do I play windows-only network games? ie: SubSpace (aka Continuum).

      --
      Sig Return: 204 No Content
    4. Re:Dual boot works for me... by pknoll · · Score: 1
      Log off the internet or disconnect your DSL or broadband before you reboot into Windows, and you'll be fine.

      I only run Windows to play games, but the games I play are online. So, while certainly effective, this solution is not practical for me.

      So I guess I'll have to stick with my firewall, NAT'ing, AVG, Spybot, and AdAware. /sigh.

    5. Re:Dual boot works for me... by necro2607 · · Score: 1

      Sweet, people actually play that? A band I like (Funker Vogt), which I saw a live concert of last year, made music for it... probably a theme song. It's called Subspace if you want to search for it online or whatever. :)

    6. Re:Dual boot works for me... by adamofgreyskull · · Score: 1

      That's fine unless you want to play one of those spiffy windows games on the internet...

      I don't have this problem because I only play CS/Q3/UT200* on-line under Linux, but I'm sure there are many new network-enabled games that only run in Windows.

  131. A previous posting by cexshun · · Score: 1

    This was posted to a comment I made about an earlier article regarding port scans:

    Re:Reduce Load (Score:0) by Anonymous Coward on Tuesday April 27, @09:42AM (#8983914) yeah, because connect() is such a bandwidth hog...

    Here ya go buddy. Eat it!

  132. Re:Windows only by Anonymous Coward · · Score: 0

    dude, Macs is not an OS

    I think he meant "emacs" :)

  133. Backdoor Dangers by gregarican · · Score: 2, Informative

    To me the more dubious part of the Sasser worm is that it can lead to other backdoor processes being planted on a host PC. That's why some sources are stating that just running a removal tool and then patching is enough. The backdoor processes would still be present on the host PC. That means the best removal tool would be the old format command. Ouch.

    Starting with Code Red and Slammer I would just bash Microsoft without regard to any other factors. But now I am seeing things a bit more objectively. After all, these recent exploits weren't created until after the security bulletins and patches were released to the public. And there was about a full two weeks for the public to patch their systems.

    If Linux had as broad of a home user base I'm sure some published vulnerabilities and patches would result in much the same. Joe Six Pack, whether using Windows or Linux, would be slow to patch their systems. And that would lead to some rather uninventive script kiddies writing easy exploits working off of published POC examples.

    1. Re:Backdoor Dangers by gnu-generation-one · · Score: 1

      "If Linux had as broad of a home user base I'm sure some published vulnerabilities and patches would result in much the same."

      Did we mention the difference in severity between Windows and Linux exploits?

      (i.e. the Linux ones don't usually lead to the meltdown of any network they're connected to)

    2. Re:Backdoor Dangers by gregarican · · Score: 1

      They could if effectively exploited. A root exploit could just lead to planting a zombie process that blindly scans the network with dozens of threads, replicating itself out. Wouldn't this be similar to what we are seeing with Sasser?

      Any vulnerability that allows admin/root access would leave a host open for network meltdown I would think.

  134. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0

    Yeah, because they need to learn about firewalls in order to get their work done.

    Do you know how to change your radiator fluid? Is that part of the drivers test?

    No, because it's not necessary to know in a WELL BUILT system, car or OS.

    Dicknose.

  135. Easy to remove by Overzeetop · · Score: 2, Funny

    Actually, this is quite easy to remove...I talked my mother through it over the phone (and she doesn't know the difference between AOL and the internet). Sure, it took her 30 minutes to perform all three steps (boot to safe mode - 8 minutes, delete the exe's - 12 minutes, and remove the registy keys - 10 minutes), but it was actually quite simple. Most of the delay came from me trying to walk her tough the process over the phone wihtout having my machine set up identical to hers:

    Me: Okay, press the button on the computer to turn it on and then press f8
    Mom: Ess or Eff?
    Me: Eff-Eight, the function key
    Mom:Press F8 and hold it? Do I press F and hold it while I press the 8?
    Me: No, F8 is a key at the top of the keyboard, near the center.
    Mom. Oh. Okay, the starting windws screen is up, do I press F8 now?
    Me: Yes
    Mom: (long pause) It's coming up (pause) Okay, I have my normal picture on the screen.
    Me: Oh. Okay, lets turn the computer off and try again.
    [rinse, repeat, rinse, repeat, rinse, repeat]

    It's sort of like talking your dog through doing open heart surgery over the telephone, with the only commands you can give being "sit", "speak", and "heel", and the only feedback is the dog barking.

    At least now she's been forced to install a working antivirus program and the firewall software.

    --
    Is it just my observation, or are there way too many stupid people in the world?
    1. Re:Easy to remove by metamatic · · Score: 1

      I didn't have to talk my mother through anything, because her computer's running Linux.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  136. What ARE Win98SE users supposed to do? by dpbsmith · · Score: 1

    OK, I'm completely baffled. My wife is a non-techie but cool-headed. She runs Win 98 SE and installs any critical Microsoft patches when the system prompts her that such updates are available.

    I just checked the MS website and they say no patches are available for Windows 98 because it is not considered a "critical" problem and they only patch "critical" problems.

    So presumably my wife will not even be informed of the problem.

    Is there anything in particular that she ought to be doing?

    The descriptions say that Windows 98 systems cannot be infected "but can spread the infection." How is this possible? How can a program that runs on a system and spreads an infection not be considered "an infection?" Does the infection-spreading-program-that's-not-an-infectio n survive a reboot?

    1. Re:What ARE Win98SE users supposed to do? by gregarican · · Score: 4, Informative

      Just like the ASN.1 vulnerability that is patched through one of the recent Microsoft patches. Supposedly Win98/ME PC's aren't affected by the issue. But looking at my company's Win98 PC's I saw the msasn1.dll file present. And researching things a little bit I saw that the standard implementation of the ASN.1 command parser is affected on any and all platforms. From a Nortel H.323 gateway to a Cisco router to a Windows 2003 Server to a Windows 98 PC.

      This was months ago that I read this. I called into the Microsoft PCSAFETY toll free number and a tech indeed acknowledged that Windows 98 and ME PC's were vulnerable. And they e-mailed me a link to download the patch (not one of the hoax e-mails either, so no jokes!!). Since then I deployed it to all of my Windows 98 PC's and know that they are at the same standard as the Windows 2000 and XP machines.

      What kind of company releases patches and leaves out some client versions that are still safe from the EOL cycle? That's what Microsoft did with the ASN.1 patch.

      And what kind of company releases patches that obviously weren't tested on clients that were running USB storage, DLT storage, and IPSec agents? Look at the KB835732 patch. It broke all of these driver loads, leaving patched PC's running at 99% CPU utilitization after rebooting.

      Nice, really nice. Risk stability and compatibility issues versus being exposed to an Internet-borne worm. I'm not blaming Microsoft for having vulnerabilities. All OS'es do to one degree or another. But I am blaming them for leaving our client versions and not thoroughly testing code they should've been working on for 5 months.

    2. Re:What ARE Win98SE users supposed to do? by gregarican · · Score: 1

      I saved the e-mail the Microsoft rep sent me regarding the Windows 98 SE client fix. Just in case anyone called bullshit on it. Here it is below, although the password has long since expired...

      CASE_ID_NUM: SRX040219602629
      MESSAGE:
      Hello,

      The hot fix for your issue has been packaged and placed on an HTTP site for you to download.

      WARNING: This fix is not publicly available through the Microsoft website as it has not gone through full Microsoft regression testing. If you would like confirmation that this fix is designed to address your specific problem, or if you would like to confirm whether there are any special compatibility or installation issues associated with this fix, you are encouraged to speak to a Support Professional in Product Support Services.

      The package is password protected so be sure to enter the appropriate password for each package. To ensure the right password is provided cut and paste the password from this mail.

      NOTE: Passwords expire every 7 days so download the package within that period to insure you can extract the files. If you receive two passwords it means you are receiving the fix during a password change cycle. Use the second password if you download after the indicated password change date.

      Package:

      KB Article Number(s): 828028
      Language: English
      Platform: i386
      Location: (http://hotfixv4.microsoft.com/Windows%2098%20Seco nd%20Edition/nosp/29224/1/free/167199_ENU_i386_zip .exe)
      Password: {wY7cF7

      NOTE: Be sure to include all text between '(' and ')' when navigating to this hot fix location!

      Thanks!

    3. Re:What ARE Win98SE users supposed to do? by sgasch · · Score: 1

      Upgrade.

    4. Re:What ARE Win98SE users supposed to do? by Anne+Thwacks · · Score: 1
      A: Upgrade to Linux.

      Dont you even read ./?

      --
      Sent from my ASR33 using ASCII
    5. Re:What ARE Win98SE users supposed to do? by CowboyBob500 · · Score: 1

      My sister runs an old P233 with Win98 SE. Explain how she upgrades Windows without buying new hardware?

      Don't worry though, she'll soon be following the lead of my mother and having Mandrake installed on there next time I'm over her house.

      No smart comments about needing someone's help to install Linux either, she needed my help to show her how to upgrade her IE for her online bank, never mind install Windows.

      Bob

    6. Re:What ARE Win98SE users supposed to do? by Anonymous Coward · · Score: 0

      Upgrade, so we can be left wide open to vulnerabilities as well? I feel much safer knowing that the majority of worms affect 2K/XP only.

  137. As they say... by Anonymous Coward · · Score: 0

    History for Nerds. Stuff that mattered.

  138. Re:Windows only by abb3w · · Score: 1


    We had one machine left that missed the regular updates. Due to its horrible programming, the worm interferes with normal TCP/IP operation, which made updating afterwards difficult. Pulling up the task manager and killing the process it ran as (avserve.exe) then allowed me to get the machine to update windows and the anti-virus definitions normally.

    --
    //Information does not want to be free; it wants to breed.
  139. Coast Guard by baldcamel · · Score: 2, Interesting

    For those that are interested the worm serverly affected the UK coastguard BBC

  140. Re:Windows only by Anonymous Coward · · Score: 0


    VIRUSES not VIRII you fucking retard.

  141. You gotta be kidding me by gosand · · Score: 2, Insightful
    still am of the opinion that it doesn't matter how many patches M$ releases. The fact is, we need an educated user base. So many people continue to use computers without knowing the full risks associated with them.

    Really? Who do you know that knows the FULL risks associated with using computers? Before this worm, I didn't know what port 445 was for - but I knew I had it blocked on my firewall. Maybe you are talking in a perfect world, but there is ZERO chance that all computer users will realize the full risk of using them. If they did, they wouldn't be using computers. I have been using computers since the early 80s, and I don't claim to know all the risks associated with using them.

    I am not anti-computer-education, but what you are talking about is a pipe dream. For jebus sake, we still have people wiring their life savings to people in Nigeria, and guys buying penis enlargement pills.

    --

    My beliefs do not require that you agree with them.

  142. And all you 'marketshare' trolls just STFU now... by Anonymous Coward · · Score: 0

    ...because even if OS X had Windows-level marketshare, worms and viruses would not be much of a problem. Why? Because OS X ships with 0 ports open, the root account is disabled by default, and even when you're running as an admin, you have to authenticate before any serious damage could be done.

    The difference is Apple designed the security into OS X from day one, they didn't try to bolt it on later like Microsoft did with Windows.

  143. Re:M$ - First Post? by Paulrothrock · · Score: 1

    But Linux can be patched in such a way that regular users can't do anything nasty to their systems. Perhaps that's the key: Limitations on the use of the system that require some level of skill to remove, therefore proving the intelligence of the user. Dumbasses get one that's totally tied down (for their own protection) while 1337 g33ks get powerful systems because they're not chocaholics.

    --
    I'm in the hole of the broadband donut.
  144. can't use the patch by SoupGuru · · Score: 1

    Unfortunately, whenever I try patching my Windows box it brings it to a crawl. Literally hours before I can navigate to a point to uninstall it. MS has a KB on the problem with very sketchy details on a workaround.

    It has gotten me to use my Mandrake box a little more....

    --
    What doesn't kill you only delays the inevitable
  145. Problem with Microsoft, NOT the Worm by SamSpectre · · Score: 1

    We had a TERRIBLE time with the Sasser worm at work today. When I went home afterward I decided to run the Windows Updates (that I almost never do) to patch my game machine at home. My XP-Pro machine on a cable-modem was running clean (I've been playing City of Heroes since Saturday) before the Windows Updates. Ran the patches. Rebooted. Hangs on reboot. Hangs on reboot again. Hangs on a third reboot. After an hour of percussion therapy I booted into Safe Mode w/ Networking and updated a newer Video driver. Rebooted. Works fine now. It's amazing to me that Microsoft's own updates can render a machine unbootable (to a desktop).

    I'm wondering if there's any way people (the world?) could begin a Class-Action Lawsuit against Microsoft for lost time, mental anguish, etc. due to their crappy software! Everytime this stuff happens I'm reminded of the Bill Gates cameo in the South Park movie. The memory of that scene never fails to make me smile!

    1. Re:Problem with Microsoft, NOT the Worm by SamSpectre · · Score: 1

      If stupidity equals running Windows Update and then rebooting to a blank screen? Yup, guess that's me! Wow, I am in awe of the size your brain! Idiot.

    2. Re:Problem with Microsoft, NOT the Worm by Anonymous Coward · · Score: 0

      Windows Update sometimes screws up. The best way to get updates is to click the Windows Update catalog and download them from there. Then you can close your browser and other programs and safely install them from your hard drive.

  146. Don't worry.... by vwjeff · · Score: 4, Insightful

    If enough machines get infected you won't have to worry about anything. The network will be flooded.

    Seriously folks. Microsoft release the patch 21 days ago. If the worm came out before the patch I would be more critical but it didn't. Hopefully Microsoft decided to turn on automatic updates by default in service pack 2 for XP.

    1. Re:Don't worry.... by Ruprecht+the+Monkeyb · · Score: 5, Interesting

      Yes, they released the patch 21 days ago. They also released a hotfix at the same time that breaks a non-trivial # of computers.

      Those of us forced to work and support a Windows environment are caught between a rock and a hard place. We don't dare apply a brand-new patch on production servers, or roll it out across the enterprise, but if we wait too long, an exploit hits what the patch supposedly fixed, and we get smacked (plus raked over the coals on /. for being incompetent).

      I try to get new so-called critical patches applied within 7 days -- usually sooner, depending on when I can afford to take servers down, etc. But it won't be long before one of these wide-spread worms hits a vulnerability that's just been patched in the last day or two. Hell, I run several layers of AV protection that checks for updates hourly, and twice I've gotten hit by viruses before the updated signatures were available.
      -

    2. Re:Don't worry.... by bluntmanspam · · Score: 2, Interesting

      About the patch being released 21 days ago:
      Our machines were all patched up as of Wednesday and still got screwed by this worm. Microsoft released a new patch after that and we all apparently needed it to stop the servers rebooting. They weren't getting infected, but they were effectively DOSed until they were patched Saturday.

      Before I get derided about not having them behind a firewall, they were getting hit by users who were behind our shields.

    3. Re:Don't worry.... by spectecjr · · Score: 1

      Hell, I run several layers of AV protection that checks for updates hourly, and twice I've gotten hit by viruses before the updated signatures were available.

      Why not use one really good AV instead of "several layers" - which can interact with one another and cause files to be locked when they're scanned?

      Use realtime file checking, and you won't need to scan hourly.

      I'd recomment EZ-Antivirus from Computer Associates. They have 3 teams around the globe working 24/7 to produce updates as the viruses happen.

      --
      Coming soon - pyrogyra
    4. Re:Don't worry.... by Ruprecht+the+Monkeyb · · Score: 1

      I am using good AV software. By 'several layers' I mean at the server, at the workstation, inbound and outbound email scan, gateway, etc.

      And I do real-time scanning; if you read my post again, you'd see I wrote that it checks for updated signatures hourly, not that I ran scans hourly.

      And, honestly, I wouldn't run CA AV software if you put a gun to my head. FAXServe and ARCserve are some of the worst pieces of software I've ever had the misfortune to use. If someone whose opinion on such things mattered to me suggested it, I might look at it. But I'd be very skeptical.

    5. Re:Don't worry.... by WNight · · Score: 1

      What I wonder is why you try to keep users secure on the internet. Why not pull them back behind a firewall that only lets text email and "safe" web pages through? (Strip out javascript, activeX, etc.)

      I understand that people need access to the database server, and to the version control software, and even to google (and what it points to) and email, but I think you could do this fairly safely if you took the right approach. Start by chopping everything off, then selectively send some sanitized data.

      People whine about using only apps that people know, but nobody ever joins a company knowing the five or ten weird apps that only that company uses. Few of our users have used any of the three version control apps we use and we manage to teach them - usually in fifteen minutes and life goes on. Why the big fuss about using an email client they know, or a browser they know?

      EMail clients are dead simple to use and they aren't supposed to be browsing the web all day.

      It seems like we could end this whole "virus" thing if we made a few decent decisions at a management level. Not get a handle on the patches, not keep up, but end the whole thing.

    6. Re:Don't worry.... by AJWM · · Score: 1

      Amen. A few known apps, a few known ports, and close off everything else.

      I've got pretty much everything firewalled off here. The 'nix boxes don't really care that much, but it keeps the Windows boxes safer. I just looked at my firewall logs and it looks like sasser attacks were coming in every couple of minutes for a while, then dropped off for about a half-hour, then there was a brief flurry of one every six or seven seconds for the last couple of minutes.

      I'm tempted to program it (the firewall box) to make a "SPLAT!" sound every time an offending packet hits the iris, er, is dropped.

      --
      -- Alastair
    7. Re:Don't worry.... by Red+Pointy+Tail · · Score: 1

      I don't get you. You are saying that the DOS causes the server to reboot, until a hotfix was applied?

      Yes, there was a list of hotfixes for computers with specific issues with the MS04-11 patch - but none of it seem to be that your computer would continually reboot, unless you are really infected with sasser itself.

    8. Re:Don't worry.... by Carnildo · · Score: 1

      Seriously folks. Microsoft release the patch 21 days ago. If the worm came out before the patch I would be more critical but it didn't. Hopefully Microsoft decided to turn on automatic updates by default in service pack 2 for XP.

      I've got an XP box sitting next to me that I don't dare turn on. I patch it every time I turn it on, but it's been a little over a month since I last needed to use it, so it's unpatched.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    9. Re:Don't worry.... by slashdot_commentator · · Score: 2, Informative

      Don't blame the user for an inadequate network design. Servers should be segregated from "users" on separate subnets with firewalls between them. You can poke some more holes into the internal firewalls to account for applications; it sure beats having nothing.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
    10. Re:Don't worry.... by spectecjr · · Score: 1

      And, honestly, I wouldn't run CA AV software if you put a gun to my head. FAXServe and ARCserve are some of the worst pieces of software I've ever had the misfortune to use. If someone whose opinion on such things mattered to me suggested it, I might look at it. But I'd be very skeptical.

      Well I don't know if this counts for anything but CA's AV software is what Microsoft uses internally.

      --
      Coming soon - pyrogyra
    11. Re:Don't worry.... by nacturation · · Score: 1

      I've got an XP box sitting next to me that I don't dare turn on. I patch it every time I turn it on, but it's been a little over a month since I last needed to use it, so it's unpatched.

      Um, you do run a firewall don't you? Prefereably such as a hardware firewall/router rather than directly connecting it to the internet on a publicly accessible IP address? Or, if not that, then you certainly have ZoneAlarm or other similar software firewall? Okay, at the very least you turned on the Internet Connection Firewall that is included with XP, right?

      --
      Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
    12. Re:Don't worry.... by WNight · · Score: 1

      Yeah, the concept of firewalls is now obsolete. They were great in the day when you were protecting against outsiders but the aptly-named 'Trojan' worms filling the net have shown that assumption to be flawed.

      Instead everything needs to be firewalls from everything else. Through every means too. hosts.deny everything, opening only specific holes. Have a router that blocks everything but web traffic to the web proxy, email to the email server, and file sharing with a specific trusted machine. No peer-2-peer access allowed at all, even between servers. Filter *all* broadcast traffic. You, the admin, can turn bits on as needed for diagnostics (and off right away!).

      Then, have the email server strip everything except text out of the email. Run it through an HTML parser and send the text output if needed. Web bugs can be a real security problem in high-security installations. Keep the attachments (if any) and let users request them from an admin after your staff scans them. (This process - necessarily in "writing" will keep them from having personal email sent to work - serves two purposes.)

      Ditto for web stuff. Filter out javascript. Filter out flash, quicktime, and all other pluggins unless you need one for work. Ideally, filter out downloads of anything but html pages except for certain developer machines (or whoever *needs* it.)

      But mostly, never allow any peer-2-peer visibility or access within the company. Treat everyone as if they're a virus-ridden outsider; they probably are.

    13. Re:Don't worry.... by Cardbox · · Score: 1

      The patch they released 21 days ago was the one that broke SHARE detection so that all our users were getting "Missing SHARE.EXE" reports from their applications. We had to patch our app to work with the patched XP.
      Fortunately users are so used to Microsoft buggering things up that they accept it as a perfectly normal part of life and don't claim that we're lying to get ourselves out of trouble.

    14. Re:Don't worry.... by mpe · · Score: 1

      People whine about using only apps that people know, but nobody ever joins a company knowing the five or ten weird apps that only that company uses.

      Or whatever customisations/templates/etc the company might use in order to make it easier do whatever they do.
      Few of our users have used any of the three version control apps we use and we manage to teach them - usually in fifteen minutes and life goes on. Why the big fuss about using an email client they know, or a browser they know?

      The real big here is "We must use Windows because people only know how to use Windows". When there isn't even one interface called "Windows", it's not unknown for the real user interface to be a custom application which runs in a maximised window or even the actual user interface is something other than a QWERY keyboard mouse and monitor (such that no user could possibly tell if the machine was running Windows, Doors, Floors or whatever.)

      It seems like we could end this whole "virus" thing if we made a few decent decisions at a management level.

      e.g. doing some good (old fashioned) "systems analysis" rather than Microsoft Windows everywhere as some kind of fashion statement.

    15. Re:Don't worry.... by fanatic · · Score: 1
      What I wonder is why you try to keep users secure on the internet. Why not pull them back behind a firewall that only lets text email and "safe" web pages through? (Strip out javascript, activeX, etc.)

      Somebody puts laptop on external network, gets infected, then puts laptop on internal network. Congratulations - you're toast.

      Somebody has laptop or desktop at hjome, gets infected, dials in through your fancy VPN. Congratulations - you're toast.

      There may be a simple easy answer, but you haven't overed all the bases yet.

      --
      "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
    16. Re:Don't worry.... by dcam · · Score: 1

      I installed the CA AV that came free with the CDs of updates that MS is now shipping for free. With everything enabled and with the latest pattern file, it didn't catch a Netsky variant that came in by email, until I went to save the file to the HD. Given that the home network is sitting behind a NAT box, and that most information flows in and out through the router, the greatest vector for attack is email. If the AV can't pick this up on the way in I'm not interested. AVG had no problems.

      --
      meh
    17. Re:Don't worry.... by Carnildo · · Score: 1

      Um, you do run a firewall don't you? Prefereably such as a hardware firewall/router rather than directly connecting it to the internet on a publicly accessible IP address?

      I assume so, but since this is a work machine, I don't know the details. I do know the IP address is a routable one.

      --
      "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
    18. Re:Don't worry.... by WNight · · Score: 1

      Yeah, I didn't go into detail in this post. The only real way to do it is assume that everyone is an attacker. Don't have a safe and dangerous side of a firewall, instead block everything between everybody, except for known safe things.

      Because nobody can see anyone else, infections can't spread. (Assuming you trust your servers - still a lot easier to trust a single machine.)

    19. Re:Don't worry.... by bluntmanspam · · Score: 1

      Right, but if you take a look at some of the newsgroups (like microsoft.public.windows.help_and_support) you'll find that many people were having this issue and no antivirus tool could find the worm. Also, none of the files that the worm was known to drop existed on these systems, and the registry entries it was known to create were not there. It wasn't common, so nobody really has an answer for it, but there were several machines that, like mine, were fully patched and showed no other signs of infection apart from lsass crashes and reboots.

      There probably weren't enough of us to get any attention, so we were all just left wondering. Let me reiterate, though, that Microsoft either released a new patch for this or Windows Update didn't patch the machines properly, because all of the machines showed that one update as the only one they needed to install. AND we know that they were patched up previously.

    20. Re:Don't worry.... by bluntmanspam · · Score: 1

      I'm not blaming anyone for anything, I am simply stating fact. However, if you look at the characteristics of the worm and the way Windows 2000 networks operate, you will see that the two most vulnerable ports in Windows are the exact ones that a server uses to communicate with client machines. Ports 139 and 445 are required for network communication to a client machine (actually either/or). Without those ports open to clients, there can be no file sharing, drive mapping, etc.

      Basically what you are suggesting is that we make our network non-functional.

    21. Re:Don't worry.... by spectecjr · · Score: 1

      I installed the CA AV that came free with the CDs of updates that MS is now shipping for free. With everything enabled and with the latest pattern file, it didn't catch a Netsky variant that came in by email, until I went to save the file to the HD. Given that the home network is sitting behind a NAT box, and that most information flows in and out through the router, the greatest vector for attack is email. If the AV can't pick this up on the way in I'm not interested. AVG had no problems.


      If you want it to scan your email, you buy the add on to scan your email. That way if you need that false veneer of protection, you can pay extra for it if you want it.

      The virus is ONLY dangerous once it gets saved to the HD. It's not dangerous sitting as a MIME encoded packet in your inbox.

      --
      Coming soon - pyrogyra
    22. Re:Don't worry.... by slashdot_commentator · · Score: 1


      What server is going to need mount a filesystem to a user's PC? You close outbound port to 445 and at least you constrain the ability of the worm to spread from the servers. Also, by having the internal firewalls in place, you can localize and locate any damage the rogue worm will do.

      As long as you allow laptops or let users introduce material to a PC, you have to acknowlege that internal connections are as able to introduce worms/viruses as external network connections. That requires use of internal firewalls. Even if it may be problematic in this instance, its still better than nothing.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
  147. Weeks to patch by truthsearch · · Score: 5, Interesting

    And let's face it; if your machine is not properly patched, it's probably already being used as a spam relay, so it's not the spammers who would want this.

    In a corporate network environment, such as mine, a few weeks is barely enough time to get a patch onto every desktop. First a few days are spent testing it. Then it has to be pushed out to all of the users. Server patches often have to wait until weekends because they can't be down during the week. Then manual installs have to be done for all the "non-standard" setups.

    Then there's the new computer I got yesterday with our standard corporate developer's build. Of course the build doesn't have the latest patches yet, so when I turn on the computer for the first time, immidately after logging in McAffee catches the virus. So then I have to hunt down the right patches from the right people and reboot repeatedly until I can log into the network without getting the virus.

    So I lost all of yesterday fixing the problems on my two computers and my office is as up to date as possible with getting patches onto workstations. Machines go for weeks without new patches because it's impossible to distribute them when some break applications, and therefore require much testing.

    I wrote a 70 page document explaining why we should switch from Windows to Linux. Management wouldn't even start to read it. This is what they get for their ignorance.

    1. Re:Weeks to patch by BigBir3d · · Score: 2, Insightful

      Send them your post instead of a 70 page report. Mgmt sees 70 pages as a way to try to confuse them into making a decision. They want a one page answer. Doesn't make it right... but you need to work within the system to work the system. No different than a computer really.

    2. Re:Weeks to patch by dasmegabyte · · Score: 3, Insightful

      Their ignorance? What about yours?

      A new computer is like a new baby. You need to inocculate it or it'll get sick. If you're putting out in a wild environment without protection -- and a suitably large organization is almost as bad as the internet itself -- you're just asking for trouble. The best way to prevent this is to patch it up to a useful level behind a one way firewall. An even better way is to update your corporate ghost image once a month so you're never more than 30 days behind in your patches.

      Furthermore, the days of agressively testing patches should be over for everything but servers. Let your employees run autoupdates and if one of them does break your machines, roll it back. Servers are a special case, because if you lose the TCP stack on your mail server it's much worse than if Ted from Marketing loses his.

      Management doesn't want Linux because they don't want to lose days learning an alien operating system when they already have YOU to do the job of protecting them from viruses. What would you say if your plumber told you that to unclog a leak, you'd have to buy a new house?

      --
      Hey freaks: now you're ju
    3. Re:Weeks to patch by surprise_audit · · Score: 1
      Let your employees run autoupdates and if one of them does break your machines, roll it back.

      Chances are, if it breaks one machine it'll break a whole department, if not the whole company. That'll look really swell on your resume...

    4. Re:Weeks to patch by bankman · · Score: 5, Insightful
      I wrote a 70 page document explaining why we should switch from Windows to Linux. Management wouldn't even start to read it. This is what they get for their ignorance.

      This is a very typical mistake. Management, especially senior management does not read 70 page long pamphlets about a topic that they most likely don't understand.

      Write a very concise executive summary, comprising no more than two pages, outlining in an easy to understand language why switching to Linux will be beneficial to your organisation. Emphasise on cost and security and explain the interdependencies. Also explain the business freedom your organisation will gain (management decides when to make major changes to your infrastructure, not Microsoft etc.). Preferably get a colleague with an idea of management's language to help you with it.

      It's like every business pitch: First you get them hooked with what they really want, then you get the stuff in that you want.

      --
      I feel so sig.
    5. Re:Weeks to patch by Anonymous Coward · · Score: 2, Insightful

      I wrote a 70 page document explaining why we should switch from Windows to Linux.


      Maybe if you spent the time patching machines instead of writing proganda your managment would have more faith in your decision making skills.

    6. Re:Weeks to patch by Spoing · · Score: 1
      1. In a corporate network environment, such as mine, a few weeks is barely enough time to get a patch onto every desktop.

      Suggestions;

      Create a base-line standard machine and make sure everything matches (including firmware).

      Reduce any odd-ball computers so that the baseline means something.

      Automate mainteance to these machines *entirely*.

      Put everything you can on the network -- data and applications. (Runtime environments should be local, though custom apps should be locked down elsewhere.)

      For servers, have a seperate baseline installation. Automate the deployment also, though set aside test and roll-back time.

      1. I wrote a 70 page document explaining why we should switch from Windows to Linux. Management wouldn't even start to read it. This is what they get for their ignorance.

      I wrote a 50 page document and a 30 page add-on that described basic admin functions. One tip: Don't use the default password on the database. Really; it's that bad.

      Show that you can handle Windows, and while you're at it drop in something that runs on Linux that management can get all excited about. A wiki, a test replacement for Exchange (if you have Exchange). The costs -- risks and money -- to switch are minimal since it's "done"; that will be more effective. That said, I did a similar demo for my boss and his reaction was "good...does it run under Windows?". This was for a web app.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    7. Re:Weeks to patch by dasmegabyte · · Score: 1

      Will it look as bad as allowing your entire company to get a virus?

      Since exploits come out less than a month after Microsoft releases a patch, you better damn sure get your ass in gear when one's released. And how long does it take to test the basic functionality of a machine after a patch? Less than an hour I'd wager. A day to look for flakiness. Waiting two weeks is surely overkill.

      I for one thing it's far superior to break a network trying to fix it than waiting for a virus to take it down. The former you can in earnest blame on the vendor. The latter -- well, since the fix already existed, the blame's on you.

      --
      Hey freaks: now you're ju
    8. Re:Weeks to patch by surprise_audit · · Score: 1

      Luckily, I'm not one of the poor bastards supporting Wintel boxes. I didn't see it, but apparently all our monitoring systems were constantly rebooting, except for the one running RedHat. I'll be putting a couple more like that into use Real Soon. :)

    9. Re:Weeks to patch by Spoing · · Score: 4, Interesting
      I agree on the reasons why management doesn't want Linux. That and fear; they don't run it so they suspect it's major voodoo. Running a test system with a web app or two is like a camel's nose, though.

      1. A new computer is like a new baby. You need to inocculate it or it'll get sick. If you're putting out in a wild environment without protection -- and a suitably large organization is almost as bad as the internet itself -- you're just asking for trouble. The best way to prevent this is to patch it up to a useful level behind a one way firewall. An even better way is to update your corporate ghost image once a month so you're never more than 30 days behind in your patches.

      I strongly disagree;

      Firewalls don't protect jack if ports are open client side within your network that shouldn't be.

      Infections can't be stopped by running virus scanners.

      Testing is very much necessary, as are customizing the desktop so that it doesn't have exposed interfaces. (Run a port scan or better yet Nessus. Know what's running and in most cases TURN IT OFF.)

      Baseline configuration is the way to go since you're at the mercy of the vendor's marketing team otherwise -- and marketing teams don't care about security, stability, or usefulness.

      When done with this, go back and work on tuning firewall(s) and routers. Split the network into parts that are isolated by function using the router; accounting should not be directly accessable from development or development from production.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    10. Re:Weeks to patch by Anonymous Coward · · Score: 0

      > Write a very concise executive summary, comprising no more than two pages, outlining in an easy to understand language

      Just use PowerPoint (gag, yes, just do it). Up to 8 slides should be fine. Emphasize saving money. Every statement should be about saving money. Whether it's about security, licensing, support, or whatever, tie the statement into reduced overall costs.

      Then if they like it the next step is to give them the Cliff Notes version of that 70 page document.

      Would you get your Dad to switch to linux using a 70 page document??

    11. Re:Weeks to patch by dasmegabyte · · Score: 1

      Firewalls don't protect jack if ports are open client side within your network that shouldn't be.

      I was suggesting to put up the box behind a firewall appliance -- a cheap Dlink would do -- as the ONLY thing behind it. Put it on your installation bench sort of like a surge protector for viruses.

      --
      Hey freaks: now you're ju
    12. Re:Weeks to patch by Hadlock · · Score: 1, Redundant

      You should try typing up a summary of your paper. It should be less than a page and any details should be left to be near the bottom of the page. The first Three sentences should go somthing like this:

      We can save $X and improve efficency. Converting from Windows to Linux will increase uptime, improve employee morale, and overall make our division more productive and visible to upper managment in a good light. Here's why:

      Talk in terms they understand, give incentives, then (possibly) explain to them how your division is going to make them look good.

      --
      moox. for a new generation.
    13. Re:Weeks to patch by Anonymous Coward · · Score: 0

      "I wrote a 70 page document explaining why we should switch from Windows to Linux. Management wouldn't even start to read it."

      Powerpoint is your friend.

    14. Re:Weeks to patch by komisar · · Score: 1

      This is really important, so you should limit your executive summary to one page, not two.

      The meek shall inherit the earth, but not the mineral rights. - J. Paul Getty

    15. Re:Weeks to patch by phallstrom · · Score: 3, Insightful

      Couple of thoughts in a "windows world"...

      - as soon as your baby is born and put in the nursery with the other brand new babies... they would all be infected... where would you suggest we put the new baby right off the bat?

      - have you ever dealt with Ted from Marketing? I've found that if Ted is high enough up and he can't play solitaire then the sh*t is going to hit the fan pretty dang fast!

      - if a plumber, electrician, and carpenter told you that in the long run it would be a lot cheaper just to buy a new house instead of have them out every other day, wouldn't that make sense?

    16. Re:Weeks to patch by Spoing · · Score: 1
      1. I was suggesting to put up the box behind a firewall appliance -- a cheap Dlink would do -- as the ONLY thing behind it. Put it on your installation bench sort of like a surge protector for viruses.

      I still disagree. Let's start with the surge protector. If you plug your power into a good surge protector but not any other wires (network, phone, external audio, ...) you can still have your system fried. My little sister did that, and I spent way too much time on the phone walking her through repairs...eventually buying the system from her to get off the hook on supporting it. Turns out the system board and network card were fried.

      Getting back to firewalls...

      For a home user? Even if not, it's not very effective since connecting to other systems opens up the chance that the user will choose to do something they shouldn't, or may turn off system-level protections, or a "helpful" program will open up a hole that normally would be plugged by the firewall itself.

      Example: I helped "speed up" one friend's machine. It was the only one he had, behind a cable modem and a firewall router.

      Checking the firewall using a remote scanner showed that the system had all ports completly hidden.

      Checking his system, it had Microsoft's "low security" setting. That was enough for about 30 spyware programs (not cookies) and 6 viri to end up on his system.

      After cleaning up the mess and reinstalling some dammaged software, I turned it up to "medium". Not because I thought this would protect him much, even with the firewall, but because it was a good first step and with some people no good deed goes unpunished. (I told him explicitly what I proposed, what I suggested for the future, and he agreed before I made changes. If it were my system, I would have backed up data, nuked it, and put back a minimially exposed OS installation.)

      Firewalls aren't security. They are a tool to be used with other tools to perform a task that may lead to better security; "process before product" or "process not product" are two mantras to keep in mind. Firewalls are ineffective and give a false sense of security if you just plug them in like a surge suppressor and do nothing more.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    17. Re:Weeks to patch by truthsearch · · Score: 1

      I'm a developer, not an admin. I don't patch machines. And the document was written on my own person time. A factual comparison of operating systems and development platforms is not propaganda.

    18. Re:Weeks to patch by KinCross · · Score: 1

      Management doesn't want to read a 70-page document.

      Make it one page. Make it compelling. Put the numbers up front.

      Then back it up with appendices with the more granular arguments.

      --
      -- secret asIAN man (not Secret Asian Man)
    19. Re:Weeks to patch by dasmegabyte · · Score: 1

      I get upset by slashdotters who argue "phantom" points -- points that I didn't make or imply in either of my grandpatent posts.

      What I said, paraphrased, was: "If you are head of an IT department charged with installing software on a new machine, a good idea is to place it behind a firewall with no open ports, to prevent worms from exploiting the vulnerable operating system while you patch it."

      How you got from that I was suggesting that a firewall is the only security you need, or that I was making any suggestiong to home users, I have no idea. My guess is poor reading comprehension skills, as this would also explain why you think the plural of virus is viri when it's goddamn viruses.

      <Offtopic-rant>
      Why do people insist on putting -i at the end of every word that has a singular form ending in s? The plural of iris isn't irii. The plural of axis isn't axi. The whole purpose of the -es plural is that you are supposed to use it when a word ends in s. Why must people emply this queer new form? It just makes them sound like pompous douches -- or is it douchi?
      </Offtopic-rant>

      --
      Hey freaks: now you're ju
    20. Re:Weeks to patch by dasmegabyte · · Score: 1

      as soon as your baby is born and put in the nursery with the other brand new babies... they would all be infected... where would you suggest we put the new baby right off the bat?

      I believe I suggested plugging it into a firewall that was one way, e.g. denied all incoming connections regardless of port or source. Yes, I did suggest that.

      have you ever dealt with Ted from Marketing? I've found that if Ted is high enough up and he can't play solitaire then the sh*t is going to hit the fan pretty dang fast!

      This is true enough, but it's also true that if Ted's machine gets a virus and has to be completely rebuilt, he's probably going to blame you for not protecting his machine. And he'd be right to do so, since you didn't do it. Which is why you should get the patch out to one or two underlyings in marketing the instant it's released, see if they have any trouble, and then roll it out to everybody else within the next day or so.

      With security, if you're waiting two weeks, you're not doing your job. When the front door needs a new lock, you don't leave it open for 15 days, you don't care if Ted the Marketing Asshole has keys or not, you just fix it, and deal with the consequences later -- because they're nowhere near as bad as leaving the door open!

      if a plumber, electrician, and carpenter told you that in the long run it would be a lot cheaper just to buy a new house instead of have them out every other day, wouldn't that make sense?

      It would. But I'd probably still ignore them. I like my house and moving is a hassle I don't need, so it is worth the extra effort and expense to keep the current one. I'd pay even less mind to the suggestion if it appeared to me that the plumber, electrician, and carpenter who I was paying anyway wanted me to shell out extra cash and effort just to make their jobs easier.

      --
      Hey freaks: now you're ju
    21. Re:Weeks to patch by Anonymous Coward · · Score: 0

      Getting back to firewalls...

      For a home user?


      Yes, if a home user has trouble with a firewall just sitting between their machine and internet connection, I doubt they would have much luck getting accustomed to using Linux on a daily basis. Unless its one of those "I installed Debian for my Grandma" success stories.....

    22. Re:Weeks to patch by Anonymous Coward · · Score: 0

      A new computer is like a new baby. You need to inocculate it or it'll get sick.

      Horrid analogy... a more proper analogy is that a new computer is like a baby without an immune system. Inocculation is the process of teaching the immune system what "bad" looks like so that it can fight it off if it ever shows up in the system.

      Computers are not self-healing and they don't have an immune system.

    23. Re:Weeks to patch by Anonymous Coward · · Score: 0

      STFU or I'll send the Sasser wormii down your path.

    24. Re:Weeks to patch by Spoing · · Score: 2, Insightful
      Have you seen the cartoon "Jacki Chan's Adventures"? Think Uncle: "Firewall not important!" (You talk to Uncle now.)

      1. I get upset by slashdotters who argue "phantom" points

      That not me. Check the thread again; here.

      If you pick on someone else's ignorance, do not get upset if the favor is returned.

      Your rant at the end about viri/viruses/... is the same nit picking.

      The distinction between process and tools is bedrock; it's the single most important part. Your comments ignored it; you yourself gave the dumbed down 'use a firewall'.

      Specifically;

      1. What I said, paraphrased, was: "If you are head of an IT department charged with installing software on a new machine, a good idea is to place it behind a firewall with no open ports, to prevent worms from exploiting the vulnerable operating system while you patch it."

      "Firewall not important!"

      1. How you got from that I was suggesting that a firewall is the only security you need, or that I was making any suggestiong to home users, I have no idea.

      This;

      1. I was suggesting to put up the box behind a firewall appliance -- a cheap Dlink would do -- as the ONLY thing behind it. Put it on your installation bench sort of like a surge protector for viruses.

      Why bother with a cheap hardware firewall box for one machine unless you're talking about a home machine. (Isolate machines at the router and update from a trusted server that is read-only and exposed to the isolated segment only.) Home or corporate network, you've shot a degree of certianty by relying on a firewall to ensure security; "Firewall not important!"

      I'll match your rant: As for things that I'm sick of one is being forced to deal with the apathy and 'it is good enough' attitude of people who are paid to know better.

      --
      A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
    25. Re:Weeks to patch by dasmegabyte · · Score: 1

      Computers are not self-healing and they don't have an immune system.

      Well, one could argue that virus software is your PC's immune system. But i didn't want to overthink the analogy, because that's butt.

      --
      Hey freaks: now you're ju
    26. Re:Weeks to patch by claygate · · Score: 1

      I know this sounds weird, but maybe someone should form an Open Marketing standard. It has short essays and forms that can be customised easily so that the network admins or tech guys who aren't exactly skilled in rhetoric could hand in a memo that is written by someone who is skilled.

    27. Re:Weeks to patch by CodeTRap · · Score: 1

      "Firewall not important!"

      You're missing the point completely. The point of his suggestion is, that after you ghost that nice little image, you place it behind a small hardware firewall, patch it up to snuff, then deploy it. Leaving the nice little firewall back on your bench, ready to be used for the next deployment.

      I thought it was obvious.

      --
      CodeTrap (www.codetrap.net)
    28. Re:Weeks to patch by wcdw · · Score: 1

      Several people have offered good advice vis-a-vis the 70 page document. Keep it short, simple (facts and writing level) and heavily biased. ;)

      It also helps, particularly if you are a known Linux advocate, if you can find a relatively senior person who is sympathetic to your cause, and have them present the idea as if it were their own.

      It's beyond sad that politics should enter into the realm of logic, but it's also inescapable....

      --
      If you're not living on the edge, you're just taking up space!
    29. Re:Weeks to patch by Anonymous Coward · · Score: 0

      Active directory policies can be used to great effect to a) automate patch distribution and b) set up a new PC install AND patch at the same time.

      Dont blame Mircosoft that you dont know how to use the tools they provide.

      And Critical updates break apps? Bffft. I'm calling bullshit.

    30. Re:Weeks to patch by Anonymous Coward · · Score: 0

      You are an idiot.

      What kind of programmer writes 70 pages without compensation. An obsessive one. You are not an artist. You are skilled labor. Deal with it. If you want to programm for a company that uses Linux as their OS then quit your job and find another one, otherwise, STFU!

    31. Re:Weeks to patch by dkf · · Score: 1
      I've found that if Ted is high enough up and he can't play solitaire then the sh*t is going to hit the fan pretty dang fast!
      But only if you position the fan carefully under the building that you push him off of. Working out those trajectories can be a real b*tch...

      On the plus side, he's a goner either way. ;^)

      --
      "Little does he know, but there is no 'I' in 'Idiot'!"
  148. This is so frustrating by j-turkey · · Score: 3, Insightful

    It's funny how articles claim that the worm has caused all kinds of damages -- from banks to postal systems, to transit systems. The tone of the article seems to lay blame largely upon the worm itself. This is absolute horseshit. If users (and IT personnel) at these governments and places of business were responsible enough to do their jobs and ensure that computers were adequately patched, this problem never would have occured.

    Furthermore, if personnel took a single iota of initiative by installing and maintaining a simple firewall -- these issues would have been far less widespread (although this can still be spread through a network via infected laptops brought in from a home network). The important thing here is that the creators of this worm, the IT groups who let this happen, and the individual broadband users affected really share blame for the spread of this worm. Let me use an example, if you live in a shitty neighborhood and you leave your door unlocked, you are partially responsible for some jerk breaking into your house -- sure, they broke the law, but you helped facilitate that.

    OK, one more topic to rant over then I'll STFU. I see alot of Slashdotters blaming Microsoft for this problem -- saying that running Linux or xBSD would solve this problem. Bullshit, fanboys. I am a Linux/Free software advocate and that argument is absolute bullshit. Every once in a while, remote exploits are discovered for these Free products. Most of the time, patches for these apps are released right away -- faster than their commercial counterparts are able to react. The users will still need to be smart enough to apply the patch. Well, in this case, Microsoft's patch was available before an exploit was in the wild. The reason why this worm is so widely distributed is because the user base (and administrative base) is large enough that there is a large cross section of people who have no idea what they're doing.

    If Windows went away tomorrow and Linux became the defacto standard, we would have the same issues. All of those MCSE's who allowed this to happen will become RHCE's who will still allow something like this to happen. That certification doesn't make them any smarter -- bad admins are bad admins. Clueless users are clueless users, regardless of the operating system they use. It's easy to blame Microsoft for this, because they have deep pockets, a huge market share, and shady business practices -- but all code has bugs. Microsoft did the right thing, their userbase just wasn't smart enough to do the right thing.

    --

    -Turkey

    1. Re:This is so frustrating by wintermute740 · · Score: 1

      "...systems. The tone of the article seems to lay blame largely upon the worm itself. This is absolute horseshit. If users (and IT personnel) at these governments and places of business were responsible enough to do their jobs and ensure that computers were adequately patched, this problem never would have occured."

      I have to take exception with this little bit of your rant, as others have pointed out that the patch itself has broken things for several users. And patching 5000 machines in a corporate environment takes lots of testing to avoid killing a critical app. Otherwise, I completely agree with your other points.

    2. Re:This is so frustrating by darkfire5252 · · Score: 1

      While users/admins failing to patch is a large part of the problem, an even bigger part is this:

      LSASS listens to the internet, and you can't tell it not to. This isn't a problem for people running behind NATs or in otherwise secure networks, but for the general public, this is a stupid thing to have on by default, and AFIAK you can't turn it off, you can only block it.

      As far as the MS firewall, the reason it doesn't get used much is that it completely lacks the ability to open up a port that you want open: it's all or nothing.

      These are both rather large problems that are WELL within MS's ability to fix. It's not like this is the first worm to take advantage of ports open by default.

    3. Re:This is so frustrating by soliptic · · Score: 1
      This isnt actually fair.

      Its 4:30pm. I should be working til 5pm. But I came home at 3, because none of the bloody computers worked, thanks to Sasser.

      Our IT dept run a very tightly maintained Windows network - firewalls, industrial email/attachment scanners, virus checkers, etc. I spend all day at work chucking as the spam+virus rolls in (hundreds per day) to our public mailboxes, every one correctly flagged, every dangerous attachment correctly stripped. I've only seen one false positive in 6 months, and that was marking a legit email as 'Spam?' - I've not seen it remove any attachment which was legit.

      I'll think you'll find there are many companies and organisations whose IT staff are responsible and on-the-ball, but the shocking mess that is Windows, means that this crap beats them anyway. Honestly - I'm not one to bash Microsoft, but after this run of worms, I've realised that the state of OS security is inexcusable. Literally - there are no excuses for it, whatsoever. Its shoddy as fuck.

      Allow me to underline the I'm-not-one-to-bash-MS topic. Yes, I think Windows security is a disgrace, but I dont blame the IT guys for not running Linux(etc) instead. We are too dependent on specific business apps. Similarly, I still run XP at home, and will switch to Linux, ooh, maybe when hell freezes over - not because I want it that way, really, but because I'm dependent on application level software.

      I will, however, be setting up a physically separate PC running Linux or *BSD to act as a firewall - as soon as I have the money for another PC - which is, again, probably when hell freezes over, sadly.

    4. Re:This is so frustrating by j-turkey · · Score: 1
      LSASS listens to the internet, and you can't tell it not to. This isn't a problem for people running behind NATs or in otherwise secure networks, but for the general public, this is a stupid thing to have on by default, and AFIAK you can't turn it off, you can only block it...As far as the MS firewall, the reason it doesn't get used much is that it completely lacks the ability to open up a port that you want open: it's all or nothing.

      I only looked into the MS Firewall a little and I felt that there are better apps out there that are freely available (like Zone Alarm, etc). Broadband networks are dangerous -- probably the most targeted networks out there (by script kiddies). I don't mean to sound like an elitist, I understand that not everybody knows how to protect themselves, but it's a dangerous world. Users absolutely need some kind of firewall protection -- whether it's NAT or something local to stop unwanted packets (I prefer both, actually).

      The fact is that alot of OS'es have unnecessary ports open - Microsoft isn't hte only one -- RedHat does the same thing (although RH9 seemed to be a bit better than previous versions). You're right though -- Microsoft is particularly bad about this.

      If I had more time, I'd dig around and find the article where Microsoft promised to shut off unnecessary services (by default) in future versions of their OS -- I know I'd read about it somewhere. I guess in this case, it's too little, too late.

      --

      -Turkey

    5. Re:This is so frustrating by praxis · · Score: 2, Interesting

      "I'll think you'll find there are many companies and organisations whose IT staff are responsible and on-the-ball, but the shocking mess that is Windows, means that this crap beats them anyway. Honestly - I'm not one to bash Microsoft, but after this run of worms, I've realised that the state of OS security is inexcusable. Literally - there are no excuses for it, whatsoever."

      Do responsible and on-the-ball IT staffs use SMS to patch their workstations in case individuals forget. Do responsible and on-the-ball IT staffs use a domain policy to enforce firewall rules on individual workstations. Do responsible and on-the-ball IT staffs enforce the running of up-to-date antivirus software on each workstation. Do responsible and on-the-ball IT staffs use external firewalls, IDSes, etc? Is there an excuse *not* to? Is it not due diligence on MSFTs part to release the patch (a month ago), supply a domain policy controlled firewall for each workstation, SMS servers for patch distribution, and leave it up to the IT staffs to deploy them properly. I think MSFT did it's due diligence here, and the IT staffs of infected networks did not.

    6. Re:This is so frustrating by ryanw · · Score: 1
      If Windows went away tomorrow and Linux became the defacto standard, we would have the same issues.
      Personally, I used to be a heavy Linux fan, but in the last two years I've converted to a MacOSX fan. But I still believe you're wrong. Having a Unix based OS dominant in the community would not result in the same wide spread of viruses/trojans.

      Unix by it's nature does not have you running as root/administrator. The logged in user does not have access to put binaries and startup scripts all over the harddrive. The logged in user can't start a service below port 1024. So the wide spread of viruses sent via email would affect the current logged in user only.

      I'm sure linux virsus could be just as nasty or worse, but they would not have the same global impact and spread like wildfire like windows ones do. Windows 95/98/ME is nothing like a Unix box. And most of the problem systems aren't running XP/2000 yet.

    7. Re:This is so frustrating by miffo.swe · · Score: 1

      From your reasoning every apache server out there would be a slave because what better zombie than a real server with a nice hookup? The real reason windows is so popular is that its so damn easy to write viruses for it. Dont blame the users who thought they bought an easy OS to take care of security for them. Microsoft is responsible for the security of windows and not anyone else just as much as the free software movement is responsible for its security.

      --
      HTTP/1.1 400
    8. Re:This is so frustrating by soulhuntre · · Score: 1

      "As far as the MS firewall, the reason it doesn't get used much is that it completely lacks the ability to open up a port that you want open: it's all or nothing."

      Hmm... thats an odd statement. I knwo we sure as hell can open up specific ports when we want to. Care to explain the problem?

      --
      --> Fight tyranny and repression.... read /. at -1!
    9. Re:This is so frustrating by soulhuntre · · Score: 1

      "Do responsible and on-the-ball IT staffs use SMS to patch their workstations in case individuals forget. Do responsible and on-the-ball IT staffs use a domain policy to enforce firewall rules on individual workstations..."

      No. That would involve them actually learning the tools MS provides to make administering a large network easier instead of whining about how they want to switch to Linux all day.

      This type of thing is EXACTLY what the domain policy system is in place for, between it and SMS there is really no excuse to whine and cry.

      --
      --> Fight tyranny and repression.... read /. at -1!
    10. Re:This is so frustrating by SlashDread · · Score: 2, Interesting

      I take offence at you remarks.

      - After 15 years of exp in the field, I DO have an iota. At least one for initative.

      - We DO have a firewall.

      - We have an Auto-Update push server. It should have updated us last week, but who knows? SUS server reporting is crap.

      - We were hit, four laptops running XP. (They may have picked it up from outside, but they were surely spreading it inside.) A Citrix server BSOD'd from the patch.

      - Microsoft sells its products as if 12 y/o can administrate it, knowladge where it is needed about security and firewalls, is not properly taught.

      - MS admins generally are busy reinstalling laptops, updating MS office, cleaning up after McAfee detected Yet Another Virus.

      - MS is totally dominant on the desktop, which they dont mind, but does help the fastness of the spreading of worms.

      - These remote root exploits, seem to often hit EVERY windows flavour, that worries me. When will this cardhouse fold?

      - If you piss off enough people, people will push back. MS pisses off a lot of people.

      In essence, all this I blame on... well not me.

      well I learned one thing, personal firewalls on windows, are becoming a nessicity.

      "/Dread"

    11. Re:This is so frustrating by j-turkey · · Score: 1
      And patching 5000 machines in a corporate environment takes lots of testing to avoid killing a critical app

      You make a good point. For some groups, these patches take their toll, and they're certainly an exception. I don't claim to be a security expert -- but surely there's a way to help slow the spread of such a worm across an internal network (I've already seen snort rules that can take care of it). The fact is that something can be done, and to do nothing out of fear that something will be broken is clearly not the solution -- because doing nothing has turned out to be just as much of a liability as acting too soon.

      However, you do have a valid point. There are always exceptions. Maybe the linked article found them all. Personally, I doubt that these issues were all due to the fact that a network was too large to act quickly enough.

      --

      -Turkey

    12. Re:This is so frustrating by Anonymous Coward · · Score: 0


      Why do ill-informed rants by pinheads unable to read previous, highly moderated posts on the same page constantly get moderated as informative?

      I don't need to knock down this ID10T's rantings point by point, it has already been done before s/he/it even posted.

      If you have mod points, knock the parent down to size (-1), and s/he/it better hope I don't have mod points when I get home or I'll mod down other posts by this slack-jawed, drooling lump of unworthy clay.

    13. Re:This is so frustrating by j-turkey · · Score: 1
      I'm sure linux virsus could be just as nasty or worse, but they would not have the same global impact and spread like wildfire like windows ones do. Windows 95/98/ME is nothing like a Unix box. And most of the problem systems aren't running XP/2000 yet.

      I think that you're contradicting yourself here. This worm is a WindowsXP/2000 worm -- the problem systems are running XP/2000.

      Also, if you look at the latest series of outbreaks using email as a vector, Unix is just as vulnerable. User accounts can still spam out and propigate a worm. A user account can also trojan itself (although usually not as root). If someone can trojan a user account, the getting-root part becomes far easier.

      Furthermore, the same amount of widespread damage can occur from a user account. A worm can put itself in the user's home directory, and can put it in a user's startup script. The concepts aren't any different. Sure, you don't have access to directly open services below port 1024, but you can sure create an outbound BSD socket. You've still got full outbound network access and if you believe that *nix's networking code is truly faster than that of Windows, then you've got an even more widespread problem.

      Finally, most of the attacks that we see (the Sasser Worm is an exception) relies on social engineering to spread. A user has to intentionally launch an application. Again, this takes us back to a user account, but with the latest spam worms, that's all they need.

      I just don't see how *nix is any different. Your argument does nothing to support why *nix worms couldn't spread like wildfire like the Windows counterparts do.

      --

      -Turkey

    14. Re:This is so frustrating by Anonymous Coward · · Score: 0

      I'll think you'll find there are many companies and organisations whose IT staff are responsible and on-the-ball, but the shocking mess that is Windows, means that this crap beats them anyway.

      So this thing just strolled right through the firewall, sat down and ordered an iced tea? Come on.

    15. Re:This is so frustrating by j-turkey · · Score: 1
      The real reason windows is so popular is that its so damn easy to write viruses for it.

      Just re-read that statement and tell me whether or not it makes sense. Are you suggesting that the vast majority of consumers prefer Windows because it's so easy to write viruses for it? That's absolutely nonsensical. Maybe you meant something else.

      Microsoft is responsible for the security of windows and not anyone else just as much as the free software movement is responsible for its security.
      Microsoft is responsible for the security of its own computers, nothing more. You are responsible for the security of your own computer, regardless of the OS. The open source community isn't responsible if my computer gets owned. I am.

      Am I totally misunderstanding you or are you putting somethign really funny in your pipe?

      --

      -Turkey

    16. Re:This is so frustrating by j-turkey · · Score: 1
      I take offence at you remarks.

      First of all, there are exceptions to everything. Nothing is absolute.

      In essence, all this I blame on... well not me.

      Well, that's very convenient. If you're in charge of the network, you should accept some responsibilty. You should have been reading up on this -- you should have been reading up on how to stop the internal trafficing of this worm. And right now, you should at least be asking yourself "how can I stop this from happenning again". To not accept any responsibility for your part in this is reckless. You should be informed as to your IT strategy. You should be proactive and asking questions like: How much downtime is acceptable? What will we have to spend to get to that point? Is it worth it? Is there a compromise that we can make so it is worth it? What are the risks? Do we have the IT staff to maintain that kind of infrastructure? Can we afford it? If you are not in a position to make these decisions, but are "in the know" enough to think about this stuff, then it's probably part of your job to bring these questions to someone who can make these decisions.

      If you piss off enough people, people will push back. MS pisses off a lot of people.

      aah -- the mantra of the free enterprise. I hear you, I agree, and I believe it. Microsoft will eventually go away.

      well I learned one thing, personal firewalls on windows, are becoming a nessicity.

      Indeed, in fact, this is very important: a gateway firewall != security. Not by a long shot.

      Microsoft sells its products as if 12 y/o can administrate it, knowladge where it is needed about security and firewalls, is not properly taught.

      MS admins generally are busy reinstalling laptops, updating MS office, cleaning up after McAfee detected Yet Another Virus.

      In both cases, you are blaming the structure of how a business is run. In the former case, a CTO should know better than to believe that Windows just runs itself with a 12-year-old at the helm...that's why they're a CTO. That CTO should hire competant admins, and they should know what to look for. In the latter case, that a problem with how IT is implemented within a company. How can Microsoft possibly be responsible for that?

      I think you may have taken exception in part because I appeared to be bashing MCSE's. That's not what I was trying to do. The example I used was trying to call out the vast number of MCSE's out there and show that because of the size of the pool, there are going to be a large number of dumbasses out there. The point is (through all of this) is that it's not entirely Microsoft's fault. It might not be your fault -- but someone in your organization clearly is...and it's not as simple as blaming the guy who chose Microsoft for choosing Microsoft.

      --

      -Turkey

    17. Re:This is so frustrating by j-turkey · · Score: 0, Flamebait
      don't need to knock down this ID10T's rantings point by point, it has already been done before s/he/it even posted.

      Maybe they weren't effective. Maybe I don't buy it. Maybe you can't effectively knock my points down. Unfortunately for you, there's no consensus at Slashdot. Nice try on the anonymous though.

      f you have mod points, knock the parent down to size (-1), and s/he/it better hope I don't have mod points when I get home or I'll mod down other posts by this slack-jawed, drooling lump of unworthy clay.

      Pahahahaha! Bring it on. I could care less about Slashdot karma.

      --

      -Turkey

    18. Re:This is so frustrating by Anonymous Coward · · Score: 0

      LSASS listens to the internet, and you can't tell it not to.

      Absolutely untrue. RTFM Lamer.

    19. Re:This is so frustrating by MCraigW · · Score: 1


      Hmm... The user interface doesn't let you open or close specific ports in the built-in XP fire wall. Or perhaps I'm missing something. I'm certain there are registry settings to block specific ports, but that isn't exactly the same thing.

    20. Re:This is so frustrating by soulhuntre · · Score: 1

      It's there, but I don't have a non SP2 XP box to look up the method.

      On a happy note, a XP box with SP2 installed has a nice GUI for such things right in Control Panel.

      --
      --> Fight tyranny and repression.... read /. at -1!
    21. Re:This is so frustrating by Anonymous Coward · · Score: 0

      "If users (and IT personnel) at these governments and places of business were responsible enough to do their jobs and ensure that computers were adequately patched, this problem never would have occured."

      If they had done their jobs and ensured that computers were adequately patched, their computers would likely have broken by the patch.

      Of course, that's even better, because we can berate them for installing patches without testing, and we can berate them for not patching in hour 1 and getting a virus. Lamers.

    22. Re:This is so frustrating by Tony-A · · Score: 1

      In essence, all this I blame on... well not me.

      Right.
      Design problems? User error. Administration error. Pilot error.
      Ever notice how Microsoft software always subtly shifts any possible blame ohnto somewhere else. Anywhere else. Read them sometimes when you actually know what is going on.

      What else can they do? That is Microsoft's problem, not my problem.

      Microsoft sells its products as if 12 y/o can administrate it
      Well Microsoft does make it easy to set up something as long as you do everything Microsoft's way (although a hard disk installation of Knoppix is aruguably much simpler and easier). Get into something complicate or where you want to do things your way, and you discover that OpenBSD is actually user-friendly (but don't tell anybody).

      The difference between perception and reality makes a big crack for all the malware. The idea of hiding all pertinent information possible and then expecting expert knowledge from the user if something does go amis ought to be preposterous, but Microsoft has been doing it for a long time and seems to be intent on doing more and more of it. By some counts, Linux has many more security issues than Microsoft, but the Microsoft exploits seem to accomplish something and the Linux exploits never seem to do much of anything.

    23. Re:This is so frustrating by rnelsonee · · Score: 1
      I think people should take reasonable steps to protect their own data - but c'mon, the blame lies on the shoulders of the virus writers. If you leave your door unlocked and someone goes on your property, opens your door, and steals all your stuff... it's not your fault! Sure, you could have prevented it, but it still took the willful act of someone else to break the law. If this happened to you, you should feel a little embarassed, but you have every right to be mad at the burglar. Your argument is like saying it's the womans fault for being raped just because she doesn't carry pepper spray, or never took a self-defense course.

      I'm only saying this because since Sunday night, two of my friends (neither of which are into computers) had to wipe their hard drives, and most likely because of this virus/worm (PCs constantly rebooted). One friend is a teacher at a University, which usually has excellent IT security. The other is my roommate who is on a network with me (I have a hardware firewall and ZoneAlarm on my PC). Granted, my roommate doesn't do much in terms of anti-virus software, but he does run Norton once in a while. And the teacher, well, he shouldn't have to worry about patching his system. But the end result is two 'normal' users had to wipe their drives. And they're both smart enough not to download crap the don't recognize, which makes them smarter than half the users out there. I just don't see how we can blame them when they make, in my eyes, reasonable efforts to avoid viruses. They *should* do things like run AV once in a while, but anything else, like patching your OS, is crap. Either make a secure OS in the beginning, or have the OS patch itself. We all know most users have no idea what a patch is anyway, so why expect them to do so?

    24. Re:This is so frustrating by mckyj57 · · Score: 1

      > OK, one more topic to rant over then I'll STFU. I see alot of Slashdotters
      > blaming Microsoft for this problem -- saying that running Linux or xBSD
      > would solve this problem. Bullshit, fanboys. I am a Linux/Free software
      > advocate and that argument is absolute bullshit. Every once in a while,
      > remote exploits are discovered for these Free products. Most of the time,
      > patches for these apps are released right away -- faster than their
      > commercial counterparts are able to react. The users will still need
      > to be smart enough to apply the patch. Well, in this case, Microsoft's
      > patch was available before an exploit was in the wild.

      The patch was available, yes. But unfortunately as with most Windows patches,
      they release an omnibus that changes library code that can affect virtually
      any other application and service on the system. This one did,
      too; it was very buggy.

      Most *nix-based software doesn't have this problem. Unless it is something
      like the kernel or glibc being fixed, a patch to one service has almost
      no chance of causing problems in other services.

      That is the downside of the "seamless integration" that Microsoft
      so often trumpets, and that is why Windows sucks for maintainability.
      It is also the reason that no one should listen to Microsoft patch-whiners
      (like you?).

    25. Re:This is so frustrating by Anonymous Coward · · Score: 0

      It's there, but I don't have a non SP2 XP box to look up the method.

      On a happy note, a XP box with SP2 installed has a nice GUI for such things right in Control Panel.


      Although I didn't use the Firewall before SP2 much at all, the Windows XP Service Pack 2 update for the Firewall looks like it has alot better features and much-improved interface. I believe parent poster was referring to the pre-SP2 Firewall that comes with XP, which from what I hear sucks.

    26. Re:This is so frustrating by j-turkey · · Score: 1
      Your argument is like saying it's the womans fault for being raped just because she doesn't carry pepper spray, or never took a self-defense course.

      What if that woman is in a dangerous neighborhood wearing nothing but high heels, a black lace thong, and a bra? It's not her fault per se -- but she sure as hell could have done something to prevent it from happenning. In this case, she needs to accept responsibility for not taking precautions. The rapist is the bastard who commited the heinous act -- he's clearly the bastard in the situation. He is to blame...but responsibility? The situation could have been avoided. Just like I shouldn't walk down the street in a shady neighborhood with a clip full of $100 bills hanging out of my pocket. It's inviting trouble. I've got news -- your computer is in a dangerous neighborhood. You've gotta patch your security holes (no pun intended) and start putting some clothes on so your computer doesn't get hosed. Your analogy isn't really fair either...it would only be fair if your proposed rape victim immeadately became a serial rapist after being violated.

      Either make a secure OS in the beginning, or have the OS patch itself.

      Obviously, the former is impossible. Computers are vulnerable -- and there is no such thing as bug-free code. I want to say that again, because you seem to imply that such a thing is possible...there is no such thing as bug-free code. Windows can patch itself (as most other modern OS'es can). You just have to turn it on. Is it Microsoft's fault if you don't know how to turn it on? No -- just like it's not Ford's fault if you don't know how to change a tire.

      As for your example, it's completely antecdotal. What virus/worm were they infected by? How did they get it? How could have they prevented it? Obviously, there has to be some way. And your teachere does need to worry about patching his system...otherwise he wouldn't be in this mess. I've got news for you...viruses and worms will not go away. It sucks -- I know. But sitting there, blaming the people for writing them and not taking precautions is unwise. With that attitude, many more people will fall victim.

      --

      -Turkey

    27. Re:This is so frustrating by shfted! · · Score: 1

      You missed the key point. People DON"T patch Windows boxen because patches are well known to often cause problems. With FOSS, patches rarely if ever cause problems, and never cause problems in unrelated areas -- upgrading Apache doesn't break mail, for instance. If we could trust Microsoft, we'd all be using automatic updates and there wouldn't be a problem -- but we can't, and so people reasonably don't auto-update. The blame is in Microsoft's court.

      --
      He who laughs last is stuck in a time dilation bubble.
    28. Re:This is so frustrating by j-turkey · · Score: 1
      The patch was available, yes. But unfortunately as with most Windows patches, they release an omnibus that changes library code that can affect virtually any other application and service on the system. This one did, too; it was very buggy.

      Most *nix-based software doesn't have this problem. Unless it is something like the kernel or glibc being fixed, a patch to one service has almost no chance of causing problems in other services.

      That is the downside of the "seamless integration" that Microsoft so often trumpets, and that is why Windows sucks for maintainability. It is also the reason that no one should listen to Microsoft patch-whiners (like you?).

      Oh, come on. Look, if you're in a business running custom apps and you find a security advisory with a patch that you don't have time to test before you apply -- most security advisories have information for workarounds. Any admin worth their salt will be able to read these and plan for the worst. That's why they're paid the big bucks. How long have you been doing this for? Can anyone accept responsibility for anything anymore?

      And seamless integration? This integration is between Microsoft apps and the OS -- and Microsoft patches don't usually break Microsoft apps. These apps are either third-party, or custom. You're whining about somethign that isn't necessarily Microsoft's problem. Furthermore, I've had first-hand experience with RedHat's Glibc breaking stuff (which you did mention). A patch to any shared library has an equal chance of breaking something that uses it...regardless of the operating system. It's because of the library, the application which uses it, or both. Changes break things -- I've worked in software development, I've worked in change management -- it's a fact of life. I prefer using *nix...but I don't pretend that just because I use it, my shit doesn't stink. You're whining because you can't find a workaround -- because you can't tie down your internal routers to stop malignant packets. Stop blaming Microsoft for all of the world's problems and open your eyes. I don't care for Microsoft's software or business practices either -- but you know what? Whining about it isn't going to make it go away...and blindly blaming Microsoft every time something goes wrong is just ignorant.

      --

      -Turkey

    29. Re:This is so frustrating by Trogre · · Score: 1

      It's funny how articles claim that the worm has caused all kinds of damages -- from banks to postal systems, to transit systems. The tone of the article seems to lay blame largely upon the worm itself. This is absolute horseshit. If users (and IT personnel) at these governments and places of business were responsible enough to do their jobs and ensure that computers were adequately patched, this problem never would have occured.

      If somebody breaks into your house and you didn't have a burglar-alarm or deadlocks installed, whose fault is it really?

      Society (and your insurance company) will try to tell you that it's your own dumb fault for not having adequate security, but that doesn't change the unwavering fact that the burglar should not have been in your house in the first place.

      Yes, in a hostile environment such as a computer network, administrators are responsible for ensuring the systems are adequately locked down from attacks, and we can call them silly if they don't, but that in no way gives an attacker more rights to invade the computers therein.

      Let's put the blame where blame is due.

      --
      "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    30. Re:This is so frustrating by j-turkey · · Score: 1
      People DON"T patch Windows boxen because patches are well known to often cause problems. With FOSS, patches rarely if ever cause problems, and never cause problems in unrelated areas -- upgrading Apache doesn't break mail

      I run both F/OSS and Windows systems...and I've run all kinds of F/OSS systems. I've run both in a number of different environments. You are wrong about F/OSS patches. Shared libraries are what they are -- if you make a change in a library that lots of applications use, things can break, regardless of the OS. I've seen glibc patches break a number of things in RH. It happens. Just because we use OSS doesn't mean that our shit doesn't stink. The blame certainly doesn't fall in Microsoft's court.

      What applications did the patch break? Some custom-built internal application at someone's company? Well, if they have cash for that, they can afford a systems/network administrator who can actually read the security advisories, look at the proposed workarounds and fix their internal firewalls to stop traffic from this worm. In the business world, you've gotta pay to play, my friend.

      If you run a Microsoft system, and you fail to patch a Microsoft system because you "don't trust Microsoft's patches" and your systems get hosed, it's your fault. It couldn't be any more simple. If you don't like that your CTO decided on Microsoft, find another job that doesn't require you to work with it. If you don't trust their system in the first place, why would you ever run it? I'm amazed by your logic here.

      --

      -Turkey

    31. Re:This is so frustrating by j-turkey · · Score: 1
      Yes, in a hostile environment such as a computer network, administrators are responsible for ensuring the systems are adequately locked down from attacks, and we can call them silly if they don't, but that in no way gives an attacker more rights to invade the computers therein.

      I'm not saying that an attacker has a right to invade anything. However, people need to accept responsibility for not taking precautions. Why do people have to blame something else for everything that happens? We live in a hostile world...be vigilant.

      --

      -Turkey

    32. Re:This is so frustrating by Sj0 · · Score: 1

      hmmmm.... RTFM yourself. The FM sucks assholes. All Microsoft manuals suck assholes. They look thick alright, but then you realize that it's 3 pages long(1 for the manual in your language, 1 for installation instructions, 1 for warantee information) in sixteen different languages.

      Hooray! thanks to the FM I just read, I now know how to say "Microsoft gives you no rights, but we have more" in 16 different languages! THANKS AC!!!

      --
      It's been a long time.
    33. Re:This is so frustrating by Sj0 · · Score: 1

      There's more to adminning than obsessive compulsive security research. Every admin I've ever met who was out there actually earning his paycheque had ten thousand better things to do than putt around slashdot or bugtraq reading up on the latest worm.

      'course, this doesn't matter, since you're being self-righteous. Don't let me get in your way. By all means, keep whining. It's not like the worlds largest software company makes enough profit to start a true security initiative, starting with innovative new designs to stop security holes before they start or anything. Nope, software is insecure, period. It's our fault that microsoft can't get it right the first time. Yup.

      --
      It's been a long time.
    34. Re:This is so frustrating by Sj0 · · Score: 1

      Technically, there were locks on the house, and the house was marketed to you as being secure.

      'course, it's our own damn faults for believing their maketing. I mean, MS has been claiming to be more secure since Windows 98, which is totally ironic, since it seems the newer the version of windows, the easier to exploit it is.

      For all the hoopla, I'd sooner trust a patched, secured(no shares, etc...) Windows 98 machine on a broadband connection than a similarly patched, secured 2k or XP machine. How many of these self-propogating worms existed before 2k introduced the complexities of the NT system?

      --
      It's been a long time.
    35. Re:This is so frustrating by j-turkey · · Score: 0, Flamebait
      There's more to adminning than obsessive compulsive security research. Every admin I've ever met who was out there actually earning his paycheque had ten thousand better things to do than putt around slashdot or bugtraq reading up on the latest worm.

      That's one of the dumbest things I've ever heard. Of course there's more to the job than research, but it's definitely a big part of the job. How are you supposed to adequately keep your systems patched if you're not actively researching new issues? Research is part of the job. Keeping current is also part of the job. If security is important to your company, then that's part of the job. If it's not an important part of the job, then stop whining about what happens when you don't act properly. If you're overworked -- it's not my problem, and it's not Microsoft's fault. The point is that people need to stop blaming everyone else for their own problems, organizational or otherwise. Companies have to pay to play -- and it's not Microsoft's fault if you or your organization can't provide.

      'course, this doesn't matter, since you're being self-righteous. Don't let me get in your way. By all means, keep whining. It's not like the worlds largest software company makes enough profit to start a true security initiative, starting with innovative new designs to stop security holes before they start or anything. Nope, software is insecure, period. It's our fault that microsoft can't get it right the first time. Yup.

      On the contrary, I believe that you may be a little self-righteous as well. All I'm saying is that it's the admin team's responsibility to make themselves aware of, and assess security risks. These things do not find and report themselves...nobody else is more qualified. It's not a perfect world, and bugs will always be found, even if Microsoft does take a proactive OpenBSD-style approach -- security holes will still be found (even OpenBSD has vulnerabilities). I'm not suggesting that it's our fault that Microsoft can't get it right the first time. You are insane if you took that away from my post. I'm saying that there is no such thing as 100% bug free software. It doesn't exist -- period. If you roll out software with the expectation that it is 100% bug free, the consequences resulting from such an action are your fault. Why would Microsoft be culpible for your ignorance?

      If you have a good idea for an amazing, innovative design that magicly stops security holes before they become a problem...by all means, it's a free market. Go nuts. Frankly, I think you're insane if that's the standard that you hold developers to. Nobody does this. Nobody has figured out how to. Back here in the real world, we research security holes and patch them when a patch is available.

      My friend, if you are indeed an admin, you need to grow up and take responsibility for your part instead of finding the guy with the deepest pockets and the worst reputation and pointing your finger there.

      --

      -Turkey

    36. Re:This is so frustrating by j-turkey · · Score: 1
      For all the hoopla, I'd sooner trust a patched, secured(no shares, etc...) Windows 98 machine on a broadband connection than a similarly patched, secured 2k or XP machine. How many of these self-propogating worms existed before 2k introduced the complexities of the NT system?

      The system is more complex because that's what the market demands. If we all used Commodore 64's we'd be secure as hell, because the only way in is via 1200 baud dialup. Now that we have high speed broadband connections, as well as tons of Internet connectivity in our homes, as well as every other integrated bell and whistle imaginable -- operating systems have become bigger and more complex. It's not just Windows, it's every modern OS (with a few exceptions). None of these widespread self-propigating worms could exist before a large percentage of homes and businesses were hooked into a high-speed always-on Internet connection.

      I'm not being pro-Microsoft here -- I'm just being anti-bullshit. Let's try to be objective about this.

      --

      -Turkey

    37. Re:This is so frustrating by j-turkey · · Score: 1
      Of course, that's even better, because we can berate them for installing patches without testing, and we can berate them for not patching in hour 1 and getting a virus. Lamers.

      I'm beginning to feel like abroken record here. First -- what software does the patch break? Anything? Anything shrinkwrapped? Did the admins test the patch? If it really broke something, what about all the workarounds mentioned in the bugtraq (and other) advisories?

      Finally, we're not talking about patching within an hour. We're talking (in this case, it depends on which patch) between 1-4 weeks.

      --

      -Turkey

    38. Re:This is so frustrating by mmurphy000 · · Score: 1
      Do responsible and on-the-ball IT staffs use SMS to patch their workstations in case individuals forget.
      Many smaller businesses do not have SMS. One hopes that smaller businesses run around and apply Windows Update frequently enough, or are set up for automatic patching, but SMS isn't the answer for the majority of the world's businesses.
      Do responsible and on-the-ball IT staffs use a domain policy to enforce firewall rules on individual workstations.
      Many smaller businesses are using a simple SOHO router with NAT as their only firewall.
      Do responsible and on-the-ball IT staffs enforce the running of up-to-date antivirus software on each workstation.
      I sure hope even small businesses pull this much off...
      Do responsible and on-the-ball IT staffs use external firewalls, IDSes, etc?
      See above regarding firewall, and I'm betting most small businesses don't even know what an IDS is.
      Is there an excuse *not* to?
      Sure. Not having an IT staff would be one good reason. The parent poster, like a lot of Slashdot denizens, seem to think the world is flush with IT staffs, when the reality is that many more businesses are small than large, and small businesses typically lack IT staff, almost by definition.
      I think MSFT did it's due diligence here, and the IT staffs of infected networks did not.
      Again, the assumption of the existence of IT staffs. This is not to say that Microsoft is solely to blame for the current situation, but there needs to be better answers than "have a quality IT staff" if you want the problems to go away.
    39. Re:This is so frustrating by mckyj57 · · Score: 1

      > > The patch was available, yes. But unfortunately as with most
      > > Windows patches, they release an omnibus that changes library code
      > > that can affect virtually any other application and service on the
      > > system. This one did, too; it was very buggy.
      > >
      > > Most *nix-based software doesn't have this problem. Unless it is
      > > something like the kernel or glibc being fixed, a patch to one
      > > service has almost no chance of causing problems in other services.
      > >
      > > That is the downside of the "seamless integration" that Microsoft so
      > > often trumpets, and that is why Windows sucks for maintainability.
      > > It is also the reason that no one should listen to Microsoft patch-
      > > whiners (like you?).

      > Oh, come on. Look, if you're in a business running custom apps and you
      > find a security advisory with a patch that you don't have time to test
      > before you apply -- most security advisories have information for
      > workarounds. Any admin worth their salt will be able to read these and
      > plan for the worst. That's why they're paid the big bucks. How long
      > have you been doing this for? Can anyone accept responsibility for
      > anything anymore?

      What are you even talking about? I have been a system administrator for
      over 20 years. I have patched hundreds of systems thousands of times.
      The current state of Linux update management is far and away better
      than what ever used to be on Unix, and it is miles ahead of Windows update
      which is an opaque, reboot-on-general-principles mess.

      When you update on Linux, you have a reasonable chance of divining which
      subsystems will be affected, and you can easily restart services with a
      great deal of confidence that is all it will take. If something doesn't
      work, it is an extremely quick back-out.

      On Windows, it is reboot and hope. Literally.

      > And seamless integration? This integration is between Microsoft apps and
      > the OS

      That is not what Microsoft claims. They claim that other applications
      should be able to link in seamlessly.

      > -- and Microsoft patches don't usually break Microsoft apps.

      They break them frequently.

      > These apps are either third-party, or custom. You're whining about
      > somethign that isn't necessarily Microsoft's problem.

      I'm not whining about anything. I am replying to the whiners who
      claim "all you have to do is patch". Their last patch broke Citrix,
      certainly one of the most mainstream of corporate apps on Windows.

      > Furthermore, I've
      > had first-hand experience with RedHat's Glibc breaking stuff (which you
      > did mention).

      It is only common sense to restart daemons when you update something
      that basic. You don't need to reboot like on Windows.

      > A patch to any shared library has an equal chance of
      > breaking something that uses it...regardless of the operating system.

      Only if the granularity of the libraries is the same. And it certainly
      is not. Microsoft has huge shared libraries with everything lumped together,
      therefore it will break much more often. And does.

    40. Re:This is so frustrating by Sj0 · · Score: 1

      Just keep telling yourself that. I mean, there's so much that you can do with 2k/XP network-wise than you can do with 95/98! :P

      --
      It's been a long time.
    41. Re:This is so frustrating by SlashDread · · Score: 1

      Well in risk of you never reading this Ill reply to an out-of-fp comment.

      I obviously DO take some repsonsibility over our network. Hence the update serve, hence the firewall, hence the risk analasises aboput downtime we DO have, hence the IT strategy (More linux, less windows and NO SCO) at the moment.

      My POINT was, it IS 99% Microsofts fault. Which is what I ment by well, not me.

      The ONLY reason why personal firewalls will be the next big thing in Office env, IS MS crap products, that get owned time and time again OVER REMOTE EXPLOITS.

      Microsoft is responsible for marketing their product as if 12 y/o can admin it, and in most smaller orgs, of less then 200 emps, the admin IS the CTO, but the PHB makes the decisions.

      MS has made it damn wel near impossible for most orgs to ditch them, again, thats THEIR fault, not mine.

      I cant even blaim the PHB for choosing MS, there is simply too much things relying on it. The fileformats f.e.

      So that leaves really just one big finger at MS. What I took offense of is, you state its ENTIRELY the DUMB sysadmins that dont patch their systems fault. THAT. IS. BS.

      The only thing my org can do better, is EVEN STRICKTER security policies, personall firewalls and all that, but why do I feel thats a loosing battle? Why am I feeling Im flying a space shuttle, but servicing requires Sojouz parts, and duct tape? I should have bought Sojouz dammit.

      But how do you sell an 80's rocket to people buying space shuttles? Evidently the fact that a sojouz wont crash is no argument.

      peace

      "Dread"

  149. Old MainFrame Days.. by nurb432 · · Score: 2, Informative

    I used to work at a remote IBM shop years ago, you could tell the mainframe was down when you walked in the ofice and saw the people roaming the halls..

    It was 4 states away, nothing we could do about it, but have chair races and hit the vending machines...

    --
    ---- Booth was a patriot ----
  150. Exactly! Win95 was pretty good. by Bob_Robertson · · Score: 1

    You cite one of the primary reasons that I liked Win95. After 5 years of using it, I had been able to pare down the system processes to a minimum, no open holes, no pointless apps. It ran quite well.

    I missed it until I found KDE.

    Bob-

    --
    The Ludwig von Mises Institute. The reasoning individuals economics
    1. Re:Exactly! Win95 was pretty good. by gregarican · · Score: 1
      "...no open holes..."

      You mean like the WinNuke exploit? Remember when any Windows 95 box could get blue screened from someone remotely sending an out of bounds TCP/IP ping packet? I can't count how many GUI tools that were going around where folks could blue screen others until hearts' content. I must confess my IT team would bounce a PITA company enduser every now and then where I worked :-)

      That would make conference calls pretty funny. Hear folks on the call curse under their breath....$%#$# Windows...grrrr....

    2. Re:Exactly! Win95 was pretty good. by Anonymous Coward · · Score: 0
      No, WinNuke made WinNT machines crash, not Win95.

    3. Re:Exactly! Win95 was pretty good. by Anonymous Coward · · Score: 0

      Not too hot with the old memory there, are you?

      WinNuke most certainly did crash Win95.

      A little education for your trigger-happy ass

  151. Re:If Im totally up to date with my MS Security st by Anonymous Coward · · Score: 0

    I can't believe someone beat me to the Herman's Hermits joke.

  152. Re:If Im totally up to date with my MS Security st by Anonymous Coward · · Score: 0

    Actually, there are several variants of this construction, and it depends on which dictionary you use.

    "No one" as you suggest
    "Noone" as the parent suggests
    "No-one" is acceptable, too

    Not to mention "noone" follows the same pattern as "nobody" or "anyone".

    Get off yer high horse and learn about descriptive linguistics!

  153. Two words.. Hardware Firewall by Nonillion · · Score: 5, Interesting

    If most users would quit being so cheap and buy a firewall appliance like a linksys router, or (for the more savvy) build a Coyote linux box we wouldn't have half of these problems. I run Win2k, Solaris and SuSE linux. The linux box is the only one exposed to the net and hasn't been rooted/hijacked once in the three years it has been exposed. Running stuff like Zone Alarm is like giving a band aid to someone who has a big gaping wound.

    --
    "I bow to no man" - Riddick
    1. Re:Two words.. Hardware Firewall by Anonymous Coward · · Score: 0

      Why is running zone alarm like a band aid? I run ZA and it's set up to block all traffic on all ports except for the ones I allow. Is this not safe enough?

    2. Re:Two words.. Hardware Firewall by maximilln · · Score: 1

      -----
      Is this not safe
      -----
      No, it's not safe.

      Untrusted, invisible code on webpages does have the ability to open holes in any firewall as most users let the firewall autoconfigure for common apps like web browsers. I also wouldn't be too surprised if virus/trojan writers have figured out a way to implement a modified port forwarding which circumvents the holier-than-holy 7 layer model of networking. Any port, even port 80, can be hazardous if there's some webapp which has made itself resident for as long as your web browser is open.

      With web browsers becoming entire OS environments on their own I look forward to the next slew of relays and trojans which filter and pass packets from inside the web browser. Call it a "wrapper" around the interior machinery of the web browser.

      "Hmmmm... packets on port 80 through the firewall. One for me, one for the legitimate user. One for me, one for the legitimate user."

      --
      +++ATHZ 99:5:80
    3. Re:Two words.. Hardware Firewall by Luscious868 · · Score: 2, Insightful

      You simply have to do what I do on my home PC. Use ZoneAlarm for a firewall and Moziall for the web browser and e-mail. If you're using Internet Explorer or Outlook Express and you don't have to then you're crazy. OE is full of holes and I wouldn't trust any web browser that's integrated with an operating system for exactly the reasons you've mentioned. If you use ZoneAlarm at home, keep your system patched and don't use IE or OE then your perfectly safe.

    4. Re:Two words.. Hardware Firewall by maximilln · · Score: 1

      -----
      then your perfectly safe
      -----
      "Perfectly" might be optimistic but I'd settle for "reasonably". I have suspicions that Mozilla has a few exploitable code faults as well, especially if coupled with Javascript, JVM, PHP, Flash, etc.

      --
      +++ATHZ 99:5:80
    5. Re:Two words.. Hardware Firewall by Anonymous Coward · · Score: 0

      ny port, even port 80, can be hazardous if there's some webapp which has made itself resident for as long as your web browser is open.

      So what? (Non-IE) Browser-based programs can't write to disk, and they certainly can't change firewall settings. What's it going to do? Even |337 viruses and trojans have to give way to limits on hardware access.

    6. Re:Two words.. Hardware Firewall by Anonymous Coward · · Score: 0

      especially if coupled with Javascript, JVM, PHP, Flash, etc.

      Mozilla has been around for years and there has never been an "exploitable code fault" published that I'm aware of. Javascript can't write to disk. Java has been around for years: no viruses. PHP runs on the server. Flash had one obscure problem a while ago, but it was apparently harmless.

      Running a binary attachment on a client machine is one thing, but I really don't see the problem with web browsing, PHP, Java, etc.

    7. Re:Two words.. Hardware Firewall by MyHair · · Score: 1

      See also the LEAF Bering firewall/router mini Linux distro. With some tweaking the uLibc version can even do a bridging firewall with traffic control.

      With some carefully crafted traffic control/shaping I can now run multiple P2P apps (legitimate ones, FWIW) on multiple machines and still surf the web, download http & ftp, ssh and serve web pages with low latency and high bandwidth while the p2p traffic fills in the gaps. Traffic control is to bandwidth what nice is to CPU utilization.

      LEAF Project
      LARTC, good info on traffic control. Ignore the crap about giving ACKs priority, though. I quickly found out most p2p traffic packets have ACKs and choke the connection if you give them priority.

    8. Re:Two words.. Hardware Firewall by Anonymous Coward · · Score: 0

      Sounds overkill, but I run a Cisco 3620 at home on my rack (yeah yeah...). The first set of ports that I deny incoming on ANY interface are 445, 389, 135-139 with both TCP and UDP packets (definitely not the only ports I block). I'm not sure if its completely necessary to block all those ports for both TCP and UDP, but I figure better safe than sorry. I also use Norton Antivirus Corporate Edition and Software Update Services from Microsoft, and keep both of these up to date regularly. But I have never in my life seen a worm on my network that my family uses for browsing, email, etc.. The only virus I ever had was from copying an old DOS game from a friend years ago, back when 20MB hard drives were big.

      But if you have a good system in place, using the resources of AntiVirus, Firewalling, and Updating your Software, it will be very hard to get infected/infested/etc.

  154. The patch kb835732 breaks oracle by Maliq · · Score: 3, Informative
    Here is the kicker, if you're running oracle 8i to 9 when you run the patch it stops oracle from starting. And the worm that is running around automatically fixing the problem, it doesn't check if your running oracle, could someone update that good bug to check??

    this is going to be a long day.

    1. Re:The patch kb835732 breaks oracle by djmurdoch · · Score: 2, Informative

      That patch also broke R (the open source stats package). We tracked it down to the fact that after installing the patch, the HOMEPATH environment variable is no longer set properly.

      Details here.

      By the way, we had a patch out to work around this bug within a couple of days. Open source is good.

    2. Re:The patch kb835732 breaks oracle by slashdot_commentator · · Score: 1


      Breaks my heart. Who the hell would run Oracle off a Windoze box? If you don't need an ACID database, who the hell needs Oracle?

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
  155. Microsoft Security Advisor Email by stecoop · · Score: 1

    Got this from my hotmail account talking about MS statement and Fix for the sasser worm:

    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable

    -----BEGIN PGP SIGNED MESSAGE-----

    Valued Microsoft Customer,

    If you are still evaluating or testing the updates detailed in Microsoft Security Bulletin MS04-011, we strongly recommend that you expedite your review and deployment of these updates as soon as
    possible. These updates will protect your systems from the Sasser worm and its variants. If your systems have become infected, we have made a tool available for download that will detect and remove
    the Sasser worm and its variants. The tool is available at www.microsoft.com/sasser.

    In addition, on Tuesday May 4th, the Security Business and Technology Unit and Product Support Services are hosting two technical Web casts to provide the latest details of the Sasser worm and answer your questions about deploying MS04-011 to help protect your network.

    Please join us for one of the following Web casts by registering using the links below. The Web casts also will be available on demand at the same links.

    Tuesday, May 4th, 9:00 am - 10:00 am PT
    TechNet Webcast: Technical Update on the Sasser Worm http://go.microsoft.com/fwlink/?LinkId=28571

    Tuesday, May 4th 6:00 pm - 7:00 pm PT
    TechNet Webcast: Technical Update on the Sasser Worm http://go.microsoft.com/fwlink/?LinkId=28573

    For the latest information on Sasser and the cleaner tool, please go to www.microsoft.com/sasser.

    For technical details on Sasser and manual steps to remove, please to go http://www.microsoft.com/technet/security/alerts/s asser.mspx .

    Thank you,
    Microsoft Corporation

    *
    Protect your PC: Microsoft has provided information on how you
    can help protect your PC at the following locations: http://www.microsoft.com/security/protect/

    If you receive an e-mail that claims to be distributing a Microsoft security update, it is a hoax that may be distributing a virus. Microsoft does not distribute security updates via e-mail.
    You can learn more about Microsoft's software distribution policies here: http://www.microsoft.com/technet/security/topics/p olicy/swdist.mspx
    *
    -
    THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING
    THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT,
    INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY
    FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
    -

    -----BEGIN PGP SIGNATURE-----
    Version: PGP 8.0.3

    iQEVAwUBQJbdKY0ZSRQxA/UrAQG0bwf/VTf/AHfcaBibA6OM +7 HXKDz8ko7HzLLK /mfQ0d07KuQRm/UtxfmrU04yYpI04oEhf8UsQQkHCW0oHtO8ol NK8+yBw46knJ9S
    v/zxibsj8tLcaxIZ5NX9db6tlj+o4A4f5f 3enYxD7fyxaRKXp0 pRFoDH9eJ6o+M/
    Jk2jV6c0BF6xNljx0EwwLpbP5FBfIVSIsw CmPM0gMos7uW3vuq jw2nKWUAtBjAv0
    GOi+3baxSq3KVLlylxDfHWvgs7jus7O+7e gFl5c+Dne28Do+AJ 5xdnHJkztXvtM+
    PsELBl9mBkGziOnsFQD5e5VNttug0ufhbT xbX6plcx8hW+DBwM atFA==
    =tV/F
    -----END PGP SIGNATURE-----

    *

    You have received this e-mail bulletin because of your subscription to the Microsoft Product Security Notification Service. For more information on this service, please visit http://www.microsoft.com/technet/security/notify.a sp.

    To verify the digital signature on this bulletin, please download our PGP key at ht

  156. What more could M$ do? by stridebird · · Score: 1

    I heard about this new worm on the radio this morning before coming in to work. Actually my first thought was that's a bit early for the mainstream news channels to cotton on to a network threat, they are bound to have their underpants on their heads...still... ...I duly check the story and get the virus descriptions for Sasser, and I see that I am already protected. I use Microsoft XP Pro. I am on the network and I may have left my machine on over the weekend too. No Problem though, windows update has already taken care of my machine and I am patched.

    They have been shipping auto-update for some while in their OS, you can check any machine from what, 98, onwards online at the website, the patch install is unobtrusive and intuitive. I think that in this respect (not necessarily others) MS has at least caught up with automating updates on systems and that their system is working very well. It's the computing public who need to understand that any OS should be regularily patched - this should be hammered home in computing 101.

  157. But if you had patched... by MasonMcD · · Score: 1

    I'm so tired of hearing that.

    It's like someone nagging you, "well, I didn't get cancer because I go to the doctor for regular checkups. You only have yourself to blame."

    STFU. How many people get regular doctor and dental checkups? Do you floss? How about eat right and exercise?

    Malware authors just rely on this basic human inertia. Having said that, if you had to read the USDA inspection notices every time you bought a batch of hamburger, I'd hope we demand more of the hamburger meat processors, and not point fingers at the people who get sick.

    1. Re:But if you had patched... by praxis · · Score: 1

      Patching is more akin to getting an immunization, not a checkup. If someone was not to get a malaria shot (patch their box), and then go out to a malaria infested jungle (connect to the internet) without wearing proper clothing (running a firewall), and they got malaria, who are you going to blame? (I couldn't come up with the analogy for the OS vendor here, but was thinking the jungle itself).

  158. Auto updates and quick patches by truthsearch · · Score: 5, Informative

    Autoupdates and immediate patching aren't options for large corporate networks. Patches often break existing applications. Even after extensive testing some patches have caused more problems than they fixed. Windows Update sends enough information back to Microsoft for them to determine what's installed on our private network, so we block it from running.

    It takes weeks to test a patch and push it out. Servers often can't be rebooted until weekends. Then there are users with special situations that require manual installs. It takes time to do hundreds of installs manually. It also takes time to get the patch onto the standard corporate "build" of Windows, so for a while new computers need the patch pushed out after logging into the network the first time, leaving a gaping hole for this virus to spread.

    1. Re:Auto updates and quick patches by Anonymous Coward · · Score: 3, Insightful

      Bah...like Linux or OS X or BSD or Solaris are any better. Nobody really has desktop patches down all that well, the users make the machines too personalized.

      Plus, any OS that has 95% of the desktop market is going to attract worm/virus writers, and I don't care how open or closed source the code is. If things were reversed and Linux was had hundreds of millions of installs it'd be hacked to pieces. Even now I get all kinds of patches on my RedHat and SuSE boxes, it's no different than Windows.

      It's easy to maintain and patch 10K servers of any kind because you have control over everything. But any kind of desktop support is going to suck major a$$, regardless of the OS.

      In reality, computers just plain suck. They're still very young compared to, oh I don't know, combustion engines...the human body...the planet's ecosystems.

    2. Re:Auto updates and quick patches by coulbc · · Score: 3, Insightful

      Exactly right about breaking things. I found this patch broke Kerberos Authentication when double hop's are used. It broke a lot of our Intranet applications. Fortunately, we are firewalled and our internal MS machines were patched. I'm waiting on MS to resolve the issue so I can apply the updated patch.

    3. Re:Auto updates and quick patches by 7-Vodka · · Score: 2, Interesting
      What is worse? A few broken computers, or a r00t3d network?

      I think your priorities are wrong. Patch them, patch all the mofos on the day the patches come out. Do it automated if you have to. I wouldn't even care if my patching rebooted a computer while the luser was doing something on it. "If you wanted 5x9's of uptime you woulnd't have gone with windows, now suck it up while I do the ritual that keeps this shitty OS semi-secure"

      If the patches break a few apps, then take the time to go fix them individually. If they do real damage sue the shit out of M$. Isn't that the usual attack on Free Software? "who do we sue when shit breaks?". Besides, no one ever gets fired for choosing M$ right? Instead of having a compromised network (IMHO 100X worse) you may have some borked apps. So tell people it's all M$'s fault, go fix them and at least your network is secure for now.

      That is until M$ holds onto a security hole for months without patching it and someone releases a worm first.

      And if you're worried M$ is spying on you, why don't you call and complain? why don't you sue them? Oh yeah that's right it must be that legally-binding contract you have with them called an EULA which gives them all your base and the right to piss on you too. Have a nice day.
      --BOFH

      --

      Liberty.

    4. Re:Auto updates and quick patches by surprise_audit · · Score: 1
      Patches often break existing applications.
      Yep, that's fer sure. Last round of updates broke all our CA Unicenter infrastructure, which forced us to update to a newer version of Unicenter before we were really ready for it.
    5. Re:Auto updates and quick patches by cavebear42 · · Score: 3, Interesting

      IT@large_corporate_network here.
      True, auto updates aren't good for business critical machines. Microsoft gives you 2 ways to do the updates, you could use the automatic updater and put up a update server so you can control what is updated. Alternately, you could use SMS.
      If it takes you weeks to do testing, you should consider a more standardized loadset. If you were using one, the 90% of the systems who can use that loadset could be tested in a few hours. If you have users requiring manual installs, there are options like patch management systems (I like HFNetChkPro by Shavlik) or putting the patch installer into the login script.
      On adding to the corp. build, you need a leaner process, I can get it up in about a week.
      For all of this, and the server reboots, let me remind you that the patch was 21 days before the worm.

      Also, why does this article act like the worm is a new concept?

    6. Re:Auto updates and quick patches by RhettLivingston · · Score: 4, Insightful

      In that case, you're just tough out of luck, because there have been plenty of exploitable Linux and OpenBSD patches in the last couple of years. In fact, if you're a server manager, you might look through Slashdot's history for the last year. Somewhere, there was an article pointing out that the majority of the actual server breakins were not on Windows servers. After all, how could they be since there are so few Windows servers. People breaking into servers are more than happy to encounter an unpatched Linux or OpenBSD machine.

      I've got both Windows and Linux machines and have them both fully autoupdating. They only time I've ever had anything "break" due to autoupdating was when one of Microsoft's patches about a year ago caused machines running Norton Antivirus to slow down in some activities. Yes, 4 or 5 years ago when NT was the game, it was different and the patches tended to bite you. But it hasn't been that way for a long time.

      Overall, I'd say the risk of a patch breaking something on your specific machine (as opposed to a few random thousand of the 100s of millions out there) is much lower than the risk of a virus hitting you while you're "testing" the patches.

      I think that the real driver for people using your excuse for not patching is one of responsibility shifting. If you don't patch and get hit by a virus and its not an extreme case like taking more than a year to patch, you can whine about MS even though it was really your choice to bet the farm on 10:1 odds just because whining about Microsoft is a popular thing. If you do patch and you encounter that more rare condition that the patch busted you, you'll catch hell for patching without testing. So, not patching is the safer bet for you, patching is the safer bet for your machine.

      If you don't believe me, Google around for articles about patches breaking machines versus articles about viruses breaking machines. I think you'll see that some of the latest viruses and worms hit in the many millions, whereas the problems experienced from patches hit in the many thousands or are not completely debilitating.

    7. Re:Auto updates and quick patches by RobFrontier · · Score: 2, Insightful

      I work for a global top 50 company, and they quickly realized that we needed a strategy for securing our environment within a few days of patched being released. Our WINTEL group tests the patch for 2 or 3 days in a production environment, then sends it to a pilot plant who tests it for a day, then it's released to everyone else. Is it a pain to have to patch all our machines on a deadline in a production environment? YES. Does it work? YES. It can be done in a relatively short period of time in a very large production environment. Is Windows the greatest thing since sliced bread? NO. But we have to use it so we cope.

    8. Re:Auto updates and quick patches by dylan.ucd · · Score: 1

      yep, one of the patches that was issued 2 weeks ago broke our oracle server! damnit!

    9. Re:Auto updates and quick patches by Anonymous Coward · · Score: 0

      apt-get update; apt-get upgrade

      There--You've got patches that are tested. Happy?

    10. Re:Auto updates and quick patches by cyfer2000 · · Score: 1

      I've got a lot of problems with the dialup connection after this patch.

      --
      There is a spark in every single flame bait point.
    11. Re:Auto updates and quick patches by crotherm · · Score: 2, Informative

      Is The Boeing Company large enough for you? The admins have been running around patching like fools the past few days either by hand, or an SMS push.

      Ever since the company got owned by the Slammer virus, they have been very proactive in mandating patches.

      Of course as soon a patch breaks something..... :)

      --
      "Those who make peaceful revolution impossible, make violent revolution inevitable" - JFK
    12. Re:Auto updates and quick patches by thebes · · Score: 0

      Automatic updates may not be plausible...but SUS is! It's designed for the very reason of testing before deployment. No corporation that uses windows should be without SUS and group policy. It gives complete and utter control of updates to the admins, and therefore renders them responsible for all issues, and not the users.

    13. Re:Auto updates and quick patches by gnuman99 · · Score: 2, Funny
      Servers often can't be rebooted until weekends

      Are we talking about the same Windows here? :)

      Last time I checked, they almost rebooted by themselves. ;)

    14. Re:Auto updates and quick patches by Fulcrum+of+Evil · · Score: 1

      Somewhere, there was an article pointing out that the majority of the actual server breakins were not on Windows servers.

      Meanwhile, a million zombie windows boxes lurk, awaiting orders through obscure IRC channels. Question: if a windows box gets rooted when there's already a zombie controller present, does that count as one compromise or two?

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    15. Re:Auto updates and quick patches by mindriot · · Score: 1

      Your comment is on the edge of being flamebait, but the gist of it has a good point. What is worse, a few broken computers, or a r00t3d network?

      Or, another way to put it: If you think security is expensive, try an accident.

    16. Re:Auto updates and quick patches by Anonymous Coward · · Score: 0

      Hows unemployment treating you?

    17. Re:Auto updates and quick patches by soulhuntre · · Score: 1

      "Autoupdates and immediate patching aren't options for large corporate networks"

      Understood - but if you don't have a structure in place these days to test, validate and deploy a critical security patch in less than 14 days your begging to get an intruder or DOS.

      The security landscape for ALL operating systems has changed, the internet means you no longet have the luxury of taking months to test every patch... you need to be able to test and deploy critical updates in a short timeframe.

      Your inability to do so is not Microsofts fault.

      And let's not forget if this was one of the SSH exploites everyone would have bee saying "thank god the patch is already online, I just ftp'd it down and we are up and running!".

      --
      --> Fight tyranny and repression.... read /. at -1!
    18. Re:Auto updates and quick patches by Anonymous Coward · · Score: 0

      Your IT managers suck! We have 1500 PCs (ok, so maybe that's medium, not large) and we have no trouble getting Windows updates out to the 2k,XP,2k3 boxes.... Ever heard of SUS? Sure you have... Use it. You don't have standards in your organization -- if you did it would not take weeks to test patches. You probably let department heads buy software without IT approval. You probably have a nasty mix of [pick you favorite 6 PC makers] PCs. Make some policies and stick with them... if IT management will back you that is... that is where it starts.

    19. Re:Auto updates and quick patches by RESPAWN · · Score: 1

      You're telling me. I refuse to use automatic updating here simply because it has in the past broken some of our internal applications. I had read about this vulnerability a couple of weeks ago and had even downloaded the patch before the worm broke out in preparation for the coming shit storm. But I unfortunately still had to wait until I was given the all clear to install the patch. That happened late last week, with me planning to install the patch during users' lunch breaks over the course of this week... ...Until I came in to work on Monday and saw that about half of our Windows 2000 machines were restarting at semi-regular intervals as they were being attacked by the worm. Since then I spent all yesterday and most of the morning today installing the damn patch on each of my 200+ machines.

      --

      If Murphy's Law can go wrong, it will.

    20. Re:Auto updates and quick patches by llefler · · Score: 3, Interesting

      Overall, I'd say the risk of a patch breaking something on your specific machine (as opposed to a few random thousand of the 100s of millions out there) is much lower than the risk of a virus hitting you while you're "testing" the patches.

      That hasn't been our experience here. Less than a year ago we specifically put together a plan for staged rollouts of patches. It started with a get tough plan to make sure all servers were up to date, followed by several applications on all of our middletiers working erratically. It took a week for the programmers of the effected apps to get the problem fixed and working reliably. Things were starting to get a little ugly and users were not happy. Result, we have three stages of rollouts; test systems, first half production, last half production. None of which install automatically.

      I wasn't effected on that case, but I have had MS 'fixes' break critical systems. A while back a 'fix' of the generic text printer driver caused it to eat the first character of each line. Barcode printers stopped working. And no barcodes, no shipping. Spent a day finding it, added a sacrificial space to each line, system is back online. A year later, MS fixes the 'fix' and the driver is working correctly again, but now the printers are choking on the extra space. Pull our fix for their 'fix', and our systems are back in a couple hours. But only because I remembered the previous problem and work around.

      As to timeframe; it takes time to test complicated systems. Add to that the effects of the ecomony and companies are expecting more from fewer developers. So we have to balance our time between business requirements and testing MS patches. Being late installing a patch doesn't show up on my annual review, missing development deadlines does.

      As far as getting hit; we don't get hit very often, today is the first case of an infected server that I can remember since code red hit our website. We have up-to-date scanning on our systems, SUS for desktop patches, email scanning, and properly configured firewalls.

      Today we are fighting with a variant of a worm that isn't being detected by our scanners. But also doesn't appear to be using a vuln fixed by any patch. But that's a problem for Operations; developers are coding today, not chasing MS bugs.

      --
      It is amazing what you can accomplish if you do not care who gets the credit. -- Harry Truman
    21. Re:Auto updates and quick patches by truthsearch · · Score: 1

      I'm a developer, not an admin, so I have no control over the patching situation. But I can remember many times in the last year that a patch failed testing because it broke a VB application or caused network problems. If you're only running Microsoft applications then the patches probably won't break anything. But with custom applications only a fool would release Microsoft patches with no testing. A patch breaking our apps is just as bad (from management's perspective) as a virus breaking our network. Either way we can't work.

    22. Re:Auto updates and quick patches by blincoln · · Score: 1

      Is The Boeing Company large enough for you? The admins have been running around patching like fools the past few days either by hand, or an SMS push.

      Ever since the company got owned by the Slammer virus, they have been very proactive in mandating patches.


      We've probably seen each other at the SMS conferences in Bellevue =). I'm not going to reveal who I work for on Slashdot (it's another large Northwest company, a bit smaller than Boeing), but we have a similar patch policy now, and SMS is the main engine for getting them out to workstations.

      Out of all the patches we've sent out, only a few have caused problems and that was because of poorly coded software on the workstations, particularly third-party-written/third-party-hosted web apps and browser add-ons. It certainly seems a small price to pay compared to another Blaster.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    23. Re:Auto updates and quick patches by nukem1999 · · Score: 1

      Note that Shared Services sent out the memo saying that the pushes were in progress as of May 1 (Saturday, the day after patient zero). They didn't push the patches when they were first available, they were reactive instead of proactive. One broken application per person is better than one broken computer per person. In non-urgent situations, the patches come when they're done testing them.

    24. Re:Auto updates and quick patches by zcat_NZ · · Score: 1

      Nobody?

      0 3 * * * root apt-get update && apt-get dist-upgrade

      My desktop is highly customised. What the fsck does that have to do with the security of the underlying OS?

      --
      455fe10422ca29c4933f95052b792ab2
    25. Re:Auto updates and quick patches by andcal · · Score: 1

      Autoupdates and immediate patching aren't options for large corporate networks.

      Yeah, you're totally right, so the people who make a living administrating systems would know enough to turn that feature off more readily than non-admins would know to turn it on. Right?

      If the dummies had this option turned on, and the people who know better had it turned off, it would make it harder for any new virus to infect enough machines to get a critical mass

      --
      --something witty
    26. Re:Auto updates and quick patches by mpe · · Score: 2, Informative


      Bah...like Linux or OS X or BSD or Solaris are any better. Nobody really has desktop patches down all that well, the users make the machines too personalized.

      What you are missing is that with unix type systems there are clear distinctions between what is "Operating System" and what is "Application" (as well as "user" and "sys-admin"). Whereas with Windows things are quite deliberatly intertwined.

      Plus, any OS that has 95% of the desktop market is going to attract worm/virus writers, and I don't care how open or closed source the code is. If things were reversed and Linux was had hundreds of millions of installs it'd be hacked to pieces.

      This explains why IIS is more commonly attacked than Apache, even though IIS is a minority webserver. Possibly even more important than numbers is how "attackable" a platform is and how "malware friendly" it is.

      Even now I get all kinds of patches on my RedHat and SuSE boxes, it's no different than Windows.

      It's a lot different from Windows. The typical Linux distribution contains a huge amount of software, which in many cases includes several alternatives for the same function. As well as many pieces of software which will only be installed on a few machines. Desiging a worm which will "work" is sveral orders of magnitude easier with the homogeneous Windows population than the heterogeneous Linux population. Even the "Redhat", "SuSE", "Debian", "Gentoo", etc populations are likely to far more diverse than the Windows population.

      It's easy to maintain and patch 10K servers of any kind because you have control over everything. But any kind of desktop support is going to suck major a$$, regardless of the OS.

      It matters a lot if you are dealing with a "workstation" class of operating system or a "personal computer" class of operating system. Just bacause Microsoft have tacked "workstation" only the name of their product does not mean that it is a workstation OS. Single user, personal computer design assumptions are still there in Windows and a lot of Windows software. e.g. that which requires the user to have administrator privs to even run...

    27. Re:Auto updates and quick patches by bmw · · Score: 1

      I've got both Windows and Linux machines and have them both fully autoupdating. They only time I've ever had anything "break" due to autoupdating was when one of Microsoft's patches about a year ago caused machines running Norton Antivirus to slow down in some activities. Yes, 4 or 5 years ago when NT was the game, it was different and the patches tended to bite you. But it hasn't been that way for a long time.

      Overall, I'd say the risk of a patch breaking something on your specific machine (as opposed to a few random thousand of the 100s of millions out there) is much lower than the risk of a virus hitting you while you're "testing" the patches.

      I think that the real driver for people using your excuse for not patching is one of responsibility shifting. If you don't patch and get hit by a virus and its not an extreme case like taking more than a year to patch, you can whine about MS even though it was really your choice to bet the farm on 10:1 odds just because whining about Microsoft is a popular thing. If you do patch and you encounter that more rare condition that the patch busted you, you'll catch hell for patching without testing. So, not patching is the safer bet for you, patching is the safer bet for your machine.


      Obviously you've never worked in an environment with lots of mission critical systems. Even if MS patches didn't regularly hose your system (in my experience they do) then you still have to be extremely careful when applying any updates. Having your PC at home or you desktop at work automatically update itself isn't a big deal because you aren't going to lose millions of dollars if the patches do break something. Think about companies with 300+ machines that all need to work. If a particular patch does break something and all of those machines are automatically updated then you're going to waste a whole lot more time, energy, and consequently money fixing them than you would have needed to actually do proper testing before applying the patch network-wide. Either way, I would sure as hell rather risk getting the latest worm or virus than risk hosing the entire network with untested patches.

    28. Re:Auto updates and quick patches by Anonymous Coward · · Score: 0

      How many admins reading this work in a 24X7 manufacturing environment? We can't wait until after hours to patch and reboot. Patching our W2K servers today caused a disruption of our manufacturing process. Fortunately, our most critical server is running HP-UX. Wish we had more of those. My boss curses the worm writers, while I curse MS developers for coding so many unchecked buffers. My recommendation: W2K is great for non-critical servers, but if you need five-nines of uptime, look at other OS's.

    29. Re:Auto updates and quick patches by LinuxHam · · Score: 1

      Isn't that the usual attack on Free Software? "who do we sue when shit breaks?"

      Fsck sue, companies really didn't know who to *call*. Knowing us zealots, being more tech than business-oriented, how many of us have said, "don't BUY it, I'll just bring in a copy from home. Yes its legal. You can install it on every single PC and server in the company." So the next question is, "who am I gonna call when something is broken?" After about 5 years, we could reply, "LinuxCare" (for distros other than RH and SuSe) and then after another 5, we could finally say "IBM".

      --
      Intelligent Life on Earth
    30. Re:Auto updates and quick patches by Anonymous Coward · · Score: 0

      The people at Boeing who made their "recent" software decisions were/are fools. I do not wish to put words in anyone's mouth; talk to some Boeing IT people (not PHBs) and see what they have to say about this mess.

    31. Re:Auto updates and quick patches by RhettLivingston · · Score: 1

      Actually, I have worked in that kind of environment and think that you're all missing the lesson of nature here. I work to maintain variety in my environment because that is the only true defense. If all of the machines are so tightly controlled to a standard that variety is absent, then the target profile you are offering to an attacker is very juicy. Once they figure out one vulnerability you haven't covered, you lose everything. If you have to protect a system with standardized, controlled PCs, I feel for you. You've been given the worst possible handicap, that of having to maintain a perfect defense, and will someday lose the game because perfection doesn't exist.

      I also just left a company of software engineers who all maintain their own Windows machines and work from home. Due to the work from home nature, many of the machines were both exposed to the net and tunnelled into the company at alternate times. So, there were essentially over 100 holes in the company firewall. Over a year ago, company policy changed to everyone staying up to the week at least on their patches with heavy consequences if anybody allowed a breech by not patching. We encountered the occassional glitch, but it rarely affected more than a handful of individuals, probably due to the wide variety of configurations. Those effected usually just looked at why they were affected when the rest of us weren't and quickly figured out what they needed to change or find an update on.

      I've also found that keeping all apps up to date in addition to the OS results in far less problems. There's only so many old versions of popular apps they can afford to test against even with their farms of 1000s of machines.

      As for running non-Microsoft apps, yes, as a policy, I will not touch many of the non-Microsoft apps unless I have too or they are Cygwin based. I specifically don't run anything from Symantec. They are the absolute worst about using interfaces they have no business being anywhere near, even going to the point of replacing critical system DLLs like the login application to get some of their functionality implemented. Microsoft SHOULD trash their stuff just as a matter of principle. I got bit one to many times by their cowboy hacker style programming and have now cleansed my machines of Symantec software. If you run their trash, you're asking for trouble. Beyond Symantec, Roxio (whose software makes a point of breaking all of their competitors), and Oracle (I think they go out of their way to try not to run well on Windows and the other databases including MySQL seem to prove it by not having the same issues), I've had no trouble in the non-Microsoft arena under Windows. Interestingly, the bulk of the 3rd party packages and utilities I run are GNU utilities and I've never seen any indication of the many Cygwin based programs I run breaking due to a MS patch. And you would think that Microsoft would be breaking them first :o)

    32. Re:Auto updates and quick patches by NuclearDog · · Score: 1

      "first case of an infected server that I can remember since code red hit our website."

      I'm hoping it was a management decision to use IIS for your website?

      --
      This statement is forty-five characters long.
    33. Re:Auto updates and quick patches by aztracker1 · · Score: 3, Insightful

      This explains why IIS is more commonly attacked than Apache, even though IIS is a minority webserver. Possibly even more important than numbers is how "attackable" a platform is and how "malware friendly" it is.

      IIRC, the original IIS exploits came from a legacy ISAPI that was there by default... also, that followups where exploiting holes the originals had created...

      I usually remove any unused ISAPI filters as one of the first things on an IIS machine, as well as bringing patches to current.

      Desiging a worm which will "work" is sveral orders of magnitude easier with the homogeneous Windows population than the heterogeneous Linux population.

      It's also easier to write gui software that will work on 99.99% of all windows 98 or higher installations without extensive tweaking, than it is to get running on even 50% of linux installations. Especially if sound is a requirement.

      --
      Michael J. Ryan - tracker1.info
    34. Re:Auto updates and quick patches by turnin · · Score: 1

      >Google around for articles about patches breaking >machines versus articles about viruses breaking >machines. Virus breaking-in is public news ... Patches breaking machines is corporate news. There is a difference.

    35. Re:Auto updates and quick patches by fishfinger · · Score: 1

      It's also easier to write gui software that will work on 99.99% of all windows 98 or higher installations without extensive tweaking, than it is to get running on even 50% of linux installations. Especially if sound is a requirement.

      It is just as easy to write software for linux that will run on all installations. Just make it statically linked or take the Mac OSX approach and include all the libraries with the application and stick the lot in a single directory.

      Many of the reasons for not doing it like this are going away these days (such as slow network links (as most *nix software is distributed via the web rather than CD), and disk space).

      As for sound, it's funny how I can take a copy of UT2003 for linux and have no problems running it on any linux box I've tried!!!!

    36. Re:Auto updates and quick patches by mpe · · Score: 1

      It's also easier to write gui software that will work on 99.99% of all windows 98 or higher installations without extensive tweaking,

      If it's actually used by more than about 30% of Windows users there is a fair chance that Microsoft will make a work-a-like part of the OS...

    37. Re:Auto updates and quick patches by aztracker1 · · Score: 1

      Hmm.. then more people need to learn how, seems every time I want to try a software, I end up installing 3-5 dependancies first, in order to do so, and about 1/2-2/3 the time, I *HAVE* to have gcc, and other dev. tools installed...

      --
      Michael J. Ryan - tracker1.info
    38. Re:Auto updates and quick patches by Blackknight · · Score: 1

      That's because on unix you can restart a service without restarting the whole machine. Updating ssh will have no effect on other services that are running.

    39. Re:Auto updates and quick patches by soulhuntre · · Score: 1

      Of course the same is true under 2K3 and XP. Reboots are very rare for minor patches.

      But don't let reality intrude on your dogma :)

      --
      --> Fight tyranny and repression.... read /. at -1!
    40. Re:Auto updates and quick patches by fishfinger · · Score: 1

      But the other thing you have to bear in mind about *nix software is that it is, more often than not, written portably so it will build on several platforms/architectures in which case the application you want to install may have slightly different dependencies based on the architecture.

    41. Re:Auto updates and quick patches by aztracker1 · · Score: 1

      yeah, but that won't help someone trying to support a user over the phone... who may well be on a dialup connection, and expect to be able to install from cd.. sorry, you need to get dependancy X installed before hand, and I can't help you there... your distro Y's site for this is here.... oh, you need to update to Y version Uber10.463. it's on those cd's.

      --
      Michael J. Ryan - tracker1.info
    42. Re:Auto updates and quick patches by fishfinger · · Score: 1

      I'm not saying the current way is the correct way to do things but given that 99% of *nix software it distributed via the net rather than CD, the assumption is made that the user is going to have a reasonable connection. There are distributions that make the dependancy issue less painful such as Gentoo and Debian which do a damn good job of sorting the dependancies for you.

  159. Re:M$ - First Post? by penguinbrat · · Score: 1

    It's NOT the end users fault here... Was it the end "drivers" fault that Ford has installed faulty Firestone tires on their vehicles?

    Regardless of any arguments with this, it boils down to that everyone drives cars and computers alike. Both the huge car manufacturers and software makers alike issue recalls and patches for their product - however, the software makers are largelybullet proof to any legal action because of the EULA and likewise little or no class action lawsuits are brought against them - they are essentially NOT responsible as they should be. One argument to this is that computers cant kill people like cars can - well not directly but an organization relying on computers for communication that is down and can't get help to someone that is in danger, can certainly kill someone - hence the computers and software can kill INdirectly. Just look at 911, and the UK coast guard that has gone down to this crap.

  160. Re:Windows only by wheany · · Score: 1

    But on average, Apache admins know more about maintaining a machine than the average Windows user.

  161. Remote Desktop vs. VNC? by pw1972 · · Score: 1

    Ive got a box that is co-located and unfortunately 4 hours away by car. The tech guys on site were gracious enough to patch my server and remove the worm, but couldn't get remote desktop up and running again. Looks like I'll be putting VNC on there to get in and try and figure it out myself. Any thoughts on what's more secure? RD or VNC???

    1. Re:Remote Desktop vs. VNC? by gregarican · · Score: 2, Informative

      Remote Desktop Connection encrypts the data transmission. Similar to using MPPE/PPTP for a VPN connection to a Windows host. VNC by itself doesn't encrypt data transmission. You can tunnel VNC through an SSH connection to do this, however. But straight out of the box I would say RDC is your more secure alternative.

    2. Re:Remote Desktop vs. VNC? by Isaac-Lew · · Score: 1

      Depends on how fast your link is. If your connection is 128kb/s or less, I'd say RDC/rdesktop (they use SSL). If it's faster than that, tunnel VNC thru SSH (see this Google-cached page for details.

  162. Re:If Im totally up to date with my MS Security st by IANAAC · · Score: 1
    "noone" is not a word. It is not in the dictionary.

    No Body cares.

  163. Re:M$ - First Post? by BlackHawk-666 · · Score: 2, Informative
    We will start to see the same sorts of problems I suspect, but the damage will be more limited, most likely only to the user(s) who fell for the hack if it's a social engineering attack. To help mitigate teh problem we need distros to be careful in how they provide the default setup. i.e. use Mozilla instead of IE, built in firewall on each machine using IPTABLES but with a nice interface like Zonealarm or similar. Then, as long as the mail client (I like KMail, but most are pretty damn good) is *not* script enabled it will be done to good old buffer overflows to work their magic. Oh yeh, not installing services unless requested would also be smart, and then perhaps using IPTABLES or hosts.allow to keep the consumers of the services just down to the local private subnet should do the trick for most stuff.

    Finally, make sure they use apt-get or similar to automatically update their machine. This could be configured at install or afterwards as the user grows to know their machine. A default install might be to download all security patches and install with only a confirmation from the end user. A power install would just get the patches, but not install until instructed.

    --
    All those moments will be lost in time, like tears in rain.
  164. How Come These Things Are Not REALLY Bad by theManInTheYellowHat · · Score: 5, Insightful

    OK this sasser worm can install istelf open a few ports, serve files as an FTP daemon, place itself where it pleases, and gobble up your network.

    Other virus's do all sorts of nasty things, but they all seem to stop short of REALLY bad things. Search for files they can delete, look for a network drive and have their way, find interesting files and mail to random people, rename this or that to render the machine useless.....

    To me this seems very strange. Is ther some kind of virus writers code that has some small bit of ethic? Is there some undergound society that meets the 3rd wednesday to discuss safe virus exploits? Does Microsoft create these things to get people to upgrade? Maybe McAfee and Norton are funding them and they just want a profitable year?

    Now I am not asking for this kind of damage, but as my boss points out he has no reason to switch to anything more secure because nothing really bad happens.

    1. Re:How Come These Things Are Not REALLY Bad by simetra · · Score: 3, Interesting

      I wonder the same thing. It's probably only a matter of time before one is written that deletes files. Just think, if one scanned a drive and deleted .doc, .mdb, .xls, .ppt, .zip files. Just imagine how bonkers the suits would go.

      --

      "Would it kill you to put down the toilet seat?" -- Maya Angelou
    2. Re:How Come These Things Are Not REALLY Bad by e-Motion · · Score: 1

      Other virus's do all sorts of nasty things, but they all seem to stop short of REALLY bad things. Search for files they can delete, look for a network drive and have their way, find interesting files and mail to random people, rename this or that to render the machine useless.....

      A useless machine is... well, useless. Unless the author gets off on chaos, it's pointless to disable the machine. A zombie that you can remotely use is really what they want. This worm does exactly that.

    3. Re:How Come These Things Are Not REALLY Bad by Jonny+Royale · · Score: 1

      Because it's better to have a running machine as a spam slave, than simply destroy it.

    4. Re:How Come These Things Are Not REALLY Bad by advocate_one · · Score: 2, Informative

      been done before... the "I LOVE YOU" one replaced *.jpg files with *.jpg.vbs copies of itself that became activated when the user tried to view the file. Our tech publishing house had a very close call when a manager's laptop was connected to the admin share... only those images (just clip-art) on the admin share got clobbered cos that manager didn't have write access to the graphics department's share.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    5. Re:How Come These Things Are Not REALLY Bad by Anonymous Coward · · Score: 0

      Yea, we need virus's that actually do something usefull, you know, like randomly change IE's user agant string to mozilla, firefox, opera, etc.

    6. Re:How Come These Things Are Not REALLY Bad by theCat · · Score: 4, Interesting

      We're still in the "hobbyist" phase of virus creation. Folk do this for the same reason that people used to write their own software; because it is l33t. We have recently seen some more "applied" virus writting, as when a virus sets up a zombie computer for spam uses later. Or even, when one virus goes after another.

      Now imagine a real "virus industry". There would be serious R&D, business plans, virus development models, project management, the works. Probably even some code QA and testing. Why? Because there would be money in it. Don't know what the money would be, be if there were to be some then the "virus industry" would emerge overnight.

      The idea that a virus could be stealthy (or clever) enough to avoid detection and just sit around on infected PCs is part of the transtition from hobby to a business. I've been noticing that already there is a sort of "dark Internet" of zombies that can do pretty much whatever someone needs them to do, enabled by viruses. Aside from spam, here are some other uses for those machines:

      -- set up virtual casinos that dissolve instantly when the vice cops arrive.
      -- set up distributed supercomputers for unlawful uses, like cracking access codes or breaking IPSec packets
      -- have zombies not only monitor their users, but via something like ethereal monitor the broader Internet for traffic within their subnet. Imagine Carnivore on crack, and in the hands of the Mafia.
      -- use zombies to launch focused, sustained DDoS attacks against adversary nations
      -- use zombies as advanced positions to launch new rounds of virus outbreaks with split second timing and absolute accuracy, in this way overcoming most defensive responses in the first 15 seconds. Build a newer, stronger zombie network each time. slowly take over the Internet. ...

      Profit

      It's coming, people. You know it and I know it. Every habitat has its unseen underbelly, its fetid swamp, its decaying compost, and the Internet is about to get its own sewer system, full of rats and desease and decay.

      Will we care? Nope. It will just be there and we'll eventually learn to live with it, or use it to our own purposes.

      --
      =^..^= all your rodent are belong to us
    7. Re:How Come These Things Are Not REALLY Bad by simetra · · Score: 1

      This was because Microsoft operating systems, last time I checked, have "hide extensions of know file types" enabled by default. So, porno.jpg, which would normally show up as just porno, now appears as porno.jpg (.vbs extension hidden now), which doesn't raise any flags with joe-jackass-end-user. This didn't actually delete files. I'm waiting for an all-out, delete-not-recycle-office-files type thing.

      --

      "Would it kill you to put down the toilet seat?" -- Maya Angelou
    8. Re:How Come These Things Are Not REALLY Bad by Anonymous Coward · · Score: 0

      Sasser brought down the Sydney rail network, causing tens of millions of dollars worth of damage. It's not harmless.

    9. Re:How Come These Things Are Not REALLY Bad by cookiepus · · Score: 1

      Probably not as bonkers as you'd go without your *.mpegs

    10. Re:How Come These Things Are Not REALLY Bad by Anonymous Coward · · Score: 0

      What if the government is creating all these worms (trojans) to spy on the public (fighting terrorism, you know). The relative harmlessness is hoped to not disrupt the economy too much, and the small annoyances they create are designed to merely track how sucessfully they are spreading.

  165. Smells like BS by Anonymous Coward · · Score: 0
    2 people responsible for maintaining FIVE HUNDRED THOUSAND Windows PCs??? Think for a minute how many computers that really is, how big that organization would have to be, how many people it would have to employ....

    Go on, lumpy, pull the other one.

  166. My Dad hates WindowsUpdate, but is still OK by stealth.c · · Score: 1

    What about people like my father, who avoid WindowsUpdate at all costs because of a memorable history of it breaking things? He's no techie. Far from it. He wants his computer to run and not do anything unexpected. He gets irritated if anything deeper than the wallpaper gets changed. Whenever I mention it might be a good idea to run WindowsUpdate he rolls his eyes and intimates again how effective THAT has been in the past. It always makes something go goofy or changes a trivial setting to something obnoxious that he doesn't know how to set right again. To him, WindowsUpdate is just a headache for little or no benefit. They've got McAffee Firewall and VirusShield--and I make sure he uses Mozilla/Firefox (which he loves). THOSE get updated. Updating Windows just breaks stuff.

    Some earlier poster mentioned how it broke his video driver. Heck, I've tried to install *Word* on my Win98SE box only to find out the registry has been completely fucked and Windows needs to be reinstalled. It takes too long to reinstall UT200(3/4) again when that happens, so I just use OpenOffice.org.

    In my experience, the following has always been true: The less Microsoft software you use, the less unpredictable your computing experience. When I can throw out the Microsoft OS completely--that's where the real fun begins. Slackware has been a JOY.

  167. Trend Micro Damage Cleanup by Fez · · Score: 3, Interesting

    A tool that I use quite often seems to go ignored time and time again.

    Trend Micro Damage Cleanup is a free after-the-fact cleanup tool that will fix just about any virus (As long as the pattern file is downloaded...) It scans drives, registry, etc. The only drawback is that it's quite large (The pattern file is ~8.5MB and the Scanner is ~1.6MB).

    It blows Norton's one-fix-per-virus tools away, except from a portability standpoint. Also helps make sure you don't leave other viruses behind. (Did I run the Netsky.QZX removal tool, but not the Netsky.ZZB one?)

    Yesterday it found 530 copies of Agobot (3 Variants) and Sasser.B on one person's PC.

  168. Re:Windows only by Tin+Foil+Hat · · Score: 4, Informative

    PS: Tried fooling the script at windows update site by changing browser identification, but this only prevented the thank you message, didn't allowed to download the patch

    That's because windows update installs via an ActiveX object. Only IE can run that. You probably downloaded the ActiveX object, but since it can't run without IE, it didn't download the update. If you need to download the update separately, check out the adminstrator section of windows update. MS provides all updates as a separate download that you can burn to a disk and install that way.

    --
    No matter how many of my rights are taken away, somehow I still don't feel safe. -Frigid Monkey
  169. Removal tools... by poincare · · Score: 1

    can be found here and here.

  170. Which is exactly why by phorm · · Score: 1

    I double-checked that all XP laptops (no 2k here) are patched up and put up a memo regarding the dangers of taking machines home, especially unpatched. Even users can patch, it's the "I'll just click this update icon tomorrow" attitude that kills me.

  171. User removal tool by Jackal82277 · · Score: 1

    The best way to a secure network is to implement user removal tool protocals. I found a tool I like to use. CLICK HERE

  172. Re:Windows only by commo1 · · Score: 5, Insightful

    I think you've missed the point.

    1: There ARE more web servers out there running Apache than anything else. So, why is it that there is an unbalanced proportion of these boxes remaining intact and and with 99% (sic) uptime than the Windows boxes?

    2: Apache runs properly with fewer system resources, hardware and preventative maintenance than Windows. Set & forget, to a great extent.

    3: One of the main reasons that many corporate/commercial servers are still running IIS is because of the ease of use in integrating MS SQL and specific data export services from what the desktop is running: Windows. If from your average net admin's perspective, they could easliy and definitively state to their bosses that they could run a given database server on Apache for X dollars instead of on MS for XXX dollars, they would do it. It is difficult for the admins on two fronts: a) persuading their employers that a free product could possibly outrun what the so called market leader has provided, and b) if something goes wrong, fewer heads will roll if they're using MS instead of a "free", "open-source" product that, in the eyes of their employers was a gamble to start with.

    This will all change VERY soon.

    It's all a mind game....

  173. Lol by f4igrad · · Score: 1

    folks, get a Mac and you won't have all these problems. Never had a virus on my PowerBook, and I don't even have any virus software running.

  174. Re:M$ - First Post? by Oxy+the+moron · · Score: 3, Insightful

    My point wasn't that M$ has absolutely no guilt in the matter. You bring up a good point by comparing the issue to driving. BOTH parties are responsible for using the product correctly and safely.

    The manufacturer should make every effort they can to ensure the product works 100% out of the box. If you know full well that your Ford Explorer has tires that blow up on impact, you should not sell the product with those tires. In the event that you did so accidentally, you should make the public very aware of the situation and attempt to rectify the problem. Now, Microsoft has done reasonably well on the second account (a patch was/is available) but not so much the first. I think that having something similar to a "recall notice" for Windows OS that is very public could be a step in the right direction.

    However, it is also the job of the consumer to be educated in their use of the product. A Ford Explorer is perfectly capable of towing a boat, but Ford does not necessarily include the right tools to do so. It may have the hook thingy in the back of the body (pardon my lack of vocabulary) but if you try to tow the boat behind with a rubber band, it is not Ford's fault you were uneducated about that decision. In the same way, Windows is perfectly capable of being an OS that can be connected to a network to transfer data. But if you decide to do so with a DSL modem that has no firewall, that is not Microsoft's problem. In that regard, MS has made the attempt to educate their user base (link) , but it is up to the consumer to read and educate themselves at that point.

    When this worm could have been stopped very easily with a properly configured (and inexpensive no less!) firewall, I find it hard to pin all the blame on MS.

    --

    Proudly supporting the Libertarian Party.

  175. Re:And all you 'marketshare' trolls just STFU now. by Anonymous Coward · · Score: 0

    also, Mac OS X has had the 'automatic updates' turned on by default longer than windows has IIRC, and it's a lot easier to undersdand, e.g. Security-Update-4-17-04 vs. KB835732 or MS04-011.

    however, this should also be a non-issue for end-users in any sort of office, because the admin should be running SUS and have group policy force update on all users

  176. Why Should I HAVE To? by feloneous+cat · · Score: 1

    Everyone with a Windows machine should sign up for MS's monthly security e-mail or religiously check Windows Update on the second Tuesday of each month.

    Now some IT guys may get off on knowing every frikkin' worm and virus and what stops them, but you know what REALLY stops them?

    Good software in the first place.

    Why does this make me mad? Because it is yet another goddam thing I have to worry about because someone is too goddam lazy to do QC PRIOR to the release of the software.

    If you don't create the opportunity for virus writers, then you don't get viruses. Simple as that.

    MS Windows is like the human body that has been overexposed to the sun, smoking cigerettes for its entire life, drinking constantly, and sleeps on two hours a day. Opportunity for illness? You bet!!!

    --
    IANAL, but I've seen actors play them on TV
  177. Dark Lord Seth (584963) by Anonymous Coward · · Score: 0

    NOBODY expects a worm infection! The secret ingredient to a relatively secure system is a decent firewall...a decent firewall and regular updates...regular updates and a decent firewall.... The two secret ingredients to a relatively secure system are a decent firewall and regular updates...and common sense.... The *three* secret ingredients to a relatively secure system are a decent firewall, regular updates, and common sense...and a reasonable degree of attention paid to security news websites.... The *four*...no... *Amongst* the ingredients.... Amongst the ingredients of a relatively secure system...are such elements as a decent firewall, regular updates.... I'll come in again.

    1. Re:Dark Lord Seth (584963) by Caledai · · Score: 1

      For those of you who complain that ur 'parents' dont know what a firewall is. All you need to do is install a silent firewall - ie zone alarm with all the alerts turned off. Even if its only the standard version. Make sure they can access what they want and let it do its work. It starts automatically and blocks 90% of the attacks. Set their av to update automatically, and every month of so patch the system. (more freq if they have broadband.) Works for me and my systems and my families have not been hit with virus/worms/etc since I installed it around bugbear/welchia. (When I got of my arse and decided to waste dial up time appling patches that shouldnt need to be patched.)

      --
      Although it can be funny, tell them to plug the power in.
  178. Re:I love my Mac by jellomizer · · Score: 1

    Sorry Didn't mean to mod you redundant. I am taking it back by replying to it.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  179. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0
    Do you know how to change your radiator fluid? Is that part of the drivers test?

    Yes. And over here, it is.

    They don't expect me to be able to take a car apart and reconstruct it from scratch, but they sure as hell teach me the basics for safe driving, basic maintenance, basics repairs and when the hell to get a professional to look at stuff I shouldn't get involved with. Hence why I support licensed internet access. Fuck the retards like your parents who can't maintain a simple system.

    Asshat.

  180. Dude, what the hell? by Anonymous Coward · · Score: 0
    I was setting up a new machine. I turned it on, it set up XP. Before I could get the firewall installed, it was infected.

    How's this for a strategy? DON'T CONNECT THE ETHERNET CABLE until you're finished installing. Then go to network properties, turn on the firewall for your NIC (don't leave any open ports, even the ones you might need later open for now), connect the cable, download/install patches, open up the ports you need and only those you really need open on the firewall

    If you're on of the users that are smart enough to know that you need a firewall...why the hell would you connect your computer to the 'net before that was setup?

  181. Destructive Virus? by rastachops · · Score: 1

    I know this sounds harsh, but why don't the virus makers produce something that will *really* fuck people's boxes up rather than just annoy them. Like delete My Documents & screw the windows installation over.

    Then M$ would start to have people really hating them, possibly enough to actually make someone, somewhere, with some power to actually take them to court or MAKE them change.

    It's not good enough.

    1. Re:Destructive Virus? by praxis · · Score: 2, Informative

      The patch has been available for a month, and the built-in firewall prevents it too. Two layers of defense. Did they not do their due diligence? And don't give me the "there shouldn't be bugs in the first place" because as anyone who writes code knows, there are always bugs.

    2. Re:Destructive Virus? by prescot6 · · Score: 1

      ...and the built-in firewall prevents it too. Two layers of defense.

      That's under the assumption that you're running XP. Win 2000 doesn't have that extra layer of prevention. I do agree that if the patch's been out for a while, it's your own fault when something like this goes down. But you still shouldn't unjustly accuse somebody of double-bonering.

  182. Think Prevention by pherris · · Score: 1
    "A removal tool can be found here."

    And you can download a free prevention tool right here

    --
    "And a voice was screaming: 'Holy Jesus! What are these goddamn animals?'" - HST
  183. Aren't worms good for the soil ? by RLW · · Score: 2, Insightful

    If my computer was a flower bed it would have the biggest and brightest flowers on the block. But instead I have to patch the OS time and time again. If it were a boat it would be nothing but overlapping patches; at least it would make a great anchor. Something's got to give. I can't have a system that keeps crashing, or waiting for patches which maybe worse than the disease, and then praying that the system works and that what ever it was didn't kill anything important. Sigh, :-(

  184. Re:M$ - First Post? by Fizzlewhiff · · Score: 1

    No, if Linux were to ever get the marketshare Windows has it wouldn't have these problems. There are too many flavors of Linux out there not to mention dependancy hell would also prevent worm/virus writers to exploit holes on the same level that Windows gets it. If you look at some of the recent worms, they only hit Win2k and XP. NT4 often goes untouched because less people use it so the worm authors just ignore it.

    --

    'Same speed C but faster'
  185. Firewall for Win2k? by firew0lfz · · Score: 1

    Okay, so I've got Zonealarm installed on my computer at home (sorry, I'm posting this from school), but sometimes I'm under the impression that ZA doesn't really cut it; as I've run avast! antivirus software on my computer at times and found viruses on my computer anyway.

    So after hearing about the Sasser worm, I want to really sit down and build myself a decent firewall. Google ended up bringing me this: http://homepages.wmich.edu/~mchugha/w2kfirewall.ht m

    I'm kinda lost on exactly how that one works, could anyone give me a pointer on how exactly that works on win2k, if it is effective, and is it appropriate to use on a home system?

    (I run win2k professional at home, with ZA and avast! for securing my comp. I abhor using win9x).

    Any 411 is appreciated.

    --
    Try not to let life get in the way of living.
    1. Re:Firewall for Win2k? by DeanFox · · Score: 1



      You might consider looking into, downloading and installing Kerio Personal Firewall ( http://www.kerio.com ). It's usually more than a "home" user can handle. You have complete control of both inbound/outbound traffic on all ports for all protocols for all services and programs. It's free too. I've been using it for years.

    2. Re:Firewall for Win2k? by gregarican · · Score: 2, Informative

      Windows 2000 has firewall protection built-in. It's not enabled by default, which is a shame. But anyway, go into the Properties of the Local Area Network Connection. Then click on TCP/IP Properties. Then click on the Advanced button. There you will see under the Options tab a TCP/IP Filtering option. That is where you can open or close any TCP/UDP ports you want.

  186. Re:M$ - First Post? by wintermute740 · · Score: 1

    "The Internet is great, broadband is great, computers are great. But as long as people are willing to give up their passwords for chocolate and have no clue what a firewall is or what it does, this problem will continue to plague everyone.

    Nothing beats a good educated user."

    Except, maybe, a good chocolate bar.

  187. Broken vs. rooted by truthsearch · · Score: 3, Interesting

    First, I didn't choose Windows. I recommended Linux and/or BSD with a 70 page research document to back it up. Management ignored it. Second, I'm a developer, not an admin, so I have no say in the patching process.

    As a developer I can tell you when patch goes out that breaks an existing corporate app, execs get furious at the developers. If I write application X then any time X doesn't work it's my fault. No matter what, the apps have to work. The multi-billion dollar corporation comes to a halt if the fundamental custom apps aren't working. A problem caused by a patch from Microsoft can't always be resolved by adjusting code in our apps. Management cares a lot less if we're rooted because at least business can continue.

    Of course I think Microsoft should be sued for some of the problems we have. I don't think everything in the EULA will hold up in court in every state. But it's not my decision. And I also agree management has no one to blame but themselves for sticking with Microsoft. They get what they deserve. All I can do is write the best apps I can and get paid for it.

    1. Re:Broken vs. rooted by jc42 · · Score: 1

      I also agree management has no one to blame but themselves for sticking with Microsoft. They get what they deserve.

      Heh, no. You get what they deserve.

      It's rarely the management that suffers from such things. They don't work with the computers. They hire people like you to do that. Management makes decisions. And they've arranged things so that you suffer the consequences of those decisions.

      (What, me cynical? ;-)

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
  188. Fine for mom's basement. by simetra · · Score: 1

    That's fine and dandy, but in the real world, where people work, there are thousands of networked apps that run on Windows and Windows only. As the vast majority of customers/users use Windows, there is very little incentive for software vendors to port their apps to Linux.

    --

    "Would it kill you to put down the toilet seat?" -- Maya Angelou
    1. Re:Fine for mom's basement. by Anonymous Coward · · Score: 0

      Where did this "Mom's basement" shit come from? I'll tell you what: I run Linux in my basement, along with Windows, and I'll bet that my systems are more secure than a whole lotta "real world", "where people work" (like I don't work in my basement) situations. If you can't contribute without casting aspersions about age, financial independence, etc. then just get back to work, Microsoftie! You really do have nothing to say.

  189. Reverse FUD by E-Rock · · Score: 3, Informative

    It's bullshit and you know it. One of the April 13th patches funged IE, and within a week there was a follow-up patch, that still leaves you two more weeks to patch.

    What else did it break? Nothing?

    1. Re:Reverse FUD by iabervon · · Score: 1

      So it took Microsoft part of a week after releasing the patch to deal with a problem that it caused, and you think that this is a reason that companies shouldn't spend that long testing the patches? If a company spent as long on the follow-up patch as Microsoft took on the original patch (ignoring the fact that most companies don't have IT departments as big as Microsoft), this has testing completed (assuming it indicated that the patch worked) just in time for the end-of-the-month crunch. If you want to stay in business, you have to avoid changing anything then, so applying it has to wait until now, which is too late.

      IT departments are doing the cost-benefit analysis correctly. If they'd applied the original patch immediately, they would have had a disruption worse than they've had so far. Even when an attack occurs, like it did in this case, it is better for reliability, on average, to delay applying the patches.

    2. Re:Reverse FUD by Anonymous Coward · · Score: 1, Interesting

      try admining real users instead of a bunch of secretaries than. Its not IE we're worried about. It breaks CAD programs, simulation programs, programs that tell machinery where and how to dig, etc. Hell a friend of mine admins at a coal mine. He applied SP4 to Win2K. Should be able to trust it right? WRONG!!! If he wouldn't have caught that it crashed critically software and stopped applying the service pack right away just imagine what could have happened. This is why it is so important to test patches, especially from M$. Because they can't be trusted.

      So, in answer to your question; A SHIT LOAD!!!!

    3. Re:Reverse FUD by E-Rock · · Score: 1

      Well, since 0 of the 450 workstations we patched had the problem I can't say. Even if they had, it made IE kinda slow.

      I'm not against testing, but if a month isn't enough time, firewall the servers and patch the workstations.

    4. Re:Reverse FUD by E-Rock · · Score: 1

      The April 13th security patches broke SP4? I think your apples to monster trucks analogy is crap.

      Like I said in the other reply, testing is good, we tested all our critical apps before deplying, but that meant the patches went out on the 15th not never.

    5. Re:Reverse FUD by mpe · · Score: 1

      try admining real users instead of a bunch of secretaries than. Its not IE we're worried about. It breaks CAD programs, simulation programs, programs that tell machinery where and how to dig, etc.

      The real solution would be to only have Windows used by secretaries, since that is probably something close to what it was designed for.

      Hell a friend of mine admins at a coal mine. He applied SP4 to Win2K. Should be able to trust it right? WRONG!!! If he wouldn't have caught that it crashed critically software and stopped applying the service pack right away just imagine what could have happened. This is why it is so important to test patches, especially from M$. Because they can't be trusted.

      Or more usefully use the right tool for the job. When it comes to something like mining machinary Windows probably isn't the right tool. Is a WIMP-GUI the best user interface for a machine which digs big holes in the first place?

    6. Re:Reverse FUD by Sj0 · · Score: 1

      You know, I doubt you'll get any of these softies to agree with you. They don't understand the meaning of the words "MISSION CRITICAL".

      There's a very, very good reason that most process control in instrumentation (in mines, factories, chemical plants, paper mills, etc...) doesn't use windows, or even x86, but usually some horribly expensive proprietary solution -- if that computer crashes, your company can lose a million dollars an hour until it's repaired. In fact, if a TRULY critical system fails at an important juncture, hundreds of people can DIE. Sure, the user interfaces are often in windows, but if that goes down, a well-designed system will shut things down if there's ever a real problem.

      So don't even argue with these guys. It's like a squad lieutenant arguing with a UT2k3 fan over field tactics.

      --
      It's been a long time.
  190. maybe it's someone by zogger · · Score: 1

    who actually LIKES windows, and just wants to nudge everyone who doesn't use it properly to just learn something once and for all and keep their machines reliable. As in, sometimes ya got to smack a mule in the head with a clue by four to get them to react. I mean, if you think about it, the virus/worm writers are gradually putting themselves out of business, even microsoft eventually will ship way more secure systems with a default install.

    Frankly, I am liking the "live" versions of OSes more and more, the whole concept makes a lot of sense,besides being basically unhackable-you can't write to a burned cd or dvd- just write your permanent stuff to cheap removable media. Maybe in the future we will (I mean, joe home user/surfer) just have machines with no permanent harddrives, just banks of lotsa ram, live OSes, and various cheap storage media that is removable, hot swappable, etc. and use an offsite storage server for backups of what you really want to keep.

    I imagine for not very much $ an entry level box today,for instance, just an inexpensive mid range power CPU,lose the HDDs, ship it with like 2-4 gigs of RAM, and just have firewire and usb ports, etc. Then people can do what they want to do with a live CD and like flash drives, cd/rw disks or whatever. Want to surf, slap in the surfin and chat and gimme some tunes cd. Want to be joe office and bean counter for the family finances or shopping, slap that one in,want play some games, slap them in, and etc.

    1. Re:maybe it's someone by Progman3K · · Score: 1

      Tell me about it!
      I dumped Windows 4-5 months ago because of a bug in XP's activation module.

      Even though I stopped using Windows Immediately, I still spent the first month or so looking around, evaluating distros.

      I was able to access all my data all the while because I ran Knoppix as my desktop for that period.

      TRULY a great, useful tool, Knoppix.

      Anyhow, I finally settled on Gentoo, and apart from having a much tougher time getting everything working compared to Windows, it's been rock-solid, and I'll never go back to Windows.

      --
      I don't know the meaning of the word 'don't' - J
  191. Horray for Roadrunner. by llzackll · · Score: 2, Informative

    Ever since last year, roadrunner has been blocking inbound ports 135, 136, 137, 138, 139, 445, 520, 593, and 1026 in most areas. They learned their lesson from the Blaster worm. WHy other ISP's haven't done the same thing amazes me. Unlike most of you, who deal with corporate networks, I have to deal with the public on this. I must of removed this worm from at least 40 PC's yesterday. Most of them users of Verizon DSL, or MSN. None of them who had Roadrunner were infected.

  192. And (wait for it)...patch breaks the computer! by stuntpope · · Score: 5, Funny

    I got a laugh when our security team sent out an update to their vulnerability notice for Sasser (doesn't affect my servers, hehe).

    "[We] have learned of issues loading the Windows 2000 patch in MS04-011 when complying with [vulnerability ID].... systems can stop responding, users cannot log on to Windows, or CPU usage for the system process approaches 100 percent after installation of the security update. Additionally, [we] have heard that some systems may require a complete rebuild once the patch causes system to crash."

    And the kicker, "Systems Administrators are advised to proceed with caution when patching Windows 2000 systems." Um, how exactly does one do that, with one hand on the power cord, or click the install button very slowly? Does applying the patch warn you "About to hose your system, proceed?"

    1. Re:And (wait for it)...patch breaks the computer! by Anonymous Coward · · Score: 0

      "About to hose your system, proceed?"

      Doesn't every Windows install show an alert something like this, just after you enter the registration code?

  193. Re:M$ - First Post? by List+of+FAILURES · · Score: 4, Insightful
    The fact is, we need an educated user base.

    You speak the truth. However, as always, the car:computer analogy fits here. If you think about what you need to know to use a car, it's not very complicated. There is a core set of knowledge that you need:

    1. Operational (How to turn it on/off, put it into gear, brake, accelerate, speed, re-fuel, etc...)

    2. Navigational (How to get from point A to point B. Understand traffic flow and direction. Read signs and street lights, etc...)

    That is the bare minimum you need to drive a car. Many people these days seem to just barely know (or care) about any of that. In addition there is extended knowledge:

    1. Maintenance (Get your oil and filters checked/changed. Tune-ups. Fluid checks. Cleaning.)

    2. Enhancement (Learn more about your engine to get it performing to the best of it's abilities. Understanding the interaction between your car's tires, the road and aerodynamics to get the most out of your car)

    3. Interior/Exterior Decor ("Trick Out" your car and add high performance with stickers, spoilers, tailfins and fartcans. Make sure your stereo can tip off Richter scales for miles around, etc...)

    Very few people ever get to that level of knowledge. There really isn't any real reason for "Joe Average" to get there. But as far as the core knowledge goes, would you want someone out on the road who can't read directional signs, doesn't understand the concept of direction (N, E, S, W) or speed limits? Trust me, I see people on the road every day who appear to be lacking these basic skill sets and they are largely responsible for the accidents we see regularly.

    Apply this to computers, and you can see that we are, indeed, in a sorry state by comparison. Again, there is a core skill set that a computer user SHOULD have to be fairly competent. But it's much more complex than what is required for driving a car:

    1. File System - An understanding of how files are organized in an OS is very important at this point. It's a LOT like knowing how to read a map and get from point A to point B. Sadly, most users DO NOT have this skill set. In the interest of being "user friendly", applications like MS Office have attempted to abstract where files actually are located. This harms the user because if MS decides to change the location in a new version of the OS or program (My Documents has moved from where it was in NT 4.0 compared to Win2K and WinXP for example) then the user may think their documents are "gone". Tools like "Find Files" aren't any better at helping either because the user will ignore the path and just double click the file to have it open in Word. Or worse, there will be a "shortcut" in the "Recently Used" section of the Start Menu. I ask you, would you set up a physical filing cabinet this way with post-it notes in folders saying "This file is in Cabinet 35, Drawer B, Divider 2, Folder 12"? Shortucts (and sometimes symbolic links in Unix) are a BAD IDEA.
    2. File Types - One of the worst things about most OSes (Macintosh pre and post OS X excepted) is the non-existence of standard file types. Part of this is due to the fact that file types and data types are a moving target. HTML files didn't exist in 1984, so a Macintosh from back then wouldnot have had a built in association with an application that could read them. In the Windows world, the association between application and file was (and can still be) manual procedure that will perplex most users. Considering how much data and file types come and go and change, I am still wondering why there is no DNS type of system for file types that any OS worth it's salt would hold to. Imagine... a central DNS like repository that holds a database that an OS queries: "I have a file with the following type: x-application-doc. What applications should I use?" The server responds to the OS: "mswin-winword.exe, mswin-soffice.exe -writer, generic-unix-soffice, linux-kword, multiosapp-abiword". Then the l

  194. Re:I love my Mac by Walrus99 · · Score: 1
    Mac good. PC/Widows bad.

    Just another day for me as sysadmin for all Mac office. Ho hum, wonder what's on the net today? What is Dibert up to? Wonder what's on Slashdot?

  195. Windows Registry Scanning is Critical to Disinfect by theobscurest · · Score: 1

    If this tool doesn't scan the Windows Registry, then it's worthless. Instead I am using the Sophos removal tool, http://www.sophos.com/support/disinfection/sasser. html. It has found and successfully disinfected/removed the worm from the infected machines on my network. It checks in all known locations for the virus, including the registry. This is critical, as the worm does make its way into the registry in most instances. You also have the option of scanning your entire machine with this tool if you're overly cautious.

  196. You are too busy, hey? by Anonymous Coward · · Score: 0

    I'm glad you are too busy to patch your Windows box, yet can complain about how little time you have on Slashdot.

    You sure must be one valued employee. I'm glad to see you have your time management skills so under control.

    You are probably one of those guys that doesn't have enough time to patch his kernel, or even bother patching any of his beloved "free" applications. How's WUFTP doing?

  197. Re:M$ - First Post? by pknoll · · Score: 1
    Will they have the same security problems?

    Unlikely. There may be -new- security problems if Linux, *BSD and Mac OS take over the majority of desktops on Earth, but they won't be the same.

    I'd bet long odds there won't be as many, either.

  198. From a Mac IT Guy by MarcQuadra · · Score: 1

    Well I'm the 'Mac Guy' where I work, so I spend a lot of time 'helping' the windows folks patch and update. Anyhoo, today I helped patch some VIPs, explaining that if they had Macs they'd be a lot more safe from such attacks.

    The great thing is that I did some SIMPLE research yesterday and had the network guy disable all traffic on ports 5554 and 9996, both useless ports to us. Well now the worm is locked down to whatever subnet it gets in on, it can't propagate. We've had zero confirmed infections internally, except one subnet where someone brought a laptop and hosed two other machines.

    It's easy to stop this stuff if you're heavily subnetted and can block ports at the switches.

    I think I'm going to ask for more pay, if I can stop windows infections from my desk and I'm the 'Mac Guy' I should be asking for a fatter check.

    --
    "Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
    1. Re:From a Mac IT Guy by Anonymous Coward · · Score: 0

      Well aren't you just the cat's ass?

      Pompous blowhard.

  199. Yes, blame the victim by Infonaut · · Score: 1
    The tone of the article seems to lay blame largely upon the worm itself.

    Well, yes. The worm is what's doing the damage.

    If you fail to lock your car door as you mention, you'd likely be pissed off at yourself when you realize it's been stolen. But if you get in and out of your car thousands of times each year, you're bound to forget to lock it once or twice. Or perhaps you're in a hurry to get into the bank before it closes, or you only left the car for a second while you jumped into 7-Eleven for a soda.

    There are people who generally know what they're doing, but sometimes are unable to apply patches as soon as they come out. There are workplace issues of all sorts that get in the way of good system administration, even when the best intentions are present.

    Finally, let's get clear on who really is to blame here. People who write malicious code that is designed to spread across the Net and disrupt other people's lives are fucking assholes. It's that simple. You can place the blame on their victims all you want, but when someone steals my car, regardless of whether I left the car door unlocked or not, I'm going to want their head on a stake.

    --
    Read the EFF's Fair Use FAQ
    1. Re:Yes, blame the victim by j-turkey · · Score: 1
      Finally, let's get clear on who really is to blame here. People who write malicious code that is designed to spread across the Net and disrupt other people's lives are fucking assholes. It's that simple. You can place the blame on their victims all you want, but when someone steals my car, regardless of whether I left the car door unlocked or not, I'm going to want their head on a stake.

      Yes, I agree -- these people are assholes. I think I gave a nod to this in my post. However, I think that the victim does share the blame with the perpetrator in the case of a worm. Through ignorance, the user allows their computer (or computers) to continue to propigation of this worm. If you're gonna drive a car, you'd better understand the rules of the road, and you'd better know how to change a tire if you get a flat. How is the Internet any different? The victim mentality that you try to take on here is kind of bullshit. We live in a world with underirable people. They will never go away -- regardless of enforcement. Now you can either choose to ignore this fact and become a victim, or live vigilantly. It turns out that, when it comes to Internet security, we're all in it together. Worms like this depend on ignorance to spread -- the more ignorant of a population, the faster they spread and the more devistating the effects are. It takes two for this -- the victim is not the asshole, but the victim clearly shares the responsibility.

      --

      -Turkey

    2. Re:Yes, blame the victim by Infonaut · · Score: 1
      If you're gonna drive a car, you'd better understand the rules of the road, and you'd better know how to change a tire if you get a flat.

      I wholeheartedly agree with you that ignorance keeps worms alive. But it seems to me that our automobile analogy illustrates what my point. When you drive a car you do need to know how to fix a flat, but you shouldn't have to know how to fix your engine in order to use the car. If my grandmother wants to use email, the Web, and Microsoft Office on occasion, should she have to get a certification in order to do so?

      The fact is that computers are intertwined with our everyday lives to an enormous degree, yet networked systems are fundamentally unstable and prone to attack. If you drove your car and it broke down every five miles, would you blame yourself for not having the wherewithall to fix a cracked head gasket, or would you blame the manufacturer?

      Most people aren't auto mechanics, and most people aren't sysads. Like it or not, most people who are fulfilling some sort of sysad role (the "office computer guy" for example) have very uneven education. But should we be blaming them because they're trying to get things done with their computers and might not be as capable as we'd like them to be?

      We are definitely all in it together, but my feeling is that the people who develop operating systems are like engineers, in that they should be held to a higher standard of performance than a layman. But computer science isn't nearly as evolved as the engineering profession, and as a result, we all suffer with systems that are profoundly flawed.

      I hear what you're saying, and I agree that far too many computer users have no clue about the machines they're using. But no amount of venting will help this circumstance. For one thing, the computer industry moves so rapidly that even for someone immersed in it, it's difficult to stay on top of the latest technology. Imagine how difficult it is for the average user, who just wants the product they purchased to work as advertised, without having to be constantly fixed, upgraded, updated, and re-installed.

      --
      Read the EFF's Fair Use FAQ
    3. Re:Yes, blame the victim by j-turkey · · Score: 1

      wholeheartedly agree with you that ignorance keeps worms alive. But it seems to me that our automobile analogy illustrates what my point. When you drive a car you do need to know how to fix a flat, but you shouldn't have to know how to fix your engine in order to use the car. If my grandmother wants to use email, the Web, and Microsoft Office on occasion, should she have to get a certification in order to do so?

      Right -- we're talking about basic security precautions Vs. building a custom kernel (or rolling your own patch). Just like changing a tire Vs. fixing your engine to keep the car running.

      The fact is that computers are intertwined with our everyday lives to an enormous degree, yet networked systems are fundamentally unstable and prone to attack.

      Correct again -- and part of my point is that it's kind of dumb to blindly point a finger and say "it's Microsoft's fault". It's not. Every operating system has vulnerabilities. It's not fair that responsibility has to fall on the user, and it's not fair that systems are getting more and more complicated and harder to keep current with. It's an unfortunate situation, but to blame the person with the deepest pockets isn't fair either.

      If you drove your car and it broke down every five miles, would you blame yourself for not having the wherewithall to fix a cracked head gasket, or would you blame the manufacturer?

      It depends -- did I forget to add coolant? Then it's my fault. If the car is brand-spaking new, then it has a new-car warranty and I can get it fixed under warranty. I've still gotta take the car to the dealer (unless it's a Lexus where they pick up your car and drop off a loaner for you...but I digress). But the point is that Microsoft provides a fix, and it is the user's responsibility to apply it. They don't have to understand what it does. My mother doesn't understand any of this stuff -- but she's still able to apply these patches -- the OS finds patches to install and does it for her (it's built-in to Windows). I'm fully aware that this doesn't work in all types of situations, like in a large corporate environment, but that's a separate argument with a separate answer.

      sysad role (the "office computer guy" for example) have very uneven education. But should we be blaming them because they're trying to get things done with their computers and might not be as capable as we'd like them to be?

      We should absolutely blame them. If they can't get the job done, in this job market, there are literally thousands of people in line that can get it done.

      We are definitely all in it together, but my feeling is that the people who develop operating systems are like engineers, in that they should be held to a higher standard of performance than a layman. But computer science isn't nearly as evolved as the engineering profession, and as a result, we all suffer with systems that are profoundly flawed.

      This is a very, very good point -- probably the most intelligent thing I've read all day. The problem may be that the market moves really fast. There is a demand to get applications out the door yesterday -- because if companies wait to release, their product becomes obselete. There are a variety of other problems, but this one seems to stick out. For mission critical applications...and even moreso where peoples lives literally depend on an application working (think air traffic control, pacemakers), developers are certainly held responsible. I remember having to sign off on a clause in MS' EULA that affirmed this point (it was in the earlier versions of Windows NT -- it's probably sill buried within their EULA). End user software is generally treated with a more cavalier attitude -- in part (probably) to keep costs down but the rush to market plays a huge part in that. Even in OSS, when

      --

      -Turkey

    4. Re:Yes, blame the victim by Infonaut · · Score: 1
      End user software is generally treated with a more cavalier attitude -- in part (probably) to keep costs down but the rush to market plays a huge part in that. Even in OSS, when there is no rush to market, bugs are consistently found. I'm sure that if there was a market that was willing to shell out for end-user apps developed with this type of care, a company would step forward. However, I'm not sure that there is a market for that.

      I'm not sure that either of our proposed solutions will work in real life. So... what should be done?

      That's the crux of the biscuit.

      Your points about how easy it is to apply patches are well-taken. I think part of it has to do with how computers have been presented to the public. As you mention, consumer products and services have been marketed as being effortless. Hell, it even happens in the IT world. Software and hardware are marketed as silver bullets, and even people who should know better take the bait.

      I seriously doubt that Microsoft or anyone else is going to lead their marketing with some sort of OpenBSD-like approach. We've got this crazed fixation with features: more, more, more! So people want features but won't pay for better-engineered sofware. And if consumers don't think it's important enough, how can any company (or OSS project) convince them that solid engineering is worth the cost?

      Very annoying indeed.

      --
      Read the EFF's Fair Use FAQ
    5. Re:Yes, blame the victim by Anonymous Coward · · Score: 0

      Yeah, but if you drop your soap in the prison shower, you'd be a damned foo' to bend over to pick it up.

  200. McAfee tin foil by maximilln · · Score: 1
    I'll probably be ridiculed for this...

    Does anyone else but me lose faith in an organization (McAfee) which makes use of an advertising window which places itself off-screen? Aren't these guys supposed to be helping the user to prevent cheap tricks that result in compromised machines?

    http://us.mcafee.com/root/ExitCampaign.asp?Clien tD ate=5/4/2004&ClientTime=10:19:55
    <script src='http://directads.mcafee.com/jserver/acc_rando m=10405353/site=mcafee/aamsz=popunder'></script><s cript language=javascript>self.opener.parent.focus(); window.close();</script>
    --
    +++ATHZ 99:5:80
  201. Same thing. by wantedman · · Score: 2, Funny

    If a business critical application is broken, you might as well be r00ted.

    Boss: "Why is everyone sitting around?"
    Me: "Well, the patch broke an important application, so no work can get done, but at least our documents are safe!"
    Boss: "Great! Have some more stock options!"

  202. Windows ROI by webzombie · · Score: 2, Insightful

    Okay, I just finished reading most of the posts regarding RedHat's return to the desktop and this post just f@#$'n kills me.

    MS spurts and spouts about ROI and "real" costs yet nobody seems to be able to add up the real dollar impact of these almost daily security issues and breaches that are bring businesses to a screeching halt!

    Its almost like the current US administration. You know... if we say it often and loud enough they're bound to start believing us...unfortunately I think up until now MS has been successful at convincing most that its security woes are the falt of script kiddies, terrorists and the like and is probably reassuring the big ones that once their "Trusted Computing" solutions are implemented all will be right in the "free" world again.

    If Linux has a real chance it will be in the next 2 or so years so the "community" better get its ass in gear and start making a demonstrated effort to capture the hearts and minds of the desktop users who were one of the biggest reasons Windows 3.0 was adopted by the business mainstream... remember!

    1. Re:Windows ROI by DerekLyons · · Score: 1
      MS spurts and spouts about ROI and "real" costs yet nobody seems to be able to add up the real dollar impact of these almost daily security issues and breaches that are bring businesses to a screeching halt!
      Yet somehow the *nix zealots believe that their systems would never, never behave like that. "All we have to do is replace unpatched Windows boxen on the desks of clueless users with unpatched *nix boxen!" There will never be another security problem again, ever!
      Its almost like the current US administration. You know... if we say it often and loud enough they're bound to start believing us...
      Oddly enough, that's *exactly* how the *nix folks have been behaving for years. They've shouted about Microsoft for so long, they convinced themselves, or forgotten outright, that *nix is not without vulnerabilities of it's own.
    2. Re:Windows ROI by VB · · Score: 1



      "Oddly enough, that's *exactly* how the *nix folks have been behaving for years. ..."

      Actually, *nix folks have been securing their systems since 1970 and created an OS architecture from it's foundation that places priorities on security and stability. While the desktop still isn't as pretty as the other one, it's never hidden it's features or security considerations from the operator.

      The other one made it pretty and left it wide open and they've been trying rather unsuccessfully for 5 years to attempt to secure it.

      The operators of these rather different OS architectures usually side with one or the other based upon how their philosophy lines up with which: security first, or useability? *nix users usually know where all the vulnerabilities are because they can find them easily since it's open; Windows users are hopelessly stuck clicking on things and _still_ rebooting when all hope fails. But, since I'm just a UNIX/Linux "zealot," quoting security 101, I doubt this makes much sense to typical Windows folks.

      They're entirely different animals and I'll start considering Windows users to be acceptably effective at securing their machines when they learn as much about their own architecture as most *nix users know about them. If you read the tech headlines every couple months, you know that is far from the case.

      --
      www.dedserius.com
      VB != VisualBasic
  203. Nothing really bad?? by miffo.swe · · Score: 1

    All of those worms that carry payload that makes zombies? Do you consider an open entry to your network "nothing really bad"? Dont forget all the work associated with removing the viruses either cause you dont leave them there do you?

    Just because noone has done anything malignant yet is no assurance that it wont happen. Imagine an Al Queda hacker releasing a worm? Do you think that worm wont do anything bad?

    Think before you speak.

    --
    HTTP/1.1 400
    1. Re:Nothing really bad?? by Perianwyr+Stormcrow · · Score: 1

      Dude. If Al Qaeda spent their time ginning up virus and worm payloads, we'd all be MUCH better off.

      --

      What we call folk wisdom is often no more than a kind of expedient stupidity.-Edward Abbey

    2. Re:Nothing really bad?? by Anonymous Coward · · Score: 0

      Think before you speak.

      You think he was wrong?

      Just because noone has done anything malignant yet is no assurance that it wont happen.

      So you do agree.

      The rest of your post seems to indicate that either you missed the point or you disagree. The point was that once the virus has infected your computer it is trivial to do large amounts of destructive damage... why don't more viruses do this? Most of the major outbreaks don't delete any files. If they did, people would probably quit using Windows.

      Maybe we'd see greater Linux adoption if some truely destructive worms/viruses were circulated (e.g. one that destroys your partition table).

  204. Re:M$ - First Post? by misterpies · · Score: 1

    >>Educated users are key, but because Microsoft has the largest market share, they also get the largest number of uneducated users. What will happen if Linux eventually completely replaces MS products on the desktop? Will they have the same security problems?

    No, because uneducated users will never figure out how to get a network connection.

    --
    The author of this post asserts his moral rights.
  205. Windows XP firewall by Vexware · · Score: 1

    Personally, I have no trouble dealing with worms proliferating through ports other than those I can control myself (which include HTTP and E-Mail), such as Blaster.Worm and Sasser.Worm, thanks to my ZoneLabs ZoneAlarm firewall, which allows me to protect my computer from intruding -- and protruding -- dangers, easily yet with control. I always recommend this firewall to users of personal computers because I have yet to find a free firewall which protects well yet works so simply. I have read some messages in which it is said that turning on the Windows XP firewall will suffice to protect users against such worms. I must protest against this, as I have a small anecdote of my own.

    After having reformatted my computer, I thought it would be safe to activate Windows XP's firewall as an intermediate protection against such threats until I had ZoneAlarm installed. I connected to the Internet, and in less than a minute had Norton Antivirus, which I had updated beforehand, warning me that Welchia.Worm had been able to access my system -- remember Welchia is based on Blaster and uses the same UDP ports to proliferate -- yet the Windows XP firewall was activated. I could say I was somewhat surprised, but then perhaps I wasn't all that much; after all, it is Microsoft software. I do not know if the same situation could apply to Sasser, since it does proliferate through a more commonly used port, but I must still say I have some trouble recommending the Windows XP firewall, even as an intermediate one.

    --
    "Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect" -- Linus Torval
    1. Re:Windows XP firewall by gregarican · · Score: 1

      I myself am always wary of a mechanism that doesn't have more verbose settings or options. Just one checkbox that refers to an Internet Connection Firewall as a catch-all is a bit suspect.

      It's not like you can define specific TCP/UDP ports to allow/disallow with this mechanism. Not sure what smoke and mirrors the mysterious ICF is made of, but running nmap against a host should shed some light on things. I wonder what ports it does shut off? Probably any non-Microsoft service ports. But unfortunately most of the exploits are specifically looking for MS service ports.

    2. Re:Windows XP firewall by Vexware · · Score: 1

      I myself am always wary of a mechanism that doesn't have more verbose settings or options. Just one checkbox that refers to an Internet Connection Firewall as a catch-all is a bit suspect.

      It's not like you can define specific TCP/UDP ports to allow/disallow with this mechanism.

      Actually, it is possible to define specific ports to allow, or disallow, with this mechanism. In the properties of your Internet connection, click 'Advanced', then click in the checkbox which offers to activate the firewall. Once this is done, you may click on the 'Parameters' button to access configuration of the authorisation of the system ports, though I still do think that the firewall should be securely configured on activation whether or not it is activated be default.
      --
      "Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect" -- Linus Torval
    3. Re:Windows XP firewall by gregarican · · Score: 1

      True that. Forgot about the Parameters button. It's been awhile since I've locked down ports at the workstation level. Hardware firewalls at the ISP demarc usually are locked down accordingly. Thanks for pointing out my mistake!

  206. some UK damage by jago25_98 · · Score: 1

    Plymouth University ALL computers down 4th May:

    http://www.plym.ac.uk/

    Devon Coastguard also reporting trouble.

    1. Re:some UK damage by Anonymous Coward · · Score: 0

      Perhaps the esteemed British Coast Guard could take advantage of the downtime and collectively visit an oral hygenist and get their nasty teeth cleaned. Why is it all limey have jacked-up teeth anyway?? WTF??

  207. Patch 835732 also breaks Perl Authen::NTLM module by aspeer · · Score: 2, Informative
    Have a Perl program that uses NTLM to authenticate to an IIS server and download pages ? Prepare for it to break when the IIS server has the above mentioned patch installed, if your app used the CPAN Authen::NTLM module.

    See Google thread here for further info, and possible fix.

    My biggest hassle is not distributing the patches, it is the fact that they do not become effective until the machine is rebooted. Some people leave their machines on for weeks at a time without rebooting, and until they do so their machine is vulnerable.

    Try to force a reboot, then sit back and listen to the whining about "lost an all night experiment" or similar. I am a somewhat a BOFH and would like not to give users a choice, but management wants a softly, softly approach.

    So Microsoft, to try and keep both of us happy how about getting patches to at least hook (intercept) the vulnerable system call at install time, acting as a shim to filter out exploits, even if it means slowing the machine down slighty. Then at next reboot time install and activate the fully patched replacement DLL.

  208. in our case? a broken network. by RMH101 · · Score: 4, Interesting

    we collect data from clinical trials, and we do so in a validated manner as we're inspectable by the FDA. i'd rather disconnect our LAN from the WAN and work with reduced functionality than just patch the servers willy nilly and break our validation. we can't apply *anything* without formally testing it as it could potentially affect data. it's fine if you're just doing bogstandard file'n'print, but for other stuff you can't just go installing patches that may or may not impact production systems.

  209. My experience by Anonymous Coward · · Score: 0

    I tried to do a story about this for our school's student-run newspaper. It was going to be a piece about worms and viruses going around on our (large Big Ten school) campus computers... so I asked the person in charge of the network a few questions regarding the cost in managing and cleaning up the problems... among other things. He ended up believing that I'm a security threat and reported me to the DHS.

    All I really want to do is figure out why our eMail is notoriously unreliable and filled with viruses... plus why so many ISPs filter mail from our TLD.

    I still want to do the story but I'm not sure how anymore. Anonymous for paranoia reasons.

  210. Microsoft is Slashdotted. Behold the power! by Futurepower(R) · · Score: 1

    At the time of posting this comment Microsoft is Slashdotted. Behold the power of Slashdot!

    MS04-011:

    Server Application Unavailable

    The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.

    Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

  211. Re:What ARE 80 year old Win98SE by watermodem · · Score: 1

    An upgrade would give my 80 year old dad a heart attack

    It was bad enough upgrading netscape to mozilla and changing his lame dial up provider to a baby bell provider that outsources customer support to India. He can't understand a word they say.

    Maybe I need to look in my archives for a FVWM95 window manager... make it look like win98, put a good distro with wine and ms-office on the system and do all this while he is out of town.....

    Hmm... he is out of town for a few weeks ... I wonder if he would notice? Maybe I will just make a Knoppix variant to do the same thing! I would not even need to touch his install and I doubt he would notice the CD boot...

  212. Huh by panic911 · · Score: 2, Insightful

    unlike a virus which travels through e-mails and attachments, spreads directly from the internet.

    I hate to nit-pick, but Email I think is classified under "the internet". Does he mean via http?

  213. executable bits for the stack and heap! by Steve_Jobs_HNIC · · Score: 1
  214. you have a problem if its already on your lan by Anonymous Coward · · Score: 0

    Then there's the new computer I got yesterday with our standard corporate developer's build. Of course the build doesn't have the latest patches yet, so when I turn on the computer for the first time, immidately after logging in McAffee catches the virus. So then I have to hunt down the right patches from the right people and reboot repeatedly until I can log into the network without getting the virus.

    Hate to say this, but if the virus is wondering around your network actively probing, then something's wrong and needs fixing. You need to get the virus off your network. Its a nuisance if it comes in, and patching all internal machines can only help stop it spreading, but your boundary defences should be effective. Your internal network should be a safe place. You should only need to defend against attacks internally as a precaution, (unless you're something like a university, can't trust them students!)

  215. Grammar check to the rescue! by St.+Arbirix · · Score: 1

    Sasser, unlike a virus which travels through e-mails and attachments, spreads directly from the internet.

    For shame. Try this instead:

    Sasser, unlike a virus that travels through e-mails and attachments, spreads directly from the internet.

    See, now doesn't that make sense? The sad thing is that I only know to look for those because MSWord's grammar check complains about them all the time.

    --
    Direct away from face when opening.
  216. I call bullshit by Uberbah · · Score: 1
    You're completely blaming the wrong people here.

    his is absolute horseshit. If users (and IT personnel) at these governments and places of business were responsible enough to do their jobs and ensure that computers were adequately patched, this problem never would have occured.

    Your horseshit. Why should software be the only consumer or business product where the customer is totally at fault for the products flaws? To cut to the chase, if you are running a server, yes you are resonsible for staying on top of things. But there is no excuse for a modern desktop operating system not to be secure out of the box. After enough RedHat boxes got hacked into because wuftpd ("proudly providing remote root since 1994") was installed by default, linux distro makers learned not to leave services running all over the place. That Microsoft hasn't learned this lesson, stopped sharing drives by default, and have a firewall turned on out of the box is inexcusable. This outbreak is Microsoft's fault, not consumers.

    I see alot of Slashdotters blaming Microsoft for this problem -- saying that running Linux or xBSD would solve this problem. Bullshit, fanboys. I am a Linux/Free software advocate and that argument is absolute bullshit.

    No, its not bullshit. There are four reasons why Microsoft has so many problems with worms and viruses:
    1. sloppy coding
    2. poor privledge seperation
    3. too many services and ports open by default
    4. thoughtless integration and auto-execution (i.e. legion of Outlook exploits)
    Now, while Linux, BSD and OS X may also suffer from sloppy coding, none of the other issues apply to them. So it wouldn't matter if Apple or Linux had 100% marketshare, they wouldn't have but a tiny percentage of the problems that Microsoft does with Windows.
    1. Re:I call bullshit by j-turkey · · Score: 1
      Why should software be the only consumer or business product where the customer is totally at fault for the products flaws?

      Alright -- there are a few problems with what you've said. First of all, there is no such thing as bug-free code. You need to accept this -- because it doesn't matter what you're running, it ain't bug-free. Second, the user is not at fault for their product flaws, but a user is expected to take on some responsibility in the matter. Let's say that my car comes with shitty tires that shred under heavy braking. Let's also suppose that the manufacturer makes a reasonable effort to notify me of a recall. If I disregard the information and my tires shred and I get mamed, whose fault is that? The manufacturer's? I don't think so. I knew better -- and if I didn't, I should have. In both cases, the manufacturer has made a reasonable effort to inform the end user of a product defect and offered a free solution. At what point are you willing to accept responsibilty? If the customer were expected to be totally at-fault for Microsoft's product flaws, the customer would have to pay for minor version upgrades, which they don't.

      Now, while Linux, BSD and OS X may also suffer from sloppy coding, none of the other issues apply to them. So it wouldn't matter if Apple or Linux had 100% marketshare, they wouldn't have but a tiny percentage of the problems that Microsoft does with Windows.

      But that's simply untrue. Look at bugtraq, my friend. The vulnerabilities out there are actually pretty similar, both in severity and number. It seems like you're really comparing the userbases more than the products themselves -- because you're still only talking results of bugs. Now I believe that Microsoft has owned up to the kitchen-sink approach to running default services is the wrong one. I can't readily link you to an article, but I recall that they've vowed to change what runs by default. So they're behind Linux in this front of security. There are a few reasons. First, RedHat's release cycle has been about every two years. Microsoft is on a 3-5 year release cycle. Second, OSS is able to implement sweeping change faster than commercial software can. Third, Microsoft is not as innovative as they claim -- but we know this. The privelege seperation argument that you make is not really accurate either. Major Linux distros are still running Sendmail and other suid applications by default (Sendmail being the next wuftpd snafu -- what a mess). Now there is some new buffer overflow protection in the new RH kernels, but the overflow protection is somewhat RH specific -- and it's not perfect. Microsoft has also fixed much of their "thoughtless integration and auto-execution" in Outlook. The worms now use social engineering tactics to fool the users into running them. Linux is just as vulnerable, except that the current userbase is more educated. If all of the Windows users move over to *nix, they'd be just as vulnerable.

      Now none of this is to say that I trust Microsoft's security. I believe that it largely depends on the obscurity of their source code (in fact, they've even admitted it -- calling on "national security"). But these other problems -- they're just not as exclusive to Microsoft as you suggest.

      --

      -Turkey

  217. 3rd-party software firewalls by Futurepower(R) · · Score: 1


    "Firewalling all client workstations is pretty new..."

    I don't understand all the problems with this. I thought it was absolutely standard, since January 2000 when ZoneAlarm was first released, to run 3rd-party software firewalls on every Windows computer.

    1. Re:3rd-party software firewalls by Dr.+Evil · · Score: 1

      I don't mean employee-operated software firewalls, that's just silly. Do you really think it secure to trust your clients to run a firewall on their machine?

      I mean stuffing a firewall on the employee-facing network, forcing them to use authenticated VPNs or some similar technology from inside the office, and restricting their ability to use various network resources by default (e.g. cut web access, IRC, various chatting clients, all typical tunnelling software, and allow dynamic rules to be slapped down for new worms or trojans...)

      Kick in some port-scan on login method, and incorrectly configured machines will be quickly identified, and may be refused permission to speak with the VPN servers.

      You need VPN or IP Sec so that the unauthenticated systems can't sniff local IPs and find other machines to target via broadcasts.

      That kind of stuff is too new.

  218. The real problem by dark-br · · Score: 1

    No offense, but was the poster actually reading what he wrote?

    The REAL problem is the editor not reading it!

  219. Two huge gaping problems by Aslan72 · · Score: 5, Informative
    Sasser.d attacked our University last night and we noticed two particular things.

    1) Several groups were relying on SUS in order to get those patched distributed. If you go into SUS, the patches were 'approved' on one screen, not on the other. I wasn't alone in seeing this. Suffice to say, I was also a bit shocked when it started to blow through and none of my machines were protected.

    2) When it installs (sasser.d) it writes itself to 'System Volume Information' - allowing it to not get caught by NAI's on demand scanner, and re-infect the box if you don't do a C drive scan manually.

    --pete

    1. Re:Two huge gaping problems by BenjyD · · Score: 0, Redundant

      In my department, it looks like even the Windows PC running the information display in the lobby is infected - it seems to be rebooting a fair bit!

  220. Re:Decent firewall, regular updates & common s by Anonymous Coward · · Score: 0

    My, isn't that a pretty hat??

  221. How long does it takes by Anonymous Coward · · Score: 0

    Just out of curiosity. How long does it take on average to test and deploy patches on corporate computers and servers, assuming that the patches don't break apps?

    1. Re:How long does it takes by Anonymous Coward · · Score: 0

      How long does it take on average to test and deploy patches on corporate computers and servers

      That would depend totally on the environment. Your question is like asking; "How long does it take to change all the tires on all the school buses at a school district bus depot?" Well, how many buses are there? How many people are working on the buses?

      To try to answer your question. If I had a patch that I know doesn't break anything it would take me (by myself) about an hour to come up with a script that would push the patch to all our 350 workstations. If the patch was only 1 or 2 MB then all 350 boxes should be patched within two hours of me deciding to patch them...

    2. Re:How long does it takes by Anonymous Coward · · Score: 0

      I once worked for a Very Bug Oil Company. They had ~5000 apps on the "approved for Win32 machines" list.

      Some of these were actually different versions of the same thing, so perhaps ~4500 unique apps.

      About half of these were COTS, the other half were homebrew apps written in dozens of languages/toolsets/whatever.

      Central IT was run exclusively by fuckheads. It took months to test everything well enough that they would deploy patches. I expect that a clued team could trim that down to a matter of (mere) weeks.

    3. Re:How long does it takes by Anonymous Coward · · Score: 0

      Our application (medical data stuff) takes 24-28 weeks to test and re-certify for deployment.

      Any change to OS or APP requires quorum vote of VP's

      It has to be right. Rock solid.

      Thankfully windows is only on the data entry side. We use linux/vms/sco on the db/app side.

      If you have been in hospital in USA, Your data had about a 40% chance of going through my software. ....your welcome.

  222. At my workplace by ProfessionalCookie · · Score: 1

    We have a policy that if the windows computers are going down, and people in that department are taking a paid break while the windows techs are fixing stuff, then all the Mac users get to take a break too. It happened just often enough for it to come up at a meeting.

    'Course in practice we rarely have time in out production schedule to take advantage of it, but at least no one can complain that we're slackin'.

  223. Because virus writers are not subtle enough... by alispguru · · Score: 3, Informative
    A "really bad" worm would:

    spread fast for the first few hours or days, until it saturated the vulnerable population, then cut way back on network traffic and hide.

    not crash machines or trash all their files - instead, it would slowly and subtly modify user data files (see here for a few suggestions).

    Imagine what would happen to modern business if they discovered that they couldn't trust any document that had ever touched a Windows machine... the world's economy would grind to a halt. Not even Microsoft has enough money to pay damages for an event like that, though the combined law firms of the world would try to get it from them.

    --

    To a Lisp hacker, XML is S-expressions in drag.
    1. Re:Because virus writers are not subtle enough... by Anonymous Coward · · Score: 0

      Awesome, let's do it...

    2. Re:Because virus writers are not subtle enough... by metamatic · · Score: 1

      Yeah, imagine the fun of a virus that quietly swapped names around in documents, or replaced first names with obscene nicknames. ("Smith, explain to me again why our bid for the contract referred to their CEO as 'Pin-dick' on page 6?")

      For spreadsheets, the optimum in evil would probably be to pick a random numeric cell and swap two adjacent digits. Hard to spot and correct even if you know what you're looking for.

      Both would be pretty easy to program.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    3. Re:Because virus writers are not subtle enough... by IceAgeComing · · Score: 1

      Both would be pretty easy to program.

      I was following you up to this sentence. If you're talking MS, then you're talking proprietary, binary datafiles. Or am I missing something?

      Is it possible to write a script that fires up Word or Excel, swaps values, and saves the results without a user being aware? A VB macro, maybe? If I'm missing something, please post.

    4. Re:Because virus writers are not subtle enough... by ReNeGaDe75 · · Score: 1

      Uhhhh, I think he meant editing the files directly. For a project for my new job, I was looking up tools just a few hours ago that can parse and write Excel files.

      So yes, it would be very easy to do.

      --
      Hypocrisy is the 8th deadly sin.
    5. Re:Because virus writers are not subtle enough... by metamatic · · Score: 1

      Particularly since both suggested mutations can be done without changing the size of the relevant piece of data. Just program in a table of common names, and words of the same length to substitute.

      --
      GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
  224. Disable port 445 by kaos_ · · Score: 1

    I believe you can prevent infection on Windows XP by disabling the 'Server' service under Start->Run->services.msc

  225. Wow! by arodland · · Score: 1

    It doesn't come from emails, it goes through the INTERNET! Oh, maybe they meant "intarweb".

  226. why you would want to do that by Anonymous Coward · · Score: 0
    >> You would have to run the LSASS Service under Wine...and I don't know why you would want to do that !

    Why? To ensure a continuous source of Sasser to all those winboxen, duh! Why should being off make you invulnerable? Worms ho! heh

  227. Cleaning the virus ... by Flossymike · · Score: 1

    I've been cleaning the virus off people machines over the phone using MS own instuctions here but then going to the manual removell instructions as people couldn't connect to the internet. I have noticed a lot of the computers have avserve.exe and avserve2.exe on them, but I've trouble over the phone finding *_up.exe and running the search was being incrediblely slow, ended up just going the folder and then choosing to view the contents.

  228. I have a question too by aztektum · · Score: 1

    How is this virus being installed on a computer? It's not a d/l'd attachment style. If you don't have to d/l anythin' why is it a problem?

    All the tech info I've read has said what it does, but unless I'm missing something, there isn't anythin' on how they get the virus on ur machine.

    Can someone break down what's happening to those who are getting infected?

    --
    :: aztek ::
    No sig for you!!
    1. Re:I have a question too by Progman3K · · Score: 1

      aztekum,

      I should have titled the original post "What is this virus's PURPOSE?" instead of "What does it do?"

      The method of infection is clear; it gets onto your computer by connecting on an open TCP port.

      What isn't clear is WHY was this virus developed...

      --
      I don't know the meaning of the word 'don't' - J
  229. Because Ebola burns itself out. by karlandtanya · · Score: 1

    That's how come.

    --
    "Reality is that which, when you stop believing in it, it doesn't go away." - Philip K. Dick
  230. Sasser Removal Tool by steveargonman · · Score: 1

    http://www.mind.net/stinger -> Much easier to type..

  231. Re:M$ - First Thought? by Anonymous Coward · · Score: 0

    You are surely misinformed. This particular bug requires no and I mean NO user interaction (except switching the computer on)!!! The computer only has to be connected to the internet or a LAN connected to the net.

    I think that you mean to say we need a large body of educated sysadmins who know how to apply patches (and then more and more and more patches)!

    Even then, suppose a sharp sysadmin has just done a fresh install of Windows 2000 or XP. How does he get the patch? Not by connecting to the net!!! The computer may be infected in seconds.

    But wait a minute, if the sysadmins were really first rate, they wouldn't be running anything by Microsoft, at least not while connected to the net!

    And we all know that nobody should be an "early adopter" of anything Microsoft. The horror of this bug is that anybody running Windows 2000 should be considered an "early adopter".

    I, with my trusty copy of Win 98SE, just happen to be unaffected by this bug! I guess that it follows that the time scale defining "early adopyers" has been stretched out to about a decade in the case of Microsoft!!!

  232. Re:in our case? a broken network. by Anonymous Coward · · Score: 0

    you're right, I was meaning to say that, but I forgot. *shrug*

  233. Re:Windows only by Anonymous Coward · · Score: 0

    "two years ago..."

    Holy cow, in the case of Microsoft, there was a bug about last week, or was it the day before yesterday, or was there more than one bug during that time?! Or, let me say it by asking a rhetorical question, "Which Microsoft bug were you referring to?".

    Microsoft is so busy stomping out grass fires that "two years ago" must seem like a century to them

  234. Aren't these known vulnerabilities... by rsilvergun · · Score: 1

    and probably fixed if you're willing to patch. And no, Linux isn't inherently secure, it's inherently _more_ secure (than Windows anyway). Not running as root helps. Not having you're web browser integrated into the shell does too (and by shell, we're talkin' plain X windows). Having programmers who make decisions to patch that aren't based on what it'll cost to do support is nice. And going back to integration, it's nice that if a patch does hose a program, it doesn't usually take my whole system with it.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:Aren't these known vulnerabilities... by Frizzle+Fry · · Score: 1
      Linux isn't inherently secure, it's inherently _more_ secure (than Windows anyway). Not running as root helps.

      It would seem you don't know what "inherent" means, as choosing to run as root is not an "inherent" part of the operating system. In fact, it's just as easy to do this on linux as on windows. I don't think there are many companies (other than small ones) that allow most of their employees to be Admin on their Windows machine, or even to know the Admin password.
      --
      I'd rather be lucky than good.
    2. Re:Aren't these known vulnerabilities... by rsilvergun · · Score: 1

      What is inherent is the ability to _not_ run as root, and still run all your applications. There are some apps that just will not run in Windows unless you're logged on as Admin, no matter what you do with permissions. And at any rate, in XP Home you're only choices are Admin and limited user, and you can't edit policies without mucking about with the registry (or getting a third party tool, hardly a good solution).

      --
      Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    3. Re:Aren't these known vulnerabilities... by Frizzle+Fry · · Score: 1
      What is inherent is the ability to _not_ run as root, and still run all your applications

      That's not inherent in the operating system. That's a problem with applications. One could write software for linux that requires you to be root, just like they can for windows. They tend not to, but this isn't an inherent part of the design of windows, it's poor programming on the part of application writers.
      --
      I'd rather be lucky than good.
    4. Re:Aren't these known vulnerabilities... by Anonymous Coward · · Score: 0

      I was annoyed when we upgraded to WinXP that some program would not run unless I made the person a power user on that computer. I'd much rather they be as locked down as possible.

    5. Re:Aren't these known vulnerabilities... by rsilvergun · · Score: 1

      The only way an application could do that under linux is if they had some code like:

      if (userid != root) then exit(0);

      I could take a regular user in Linux, and with enough screwing around, turn him into root. I can give him permission to do _anything_ in the system. You can't do that in windows. The feature just isn't there. Or if it is, it's buried so deep in the registry you'll never find it (and good luck getting Microsoft to help, those kind of hacks aren't supported).

      --
      Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    6. Re:Aren't these known vulnerabilities... by Frizzle+Fry · · Score: 1
      The only way an application could do that under linux is if they had some code like:

      It can do it by requiring write access to somewhere normal users won't (or at least shouldn't) have access to, like /bin
      I could take a regular user in Linux, and with enough screwing around, turn him into root. I can give him permission to do _anything_ in the system. You can't do that in windows. The feature just isn't there.

      Is this a joke? You list one of the major areas where even unix advocates admit windows is better and then say it "isn't there" in windows? In Unix, your only options are to set read, write or execute for the owner, the world or the "group". That's it. On Windows, you can use ACLs to specify exactly what permissions every individual user has from a much richer list of choices, and you can ACL any directory, file or even an individual regkey.
      --
      I'd rather be lucky than good.
  235. Yes, it is. by gillbates · · Score: 1
    Security is a process, not a product...

    Yes, though one must consider the impact of that process on other systems. Linux requires much less time to keep secure than Windows; basically, Linux requires patching every year or so, where Windows requires a patch every month. Worse, since so many of the security exploits affected required components of the OS such as IE, I seldom have the option of turning off or uninstalling insecure software. The wuftpd and SSH vulnerabilities that anti-Linux zealots love to trump up didn't affect me at all, because I don't use either, and hence, don't have to download patches.

    assume you still look both ways before crossing the street

    That was a bad analogy to prove your point, really. Yes, I look both ways before crossing the street, but in the case of Windows, its more akin to being thrown into expressway traffic and having to dodge cars. Windows simply doesn't allow you to see oncoming security problems because you can't inspect the code; their "hide everything from the user" mentality makes it difficult to find potential security flaws before they are exploited. The security flaws discovered in Linux were often discovered at the source code level before an exploit was discovered; but with Windows, almost every security patch is the result of someone's server getting exploited and Microsoft trying to figure out what happened. The fundamental difference is that Linux takes a proactive stance, fixing security problems before they cause problems. Windows OTOH mandates a completely reactive stance - you must wait on Redmond to issue a fix, and Redmond doesn't know about it until someone's box gets owned.

    To do a bad paraphrase of Clint Eastwood:

    "I know what you're thinkin': 'I just patched my windows boxen, I must really be secure.' Well just ask yourself one question: 'Do I feel lucky?' Well.... Do ya, punk?"

    Do you feel lucky? Are you betting the next Windows exploit will infect someone else's machine before it gets to yours? Are you betting that Microsoft will be able to acknowledge the problem and find a workaround before your server gets hit?

    Yeah, so Windows has patches. But how am I supposed to download said patch, when connecting to the internet to do so exposes me to the very same infection I'm trying to prevent?

    What it really comes down to is that Linux simply takes less time to keep secure than Windows. Yes, I suppose their are exploits for Linux yet undiscovered. But, it is far more likely that there are far more undiscovered security holes in Windows than in Linux.

    --
    The society for a thought-free internet welcomes you.
    1. Re:Yes, it is. by GMFTatsujin · · Score: 1

      While you're not going to get an argument from me about Linux vs. Windows and the time it takes to keep secure, the point is still valid. You need to be aware of security as an action, not a result.

      As for the proactive vs. reactive argument -- why so I keep hearing so many admins (at work and on /.) griping about how vulnerability X was taken care of by patch Y, Z many weeks ago? I keep my box at work patched up and I've hardly been touched. Seems pretty proactive to me.

      In fact, I'd venture to say that I've lost more productivity on my side from sharing my environemtn with non-patching nitwits who get infected, thus tying up the network and crushing servers that my nice clean machine needs access to. And in that case, it doesn't matter what OS *I'm* running -- it's the guys who can't be bothered to patch their own boxes who are causing the very problems they bitch about.

      Compute responsibly: either switch to a secure OS or PATCH YOUR DAMN MACHINE. Preferably, do both! It's the right thing to do.

  236. Re:in our case? a broken network. by Aetrix · · Score: 4, Interesting

    I also work with clinical trials and the FDA breathing down my neck. My office is all running Macs. Intentionally. We knew that the small functionality loss from "going Mac" would be much much less than the horrific security problems unleashed on the Windows World.

    --

    "One touch of Darwin makes the whole world kin." George Bernard Shaw
  237. Re:And all you 'marketshare' trolls just STFU now. by Anonymous Coward · · Score: 0

    ...plus the fact that Mac OS X is based on open source Uni* which has had probably 99% of it's security issues fixed in the 20+ years that it has existed.

  238. IF I had mod points... by Anonymous Coward · · Score: 0

    I would mod you -1 Apple-Zealot-Dip$hit.

    1. Re:IF I had mod points... by Anonymous Coward · · Score: 0

      But you don't! Ha HA!

  239. Casual observation... by Gooba42 · · Score: 1

    I'm watching the response from people here and now having read the article I find it kind of interesting.

    The *most* critical systems are the ones most hard hit by this worm. The reason they are so hard hit is *because* they are critical. Admins are reluctant to break these systems by installing broken patches without due diligence of testing.

    If the testing takes longer to complete than the worm takes to propagate, then we have a problem.

    I think this is as good, if not a better, argument against Windows as I've ever seen. Their security is crap and the systems we've put in place to patch over their holes are biting us in the ass as badly as if we'd never tried to fix it at all.

    --
    I just found out there's no such thing as the real world. It's just a lie you've got to rise above. - John Mayer
  240. Suing Microsoft for incompetence? by BigBlockMopar · · Score: 4, Insightful

    Of course I think Microsoft should be sued for some of the problems we have. I don't think everything in the EULA will hold up in court in every state. But it's not my decision.

    Okay. How about those people who don't even run Windows and therefore have no part in the EULA? Their networks are being ground to a halt because of flaws in Microsoft software and their patching process, as infected machines attack them.

    Analogy: car company X builds cars with defective brakes. You didn't buy that car. Your wife and children are driving home from shopping and someone driving X's car runs through a red light because he can't stop, and plows into the side of your wife and kids. Now, not that I'm overly litigious, but there's a time and place for companies to be held responsible for the damage caused by their poor products and designs.

    Who do you sue? The guy driving the car with defective brakes, or the company that has a pattern of time and time again making defective products?

    --
    Fire and Meat. Yummy.
    1. Re:Suing Microsoft for incompetence? by sr180 · · Score: 1
      You obviously dont live in the US. You dont just sue the driver and the car company, but also the owner, your car company, the dealer, the mechanic, the Road Traffic authority, the local council....

      --
      In Soviet Russia the insensitive clod is YOU!
    2. Re:Suing Microsoft for incompetence? by Anonymous Coward · · Score: 0

      Why not sue the idiot? S/he should have done some research before buying a potentially dangerous oper. . .er. . .car

  241. I'm glad you went into more detail. by Futurepower(R) · · Score: 1


    I'm glad you went into more detail. I like the idea of port-scanning on login.

    It seems to me that software firewalls on each machine should also be a matter of often-repeated company policy. I know managers who will not tolerate ignorance of computer use rules. People adjust. Most people are safe drivers, and learning to drive is much more complicated than learning to use a computer safely.

  242. Re:M$ - First Post? by Jaster+Mareel · · Score: 1

    I agree that we need a more educated user base, particularly when it comes to security concerns but at the same time computer software vendors need to work on writing better code, and they need to keep security in mind when writing the code.

    Luckily for me SUS checks and forces out the patches for MS every night (those that are turned off get the patches forced when the log on to the domain) so Sasser wasn't a problem.

  243. Scenario 2 by MyHair · · Score: 1

    A. Non-IT employee who fancies himself a PC guy brings his PC in to work on the night shift
    B. Unplugs his work PC connection
    C. Plugs in his home PC to download something from the fast company net connection
    D. Infects lan from inside
    E. Takes PC home and no one but him knew it was there.

    I wonder where these other people work where employees important enough to have laptops can be PC-Nazi'ed around. Where I work the people with laptops tell me how things are. And the guys who bring PCs in for movies and LAN games are buddies with everyone including security so I almost never find out.

    All that said, I had one infection on a laptop in 100 PCs under me, and 4 that were rebooting but didn't actually have the virus running or on the HDD because the virus scanner prevented it from saving to disk. The laptop guy was off the network before Sasser released and was hit before his scanner auto-updated. And he's the head honcho.

    I forgot to mention my LAN is part of a worldwide WAN and we're getting attacks from other parts of the intranet. So I don't know if the local head honcho caught Sasser at work or at home over the weekend.

  244. Re:Yeah..you're telling me...bullshit by Anonymous Coward · · Score: 0

    hmm. We don't love MS at my POE but we are all bright enough to update our systems and as a result have had no problems. You may try NOT announcing that you and your company slack on updates and security.

  245. Risk of applying patches by BigBlockMopar · · Score: 2, Interesting

    If you don't believe me, Google around for articles about patches breaking machines versus articles about viruses breaking machines. I think you'll see that some of the latest viruses and worms hit in the many millions, whereas the problems experienced from patches hit in the many thousands or are not completely debilitating.

    Great! You can explain that to my boss when 500 out of the 600 users in my organization are unable to work because a Microsoft patch broke one of our servers and everything has to be reinstalled from scratch and incrememental backups, only to be hit 5 minutes later by the very worm we'd applied the patch against!

    Recovery from that - conservatively, a day. Conservatively. Now, these 500 people are out of work for a day, but they're salaried... lawyers, Judges, court reporters, clerks. The average salary is probably $75,000 in this organization. That's about $300 per day per employee, or $150,000 in damages. Never mind the fact that we have to run on set schedules or else other bad things happen. I can't take that risk, even if it's 1 in 100, before I click on that little Windows Update icon.

    Theoretically, of course, the patch shouldn't do anything but fix the poor bounds checking in some DLL or something - just replace the DLL with a corrected binary. But if you've ever applied a patch, you *know* they play with all sorts of other things. We run Novell, and I've used Snapshot on PCs before and after applying what should be very simple patches, only to find dozens of files and unrelated registry keys have been changed. Microsoft clearly does other stuff in patches - quiet fixes of other problems which haven't been publicized, adding DRM software, I don't know but you can only guess at their motives - and how long until one of those breaks one of my production server?

    No, man. I need to be able to look at a patch and know exactly what it does, so that I can tell in advance if it's going to break something. I need the diffs between the patch and the original source so that if it does break something, my developers can immediately know what changed and how to work around it. I need to be able to apply them individually without requiring a reboot of the server, just a restart of the daemon (ahem... service) in question.

    And I ain't gonna get any of that from Microsoft. But, unfortunately - and it wasn't my decision - this server is running Windows 2000 Server, and the best thing I can do is hope that there's no e-mail borne version of the worm to get it into my LAN.

    --
    Fire and Meat. Yummy.
    1. Re:Risk of applying patches by Tony-A · · Score: 1

      No, man. I need to be able to look at a patch and know exactly what it does, so that I can tell in advance if it's going to break something. I need the diffs between the patch and the original source so that if it does break something, my developers can immediately know what changed and how to work around it. I need to be able to apply them individually without requiring a reboot of the server, just a restart of the daemon (ahem... service) in question.

      Well put.
      Otherwise you're flying blind.

      At the extreme, *nix allows you to compile or install the new software and then shutdown and restart the service. It might even be possible to do this on a busy server without anybody noticing anything.

  246. No-one should use IE, ever... by tiger99 · · Score: 1, Offtopic
    That is the simple answer. It is a rotten, outdated, bug-infested and insecure piece of trash which was only cobbled together in a hurry to trash Netscape and has now been abandoned (i.e. Sir Bill has lost interest....)

    Why does anyone anywhere still use it? And why do grossly incompetent web designers still make sites that only work properly in IE? (Likely they are the same bunch of no-hopers who also use small fixed-size fonts so those of us with high-res screens and IE can't read the text.... Funnily enough, Mozilla has a text zoom for such situations, IE only zooms non-fixed text! No doubt they also use feeble tools like Frontpage.)

    We have, very predictably, been hit very badly today at work, the IT Dept are blissfully unaware of the issues which reliance on the combination of trash products of the Convicted Monopolist, and the unreliable anti-virus protection of McAFraud can cause. Cost of cleanup today, maybe 5000. Cost of issuing everyone with Mozilla and IEradicator, zero. But will they do it?

    Think of the amount that would be saved if governments passed laws forbidding the use of IE or Lookout, or if shareholders held company directors responsible for the losses due to their incompetence in allowing use of such junk.

    1. Re:No-one should use IE, ever... by Anonymous Coward · · Score: 0

      you're right: no one should use IE. you're wrong, however, attributing this latest exploit to IE. it's the LSASS.exe process which authenticates users at log-on, and listens on port 445. other then that, good rant!

  247. Re:Windows only by MyHair · · Score: 1

    Windows Update is the friendly auto-patcher. AFAIK you can't download patches from there for later use. But the patches are available seperately; I used Firefox to download one of the patches I was missing. (The rest I FTP'd from a coworker who downloaded most of the patches.)

    Here is the place to download the MS04-11 patches to prevent the Sasser worm, although for the moment that URL seems hosed. Google cache here.

    Sasser detection and treatment info from Microsoft.

    http://www.microsoft.com/security/MS security home.

    I love to bash Microsoft, but if you'll look carefully there's usually a way around the candy-coated-user-friendly-tools-that-break-when-t hings-go-bad. They even have some handy downloads for detection, treatment and patching.

  248. If the patch breaks one user, it breaks them all. by BigBlockMopar · · Score: 2, Insightful

    Let your employees run autoupdates and if one of them does break your machines, roll it back. Servers are a special case, because if you lose the TCP stack on your mail server it's much worse than if Ted from Marketing loses his.

    Most corporate desktops are imaged from a standard install. They're clones of each other.

    Therefore, if a patch breaks one of the desktops, it breaks them all. And pretty soon, I have 600 employees who can't work because all their computers are down.

    All of which will remain down until either we massively roll-back the update (probably requires re-imaging each and every machine) or figure out a way to remotely deploy a fix for whatever the patch broke. Either way, 600 users are down for at least a day. Average salary in my organzation is $75,000 a year which translates to a daily loss of $180,000 - just in salaries.

    That's the sort of scenario which results in getting fired.

    --
    Fire and Meat. Yummy.
  249. Hello, our application is the business by Linux_Bastard · · Score: 1

    Talk about throwing out the baby with the bathwater.

    --
    F X=0:1:9999 F D=2:1 Q:((X>2)&(X#D=0)!((D>X/2)&(X'=1))) I D>(X/2) W:$X>75 ! W X,?$X+5-$l(X) Q
  250. Why can't we catch these guys? by bobslidell · · Score: 1

    Assuming that all 29 variants of Netsky and at least some of these Sasser variants are written by the same people, why haven't we caught them yet? If someone robs a bank, maybe you don't catch them. But >30 banks, and perhaps your law enforcement folks need some help. Is the FBI really working on this?

  251. Re:If the patch breaks one user, it breaks them al by dasmegabyte · · Score: 1

    So the solution is pretty apparent and pretty simple: find one clever, relatively inconsential guy somewhere in the company. Give him and him alone the patch on day 0. Let him use his machine as normal...if he discovers a problem, you saved your $180,000. If he doesn't, you can roll it out to the others feeling secure.

    My point is, there is absolutely no reason why you should have to test the patch yourself. And if you're waiting days, or weeks, to have "time" to test a patch, you're almost inviting viruses. I develop applications full time and also perform virus duty for 40 employees...I don't see why you can't handle 600 if you're doing it full time.

    --
    Hey freaks: now you're ju
  252. have a holiday rather than a firewall by thegoldenear · · Score: 1

    from the linked BBC article:
    "Holidays in the UK, parts of Europe and Japan may also help to limit the spread of the worm."

  253. buffer overflow? Fix the code? by ggwood · · Score: 1

    So many problems are caused by buffer overflow - my impression is that this worm is one of them (but even if it isn't, I still have a question). Why is it that we have these problems?

    Often I read something along the lines of: the C programming language singlehandedly invented many of these problems by not checking array boundaries or doing proper garbage collection, or something like this. The implication is that before C other languages did do this.

    Is this true?

    If so, isn't it just a matter of writing a compiler which checks array boundaries and re-compiling (insert your favorite OS here) with that compiler?

    Obviously, I have the feeling this is far too simplistic. I'm a programmer but not a computer engineer. Is there a simple explanation/counter arugment?
    ____________________________________

    --
    a war on terrorism? How can we end a war on a method?
  254. Re:M$ - First Post? by penguinbrat · · Score: 1

    You make some good points - however, I need to also point out that their are some very big stickers on the bumper hitch that says very clearly how much it can tow, and likewise the safe way to do so - and ALSO the very dangerous and potential results of attempting the tow. Their is a large portion of the owners manual dedicated to this feat. From what I understand, if Ford and GM "didn't" put these notices on their vehicles they would get sued for negligence (IANAL) - "That's what it is there for your honor, I thought it would work - their was nothing that said it wouldn't!?!?!".

    My main point here is that M$ has their ass completely covered with EULA - do you think there would be any vehicles sold if the manufacturer claimed indemnity due to flawed or negligent engineering? M$ is constantly getting dragged into court for their business practices, but NOT on their negligent or sloppy software - everything is blamed on the uneducated user, how far is that going to go?

    With computers used everyday as much as the everyday car - when is the blame going to shift from the end user to those who create the car. The car should be ready to go off the lot, and last a lifetime as long as it is taken care of - there should not be numerous recalls to replace critical engine parts (patches), all there should be are simple oil changes and tuneups (file system cleanup, rebooting, etc..)

    I've recently received a notice from GM about a recall concerning a faulty ignition switch that could conceivably catch on fire in the right situation. In corelation this could be seen the same as booting up my computer, and the operating system simply crashing (destroying all my data). The difference is that if the recall was never issued I could have sued GM if it ever happened to me, ie: faulty engineering (ever watch Fight Club for the reasons behind recalls? LOL) - according the EULA, it is my problem for installing the OS in the first place - which is the same as saying it was my fault for buying the car in the first place, regardless of the fact that GM used parts that simply would not hold up.

  255. Petri dish by oohp · · Score: 1

    Windows is just like a Petri dish, a good place for viruses to flourish in and spread from.

  256. Solutions for dialup users? by Brad+Mace · · Score: 1

    My inlaws managed to get this even though they have a dialup connection which they hardly ever use. Are there any hardware firewalls that can be used with dialup?

    1. Re:Solutions for dialup users? by Anonymous Coward · · Score: 0

      No black-box solutions that I'm aware of but I used to use a small linux distro with an external modem... won't work with winmodems, though, which is what most of them are nowadays. Google for Freesco if you have a spare computer and a REAL modem lying around.

  257. Re:in our case? a broken network. by zcat_NZ · · Score: 1

    we can't apply *anything* without formally testing it.. .. which brings the question; is sasser certified to install itself on your system? Because if you're unpatched it probably will sooner or later.

    Are bagle or netsky certified? How about bugbear? Claria? Hotbar? Ezula? Cydor? ComLoad? B-S Spy?

    What about 'copy-protection' CD drivers or the windows media DRM upgrade? It could well have installed itself the last time you played a CD, many of the copy-protected CD's I've seen patch XP on autorun, with no warning at all.

    Chances are one or more of these programs are already installed on your system, you just don't know it yet.

    The first requirement of any certification program should be that you run an OS where programs and patches (malicious or otherwise) can't easily install and hide themselves.

    --
    455fe10422ca29c4933f95052b792ab2
  258. Funny thing by Anonymous Coward · · Score: 0

    My company of 15,000 employees and spread out through out the country hasn't had one problem. We all have XP on our desktops. Use UNIX for software development but mainly spend all day on Win Box. No problems. I guess our IT folks know what they are doing. Don't allow that crap to get through.

    Losers!

  259. Re: plural rant by nacturation · · Score: 1

    Why do people insist on putting -i at the end of every word that has a singular form ending in s? The plural of iris isn't irii. The plural of axis isn't axi. The whole purpose of the -es plural is that you are supposed to use it when a word ends in s. Why must people emply this queer new form? It just makes them sound like pompous douches -- or is it douchi?

    It stems from octopus, one of those trivial things where people know that the plural of which is octopi (or octopuses). They then generalize this to assume that every word that ends in "us" can be pluralized by replacing "us" with "i".

    Your logic of always appending "es" to a word ending in "s" is wrong. The plural of "phallus" is "phalli" (or "phalluses"). The plural of "torus" is "tori" -- "toruses" is actually 100% wrong. The plural of "modus" is "modi" -- "moduses" is also wrong. The plural of "corpus" is not "corpuses", it's "corpora". "abacus" ... "abaci" or "abacuses". "cactus" ... "cacti" or "cactuses". And the plural of "genus" isn't "genuses", it's "genera".

    --
    Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
  260. wtf? by JeanBaptiste · · Score: 1

    how did you post your sig without the [mozilla.org] following it?

    1. Re:wtf? by Tin+Foil+Hat · · Score: 1

      Slashdot has a setting to show the domain name. You can set this to always show them, never show them, or to show them in recommended situations. The third option is the default. Mozilla.org is apparently a trusted site.

      Check your user options, there's some cool stuff in there.

      --
      No matter how many of my rights are taken away, somehow I still don't feel safe. -Frigid Monkey
  261. Re:Windows only by xcomm · · Score: 1

    > We hosted close to 300,000 web sites; both Windows and Linux. Our customer base was roughly 60% Linux and 40% Windows; hosted on a little over 5,000 servers.

    > 3,000 servers running Linux web sites
    > 2,000 servers running Windows web sites

    Hmmm... where the hell have been working, Redmond? What I see in Frankfurt (Europe's second large backbone after London) is just the opposite to Netcraft too - but in the other direction. In my company are about (50000 servers) 85 % GNU/linux (Debian/RedHat/SuSE/Gentoo), about 10 % *nix (Solaris/HPUX) and about 5 % Windoze. The last part is mostly run from non techies, or based on some dumb management's attitude or used by gameserver hosters (the only reason with some sense).

    And from what I see every day someone must really be brain damaged to run Web servers on this M$ crap in the wildlife from every point of view (recources, security, license costs, locked into a company fully untrustworthy ...)!

    Regards, xcomm

    --
    [SIG] Somewhere in Texas, there's a village missing its idiot.

    --cited from netsharc at http://slashdot.org/~netsharc

  262. Our notebook firewall is a paper notice by Slashamatic · · Score: 1
    stuck in the elevators informing all notebook users to call PC support for clearance before connecting. It didn't work though, my XP desktop was infected by the time I came in on Monday. Thank heavens it was only for testing the bank's new foreign exchange system, not in production.

    Of course, an Accenture person studiously ignored the sign and verbal instructions not to connect her notebook. Luckily she hadn't been infected over the weekend.

  263. Re:M$ - First Post? by SphericalCrusher · · Score: 1

    It depends on how user-friendly Linux becomes, but as of right now, not at all. If they can successfully learn Linux as it is right now, then they will definitely learn to use Firewalls (which I'm personally against) and Anti-Virus software.

    --
    "Instant gratification takes too long." - Carrie Fisher
  264. Re:Windows only by Disevidence · · Score: 1

    I find it very funny that your sig is trying to correct their and there, yet you use make believe words like virii in your post.

    You are such a fucking retard.

    --
    Think nothing is impossible? Try slamming a revolving door.
  265. Re:in our case? a broken network. by RMH101 · · Score: 2, Insightful
    ok, obvious answer: no, of course trojans aren't certified. no one wants them, everyone takes steps to prevent them (hence saying i'd pull my validated systems off the net if that was what was required). however, we're talking about damage limitation here. i can't possibly afford any possibility of data corruption and am legally liable for up to 25 years for any clinical data captured on my systems.

    As for playing CDs, etc: NOT ON MY CLINICAL SYSTEMS. these are *most definitely* not standard desktop PCs.

    what it boils down to is i know PRECISELY what is on my machines: from little rubber feet up - I've documented evidence down to precise driver levels and there is *nothing* on there that i haven't specifically placed there, INCLUDING NEW PATCHES that haven't been exhausively tested by me - seeing as it's my signature on those FDA documents...

    i'm not sure what your last line meant: can't specifically disagree with it, but i'm not talking about any "certification program", i'm talking about regulatory compliance in a production system.

  266. Re:in our case? a broken network. by RMH101 · · Score: 1

    ok, nice and lovely. they look pretty, too, and i can imagine they'd be easier to support.
    however, if you want, say a clinical app that does bedside CRF capture, you need to buy it from a vendor, and i've not come across any that do what we want on macs...

  267. Anyone care to use proper firewalls on their LAN? by Anonymous Coward · · Score: 0

    Really,

    Stop complaining about viruses and security holes. Most OS'es has them, including Linux. Just take a look on the update lists for a normal Linux distribution from Mandrake, Suse, RedHat or others.

    It is not about patching to prevent virus attacks. If a virus can access your computer you have big problems with security, and that is YOUR fault. Don't come and say MS or RedHat or anyone else should fix your network for you.

  268. Re:in our case? a broken network. by zcat_NZ · · Score: 2, Informative

    If you can't afford "any possiblity of data corruption", then in my opinion you can't afford to have this computer on the internet at all. Patched or otherwise.

    If you really need to get data to and from the machine, stick it on a LAN with no direct connection to the real world. Or use rewritable CD's, whatever..

    Any "Regulatory Compliance" that would let you leave an unpatched Windows machine on the internet is insane.

    --
    455fe10422ca29c4933f95052b792ab2
  269. The Real Problem by ReNeGaDe75 · · Score: 1

    The real problem is human stupidity. People get viruses in their email. They run them. It's supply and demand.

    Everybody knows Internet Explorer and Outlook Express are pieces of shit with constant security exploits. When I tell them, they say "I don't care." Those are the ignorant people who will bitch when they get a virus or worm "Oh my god how could I get a virus I'm so careful"

    Everybody knows Windows is full of security holes, yet they run it anyway, and give it to everybody they know. There is only ONE reason to run Windows: There is a major app you depend on that does not support Linux (notice I say it does not support Linux, rather than Linux does not support it). Any other reason is pointless. Easier to use? Hardly. You install a patch and suddenly your system won't boot. That's certainly hard to use. I am trying to add a network printer and suddenly it doesn't recognize the remote host. That sounds hard to use.

    Now ask yourself this. Of all the people who run Windows... do most of them have a major app that requires it? No. Hardcore gamers do. Some businesses might (though it'd be better to develop a custom app, but I can understand their reasoning still).

    Think about what would happen if everybody except those who require Windows were to switch to another OS. Microsoft's market share would be cut in half. Competition would come back.

    Operating systems should also ship with more secure settings. I mean, I see all these people saying "Well, if Linux were the #1 OS it would get all the viruses, it's not any better". Well, guess what? Linux itself has very few security patches. I've patched my kernel (and/or glibc and init) probably 3 times last year on my server. That's it. Most security flaws are in BIND or Sendmail, or some daemon that shouldn't be running in startup on a home desktop, but Linux distros always enable anyway.

    People should disable all startup services they don't need and install a firewall. And don't tell me "no home user grandma should be expected to do something like that". BULL SHIT! TOO BAD! You own a computer... take care of it. One could say "no casual driver can expect an old grandma to use a seatbelt". It's a common safety practice that everybody should learn to follow.

    --
    Hypocrisy is the 8th deadly sin.
  270. And possibly Sydney's trains by notwrong · · Score: 1

    The worm is also a suspect for causing big problems in the communications in the New South Wales (that's the Australian state Sydney's in) train network on Sunday.

  271. Re:M$ - First Post? by Anonymous Coward · · Score: 0

    Isn't that why we have Windows and Macs? hehe...

  272. Re:Windows only by ad0gg · · Score: 1

    One of the main reasons that many corporate/commercial servers are still running IIS is because of the ease of use in integrating MS SQL and specific data export services from what the desktop is running: Windows. Umm IIS doesn't intergrate with SQL server or export data. What crack are you smoking, IIS is web server that has ISAPI filters for addons. The Isapi filters are the programs exploited. Last time I checked common MS SQL access is with oledb or ODBC which are standardized.

    --

    Have you ever been to a turkish prison?

  273. hmmm by smash · · Score: 1
    Microsoft teams have confirmed that the Sasser worm (W32.Sasser.A and its variants) is currently circulating on the Internet. Microsoft has verified that the worm exploits the Local Security Authority Subsystem Service (LSASS) issue that was addressed by the security update released on April 13 in conjunction with Microsoft Security Bulletin MS04-011.

    from: https://www.microsoft.com/security/incident/sasser .asp

    Anyone else find this disturbing?

    The local security authority service, presumably one of the more heavily audited, security mechanisms in windows, is exploitable?

    I mean, of course, we all know Windows is an insecure, steaming pile of shit, but still.... doesn't say much for the trustworthy computing initiative :D

    smash.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  274. No offence intended, but... by Anonymous Coward · · Score: 0

    You, sir, think like a lawer.

  275. Yeah...this one has legs by Anonymous Coward · · Score: 2, Interesting

    This one will have real legs. You see, in order to cure the infection, you will have to get the cure. This can be gotten from various sources. That will cure it...for now. It will not immunize you from getting it again..and again..and agagggaaggaain! This is because the sucurity vulnerability in windows' Lsass.exe program remains and will remain so for as long as there is a microsoft and as long as they are a predatory computer thug on the face of this world.
    You see, to get the fix for the windows weakness that microsoft left in the system for we users and 'buyers', you first have to access their site, not someone else's mirror site, microsoft's site. Not just any access though! No! No!! You have to provide 'special' access to microsoft. Microsoft wants to 'web install' your patch. That means it downloads what it wants to, then runs it....ALL FROM THE WEB!!? And we are also expected to go into our security settings and set microsoft's site as a trusted site just like it was the computer in your father or mother's den on your home network. You are further supposed to trust microsoft explicitly and implicitly for all the content that they download into your machine. You are supposed to accept without question that you will never see what they really downloaded and ran in your machine. You are supposed to never question what they do, however they do it, or whenever they do it!. This from the company that gave you the bug in the first place and lobbied the government hard to make illegal the mere reporting of the existance of these bugs.
    Lets run this back and follow another bouncing ball. Lets say that you bought a car from a company like microsoft. It had a defect that could kill you or a member of your family. Somebody found out about this defect and reported it in a newspaper in a letter to the editor and signed it with his name (most newspapers demand this from their letter writers). Under the present laws, that person who wrote the letter could be tried under the terrorism sections of those laws for telling you that you and yours were in danger. In addition, the man could be forced to pay the maker of the car for the potential costs to the company for fixing those cars....not the actual costs....the potential costs. The company would never have to fix those cars because you signed a 'EULA' that said you would hold the company harmless for anything that happened to you and yours in connection with your allowed use of the car. In addition, you were not allowed to fix the car yourself as this would compromise the company 'secrets' and you also agreed to protect THOSE as well. On top of this, if grievious harm came to you or yours as a result of these faults of the company, and after pursuing the company all the way to the US Supreme Court you finally won a case that said the company was at fault, another provision of this same 'EULA' said that the limitation of your ability to collect from said company would be the lesser of your claim or five United States Dollars (actual EULA provisions in some software
    'licences'). On top of that, if the company did decide to fix your car, you would have to provide a room in your house for him or her to live while the fixing would be done, and you would have to leave the house and live in a hotel while it was being done. You would also have to leave all your valuables in your house for the company's perusal (secret installation of secret files on top of total access as a 'trusted' user on your network...this also gives total access to all files on your machine[s]). Don't laugh!
    This is only a real world illustration of the miserable, tawdry, mendacious 'end user licence agreements' that you and yours sign every day whenever you install a 'bought and paid for' program into your machine. If you really read those agreements and realize what you throw away every day and every time you click yes on these conundrums; if you had an ounce of pride in your evidently worthless hides; you would remove those programs and the operating

  276. Re:M$ - First Post? by Anonymous Coward · · Score: 0

    "Nothing beats a good educated user."

    And its illegal to beat uneducated users...

  277. Removal is not enough! by Animats · · Score: 1
    This is what LASSS does:
    • It includes such information as what domains are entrusted to authenticate logon attempts, who has permission to access the system and how (interactive, network, and service logons), who is assigned which privileges, and what kind of security auditing is to be performed. The Lsass policy database also stores "secrets" that include logon information used for cached domain logons and Win32 service user-account logons.

    LASSS is the security policy manager for NT and XP. If that's been compromised, you have to assume it was used to put in a back door. Or to transmit password-type "secrets" to some external site. It may also have changed the logs to hide it. You've got to rebuild and reexamine the entire security policy database. Passwords may have been compromised. Local shares may be exposed to outside attack.

  278. Maybe I'm just lucky... by NuclearDog · · Score: 1

    I must be lucky. My logs don't show any attempts to exploit this hole. Not like my linux box cares if they try.

    --
    This statement is forty-five characters long.
  279. So-called WinXP 'Firewall???' by Worm-wearied+Support · · Score: 1

    After wrestling all weekend with numerous client's PC's that were all infected, all running WinXP's built-in firewall, I have to ask - what (exactly) good is a so-called firewall that doesn't block incoming port traffic? And yet Micro$oft continues to state (on their web sites and in press releases) that enabling the XP Firewall will act as your 'first line of defense'. Bullocks! I can document dozens of infections on PC with the firewall turned on and NO PORTS OPEN!

  280. it would almost be like having PAM compromized... by Anonymous Coward · · Score: 0

    To comapre it to what Linux users would normally see... this is like have a network exploit that is able to modify the PAM subsystem in RH/Linuxes that use pam for authentication....

  281. Re:I have a doubt by Anonymous Coward · · Score: 0

    I don't think the coder is going to come out anytime soon apologizing for sloppy coding, lest he be dropped from the ranks of l33t hax0r to script kiddi3...

  282. Re:Windows only by cyborch · · Score: 1

    I find it very funny that your sig is trying to correct their and there, yet you use make believe words like virii in your post.

    You are such a fucking retard.

    The misuse of the words "there" and "their" comes from ignorance of their proper use. The use of words like "virii," "vira," and "boxen" have nothing to do with ignorance of proper english. These words are used as slang and incorporate some foreign grammar (like latin or german) into the language. There is nothing make believe about the words I used.

    Oh, and a nother thing: Go read the internet etiquette. Do not call me a retard unless you would call a perfect stranger you met in real life a retard. You should stop and consider what you write. For instance, using the lamguage you just used in a bar would most likely earn you a severe beating.

  283. ...and so the uninformed speak by RMH101 · · Score: 1

    my machines are nicely behind multiple corporate firewalls, sit in a separate domain, and the clients are ACL'd off from our main LAN as well. i take security far more seriously than you'd believe, and there's no way my clients for data capture get an internet connection.
    however, a pc that's not attached to anything ain't much use - so what you're controlling here is the (small) risk of having it attached to your main LAN in some way for data export and, say, citrix connection to your main desktop client PCs.

    did i say anywhere i'd be dumb enough to leave an unpatched wintel box on the internet anywhere?
    my point is that in the real world you don't just go chucking patches on boxes without thorough testing on your preproduction rig, user acceptance testing etc etc - and in my specific case it could actually be construed as illegal to do so.

    1. Re:...and so the uninformed speak by zcat_NZ · · Score: 1

      So what you're saying is that the box is on a strictly controlled LAN (what I was suggesting) and highly unlikely to ever see any malware.

      Thank you. You're not part of the problem :)

      --
      455fe10422ca29c4933f95052b792ab2
  284. Re:Please wake up...Linux has holes too! by Anonymous Coward · · Score: 0

    One hole only? I am glad I do not have you as a security admin on my network.

    There are plenty of security issues, for example in Samba, Apache, PAM and many applications and servers in Linux.

    Look here for example: https://rhn.redhat.com/errata/rhel3as-errata.html A rather large list of security updates. Kernel, Squid, OpenOffice, you name it.

    The reson many Linux systems go unharmed is because there are not so many virus writers that indeed target Linux (or Mac for that matter).

    Not long ago Gnome and Gentoo had security breach and their servers were compromised - leading to all packages they provided could have been too...

    Linux is not all Roses. Neither is Windows. What is bad are users that believe they are safe without knowledge.

  285. Wha?! by leonbrooks · · Score: 1
    Especially if sound is a requirement.

    I click on my Windows Update systray icon and a gutteral voice growls "Y'all'r OWNED, boah!"

    Seriously, how many viruses require a working sound system? (-:

    --
    Got time? Spend some of it coding or testing
  286. Round of applause, that poster! by leonbrooks · · Score: 1

    Do what you can to improve things, but work with what you've got rather than chucking a hissy fit.

    On a different note, perhaps your doc should have been two eye-poppin' pages with a reference to the other 68?

    --
    Got time? Spend some of it coding or testing
  287. If it takes you week to do testing... by leonbrooks · · Score: 1

    ...then use Linux instead, where you can change one package at a time or pull the source and test one patch or part of a patch at a time. Speeds up testing like you wouldn't believe, and gives you an alternative when updating is critical but the updates also knacker your production systems in some way.

    --
    Got time? Spend some of it coding or testing
    1. Re:If it takes you week to do testing... by cavebear42 · · Score: 1

      Without engaging a holy war, Migrating to Linux involves retraining of employees, this is a cost beyond your imagination. It involves retraining of IT (or hiring a new staff altogether.) It involves moving all of our apps to Linux compatible apps. This is where it gets impossible. Microsoft project manages most of our projects. Is there an alternative, prob but more training dollars. Visio makes our product drawings, more training dollars. Visual studio and visual source safe, more training dollars. Ect. Pretty soon we have spent more in training than we bring in, our apps are flakey at best and we have moved from everything working 99.97% of the time to struggling every day with the question, "Ok, now how do we use THIS one with Linux?" It would be cheaper to have 25 people working 24 hours just waiting around to test patches when they come out.

  288. umm . . . Windows admin NO INFECTIONS by Anonymous Coward · · Score: 0

    Well, I'm sitting around here posting on slashdot. I'm a Windows admin at a financial institution. Why don't we have any infections? First, all patches are applied within a week (servers auto rebooted in the wee hours). Yes this is a risk considering some Microsoft patches can cause problems. But the main reason is . . . PERIMETER SECURITY. We have firewalls and IDS, both internal and external. And no one hooks up to our network unless they are patched and scanned with anti-virus. By the way LSASS.exe is the local security provider, it logs you on, and port 445 must be open to use AD and domain logons. Its on by default because it provides basic functionality that the OS requires.

  289. Re:M$ - First Post? by AK+Marc · · Score: 1

    The manufacturer should make every effort they can to ensure the product works 100% out of the box. If you know full well that your Ford Explorer has tires that blow up on impact, you should not sell the product with those tires. In the event that you did so accidentally, you should make the public very aware of the situation and attempt to rectify the problem. Now, Microsoft has done reasonably well on the second account (a patch was/is available) but not so much the first. I think that having something similar to a "recall notice" for Windows OS that is very public could be a step in the right direction.

    They certainly don't do well on the first. Ford didn't continue to sell Explorers with the exploding tires after the issue was brought to light. MS continues to sell operating systems that they *know* have exploits against their bad code. I think it would be reasonable to require that code with common exploits for it be labeled as such on the outside of the box. If there were big stickers on the Win XP (no service pack) that was still available in stores that said "This product is vulnerable to a large number of exploits and contains security holes, you must connect to the Internet with this OS, opening your computer to infections, before you can patch it" then people would be properly warned before buying it.

    Preferably, I'd require that Microsoft send you (via express mail or faster) all patches up to the date of sale upon notification of purchase. That way, they can save the money of the extra shipping by only putting solid products on the shelves, and you can properly update your computer before having to plug it into a network.

    Except for the fact that MS has more money to throw at lawyers than most, I think they should lose a negligence case against them. The patches are not included in new OSs sold in stores. The patches are released on the web and require constant customer diligence, and even then the patches are often buggy enough that they are not of the quality needed for large deployments (you crash if you get the virus, you crash if you install the patch, so you are doomed either way)

  290. Re:Please wake up...Linux has holes too! by Ruie · · Score: 1
    You are correct.

    However, I was talking about my home network. An enterprise network is different - but then there are usually people paid to administer it.

    So the only hole that affected me personally was the one in OpenSSL libraries.

    The point I was trying to make is that in Linux you can examine yourself all pieces of software that you trust - i.e. networking code, firewall, ssh client.

    If you find a hole or just think the coding is bad you can discard that piece.

    With Windows there is a single point of trust - Microsoft. Either you trust Microsoft or you don't.

  291. Re:in our case? a broken network. by Aetrix · · Score: 1

    Oracle Clinical: http://www.oracle.com/industries/life_sciences/ind ex.html?content.html

    Additional features and support provided by Westat. They're currently working all of the CRF collection for Phase I/II/III NCI trials.

    --

    "One touch of Darwin makes the whole world kin." George Bernard Shaw
  292. It would be even cheaper... by leonbrooks · · Score: 1

    ...to put those 220,000 man-hours a year into refining OSS versions of the target apps you're interested in, so you can roll them out on MS Windows. Once that's done and everyone's used to it you can swap tablecloths underneath the crockery with nary a ripple. Goodbye, spyware. Goodbye, porn diallers. Goodbye, DRM.

    As a side bonus, your company will have become famous, you will have significantly raised the skill levels of roughly 100 of your employees, your applications will do exactly what you want them to do, and will work equally well on a management consultant's W2k laptop, your wife's Mac or a remote office's Linux gateway server. Possibly also on your 'phone or PDA.

    If a dozen suitably sized companies put in that much effort Microsoft would be history, the computing playfield would be totally different, productivity would skyrocket and there would be no next Sasser worm.

    Oh, and sooner or later there would be an end to the haemorrhaging.

    --
    Got time? Spend some of it coding or testing
  293. missed the point by cavebear42 · · Score: 1

    there isn't 220,000 man-hours to spare. the point was is that continuing to run microsoft windows is by far the cheapest way to go. the patches cost is minimal if dealt with correctly.

    btw, chances are that the haemorrhaging would end shortly after the chapter 11.

  294. Re:Windows only by randyest · · Score: 1

    I read the journal entry linked in your sig. You have an excellent grasp of the difference between there and their and I applaud your efforts to educate the teeming millions.

    Unfortunately, your journal post is archived so I can't reply there, but as one pedant to another (aspiring one, at least) please review this sentence from your journal entry on grammar:

    I have nowhere else to write but in my journal, hoping to reach out and educate the american public (and anyone else, who do not know the difference between "there" and "their").

    If I may, I'd like to suggest that your next lessons be, in order: (1) subject-verb agreement ("anyone else does," not "do," (2) capitalization ("American,") (3) comma usage (with special attention to when commas should not be used, such as is the case with both of yours), and (4) proper relative ordering of quotation marks, parentheses, and periods ("This parenthetical quote is properly punctuated; yours isn't.")

    Of course, by then you'll probably have picked up why your sentence structure is fundamentally flawed (hint: a semicolon and "I'm" instead of the comma before "hoping" would fix it.) Keep up your studies and spread the good word as soon as you learn it!

    --
    everything in moderation
  295. Re:Windows only by cyborch · · Score: 1

    Since I feel like burning some karma, and to explain (not excuse) myself: English is not my native tongue. I try to use correct spelling and grammar whenever I can, but sadly english grammar is very far that of my native tongue, and being a programmer I tend reverse the order of quotation marks, parantheses and periods.

    "This is a sentence written with programmer grammar". The idea is that a string is a single token and should not be mixed with the period which is another token.

    I will be reading up on english grammar, but I won't be preaching about it's proper use before I have a better grasp of it myself.