Slashdot Mirror


WindowsUpdate.com Secured, Permanently

Precisely nineteen months ago, Bill Gates sent out a memo to employees (and the press) announcing that security was Microsoft's number-one priority. Today, about a hundred readers have submitted the news that Microsoft.com went down last night. And now, the company has "extinguished" WindowsUpdate.com (future updates will come from a different domain). All this because of some Microsoft worm that triggers at midnight. Related news: Windows Update says you're protected, but maybe you're not; WU.com briefly ran Linux, heh; worm variant with clever "anatomical term."

766 comments

  1. Next Week.. by msblaster.exe · · Score: 5, Funny

    Don't worry next week there will be another memo with the URL for the new update

    1. Re:Next Week.. by Ledskof · · Score: 5, Funny

      secured permanently? So they unplugged it from the network to finally get that C2 security level eh?

      --
      This is my sig. The post is over.
    2. Re:Next Week.. by cravey · · Score: 5, Funny

      I wonder why they didn't just point DNS for the website to 127.0.0.1.

      Let the infected servers work it out amongst themselves. :)

    3. Re:Next Week.. by Anonymous Coward · · Score: 3, Funny

      I wonder why they didn't just point it to sun.com

    4. Re:Next Week.. by TheViffer · · Score: 2, Interesting

      Na ... nothing like that.

      When Microsoft knows something like this is going to happen they pull in there secret weapon, big-gun software to handle the load ...

      Microsoft's secret weapon

      --
      -- Knowing too much can get you killed, but knowing who knows too much can make you rich.
    5. Re:Next Week.. by kilgore_47 · · Score: 4, Interesting

      I wonder why they didn't just point DNS for the website to 127.0.0.1.

      Better still, why not put 30 or 40 round robin DNS entries in? Symantec says there's about 228,000 infected boxes; with 40 different IPs on windowsupdate.com's DNS record, each server would be hit by less than 6,000 attackers. Surely, with the time they've had to prepare, they should have been able to handle this.. I'm really surprised that they actually took windowsupdate offline. I think any competent sysadmin with the financial resources of MS behind them should have been able to weather this storm without any loss of service.

      I've been kind of wondering if there might not be some other exploit that some researcher is waiting to release, after everyone's auto update is broken...

      --
      ___
      The way to see by faith is to shut the eye of reason. --Ben Franklin
    6. Re:Next Week.. by Anonymous Coward · · Score: 0

      Let us say that, on average, each machine has a broadband internet connection with 256kbps upload... that's 6000x256=1536000kbps or 1536 mbps or 1.5gbps.

      If all the machines kept up a non stop attack utilising all the available bandwidth then I think that the servers probably would not be capable of coping with that.

      After all, each server might only has a 1gbps connection to the backbone so 1.5gbps would overload its connection quite easily.

    7. Re:Next Week.. by yomamasbooty · · Score: 3, Insightful
      Actually pointing the DNS to 127.x.x.x really doesn't do much. While it does point it back at itself, the SYN flood isn't strong enough to take itself out. With this worm you really need multiple hosts to DoS another.

      The best way to deal with the worm is to return a null value in DNS. This ensures the SYN flood never gets started.



    8. Re:Next Week.. by ak_hepcat · · Score: 1

      because the syn attack creates packets with a random source address on your network.

      The syn packet is directed at 127.0.0.1, port 80.
      90+% of people don't have a webserver running on their machine, so an RST packet, source 127.0.0.1, destination of that random address on your network is sent.

      Presto, instant DOS against your own network. Fun for the whole family!

      --
      Support FSF: Stop thinking with your wallet, and think with your imagination. (cc/non-commercial)
    9. Re:Next Week.. by totallygeek · · Score: 1
      I wonder why they didn't just point DNS for the website to 127.0.0.1.



      Find out the addresses "attacks" are coming from and update DNS records to round-robin between those addresses, rotating them out every 5,000 or so machines.

    10. Re:Next Week.. by Professor+Bluebird · · Score: 2, Interesting
      When Microsoft knows something like this is going to happen they pull in there secret weapon, big-gun software to handle the load ... According to Netcraft, and the certificate from https://windowsupdate.microsoft.com, MS has moved Windows Update to Akamai. This pushes the DoS on someone else, and obviously protects MS's internal network.
    11. Re:Next Week.. by Anonymous Coward · · Score: 0

      I suggested that, or something like it at work today and was LAUGHED at! My company is more worried about how to protect themselves via their proxy solution, and are running around like dipshits trying to put ACLs in for every "known" windowsupdate IP.

    12. Re:Next Week.. by cdecroes · · Score: 2, Funny

      I'm suprised microsoft didn't point it to 129.42.19.99 (www.ibm.com)

    13. Re:Next Week.. by Anonymous Coward · · Score: 0

      I am a linux geek and I was able to patch my home boxes and my client's winders boxes, weeks ago.

      No problem keeping up here...

      It really pays to not procrastinate. Too bad the license policy keeps me from putting the patches up for download: ) I have them all the way back to nt 4

      l8,
      AC

    14. Re:Next Week.. by yomamasbooty · · Score: 1, Informative

      "Presto, instant DOS against your own network. Fun for the whole family!"

      Actually this is not what would happen if you use the loopback.

      The host spoofs a source address and sends it to its own loopback. This part is not seen on the network with a sniffer (obviously). What is seen though is a RST sent to the spoofed source. There is a chance the spoofed source is a real host on your network, but receiveing a RST for an unestablished connection periodically will not DoS it. The other thing to remember is the RST will have a source address of 127.x.x.x, which will be dropped by any router before it leaves your local segment.

      Seeing a lot of RSTs on a segment is a lot less worse (harmless?) than directed SYNs. However the best solution is the null value for DNS queries. This keeps the SYN flood function in the worm from ever kicking off. Then download the M$ tool : KB823980Scan.exe and scan for unpatched machines. Then re-evaluate and redefine the duties of a sysadmin (ie patch management) as well as where you want to use M$ products.

    15. Re:Next Week.. by Stephen+Samuel · · Score: 1
      Actually pointing the DNS to 127.x.x.x really doesn't do much. While it does point it back at itself, the SYN flood isn't strong enough to take itself out.

      Precisely. causing the worm to start a SYN flood against itself is not going to do anything, but it will still cause the worm to think that it has succeeded in it's mission. You don't want to take out the worm boxes (they're generally just innocents stupid enough to run MS software). Neutralizing the effect is enough.

      --
      Free Software: Like love, it grows best when given away.
    16. Re:Next Week.. by gclef · · Score: 4, Informative

      Because the worm spoofs traffic from it's local subnet to the windowsupdate address. What this means is that any infected machine would spoof traffic to itself from its local subnet, and then flood the local lan with RSTs, presuming it wasn't actually running a webserver, in which case it would flood the local lan with ACKs. Either way, bad.

      The worm doesn't sanity check the DNS result, though, so if the name doesn't exist, gethostbyname() returns -1, which translates to an IP of 255.255.255.255. The reports I'm reading say that the windows stack won't allow you to send traffic to that IP, so the machine will just drop it. (that could be wrong, though. We'll find out soon.)

    17. Re:Next Week.. by Anonymous Coward · · Score: 0

      "it will still cause the worm to think that it has succeeded in it's mission"

      There is no "think" part to this worm. It has two phases: infect, and flood. The infect part is always there. The flood part is only there if the local time is after the 16th. Once the flood starts, it does not abandone the infect piece. They both operate at the same time. The loopback option does not do enough. Myself and many others have tried it. That's why everyone was poisoning their internal DNS, and why MS removed the A record.

    18. Re:Next Week.. by RevRa · · Score: 3, Funny

      Overheard:

      Co-worker1: "I wonder what would happen if I pinged 255.255.255.255?"

      Co-worker2: "Don't do THAT! You'll ping the whole Internet!"

      hahah. :-)

      --
      - Kate
      "DNA is life. The rest is just translation."
    19. Re:Next Week.. by cravey · · Score: 1

      If an admin doesn't apply the patch through either laziness or idiocy, It seems to me that it would be a good thing if his own LAN DoSed itself. Please explain how it is 'bad'.

    20. Re:Next Week.. by lhand · · Score: 1

      Why not point it at whitehouse.gov, they're used to it.

    21. Re:Next Week.. by gujo-odori · · Score: 4, Insightful

      Let us not say that.

      The MSBlast worm delivers about a 16 kbps stream, so whether the zombie is sitting on a 56k dial, a 256k upstream DSL or cable connection, or has a T-1 or larger uplink doesn't really matter. DDOS zombies don't usually consume all of the available bandwidth, since doing so would be rather counterproductive to the goal of making a DDOS attack.

      If an average user, being mostly computer-illiterate but knowing that a reboot fixes most Windows problems for a while, finds that his/her computer can't connect to the Internet (the symptom of having all of your upstream bandwidth utilized), the most likely response will be a reboot. This lowers the effectiveness of the DDOS attack compared to a large number of zombies making the attack without their owners' knowledge, which allows them to continue uninterrupted.

      Numbers of attackers are the key to a highly successful DDOS attack, not using up all the bandwidth at the zombie's dispoal. MSBlast could take a lot more bandwidth and still be not noticed by broadband users, but the authors have clearly crafted it to work and not be noticed on machines with dial-up and other low-bandwidth connections (I saw a 32-workstation LAN in a third world country; there was a 64k uplink for the whole office; things like that aren't unusual in many parts of the world. The likelihood of those machines being uptodate on patches is very low, which makes them a good target for MSBlaster.

      My purpose for being there was to install a hardware firewall in front of their network, so they are far less likely to get infected, but there are many vulnerable machines like that out there with no protection. A good DDOS client can use them; one that consumes all available bandwidth can't.

    22. Re:Next Week.. by malfunct · · Score: 2, Funny

      I thought with microsofts great resources they would have funded an effort to change time. The could just never let clocks get to the 16th and the worm would be totally neutralized.

      --

      "You can now flame me, I am full of love,"

    23. Re:Next Week.. by 13Echo · · Score: 4, Informative

      Most Windows users will know that something is wrong when "svchost" constantly crashes, prompting for a reboot. The hits on port 135 cause it to bork out. My mom, who is quite "computer illiterate", knew that something was wrong, and called me about it. We corrected the problem by upgrading her virus definitions (which were only a week out of date), and installed ZoneAlarm Free on her machine to stealth the ports from now on.

      GRISoft's AVG Antivirus, and ZoneAlarm, are two great and free tools that can fix and prevent these things.

      AVG Anti-Virus
      Zone Alarm

      A year or two ago, I wouldn't have thought that firewalls were so essential for dial-up users. Now, it's important for all users to have them, regardless of the OS.

    24. Re:Next Week.. by Anonymous Coward · · Score: 1, Funny

      I for one am willing to donate 16kbs of my bandwidth to help take out windows update for a while. Everyone should, it'll be fun. This is what community is all about, working together and stuff. Where can I d/l my copy of blaster? I think I'll get right on it.

    25. Re:Next Week.. by blosphere · · Score: 1

      it would be very unentertaining to point it to 127.0.0.1...

      But, which company is really an enemy to microsoft hmm? I wonder if a NICE RR of Sun Microsystem's critical IP's would be in order?

      Lessee... somebody creates a DDOS that attacs to an A record I control... now who want's to get some DDOS?

    26. Re:Next Week.. by AngryRodent · · Score: 5, Informative

      Windows update is already massively load balanced across multiple server farms. They use both a DNS based load balancer (F5 3DNS) and local area load balancers (F5 BIGIP). The server farms are in a number of locations. Early, and not so early in the implementation of this, a number of people were concerned that Microsoft was attacking them because the 3-DNS's would create probes from each datacenter to the end-users system. I'm not sure if that is still being used. I have no knowledge of how they Akamized so quickly since I haven't been involved with this project in years. However, it should be pointed out that the BIG-IP's make Akamizing content a very simple matter. I'm not shilling for F5- I no longer own any of the stock, haven't been an employee for years, and I'm now just a reasonably-satisfied customer.

    27. Re:Next Week.. by nyseal · · Score: 2, Informative

      I'm not so sure. I have a dial-up and I got the worm IMMEDIATELY. It kept shutting down Windows to the point I couldn't even d/l the patch in time. I eventually found (through Symantec) where the worm was in the system and in the registry. Only then could I keep going long enough to install the patch and the anti-virus definition to fully remove it. It was really frustrating.

      --
      [SIG] Remember Mattel handheld games?
    28. Re:Next Week.. by Anonymous Coward · · Score: 0

      ATTN Microsoft:
      Call off your SCO dogs!
      Do it now, or this is just the beginning!

      hehehe

    29. Re:Next Week.. by Geek+of+Tech · · Score: 1
      Well lets see. The article says that windowsupdate doesn't always work. Says it told people that their computers had already been updated, when it obviously hadn't been.

      A few months back, I was one of the lucky ones. I updated my PC and found out all my network functionality quit. Oh joy, oh joy. This update caused me several hours of anger.

      The truth of it is, we must choose the lesser of two evils.
      a) Update the box possibly letting terrors in.
      b) Don't update the box possibly letting terrors in.

      A catch 22, eh?

      --
      Stop the Slashdot effect! Don't read the articles!
    30. Re:Next Week.. by Anonymous Coward · · Score: 0

      I prefer Agnitum Outpost free, Kerio Personal Firewall is.. okay. But Outpost is much easier.

      You can set more advanced things in their free versions, such as allowing/disallowing certain ports for programs, not just allowing for all.

      Still, even ZoneAlarm is good.

    31. Re:Next Week.. by yanestra · · Score: 1
      secured permanently? So they unplugged it from the network to finally get that C2 security level eh?

      This was the way to secure NT. With 2K and XP, additionally you need to turn off power.

    32. Re:Next Week.. by Avakado · · Score: 1

      A year or two ago, I wouldn't have thought that firewalls were so essential for dial-up users. Now, it's important for all users to have them, regardless of the OS.

      On my dad's computer, I made sure no daemon listens to the ippp0 interface, except sshd. I want to be able to ssh into it, so I'm not going to block that port. Why does he need a firewall again?

      --
      The world will end in 5 minutes. Please log out.
    33. Re:Next Week.. by Anonymous Coward · · Score: 0

      It's a good idea to have a firewall to stealth most of the common ports. So, keep 23 open. Malicious attackers will likely have less of a chance of even knowing that there is a computer there, if you close of the ports with a firewall.

    34. Re:Next Week.. by gclef · · Score: 1

      You have clearly never been in charge of a few thousand machines. When you're dealing with that many machines, no matter how much of a BOFH you are, some will slip through the cracks. In those situations, any little thing that will keep that one wacky machine in the corner from taking down an entire division is a good thing. And don't even get me started on machines that you can't patch because some lame third-party vendor has no regression-testing plan, and won't support patched systems.

    35. Re:Next Week.. by MickLinux · · Score: 1

      What is the spoofing source? Is it possible that the spoofing source results in bounces that flood the site of a little-known Michigan site, possibly one belonging to a power company relay station along the 1500-MW lines from Toronto to Detroit?

      Do you see what I'm getting at here?

      --
      Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
    36. Re:Next Week.. by Rob+Seace · · Score: 1

      > so if the name doesn't exist, gethostbyname()
      > returns -1, which translates to an IP of
      > 255.255.255.255.

      Actually, gethostbyname() will return NULL on failure, since it's returning a pointer to a "struct hostent"... Perhaps you meant inet_addr(), which definitely has the problem you're refering to, where its failure return (-1) can't be distinguished from the legit limited broadcast address (255.255.255.255)...

    37. Re:Next Week.. by Oshkoshjohn · · Score: 1

      The IS people who failed to update their employer's computer's operating systems to protect them from the virus should be sacked. The people who failed to sack them should be sacked too! The moose is okay...leave the moose alone.

      --
      Goddamned kids! Get off my lawn!
    38. Re:Next Week.. by Dave2+Wickham · · Score: 1

      To allow only you to connect w/ SSH, maybe?

  2. Power outage related to Microsoft by Interesting+Username · · Score: 3, Funny

    It seems the power in one of the most populated areas of North America was out around the same time Micrsoft was making these fixes? Coincidence? I think not. For those of you in the power outage area, expect it to happen again tomorrow as the DoS is about to begin.

    1. Re:Power outage related to Microsoft by Ledskof · · Score: 1

      So how are you connecting the two exactly? Power plants running Windows, or firms somehow getting the worm and lots of high power consuming devices being triggered?

      --
      This is my sig. The post is over.
    2. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      So Microsoft shutting down a domain, knocked out the power?

      I dont get that one at all

    3. Re:Power outage related to Microsoft by mfivis · · Score: 2, Funny

      mmm, I believe it can be attributed to overload. Think about the sheer amount of Windows machines that were frozen and unable to turn off without hard Reset or power buttons, i.e. stupid new gen Dells and so forth.

    4. Re:Power outage related to Microsoft by RoLi · · Score: 3, Interesting
      Actually, there are rumors that safety systems that would have prevented such widespread failure were running on Windows and were down because of blaster.

      If those rumors are true, then the worm didn't cause the power failures, it just disabled the systems that would have prevented them. That this happened at around the same time is just a coincidence, - or maybe minor power failures happen frequently and were just prevented from spreading?

    5. Re:Power outage related to Microsoft by __past__ · · Score: 2, Interesting
      There is an article on heise.de (german) that basically claims that one of the power plants that went down belongs to a customer of a company specialized in DCOM/RPC-based technology, which could be an indication why some security systems failed (because they were busy rebooting).

      It's not too convincing, to be honest. It's just saying that there is a possible connection, and that the company running the plant didn't answer their questions yet. (Which is of course very suspicious, what could these people have better to do right now then answering to wild allegiations from a german IT magazine?)

    6. Re:Power outage related to Microsoft by Judg3 · · Score: 4, Interesting

      I don't think blaster caused the power outages or disabled the systems - have you read about the state of the US powergrid as a whole? It's horrendous!
      I was watching the discovery channel (or History channel, one of those) and they talked about that large blackout that occured back in NYC in 1977.

      The power grid protection system itself is what caused the black out. One substation sees it's getting a huge surge of excess power, can't handle it, and shuts down. This passes this huge surge to the next station, which also shuts itself down to protect itself. It's a huge chain reaction of power surge seen my a substation, substation shuts down to protect itself, surge passes on to next station, etc etc.

      The show was about terrorism in the US and how unprotected we are - and it really gets you thinking. If some jackass in Ottawa can plug in their hairblower and toast the power to seberal major metropolitan areas, imagine what a well thought out organized terrorist could do.
      Personally, I think we should some new nuclear power plants. 66 reactors provide 769 billion kWh, or about 20% of the total power produced in the US (2001 figures). These plants are old, the newest ones going all the way back to the early 80s, with no new orders for nuclear units since 77.
      The US is relying less on its hydroelectric, nuclear and coal plants and building more "peak use" and "daytime" generators, huge gas turbines that are only turned on when there's a peak demand or only on normal business hours, say 9-5.

      Why? It's not any more efficient, in fact these giant gas turbines tend to use more fuel then coal systems to produce nowhere near the same power. It's all about asthetics. No one wants a power plant near them, but everyone wants power. So they build these peak use and daytime plants - low output systems that take up almost no room and dont have the usual huge smoke stacks, etc your used to seeing with plants.

      I personally wish the US would update it's power infrastructure, and I'd be willing to pay for it. Retire old, inefficient nuclear plants and build new, more powerful, safer ones. Add in more redundancy into the network, more real-time failovers.
      They are modernizing it, don't get me wrong, but they aren't going at near the pace I'd like to see.

      (Probably kiss my karma goodbye now, oh well. The power grid is something no one cares about or wants to put money into unless something goes wrong - then we all conveinently forget about what happened when theres a bill up to repair and update it at the cost of a couple bucks a week in taxes)

      --
      Looking for hardware (Currently need: Large Etch-a-Sketch) Have one? See my journal!
    7. Re:Power outage related to Microsoft by spectecjr · · Score: 4, Insightful

      If those rumors are true, then the worm didn't cause the power failures, it just disabled the systems that would have prevented them. That this happened at around the same time is just a coincidence, - or maybe minor power failures happen frequently and were just prevented from spreading?

      Take it from someone who's soon-to-be-parents-in-law are up to their necks in the power + safety industry ... no, they don't run Windows.

      Control frontends and GUIs may run Windows. They may also run Java apps. The back-end is ALL Unix (and specifically NOT Linux), because there are very few OS vendors who will certify and indemnify the use of their OS in that kind of safety critical environment. Windows explicitly states that it's not for use in such an enviornment.

      Simon

      --
      Coming soon - pyrogyra
    8. Re:Power outage related to Microsoft by BigBir3d · · Score: 2, Informative

      Power grid in question is older that Microsoft is. I doubt it runs on Windows...

    9. Re:Power outage related to Microsoft by Cromac · · Score: 4, Funny
      I personally wish the US would update it's power infrastructure, and I'd be willing to pay for it.

      Just send that personal check for several hundred billion dollars to:

      U.S. Department of Energy
      1000 Independence Ave., SW
      Washington, DC 20585

    10. Re:Power outage related to Microsoft by FreeUser · · Score: 4, Funny

      Take it from someone who's soon-to-be-parents-in-law are up to their necks in the power + safety industry ... no, they don't run Windows.

      Control frontends and GUIs may run Windows. They may also run Java apps. The back-end is ALL Unix (and specifically NOT Linux), because there are very few OS vendors who will certify and indemnify the use of their OS in that kind of safety critical environment.


      Ah.

      SCO UNIX.

      No wonder.

      (*duck*)

      --
      The Future of Human Evolution: Autonomy
    11. Re:Power outage related to Microsoft by n1k0 · · Score: 1

      Oh yeah, I'm sure the power companies connect all of their safety systems to the Internet. :-) -Nick

    12. Re:Power outage related to Microsoft by harley_frog · · Score: 4, Funny
      I personally wish the US would update it's power infrastructure, and I'd be willing to pay for it. Retire old, inefficient nuclear plants and build new, more powerful, safer ones. Add in more redundancy into the network, more real-time failovers. They are modernizing it, don't get me wrong, but they aren't going at near the pace I'd like to see.

      Interestingly enough, Bush says that the nation's power grid needs to be updated, but doesn't know how or how much it will cost. Hmmm, I wonder if these means replacing the hampsters with ferrets?

      --
      It's all fun and games until someone loses the key to the handcuffs.
    13. Re:Power outage related to Microsoft by Poofat · · Score: 1

      The show was about terrorism in the US and how unprotected we are - and it really gets you thinking

      I think it shows quite the opposite, actually. Civillian power is out for a few days, who cares? Emergency power came on in hospitals and other critical places, the affected plants shut down just as they should, no one is panicking and looting. So the terrorists disable one powerplant. As long as it isn't nuclear we're just inconvienced. I will agree that we need to get more nuclear power plants up and running- technology is being developed that makes them safer, with the waste product being less hazardous

    14. Re:Power outage related to Microsoft by Cyclometh · · Score: 5, Insightful

      No need- end our little war in Iraq and we'll free up the funds needed. I read yesterday that the cost of the war in and occupation of Iraq will cost over $600 billion dollars.

      Just close up the operation a little early and divert those funds.

      Nah, never happen. Preemptive wars and years-long occupations of nations that are of dubious (at best) threat to US interests are more important than making sure your lights stay on.

    15. Re:Power outage related to Microsoft by Wingnut64 · · Score: 5, Funny

      "Is there any way this 'DoS' can be stopped?"
      "Impossibly, there's too many compromised machines. You'd need to turn off every computer on the East Coast..."

      --
      echo 'Header append X-HD-DVD "0x09f911029d74e35bd84156c5635688c0"' >> /etc/apache2/httpd.conf
    16. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      How about saving energy for a change?

    17. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0


      Did someone pull the string on your chest again?

    18. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      Blame the Democrats. Bush has been trynig to update it for 2 years and these liberal nutjobs won't let it get done because it might kill off the snail darter or some other worthless species that 99% of the people in the world have never of, will never see, don't care about it, and whose lives won't be impacted in any way by its absence.

    19. Re:Power outage related to Microsoft by mt2mb4me · · Score: 1

      you would be suprised, the thing is with the pollution updates needed, and everything else, most power plants themself have had to upgrade in mid 80's-early 90's now if the power grid is that big, do you really think that they rent lines to connect all of them together, or do you think that maybe they are using a vpn connection? or some other internet gate way. hey, it's been a while, but they have changed a lot since the 70's when they had the black out back then

    20. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      Well, just retire from Irak, let UN do his legitimate job, and you'll have enough fundings to turn on the light in NY (AH AH AH !! think how africa is laughing at you !!). Okay, sorry, this is because of Enron (AH AH AH !!! again).

      And, if you need more, just inforce your big compagnies pay taxes !!!

      But before that, you would have to refurbish your policital system : stop nepostism, stop corporate-funded politicians, and put some democraty in place (I mean, give the presidency to the one that actually got the more polls).

      Well, this should never happen in America today. You know, to mimic orwell, if you control the present, you control the future. I wouldn't like being american these days...

      Well, just one thing. We don't need this kind of america : learn how to turn the light on, and then maybe you'll be allowed to attend the UN and listen to other people.

      Please, stop pretend you can rule the world !!!

      AH AH AH !! I suggest other countries should alert the UN and put in place an emergency mission to provide you with candles.

    21. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      Yeah, I worked for a company that built SCADA systems. It's all UNIX. Only the machines used for pretty front-end graphics ran Windows.

    22. Re:Power outage related to Microsoft by usotsuki · · Score: 1

      Great. Just what we need, a DDOS attack on the power supply. >:[=

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    23. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      Yes.

    24. Re:Power outage related to Microsoft by reboot246 · · Score: 1

      Just send that personal check for several hundred billion dollars to:

      You wish.

      After administrative costs, several hundred billion would leave only $29.85 for your proposed update.

      --
      Head Guy In Charge U.S. Department of Energy

    25. Re:Power outage related to Microsoft by prepp · · Score: 1

      http://www.securityfocus.com/archive/1/333510/2003 -08-12/2003-08-18/0

      --
      "There is hopeful symbolism in the fact that flags do NOT wave in a Vacuum " --Arthur C Clarke
    26. Re:Power outage related to Microsoft by Jenolen · · Score: 0

      Or we could pass a collection plate around from city to city... Primarily those that lost power as they would be most likely to contribute.

      --
      Karma is like sex. I can't remember the last time I had either of them.
    27. Re:Power outage related to Microsoft by Lours · · Score: 1

      Civillian power is out for a few days, who cares? Emergency power came on in hospitals and other critical places

      What about the economic cost ?
      If a single DDOS attack shutting down a server for a few hours can cause millions of dollars of loss, then I certainly think that shutting down all electric equipments in one huge town such as NewYork is very likely to cause much more losses.
      Some companies will have generators, but I guess most won't.

    28. Re:Power outage related to Microsoft by nyseal · · Score: 1

      Will these redundant systems run Windows? Sorry; had to say it....no troll intended.

      --
      [SIG] Remember Mattel handheld games?
    29. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 1, Insightful
      The power grid protection system itself is what caused the black out. One substation sees it's getting a huge surge of excess power, can't handle it, and shuts down. This passes this huge surge to the next station, which also shuts itself down to protect itself. It's a huge chain reaction of power surge seen my a substation, substation shuts down to protect itself, surge passes on to next station, etc etc.

      I hope people realize that, since the power is indeed coming back on nearly everywhere, those systems did exactly what they were supposed to do: They protected transmission lines, generators, and switching stations from turning themselves into a flash of light, a puff of smoke, a big bang, and a small mountain of carbonized slag.

      The shutdown was a good thing, considering the alternative: Billions of dollars worth of damage to the power system.

      -- ac at home
      way to busy

    30. Re:Power outage related to Microsoft by trolman · · Score: 1

      Take it direct from someone that does application engineering in the industry. PLC controllers, servers, application tools, and workstations do run on Microsoft OS and have certification.

    31. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      I'd be the last to support the US invasion of Iraq -- but I do have to admit it makes good sense as energy policy. Certainly ensures that OPEC can't unilaterally raise the price of oil. Whether it was worth pissing off everyone else in the known world to go in on the pretext of WMD is another matter, of course...

    32. Re:Power outage related to Microsoft by Cyclometh · · Score: 1

      Hmm. Possibly true. However, I was referring to energy infrastructure, not supply. Still, it's a good point.

    33. Re:Power outage related to Microsoft by darien · · Score: 1

      Certainly ensures that OPEC can't unilaterally raise the price of oil.

      Only while the US is running Iraq. And that's extremely expensive, both in terms of dollars and in terms of exposure to terrorism and political reprisal.

    34. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      • The show was about terrorism in the US and how unprotected we are - and it really gets you thinking. If some jackass in Ottawa can plug in their hairblower and toast the power to seberal major metropolitan areas, imagine what a well thought out organized terrorist could do.

      Except that the "jackass" seems to have been from Cleveland...

    35. Re:Power outage related to Microsoft by Anonymous Coward · · Score: 0

      No QNX

  3. Loopback anyone? by Anonymous Coward · · Score: 2, Funny

    Microsoft should take a clue from User Friendly!
    We (a 30,000 student Midwest University) are currently thinking about making our DNS servers authoritive for windowsupdate.com and and pointing the A record bac k to loopback.

    1. Re:Loopback anyone? by szyzyg · · Score: 1

      This is a bad idea from what I hear, the worm throws worms out to the internet with spoofed source addresses. Which means the host will start sending responses back to all those spoofed addresses so you could find yourself with a network storm anyway.

    2. Re:Loopback anyone? by Anonymous Coward · · Score: 0

      That will lead to RST attack on your own n/w.
      Do not do it! Just let it go, windowsupdate.com is
      dead. There will be no dDOS. :(

    3. Re:Loopback anyone? by tzanger · · Score: 1

      um, no.

      If I am a.b.c.d and spoofing as w.x.y.z and I connect to 127.0.0.1, I'll hit myself every time. The packet isn't going out the ethernet interface at all, which is where your spoofing is taking place.

  4. What did they do? by Tirel · · Score: 3, Funny

    Did they point windowsupdate.com to 127.0.0.1 ? I hope not, there was a mail on FD explaining that such an action would cause it to DOS the local network.. Also, wtf is up with the site running lunix?

    1. Re:What did they do? by lucifuge31337 · · Score: 4, Informative

      Did they point windowsupdate.com to 127.0.0.1 ? I hope not, there was a mail on FD explaining that such an action would cause it to DOS the local network.. Also, wtf is up with the site running lunix?

      No, they took the A record out completely. It's not Akami-ized. That's the linux box you see.

      --
      Do not fold, spindle or mutilate.
    2. Re:What did they do? by Tirel · · Score: 5, Informative

      here it is:
      Date: Fri, 15 Aug 2003 08:33:57 +0200
      From: Carsten.Truckenbrodt@Bertelsmann.de
      Subject: AW: [Full-Disclosure] MS should point windowsupdate.com to 127.0.0.1
      To: full-disclosure@lists.netsys.com
      Cc: security@microsoft.com

      Hi,

      This might be a bad idea. If you let windowsupdate.com resolve to 127.0.0.1
      the following will happen: The worm uses spoofed IPs from the local /16
      subnet as source address. Pointing all the syn packets to 127.0.0.1 will
      generate a RST packet from the local host to the spoofed IPs and spread
      traffic over the complete internal network.
      Even blocking or routing the normally resolved IP to Null0 will be a lot
      work because this domain is loadbalanced through the world. That means you
      get a different resolution depending on your ISP or place in the world.

      If you manipulate your DNS, you should give no A-Record back to the worm.
      With this the worm will not start attacking anything. So setting up a
      nameserver zone with only a SOA record will do the job for Saturday 0:00.

      Best Regards,

      Carsten Truckenbrodt
      Arvato systems Taco Network SnotIing Security

      -----Ursprungliche Nachricht-----
      Von: Tobias Oetiker [mailto:oetiker@ee.ethz.ch]
      Gesendet: Freitag, 15. August 2003 00:15
      An: full-disclosure@lists.netsys.com
      Cc: security@microsoft.com
      Betreff: [Full-Disclosure] MS should point windowsupdate.com to 127.0.0.1

      Folks,

      How about MS standing up for the mess, and changing their own DNS to point
      all request for windowsupdate.com and whatnot to 127.0.01 ?

      This will null the effect of the syn flood very effectively. Only proxies
      will be affected.

      As far as I see it, they will not be able to use these names productively
      for the foreseeable future anyways ...

      So they will have to issue an update for windows-updater thourgh other
      channels (like their homepage for example) to point it to a different
      web-site .. that should not be all that much of a problem.

      If MS does NOT make this change to their DNS, I can see many routers who are
      trying to track connections toppling over in interesting ways.

      Because the local techs have no clue, it will
      take the affected companies ages to get back on the net.

      tobi

    3. Re:What did they do? by ceejayoz · · Score: 2, Funny

      Pity they don't know the virus writer's IP... heh...

    4. Re:What did they do? by PurpleFloyd · · Score: 1
      Why would they redirect it to 127.0.0.1? It would be easier to just wipe windowsupdate.com from the DNS servers, and leave the site up for a few weeks with a brief message saying "windowsupdate.com is now windowsupdate.microsoft.com, have a nice day," for people using a caching DNS server with stale records.

      As for 127.0.0.1 somehow DoSing a network, no! That's the local loopback, which never goes out onto the network card unless things are seriously screwed up. Even then, other hosts will immediately drop anything coming over the network from localhost; that's never supposed to happen and will be caught by sanity checks on the recieving end. As for DoSing the local machine, forget it. Even Pentium-class machines can easily generate and reply to massive numbers of localhost pings every second; denying webserver requests isn't much more trouble than replying to a ping.

      --

      That's it. I'm no longer part of Team Sanity.
    5. Re:What did they do? by Anonymous Coward · · Score: 0

      How much you want to bet Slashdot knows?

    6. Re:What did they do? by bhtooefr · · Score: 1

      But he's the original distibutor. Anyone thinking about putting a Win2K box on without MS03-026, and running a packet sniffer to grab IPs?

    7. Re:What did they do? by Anonymous Coward · · Score: 0

      well that was nice of you... posting their email addresses like that. now every /. troll and spammer has a few more valid addresses, and these people sound like they are important too... good job.

    8. Re:What did they do? by clarkcox3 · · Score: 1
      Yes, it's the local loopback, but if the trojan is using a spoofed address it can cause real traffic:
      1. Trojan connects to 127.0.0.1, using a spoofed address of 192.168.1.100 (yes, I know that's not a real routable address)
      2. Traffic doesn't leave the computer as it goes to 127.0.0.1
      3. However, when the local computer tries to reply, it does so using the spoofed address, and attempts to send it to 192.168.1.100, thereby generating traffic on the local network. (which in the case of a lot of colleges is the entire college network)
      4. multiply by thousands of students ... miniature, self-inflicted DDOS
      --
      There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
    9. Re:What did they do? by lucifuge31337 · · Score: 1

      It's not Akami-ized.

      Sorry...too much crack. Hopefully it was obvious that I meant is WAS Akami-ized.

      --
      Do not fold, spindle or mutilate.
    10. Re:What did they do? by InfiniteWisdom · · Score: 1

      Also, wtf is up with the site running lunix?
      They were obviously studying Linux's weaknesses.

    11. Re:What did they do? by golgotha007 · · Score: 5, Funny

      why would i want to help allievate the situation? hell, i get to have all my computers attack microsoft for free! and legally! wohoo! sick 'em!

    12. Re:What did they do? by dknj · · Score: 1

      and grab spoofed ip addresses?

      -dk

    13. Re:What did they do? by xanadu-xtroot.com · · Score: 3, Funny

      Anyone thinking about putting a Win2K box on without MS03-026, and running a packet sniffer to grab IPs?

      Sure I was thinking about that. Let's use YOUR network for it...

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    14. Re:What did they do? by bhtooefr · · Score: 1

      Grab the author's IP maybe...

    15. Re:What did they do? by Flunitrazepam · · Score: 1

      >Best Regards,
      >
      >Carsten Truckenbrodt
      >Arvato systems Taco Network SnotIing Security

      Nothing assures me of technical competence like Arvato Systems Taco Netowrk SNOTIING Security!

      --
      1) Your analysis is based on bad assumptions so your result is way off. 2) You're a sick bastard for fucking a horse.
    16. Re:What did they do? by Professor+Bluebird · · Score: 1

      Honeypot?

    17. Re:What did they do? by bhtooefr · · Score: 1

      I think it gets the rest of the worm from the author... it would need an IP address to work from...

    18. Re:What did they do? by BostonPilot · · Score: 1

      ditto :-)

    19. Re:What did they do? by Stephen+Samuel · · Score: 1
      Also, wtf is up with the site running lunix?

      Linux running IIS(!)... My guess is that they're using Linux for a firewall. (It's not like Microsoft would trust Windows to something like that.) It might even be an embeded box running Linux being used to protect/support their server farms.

      --
      Free Software: Like love, it grows best when given away.
    20. Re:What did they do? by Fly+Ricky+-+The+Wine · · Score: 2, Funny

      I know, I use a mac and I'm about to turn on my copy of virtual PC just to join in on the fun! Rock and roll. Take that for buying Connectix you bastards.

      Fly Ricky, the wine taster

    21. Re:What did they do? by zcat_NZ · · Score: 1

      I'm surprised nobody else has commented on this yet. (OK, I haven't read all 800-odd comments yet, but..)

      The worm attacks windowsupdate.com, which has always been simply a redirect to windowsupdate.microsoft.com and is even hosted on a completely unrelated /24

      The internal "Windows Update" menu option opens windowsupdate.microsoft.com directly. Shutting down the windowsupdate.com redirect (either through DoS attack or intentionally by Microsoft) won't make the slightest difference.

      --
      455fe10422ca29c4933f95052b792ab2
    22. Re:What did they do? by innate · · Score: 2, Interesting

      The Linux hit appears to come from an Akamai server, which is a distributed cache, under contract by Microsoft. You can bet the actual Windows Update servers are in fact running Windows.

      --
      No, I don't want to explore the Recycle Bin.
    23. Re:What did they do? by Anonymous Coward · · Score: 0

      No it is not a linux box! Damn, why does everyone keep saying that windowsupdate.microsoft.com is gone? It most certainly is not, I am connected right now, I jus scanned for new updates, and it worked. All this, at 12:24AM EST on Friday, the 16th.

    24. Re:What did they do? by lucifuge31337 · · Score: 1

      No it is not a linux box! Yes, it is AC. I'm not going to explain how Akami works to you, mostly because you can't even post under your own name, but also because based on your comment you are a waste of space.

      --
      Do not fold, spindle or mutilate.
    25. Re:What did they do? by Anonymous Coward · · Score: 0

      lunix is truly the superior operating system!

      tehy shoulds send all teh packits to teh modem house for sorteing!!1

    26. Re:What did they do? by josh+crawley · · Score: 1
      Nope. Just FYI, here's a little tidbit on how the virus is transferred (according to publicly available decompilations):
      1. Infected host sends exploit packet to IP address, which launches cmd shell and binds it to port 4444
      2. Worm sends command to this shell, using the TFTP.EXE utility available in NT, 2000, XP, and 2003 to connect back to the first infected host
      3. Worm listens for the callback on port 69, and has an extremely simple TFTP daemon built in to transfer its own executable to the new host (just starts firing packets of the binary)
      4. Worm sends command to remote shell to execute itself
      5. Lather, rinse, repeat.
      The only way to find the source would be to collect the file creation times from the virus executable on every infected computer, and look for the oldest one. Then, try to find out who infected that computer.
  5. I think the windows update botton on the taskbar.. by Squeezer · · Score: 4, Insightful

    always took you to http://windowsupdate.microsoft.com so whats the big deal about cancelling windowsupdate.com? do you think anyone will notice, or care for that matter?

    --
    Does the name Pavlov ring a bell?
  6. Not just WU... by angst7 · · Score: 3, Interesting

    but Microsoft was seen on Linux today also http://uptime.netcraft.com/up/graph/?host=www.micr osoft.com.

    Quoth Billy G: "Linux sucks, it's worthless, not usable for real . . . What? A worm? Aaaiiiieee! Tux Save Me!!!"

    ---
    Jedimom.com, that not-so-fresh feeling.

    --
    StrategyTalk.com, PC Game Forums
    1. Re:Not just WU... by BWJones · · Score: 1

      Now in all fairness it could be that they are simply testing it out. *snicker......snort.......guffaw!* Seriously though, it is not uncommon for lots of companies to have multiple platforms serving up their needs. For instance, Apple.com has in the past had their servers running a combination of Netscape, Solaris etc.... But given the success of OS X, they are moving wholesale over to their own product which says something about their faith in what they make. In fact, the Quicktime site and the iTMS are running OS X on Macintosh hardware. In the case of Microsoft, it appears they are either relying on Linux to get them through this little thing or they are experimenting with Linux. One does wonder what that says about their militant anti-linux stance though.

      --
      Visit Jonesblog and say hello.
    2. Re:Not just WU... by cameronsto · · Score: 0

      Wow this really is interesting. Microsoft.com running Linux. Oh wait, could it be that at the time their system was linux it was coming from Akamai and not Microsoft. There are systems out there that are used to relay traffic between users and the server, and Akamai just happens to be one of them.

      cameron

    3. Re:Not just WU... by Akuinnen · · Score: 1

      Linux AkamaiGHost 15-Aug-2003 213.161.82.37 Akama

      I used to work at Windows Update. Akamai is a seperate company that hosts some MS content. If I remember correctly some MS big shot has investments in it.

      Seems pretty smart that they would use a couple different OS's.

    4. Re:Not just WU... by ceejayoz · · Score: 1

      Uh, no - that's Akamai, which does load balancing for huge sites so the bandwidth is spread over a number of computers across the country. The servers that do the load balancing run Linux, but the actual Microsoft server was still running Windows behind that Linux box.

      That's why WindowsUpdate shows up as having used "AkamaiGHost" as their HTTP server, and why Microsoft.com shows IIS6 running on Linux with a netblock owned by a different company.

      MSNBC.com and Apple.com use Akamai for images and Quicktime movie trailers quite often.

      In summary: you blew your wad a little early trying to bash MS. Whoops!

    5. Re:Not just WU... by BurritoWarrior · · Score: 1

      Guys those are Akamai CACHING servers, not the actual servers from MS.

    6. Re:Not just WU... by terrymr · · Score: 1


      In summary: you blew your wad a little early trying to bash MS. Whoops!


      Not really .... They still using a service that runs on Linux to serve their website.

    7. Re:Not just WU... by willy134 · · Score: 1

      I wonder if this is what they payed SCO for??? Or if they didn't pay....

      --
      Can you ping me now?... Good!
    8. Re:Not just WU... by __aavhli5779 · · Score: 1

      Apple also uses Akamai for their online store.. While the store itself is WebObjects deployed on OS X Server, the images are hosted by Akamai's servers.

      When the G5 specs were accidentally leaked, suspicion for a while was that Akamai had been hacked because that's where the image was hosted.

    9. Re:Not just WU... by Foofoobar · · Score: 1

      Yep. Akamai runs on several windows.com servers as well using Linux. And the fact that they have to do load balancing for Microsoft on Linux machines speaks for itself I think.

      --
      This is my sig. There are many like it but this one is mine.
    10. Re:Not just WU... by shotfeel · · Score: 1

      If I remember correctly some MS big shot has investments in it.

      You may be right, but are you sure you're not thinking of Apple? http://www.apple.com/pr/library/1999/aug/18appleak amai.html

    11. Re:Not just WU... by shotfeel · · Score: 1

      you blew your wad a little early trying to bash MS

      Thanks for that oh-so-pleasant visual.

    12. Re:Not just WU... by Anonymous Coward · · Score: 0

      It just proves that for common commodity services, Linux is adequate. That's well known, and Microsoft won't deny it.

      That doesn't mean Linux with Apache is a robust intranet workgroup server.

  7. Security is #1.... again? by Alan · · Score: 0, Interesting

    Wasn't this the subject of a famous memo about a year and a half ago, when they were spending 10 months doing nothing bug security? Good job guys. Interesting enough Scoble has some things to say about windows and security. Some good comments as well (both for and against). Of course, as he's an MS cheerleader you can't expect completely unbiased reporting.

    1. Re:Security is #1.... again? by micromoog · · Score: 4, Funny
      Wasn't this the subject of a famous memo about a year and a half ago, when they were spending 10 months doing nothing bug security?

      Oh, you mean this?

      Precisely nineteen months ago, Bill Gates sent out a memo to employees (and the press) announcing that security was Microsoft's number-one priority.

      It's the first line of the fucking story! For cryin' out loud, we know you're not going to read the fucking article, we don't really expect you to even read the whole story, but can't you at least fucking read the first line?!?!

    2. Re:Security is #1.... again? by Anonymous Coward · · Score: 0
      What was your first clue? The first sentence in the article?

      It reads something like this:
      Precisely nineteen months ago, Bill Gates sent out a memo to employees (and the press) announcing that security was Microsoft's number-one priority.
    3. Re:Security is #1.... again? by Anonymous Coward · · Score: 0

      I can see the mods with their itchy trigger-fingers waiting to shoot this guy down, but please think first. He's absolutely right. Go insightful if nothing else.

    4. Re:Security is #1.... again? by druske · · Score: 2, Funny

      Funny, it looks to me like Microsoft's security is #2... ;)

    5. Re:Security is #1.... again? by Anonymous Coward · · Score: 0

      Wasn't this the subject of a famous memo about a year and a half ago

      Well if you read the intro to the story, you'd see it was 19 months ago....

      when they were spending 10 months doing nothing bug security?

      Actually, it was only one month of a focus on nothing but security. No new features, just fixing security problems. That ended 18 months ago. Now they do both again.

    6. Re:Security is #1.... again? by leviramsey · · Score: 0, Troll

      Jesus Christ, you're an idiot. Read the fucking article (not the links, the Slashdot article). It's right there in the first line.

      I'd mod you down (I have the points), but I think it'd be better to point this out to any other mods so they can mod this bozo's post to -1.

    7. Re:Security is #1.... again? by anotherone · · Score: 1

      They fixed the 8 year old bug two months ago, before there were any exploits in the wild.

      --
      Username taken, please choose another one.
    8. Re:Security is #1.... again? by SillySlashdotName · · Score: 2, Funny

      I don't know, PISS POOR seems to describe it pretty well - and that would be #1 - unless you were going for shitty, which it is and is, therefore, indeed #2. :->

      --
      Acts of massive stupidity are almost never covered by warranty. --me.
    9. Re:Security is #1.... again? by Anonymous Coward · · Score: 0

      Public Relations and Customer Service is #1... cuz they like to piss all over their customers like RIAA-man.

    10. Re:Security is #1.... again? by anotherone · · Score: 1

      EDIT: the bug was 8 years old, but it was only found a few months ago.

      --
      Username taken, please choose another one.
    11. Re:Security is #1.... again? by PhxBlue · · Score: 3, Funny

      You're new here, aren't you?

      --
      !#@%*)anks for hanging up the phone, dear.
    12. Re:Security is #1.... again? by Hatta · · Score: 1

      Hey, he read the headline. Gotta give him credit for that.

      --
      Give me Classic Slashdot or give me death!
    13. Re:Security is #1.... again? by MyHair · · Score: 1

      Oh, you mean this?

      Excuse me, but I have a short attention span and couldn't read farther than that. Could you please email a point with more brevity?

      It's just that some people....hey, pretty lights!...brb

    14. Re:Security is #1.... again? by Overly+Critical+Guy · · Score: 0, Troll

      Yeah, that line never gets old, in every single article discussion.

      --
      "Sufferin' succotash."
    15. Re:Security is #1.... again? by PhxBlue · · Score: 2, Funny

      I dunno. I just saw someone else's signature line say it's a guaranteed +5 Funny, so I figured I'd do a one-shot experiment to see for myself. 'Course, it only got to +3, so I guess the guy wasn't right after all. :)

      --
      !#@%*)anks for hanging up the phone, dear.
  8. A moving target is still a target by bigberk · · Score: 2, Insightful

    This is kind of interesting: Microsoft's insecure Windows platforms is the breeding ground of massively distributed worms, which are designed to attack Microsoft's own servers (karma?)

    While Microsoft thinks the "solution" is to move the target server, the real solution is to fix those gaping holes in their products.

    1. Re:A moving target is still a target by ebh · · Score: 5, Insightful
      Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID fix the problem.

      This is not like those stupid email trojans that are inexcusable because Microsoft intentionally opened the door (with scriptable email, etc.). This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux.

    2. Re:A moving target is still a target by Anonymous Coward · · Score: 0

      You obviously don't know Microsoft that well. Quick fix buddy, that's the way to go.

    3. Re:A moving target is still a target by Overly+Critical+Guy · · Score: 0

      fix those gaping holes in their products.

      They did. Now it's the fault of users who didn't patch their machines and let the big pretty Automatic Updates icon at least let them know there were critical updates to install.

      --
      "Sufferin' succotash."
    4. Re:A moving target is still a target by crawling_chaos · · Score: 2, Interesting
      While Microsoft thinks the "solution" is to move the target server, the real solution is to fix those gaping holes in their products.

      I don't like MS either, but this is blatantly unfair. MS did fix the gaping hole -- last month. The problem is that their customers didn't implement the fix, so they are taking reasonable precautions to avoid damage. Beat them up for the things for which they deserve, but not this.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    5. Re:A moving target is still a target by RLW · · Score: 3, Funny

      M$FT doesn't have time to fix bugs. These problems are an annoyance and only after they have been taken to task time and time and time again - they have finally decided to do something about it. They have been rushing software out the door for so long that they don't know how to perform genuine quality control. M$FT is not a software company that makes money so much as it is a company that makes money by making software. Well, buying up other's software slapping on some lip stick and then putting it out as their own.

      Bill Gates: "Leave us alone so we can innovate"
      User: "You keep using that word. I do not think it means what you think it means."

    6. Re:A moving target is still a target by blincoln · · Score: 4, Interesting

      This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux.

      Active Directory also provides a way to block this type of worm that *ix doesn't. There wasn't time to patch all of our servers during the outbreak, so one of the guys here implemented a group policy that prevents execution of msblast.exe and teekids.exe on any machine on our network. Once they're all patched, the policy can be removed really easily.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    7. Re:A moving target is still a target by WindBourne · · Score: 1

      The problem was that the fix was buggy, so no, they did not fix it. They just offered up a false sense of security.
      And that was with a focus on security.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    8. Re:A moving target is still a target by Billy+the+Mountain · · Score: 1

      No, they didn't fix the problem, they offered a solution that few people bothered to install. Truly fixing the problem? Theraputic worm! This would involve modifying the Blaster worm to contain a patch payload. Yeah, you get hit with a virus and the network slows down for a while, but the problem is solved for the future.

      BTM

      --
      That was the turning point of my life--I went from negative zero to positive zero.
    9. Re:A moving target is still a target by rhizome · · Score: 1

      You are betraying your lack of article-reading fu. Making a patch available to people who are installing it via WindowsUpdate is a problem only because WindowsUpdate could falsely report that it installed the patch when it really only added the registry key that says it's installed. Without downloading the files at all.

      --
      When I was a kid, we only had one Darth.
    10. Re:A moving target is still a target by killmenow · · Score: 1

      Yeah, but you're all gonna be hurting when they run penis32.exe

    11. Re:A moving target is still a target by Nothinman · · Score: 3, Insightful

      Too bad the target audience of this worm doesn't have an AD to help them.

    12. Re:A moving target is still a target by Anonymous Coward · · Score: 0

      Which does absolutely nothing to actually secure your machines.. but who cares about that?

    13. Re:A moving target is still a target by molarmass192 · · Score: 1

      I beg to differ, *nix certainly does provide similar functionality via restricted shells (rbash, rksh, etc) and NIS. Simply assign users to a restricted shell in their NIS profile and they'll be unable to run any programs not in their pre-assigned PATH.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    14. Re:A moving target is still a target by RollingThunder · · Score: 1

      Did they fix the problem, though, or just patch a symptom?

      It all depends what "the problem" is. If you think "the problem" is this one specific instance of bad programming, sure they fixed it. If you think "the problem" is their practices and system design that allowed this to happen in the first place, then no they didn't fix it.

    15. Re:A moving target is still a target by pjack76 · · Score: 1
      Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID fix the problem.

      Well, yes and no. It's amusing that microsoft's site went down last night. What's more amusing is that their phone system has been down all week.

      Even if you had patched all your systems, and you wanted to call tech support because, say, one of your boxes only got the registry key for the patch and you had no way of knowing that, tough luck, their support hotline is down because everyone's calling it.

      This is of course assuming you're paying them tens of thousands of dollars per year for a support contract.

      --

      Wow, a lucrative publishing contract! I don't have to be evil anymore. --Meteor

    16. Re:A moving target is still a target by MntlChaos · · Score: 0, Flamebait

      *ix does provide a way: run *ix instead of windoze

    17. Re:A moving target is still a target by RoLi · · Score: 2, Insightful
      Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID fix the problem.

      I think the original poster meant fixing it before shipping it.

      But as long as nobody complains about the wasted time downloading and patching the systems weekly, I guess Microsoft is fully correct when they use their customers as paying beta-testers.

    18. Re:A moving target is still a target by antiMStroll · · Score: 1
      This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux.

      I propose a moratorium on the "just as easily in Linux" shit until such time that it actually does happen with the same severity. Until then it means absolutely nothing.

    19. Re:A moving target is still a target by Keeper · · Score: 1

      That only helps if you've got processes being launched by an interactive user via the commandline... won't do squat against an app that launches a program on its own.

    20. Re:A moving target is still a target by blincoln · · Score: 1

      Simply assign users to a restricted shell in their NIS profile and they'll be unable to run any programs not in their pre-assigned PATH.

      That works at the user level, but is there a way to do it at the system level? The AD fix prevents the executable from running at all, even if no user is logged on.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    21. Re:A moving target is still a target by blincoln · · Score: 1

      but who cares about that?

      As I said, "Once they're all patched, the policy can be removed really easily."

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    22. Re:A moving target is still a target by love2hateMS · · Score: 1

      > Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID fix the problem Yes, but they did not put this update in the Windows Update most users use (Internet Explorer-Tools-Windows Update). It is asking alot of most Windows users to do the "easy" updates. If you don' t put this patch in there, forget it. It ain't gonna happen. You have to actually download the patch separately and install it by hand. I am honestly curious why they would decide NOT to put that patch in the automated updates...

    23. Re:A moving target is still a target by LurkerXXX · · Score: 1
      Actually, that's just a different part of Active Directory which can do that. Software Update Service (SUS).

      http://www.microsoft.com/windows2000/windowsupdate /sus/default.asp

      It can be used to automatically roll out those security updates to all machines on your domain (after you've tested each patch on your test box first of course).

    24. Re:A moving target is still a target by imnoteddy · · Score: 2, Insightful
      There wasn't time to patch all of our servers during the outbreak, so one of the guys here implemented a group policy that prevents execution of msblast.exe and teekids.exe on any machine on our network.

      There was time to patch before the outbreak and there have been advisories for weeks that the worm was coming. This guy would have been smarter to apply the patches in the first place.

      --
      No electrons were harmed creating this post, though some may have been subjected to electrical and/or magnetic fields.
    25. Re:A moving target is still a target by vsprintf · · Score: 1

      Hah! Those are just cheap shots at Microsoft. If you'd read any of the Microsoft EULAs or service agreements, you'd know that end user is responsible for everything, and nothing is promised. Waiting for weeks for a response from Microsoft support is nothing new at all. So there.

      Linux is still worse than Windows. Like Microsoft has pointed out before, if you run Linux, you can't depend on any support for the product . . . oh, wait . . . nevermind.

    26. Re:A moving target is still a target by Anonymous Coward · · Score: 1, Insightful
      one of the guys here implemented a group policy that prevents execution of msblast.exe and teekids.exe on any machine on our network.

      Note to self: If I ever decide to write a worm, code it to generate a random filename for each new infection.

    27. Re:A moving target is still a target by danheskett · · Score: 1

      This is of course assuming you're paying them tens of thousands of dollars per year for a support contract.

      Liar liar.

      Phone calls are paid per-incident, or in groups. Its something like $245 an incident or something.

      Calls related to security are free.

      Its overwhelmed because of that, I am sure.

    28. Re:A moving target is still a target by molarmass192 · · Score: 1

      Granted but if you're throwing user into a GUI like KDE you can spawn KDE in lockdown mode and maintain the same level of restriction. However, this still won't prevent non-KDE compliant apps from launching programs. If one of your "approved" apps in a restricted session can be used to fork a program and your user has execute privs on a writable directory, then by definition, it's gonna be possible to run the file. Likewise, if I rename msblast32.exe to runitbaby.exe, it's gonna be possible to run it on Win as well. Neither the original AD solution or the *NIX example are 100% idiot proof but both will prevent the "auto" running of the worm.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    29. Re:A moving target is still a target by EnVisiCrypt · · Score: 2, Informative

      That is a bad idea. Not only does it not account for polymorphism in the name, but is also not foolproof.

      For instance, block an image name, then set your Internet Explorer home page to that image. Bam. It executes with no problems. As long as a trusted program executes it, Windows will not complain. The group policy only prevents the user from running it directly.

      --


      *everything* is Orwellian to cats.
    30. Re:A moving target is still a target by pjack76 · · Score: 1
      Phone calls are paid per-incident, or in groups. Its something like $245 an incident or something.

      Microsoft offers a Premier level of support, which is not paid per incident. I was led to believe by microsoft's site that the 1-800-936-3200 number is specifically for Premier customers. I can't confirm that since it's been down all week.

      --

      Wow, a lucrative publishing contract! I don't have to be evil anymore. --Meteor

    31. Re:A moving target is still a target by vsprintf · · Score: 1

      I don't like MS either, but this is blatantly unfair. MS did fix the gaping hole -- last month. The problem is that their customers didn't implement the fix, so they are taking reasonable precautions to avoid damage. Beat them up for the things for which they deserve, but not this.

      I can almost agree with your point. Kudos to MS, they took less than six months to patch this one. However, they are peddling their product (as a secure product) to people who do not even understand what security updates are. Even companies that understand security cannot apply MS patches in a short time period because those patches often hose the entire network. With each iteration, MS claims to offer ever greater security through obscurity, and every claim is shot down, resulting in ever-increasing problems. The worst part is that MS's shortcomings don't just affect their clueless customers, everyone is affected. Sorry, I think MS deserves the flak.

    32. Re:A moving target is still a target by Anonymous Coward · · Score: 0

      http://news.zdnet.co.uk/0,39020330,39115732,00.htm
      Perhaps you missed the news.
      The updates were bad due to mistakes in the updaters, basically bad MS code that was found AFTER the msblaster was infecting systems.
      So no, it was not always the direct fault of the users

    33. Re:A moving target is still a target by Keeper · · Score: 1

      Same problem if you're in a GUI. The problem is that the process is launched by another kernel level process (or whatever the RPC process runs under).

      It just so happens that the OS level "launch" type functionality can restrict what executables launch in windows, whereas in the unix world you have to depend on apps sitting on top of that to control that process.

      For an exploit of this type, MS's implementation works to the admin's advantage, where the unix implementations wouldn't have.

      In any event, the only reason why it works is that the idiot who wrote the thing didn't devote much time to thinking out what he was trying to do in the first place...

    34. Re:A moving target is still a target by molarmass192 · · Score: 1

      If we stay in the line of how the msblaster exploit works and assume a similar situation on *nix then yeah, but the methodology is obviously totally different. The NIS r* trick works on the "in this shell you can only run these" principal while the AD trick works on the "on this system you can't run these". The r* approach would not prevent forked non-r* execution shells from running the worm. I'm certainly not insinuating that NIS and r* are a replacement for AD, it isn't, but in this very specific case, it would provide a similar benefit.

      --

      Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
    35. Re:A moving target is still a target by Anonymous Coward · · Score: 0

      The wasted time downloading and patching the systems weekly is not a problem unique to Microsoft. In fact, since there's really no central authority to look to, it could easily be said that significantly more time is needed to keep up with the problems, download, and patch Linux systems. And Linux is perpetually a beta-level project.

    36. Re:A moving target is still a target by Stephen+Samuel · · Score: 1
      Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID fix the problem.

      Problem is, although they may have fixed the problem, lots of people didn't trust the fix. Microsoft updates have a bad reputation for sometimes making systems more unstable than not installing them. As a result, many a sane admin has learned to isolate updates until they have a chance to test them.

      Linux, on the other hand, is well-defined enough that most people really can trust their non-critical system to untested updates, and the need to test updates for critical systems is usually limited to the installation with wierd software that is specifically documented to only work with their own version of certain packages. Even then, users would still have access to the source code and the ability to (hire someone to) roll their own patches if they were desperate enough.

      If Microsoft updates had a reputation for rock-solid stability, this problem wouldn't be anywhere near as bad as it is.

      --
      Free Software: Like love, it grows best when given away.
    37. Re:A moving target is still a target by freeweed · · Score: 1

      This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux.

      Yeah, except that there are no network-accesible services running under any Linux distro that I've ever seen that would break the OS if you disabled them. There's also that whole 'default firewall' thing that you tend to see with modern Linux distros.

      Have fun trying a 'garden-variety buffer-overflow exploit' against my Linux machines over the Internet. I can guarantee you won't accomplish anything.

      --
      Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
    38. Re:A moving target is still a target by James+Cole · · Score: 1

      And Windows is perpetually an alpha-level product, and, to be added: you P A Y for it.

      In SusE Linux you do: Yast -> Online Update. *POOF*, there it is.

    39. Re:A moving target is still a target by Anonymous Coward · · Score: 0

      And if you had a clue you'd read he didn't have time to finish patching them all so he applied the group policy until he was complete.

      It's a great idea really. We added a group policy to install the patch when users logged in instead. Worked like a charm except for the idiots who clicked cancel.

    40. Re:A moving target is still a target by caouchouc · · Score: 1

      Actually, this isn't entirely true. There's a design flaw in Windows Update that led to numerous people believing they were patched when in fact they were not.

      Windows Update checks registry keys to see if you've applied a patch, rather than the files themselves. It's uncomfortably common to have a machine update the registry but for one reason or another fail to update the files. From that point on the user thinks they're protected and windowsupdate.com also tells them they are. That's one hole that still isn't fixed.

      Other users can't patch even if they want to because the patches can interfere with normal operations and must be thoroughly tested first. Fixes really shouldn't break the systems they're supposed to fix, but they can and do.

      Still more users just don't know enough to update regularly. These people are a menace to their neighbors on the net, but they've never been properly educated on the importance and the how of maintaining their security... and why would they? There's no incentive to tell them something that might drive to another platform.

    41. Re:A moving target is still a target by LordLucless · · Score: 1

      This is not like those stupid email trojans that are inexcusable because Microsoft intentionally opened the door (with scriptable email, etc.)

      I wouldn't say that. Yes, it was a buffer-overflow, but if MS hadn't set Windows up so that its RPC mechanism is running by default, when most home users wouldn't need it, and is open by default to the whole wide world (instead of just to the local network, which would be sensible), then we wouldn't be in this mess.

      Half of the services Windows XP has running by default are not necessary for the majority of users. Microsoft is ignoring one of the basic rules for security. Disable everything by default, enable what is needed.

      --
      Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
    42. Re:A moving target is still a target by mesmartyoudumb · · Score: 0

      Um, not to be a Microsoft apologist or anything, but at least in the case of MSBlast, they DID [microsoft.com] fix the problem.
      This is not like those stupid email trojans that are inexcusable because Microsoft intentionally opened the door (with scriptable email, etc.). This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux

      Theres a reason....because its ATTACKING THIER FUCKING NETWORK NOT USERS. :-)

      --
      "Comedy's a dead art form. Now tragedy, that's funny."
    43. Re:A moving target is still a target by crawling_chaos · · Score: 1
      Still more users just don't know enough to update regularly. These people are a menace to their neighbors on the net, but they've never been properly educated on the importance and the how of maintaining their security... and why would they? There's no incentive to tell them something that might drive to another platform.

      And those people would still not update if they were running Linux (or, more particuarly sendworm, er sendmail). I still fail to see how poor system management practices are the fault of anyone other than the system owner.

      That isn't to say that I hold Microsoft totally blameless. Eighteen months into a major security initiative seems a little long to find a bug of this importance, particularly in a service that can't be stopped or adequately firewalled on a local network. You'd think that those kinds of services would be the first to be audited.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    44. Re:A moving target is still a target by caouchouc · · Score: 1

      I don't recall saying anything about Linux, or any of its services. You simply assumed with that counter-example that I was insinuating Linux is a silver bullet compared to Windows. Quite frankly, I'm a little offended at that.

      I'm also not happy with Linux vendors that ship disributions with unneccessary services open by default, either. That's just awful for security in Linux distributions that are supposed to be "user-friendly", where the user may be new and has no idea what sendmail is, let alone that it's compromised on a regular basis.

      Users need to at least know it's important to patch and how to do it, otherwise it's useless to blame them because they couldn't have behaved any differently.

    45. Re:A moving target is still a target by EnVisiCrypt · · Score: 1

      My point is that it wouldn't work anyway. If the work exploits a buffer overflow in the RPC service, that hack isn't going to work. Period. If the program is executed by a program that is allowed to run, it's not going to work.

      It's not a good idea, and there are better ways to handle it.

      --


      *everything* is Orwellian to cats.
  9. microsoft.com also ... by bigjocker · · Score: 0, Flamebait

    Microsoft.com also pointed to a linux machine

    jejeje ... reminds me of the whole hotmail DNS thing a few years back (my favorite slashdot story ever):

    Merry christmas Microsoft, from the Linux comunity to you ...

    --
    Life isn't like a box of chocolates. It's more like a jar of jalapenos. What you do today, might burn your ass tomorrow.
    1. Re:microsoft.com also ... by cameronsto · · Score: 0

      If you actually look into this further, microsoft.com pointed to a linux machine that was actually an Akamai server. cameron

  10. Security by obscurity. by grub · · Score: 3, Insightful


    Change the update machines, new names, etc etc. MS is resorting to smoke and mirror tricks. It will only fool the current worms, not future ones that will have the new machine names in them.

    --
    Trolling is a art,
    1. Re: Security by obscurity. by Black+Parrot · · Score: 1


      > Change the update machines, new names, etc etc. MS is resorting to smoke and mirror tricks. It will only fool the current worms, not future ones that will have the new machine names in them.

      The first of which will probably be released in the next half hour or so - if it hasn't been already.

      --
      Sheesh, evil *and* a jerk. -- Jade
    2. Re:Security by obscurity. by Bueller_007 · · Score: 1

      They're only doing it to protect themselves from the upcoming attack. They fully realize that future worm writers won't be able to figure out another server to attack.

    3. Re: Security by obscurity. by BrynM · · Score: 2, Interesting

      How hard would it be for a worm to do a google (or some other search engine) search for "microsoft windows update site:microsoft.com" and pick a target from the top results? I agree that MS is only forcing the worm writers to be smarter with their targets by shuffling things around. Eventually it will backfire. If they don't find a better solution, all of this "musical websites" shuffling could also make for some serious chaos as more people figure out how to write DOS worms and it becomes more of a common attack.

      --
      US Democracy:The best person for the job (among These pre-selected choices...)
    4. Re:Security by obscurity. by Pvt_Waldo · · Score: 1

      Parent post is troll/flame/overrated?

      As I understand it, they just shifted the load over to Akamai. That's not obscuring it or smoke and mirrors. Just shifting to a new host.

      Correct?

    5. Re:Security by obscurity. by HTH+NE1 · · Score: 1

      They're only doing it to protect themselves from the upcoming attack. They fully realize that future worm writers won't be able to figure out another server to attack.

      And holding up Akamai's Linux servers as a proverbial human shield for their own?

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
    6. Re:Security by obscurity. by Anonymous Coward · · Score: 0

      And holding up Akamai's Linux servers as a proverbial human shield for their own?

      Jeez, it's not like M$ snuck in and changed the dns entries without Akamai's knowledge. If Akamai didn't want to bear the brunt of it, I assume they just woulda just said "NO". But I assume that M$ is paying them a pretty penny for their troubles.

    7. Re:Security by obscurity. by verbatim_verbose · · Score: 1

      Right, and MS is dumb to do this, because as every super-dup3r REAL expert knows, Linux is invulnerable to distributed denial-of-service attacks.

      Somehow I feel this comment wouldn't have been made if an open-source site made the same move, and under these circumstances, most of them would have.

      Insightful my ass. Maybe +5 Way to follow the l33t crowd.

    8. Re:Security by obscurity. by HTH+NE1 · · Score: 1

      Okay then, Akamai's Linux servers acting as paid bodyguards rather than human shields. Still doesn't say much for the robustness of Microsoft's ware.

      --
      Oh, say does that Star-Spangled Banner entwine / The myrtle of Venus with Bacchus's vine?
  11. ...in related news... by Guano_Jim · · Score: 2, Funny

    ...all HTTP requests to WindowsUpdate.com will be directed to goatse.cx.

    Some speculate that this will considerably improve Microsoft's customer service.

    1. Re:...in related news... by Anonymous Coward · · Score: 0

      talk about fixing a gaping hole

      *ducks*

    2. Re:...in related news... by Anonymous Coward · · Score: 0

      >all HTTP requests to WindowsUpdate.com will be directed to goatse.cx

      "Security by obscenity"

    3. Re:...in related news... by SpaceLifeForm · · Score: 0, Troll
      Not when they hear the voiceover:

      "This is your butt on Microsoft. Any questions?"

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
    4. Re:...in related news... by Anonymous Coward · · Score: 0

      ..."WindowsUpdate.com will be redirected to goatse.cx"...."update the DNS entry to 127.0.0.1"...

      How about the best of both worlds?
      http://goatse.cx/loopback.jpg

  12. Re:I think the windows update botton on the taskba by Xentax · · Score: 1

    Yeah, the shortcut on the Start Menu does at well.

    This isn't really a big deal, IMHO...

    Xentax

    --
    You shouldn't verb words.
  13. really... by freedommatters · · Score: 1
    does anyone still believe that microsoft can, or ever will, provide secure and safe software? i don't and i haven't done for many years.

    they just aren't aimed at that sort of market. they are aimed at selling as many boxes (ideally cd's without boxes) as possible. and that's what leads to the problems.

    the os's aimed at smaller but more important markets (finance, health etc) have much safer software.

    it's the fact that the majority of people run windows, with all the bugs it has, that causes the problems, especially now all those insecure systems are linked via the net.

    the solution? who knows, but for a start the governments of the world should heavily fine ms each time a serious bug is found and/or exploited. and people should examine, and demand, better alternatives.

    1. Re:really... by Eric+Ass+Raymond · · Score: 4, Insightful
      What makes you think that Linux is secure software? Or FreeBSD for that matter. I'd argue that OpenBSD is more secure but so is Trusted Solaris. Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days. This time you cannot even blame Microsoft for delaying the patch. It was all because of a fault in software and if you argue that the open source alternatives are immune to remote holes, you're deluding yourself.

      governments of the world should heavily fine ms each time a serious bug is found and/or exploited. and people should examine, and demand, better alternatives

      Would you prepared to submit the open source community to this same program? Every time a governmental Linux server is cracked, RedHat, SuSe or fundamentally FSF will have to pay.

    2. Re:really... by conan_albrecht · · Score: 4, Informative

      Unix is more secure for (at least) two reasons:

      1. Users don't run Unix as root. Viruses have a very hard time attacking programs they have no write permissions on.

      2. Unix has a much longer history than Windows NT+. It's had more time for the holes and buffer problems and other stuff to be fixed. Linux essentially "lengthens" its short history because it has so many eyes looking at it.

      3. The killer Unix programs (Apache, SSH, PostgreSQL, etc.) don't run as root either. So even if they get exploited, worms can't do much with their rights anyway.

      Unix is just built better. It has a longer history. I'll ceed that perhaps with a larger user base (pretend Unix has 90% market share) it would be a bigger target, but it is *not* as susceptible as Windows is. Not by a large margin.

    3. Re:really... by Mr.+No+Skills · · Score: 1, Interesting

      While not a fan of Microsoft, I don't think non-Microsoft products can claim 100% security either.

      I think the problem comes from two directions:

      1) A large majority of nodes on the Internet running the same software. And,
      2) The (generally) lower understanding of security issues on the part of the Microsoft users.

      I think "1" is a bigger issue. With 90% or so of all desktops running Microsoft, any security issue has the potential to exploit explosively. I would argue that things would be better if no single operating system had this kind of market penetration, regardless of the manufacturer. Then, if a security exploit is running around it has less of an impact on the Internet as a whole.

      "2" is a contributing factor. Given that more Microsoft users are (in general) non-IT professionals or non-sysadmin-aware (not a crack against Microsoft as much as an acknowledgement that most Microsoft users are end-users and not developer/server types), they are less likely to set up their systems correctly or to quickly apply patches when holes are found.

      So, I'd like to see larger penetration of alternative OS's just to dilute the strength of any Microsoft based security exploit.

      --
      Sleep is for the Weak
    4. Re:really... by Tirel · · Score: 1

      heh I wanted to mention how most linux distos don't ship full of enabled servers... then I remembered that they do.

      but seriously, you should have a working knowledge of networking before you connect *directly* to the internet. I mean fuck, even a dishwasher can be deadly if you don't know how to use it

    5. Re:really... by freedommatters · · Score: 1
      hmmm, where in my message did i mention linux? or freebsd?

      Would you prepared to submit the open source community to this same program? Every time a governmental Linux server is cracked, RedHat, SuSe or fundamentally FSF will have to

      that comment shows either a complete lack of understanding about the difference between microsoft as a company and windows as their product and linux as an open source product, or it shows you are a troll, which is it?

    6. Re:really... by Mr.+No+Skills · · Score: 1

      Another thought ---

      I don't think I'd be in favor of "governments of the world" coming down on bugs in software. I certainly can't say that I've never written a bug in my life.... I do wish people would spend more time looking at all the possible products, and not just what Best Buy has a pile of.

      --
      Sleep is for the Weak
    7. Re:really... by JWW · · Score: 3, Interesting

      The solution is easy, limit the fine to a maximum of the full amount paid for the software. ;-)

      And really that is the case, many billions of dollars were paid to Microsoft for defective software. When auto makers have a recall, they are required to fix the problem for you. With software you have to do it yourself, and if you don't its your fault. Then again if you do install the patch yourself and your machine breaks, its still your fault!

      Basically, expect to see no real improvement in Microsoft's software until someone has the guts to sue them or the government gets involved (ala auto recalls). Otherwise there is absolutely zero incentive for them to work any harder than they have to to sell you software.

    8. Re:really... by Eric+Ass+Raymond · · Score: 1
      Users don't run Unix as root. Viruses have a very hard time attacking programs they have no write permissions on.

      Have you run any serious Windows version lately? Hint: I'm not talking about 95, 98 or ME. By default, you don't log onto them as the Administrator. Yeah, you can give yourself those privileges. How is this different from Linux?

      Unix has a much longer history than Windows

      Are you kidding me. Are you seriously trying to say that Linux is Unix? Well, while we're at it, I'll say that Windows NT (on which W2K, WinXP and Windows 2003 are built) is VMS which can compete with your concept of the Unix family-tree quite comfortably.

      The killer Unix programs (Apache, SSH, PostgreSQL, etc.) don't run as root either. So even if they get exploited, worms can't do much with their rights anyway.

      This is an administrative problem. If Linux were as widespread as Windows, you'd see exactly the same dumbness.

    9. Re:really... by Tirel · · Score: 0, Troll


      3. The killer Unix programs (Apache, SSH, PostgreSQL, etc.) don't run as root either. So even if they get exploited, worms can't do much with their rights anyway.


      Yes, they do. the apache parent process runs as root, sshd *always* runs as root, and so does postgresql.

      Also your first doesn't apply because viruses go through something called EVOLUTION, if the primary OS were UNIX, we'd have a bunch of extremely intelligent and advanced stack smashing worms and viruses. (thank god we don't though.)

    10. Re:really... by Eric+Ass+Raymond · · Score: 1
      that comment shows either a complete lack of understanding about the difference between microsoft as a company and windows as their product and linux as an open source product

      Ok, entertain me.

      Does Microsoft, Sun, Redhat or any friggin software company promise in its contracts that the software is secure and it will be responsible for any damages? No.

      What's your point? The "speedy response" from the open source community? Don't make me laugh.

    11. Re:really... by The+Bungi · · Score: 0, Offtopic
      or it shows you are a troll, which is it?

      Translation: "I can't articulate an intelligent response to the point you made, so I'll just call you a 'troll' and see if it sticks with the mods."

    12. Re:really... by wasabii · · Score: 1

      So, what runs on port 135? RPC end point mapper? You can turn this off right? It's not turned on by default, right? :D A good linux/unix/whatever comes with absolutly no services enabled by default. Of course, this excludes most Linux distributions except for Debian and Gentoo. RedHat is just as bad as Windows, maybe even worse, unless you enable the firewall.

    13. Re:really... by conan_albrecht · · Score: 1

      You should really update your SSH daemon. For example, the Debian package installs only the root process as root. The socket-opening process is run as non-root.

    14. Re:really... by alcmena · · Score: 3, Informative

      I could be wrong, but I'm pretty sure that PostgreSQL complains very loudly when run as root, and instead prefers to be run in a separate account named "postgres". Likewise, my Apache was by default set to run in an account named "httpd". As for sshd, I dunno, you may well be right about that one.

      This is on RH 7.1, so it may have changed.

    15. Re:really... by Omnifarious · · Score: 1

      Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days.

      And, so the solution to this problem is to continue to go sheeplike to a single OS vendor because if we had a more even distribution of marketshare the network as a whole would be less vulnerable to attack. Explain to me again how this makes sense.

      The problem you talk about is monoculture, and the solution to that problem is still to drop Microsoft like a hot potato. Monocultures are bad. The solution is to stop using the same software everybody else does. As such, most people should stop using Microsoft software.

    16. Re:really... by conan_albrecht · · Score: 1
      Have you run any serious Windows version lately? Hint: I'm not talking about 95, 98 or ME. By default, you don't log onto them as the Administrator. Yeah, you can give yourself those privileges. How is this different from Linux?


      Perhaps you should try dragging your c:\windows directory to the trash on XP, then? I just tried it with /usr/bin, and it didn't do much.

    17. Re:really... by deaddrunk · · Score: 1

      If dishwashers were built like Windows, sales of washing up liquid would rocket.

      --
      Does a Christian soccer team even need a goalkeeper?
    18. Re:really... by Nogami_Saeko · · Score: 2, Insightful

      The obvious thing you are missing at this point is that most people have unix installed know what they're doing. Even with all it's recent GUI advances, unix is still a pain to setup and configure.

      Disagree? Give a brand new machine to your parents, or grandparents and get them to install unix. See what happens, and if you have any hair left after walking them through.

      Now, granted, a good unix installation can be very secure indeed. So can a good windows installation. I know how to configure my webserver (running on apache under windows), and it's never been hacked, and never will. I keep on top of security issues, watch bugtraq, regularly check for updates and patches, etc.

      The problem is regular users - just wait until "joe average" who wants to surf the web, look at Pr0n, and read his email installs unix. Maybe he'll be running as root "because it's easier". I'm sure lots of security problems will spring up.

      At the moment, I'd argue Unix has the old "security through obscurity" to some extent. As soon as everyone has a Unix/Linux desktop, the exploits will come out in full-force.

      N.

      --
      "Nothing strengthens authority so much as silence." - Charles de Gaulle
    19. Re:really... by pyros · · Score: 2, Insightful

      Saying that users don't run as administrator on windows is a fallacy. At every office I've ever worked in the first thing the IT department does when setting up a new user's machine is add them to the administrator group. On top of that, the service run as privileged users by default. It's possible to run windows without admin rights, but very rarely happens in practice. It's possible to run services as unprivileged users, but again it rare in practice. You also don't need to be administrator to open privileged ports on Windows like you do on *nix. Unix and Linux have the advantage that users and services run unprivileged by default.

    20. Re:really... by h3 · · Score: 1
      Yes, they do. the apache parent process runs as root, sshd *always* runs as root, and so does postgresql.

      Postgres does not run as root. Here's what happens if you try:

      "root" execution of the PostgreSQL server is not permitted.

      The server must be started under an unprivileged user id to prevent
      a possible system security compromise. See the documentation for
      more information on how to properly start the server.


      -h3
    21. Re:really... by GlassUser · · Score: 1

      The equivalent would be deleting %PPDATA% (usually "c:\Documents and Settings\%USERNAME%\Application Data"). It doesn't do much either.

    22. Re:really... by The+Bungi · · Score: 1
      That's stupidity as a result of acute ignorance. Adding normal users to the "Power users" group and then using policies to determine what tehy can do beyond their given auth level is the way that works. As of Windows 2000 there is no fucking need to have users be administrators, period.

      That 90% of the IT wizards out there can't figure this tiny part out is not Microsoft's fault. They already provide the tools to do it right.

      There are some cases (specifically developers) where you do need some modicum of admin permissions, but that can be worked around. Windows has a system-level service that works like su.

    23. Re:really... by pyros · · Score: 1

      no. Many packages are started as root so they can bind privileged ports, and then fork and switch to an unprivileged users. so you are left with a process bound to a privileged port without root privileges. If your serivces are running as root, then you either set it up that way yourself, or you are using a terrible distribution.

    24. Re:really... by op00to · · Score: 1

      Is XP pro "serious" to you? On my laptop (IBM T40), the initial user account created has administrator privs by default, and there's nothing warning you that this is a bad thing.

      How is this different from Linux?

      Linux distributions as a rule do not create a regular "user" account with administrator privs. XP Pro does. To get these privs on a normally configured unix box, you have to specifically type a command such as "su" or "sudo" to get these privs.

      Many Unix services will have large notes in their documentation stating the fact that the service should NOT be run as root. In fact, there are many services which complain if run as root. I have never seen anything on a Windows box telling me not to run Apache as Administrator.

      Finally, please show me how you arrived at the following statement:

      "If Linux were as widespread as Windows, you'd see exactly the same dumbness."

      How can you prove a claim like this? Are you claiming that when something becomes widespread, all of a sudden standards drop? I'd say Redhat Linux is pretty widespread. Yet, when I installed Apache on a freshly installed Redhat box, I see that Apache is running as Apache, not root. I didn't have to do anything, except put the CD in the drive and push OK a few times. I'm sure any Windows admin could handle this.

    25. Re:really... by Anonymous Coward · · Score: 0

      Unix is more secure, because secutity is a process, not a product, and it is easier to implement the process on unix than it is on windows.

      As an example: imagine there is a new security flaw on unix.

      On unix I can quickly see if I am vulnerable,
      eg my package manager will tell me what version of the software is installed, or I can check it myself from the command line. (eg /some/deamon --version)

      I can install the new version of the software quickly. My package manager will also confirm that the updates really have taken place.

      Unix software in more modular. I can be reasonably sure that upgrading a vulnrable version of ssh is not going to break my sendmail installation or relational database.

      Due to the scriptable nature of unix, it is just as simple to do my security updates on 1000 machines as it is on 1.

      On windows, not only is it difficult to find out if you are running vulernable software or not, but due to the "intergrated" nature of windows, you can never be sure that microsoft's new patch is not going to break some other vital service.

      Unix software may not be more secure per-se, but it is a damn sight easier to manage in the real world.

    26. Re:really... by pmz · · Score: 2, Insightful

      Unix is more secure for (at least) two reasons:

      I'd like to add:

      - UNIX is simple (yes, UNIX is simple).
      - UNIX is transparent (post-kernel bootstrapping is via shell scripts for god's sake--it don't get better than that).
      - UNIX is documented, bugs and all (thirty years of history plus POSIX ain't too shabby).
      - UNIX is modular (I can guarantee not everyone runs the same mail server, DNS server, or even window manager).
      - As a result, fixing UNIX is easy (all the system administrator has to do is admit "Oops, I was a real dumbass there" and either fix it or replace it (again, UNIX is modular, transparent, and documented)).

      A cracker could attack certain subsets of the UNIX realm, but diversity is on the side of the users, in this case. It isn't like 95% of UNIX users happened to leave RPC open to the Internet, or something like that.

    27. Re:really... by Eric+Ass+Raymond · · Score: 1
      And, so the solution to this problem is to continue to go sheeplike to a single OS vendor because if we had a more even distribution of marketshare the network as a whole would be less vulnerable to attack. Explain to me again how this makes sense.

      I'm not telling anyone to use any particular operating system or application. Hey, you can use whatever floats your boat because "there is no spoon" - there is no problem.

      I run Linux on my home server, because I prefer Samba over NFS or Microsoft's own aborted version of this protocol. I keep my files there, on a Linux server, but I access them over the net purely using a Windows XP Pro, Office and Microsoft Visuals (Fortran and C) because I find these more productive.

      On my Win computers I have Python and Perl installed and I even agree with your monoculture argument.

      As such, most people should stop using Microsoft software.

      Which brings me to the core of my posts. No, no, no. People should not stop using Microsoft software anymore than they should stop using free software, public domain software, shareware software, malware, spyware or any other kind of software. Telling people to stop using Microsoft software IS a call for a monoculture.

      Leave people alone. Let them choose their own tools. Yes, sometimes it sucks and is definitely suboptimal but it's their way.

    28. Re:really... by alernon · · Score: 1
      Disagree? Give a brand new machine to your parents, or grandparents and get them to install unix. See what happens, and if you have any hair left after walking them through.


      That's pretty funny, because actually I have given both my parents and my grandparents my old machines running Unix, and I've never had a big problem. ;)

    29. Re:really... by kilgortrout · · Score: 1
      Unix is just built better. It has a longer history. I'll ceed that perhaps with a larger user base (pretend Unix has 90% market share) it would be a bigger target, but it is *not* as susceptible as Windows is. Not by a large margin.
      I agree with most of what you said, but come to a different conclusion. Linux/unix may not be as susceptible, but it is susceptible enough IMHO. It's small comfort to be better than windows in this regard. It's like boasting about who's the world's tallest midget. There's a whole lot of security work remaining for both platforms.
    30. Re:really... by Some+Dumbass... · · Score: 2, Insightful

      Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days.

      I'm getting sick of hearing this particular bit of FUD.

      First of all, when a vulnerability of this calibre is found in Linux or in common Linux utilities (e.g. the ssh vulnerability) it _does_ get attacked, despite Linux's smaller marketshare. RedHat lpd anyone?

      Second, didn't the last big Windows worm only affect people running MS SQL? What is that, 1% of all Windows installs? So despite the small number of computers which would be affected by this worm, it was still written. Note that it also did a fair amount of damage (took down some root nameservers, I think), which is exactly why worm writers are targetting systems with smaller marketshare -- because "smaller" still means something in the realm of a million or so computers, which is more than enough to do some serious damage!

      Thus the argument that Linux's marketshare is the reason why it doesn't get attacked does not make sense. Systems with limited marketshare (like Linux) _do_ get attacked by worms, presumably because they can still do lots of damage.

      So why so few Linux worms? I suspect the reason why there have been fewer Linux worms is in the past few years is that there have been fewer vulnerabilities in Linux and common Linux utilities which were severe enough to allow a worm to spread. Linux has its share of security vulnerabilities, but there's a big difference between a bug which allows a user to, say, overwrite arbitrary files on a system, and one which allows them to execute code on the system without even logging in!

    31. Re:really... by Billnvd65 · · Score: 1
      I don't think that the market share is really the cause here. What I think is to blame is the extension of an extension of an extension of a really bad idea called the windows OS.

      Even if the "VARIOUS" *nix type OS's were holding 99% of the market, the point is the word VARIOUS. Each haveing slightly different bugs/vunerabilities. In example, let's Linux had 90% of Home User desktops. How many would be running Mandrake, SUSE, RedHat, etc? How many would be running Kmail, Evolution, Sylpheed, etc? How many would be running Opera, Mozilla, Netscape, etc?

      The uniqueness of the "VARIOUS" *nix installs and OS's is quite possibly the single largest strength. Assuming I have 500 fellow * nix users in my email address book, what percentage can any virus author hope to infect if he manages to sucker me into executing his nasty code on my Mandrake Box?

      Sure, I might know 100 fellow Mandrake users, but what percentage also use the Sylpheed client as I do? Then, what percentage of that group use the same vunerable version that I do?

      I think the diverse OS like Linux, BSD, etc is exactly what will stop the rampant malware outbreaks.

      That is, in my opinion, why no version of MS windows will ever be secure or immune. When you run a cookie cutter OS, you are vunerable to cookie cutter problems!!!!

    32. Re:really... by pyros · · Score: 1

      Gee, too bad I didn't do something silly like say "in practice" or "its possible to [do something intelligent in windows]". Oh wait, I did ... Guess I really am able to distinguish between how a system is capable of being configured and how it is usually configured. And you're mistaken about no need. Upon upgrading the drivers for my 802.11b card (a linksys), I needed to be an administrator to be able to configure the drivers to non-default settings. This persisted through several re-installs of the drivers and utilities, and a tech support call that went through 2 levels of support reps. I've also had trouble with CD burning (Nero) when not administrator.

    33. Re:really... by Eric+Ass+Raymond · · Score: 1
      Unix is more secure, because secutity is a process, not a product

      Ok. And, getting back my original claim, if *nix were as popular Windows is these days. Would its security still be a process and not a product. Forgive me for being cynical, but I think not.

    34. Re:really... by sootman · · Score: 1

      Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days.

      Yeah, the fact that *nix/apache powers over half of all websites (meaning, more than Win/IIS _and_everyone_else_combined_) has nothing to do with anything. Accept it: *nix is inherently a more secure design. Neither is perfect, and yes, I'd rather have a well-admin'ed Windows box than a non-patched *nix box, but the fact is, out of the box and/or with standard settings, *nix is more secure, period. I won't go into how and why, that's well covered in other replies and anywhere on the Net you care to look. Just wanted to make sure someone poked a hole in your "marketshare" theory.

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    35. Re:really... by antiMStroll · · Score: 1

      Maybe you haven't noticed just how many Linux and FreeBSD boxes there are on the internet. MS is a target because it's an easier box to break. Period.

    36. Re:really... by clarkcox3 · · Score: 1
      Disagree? Give a brand new machine to your parents, or grandparents and get them to install unix. See what happens, and if you have any hair left after walking them through

      Well, my parents had no problem installing MacOSX. *ducks*

      --
      There are no tiger attacks in my area and it's all because this rock I'm holding keeps the tigers away.
    37. Re:really... by Anonymous Coward · · Score: 0
      The equivalent would be deleting %PPDATA% (usually "c:\Documents and Settings\%USERNAME%\Application Data"). It doesn't do much either.

      Erm...no, no that wouldn't be similar to /usr/bin. /usr/bin is the place where quite a few programs get installed, usually utilities, so it is similar to c:\windows or c:\winnt.

    38. Re:really... by whitmer · · Score: 1
      What makes you think that Linux is secure software? Or FreeBSD for that matter. I'd argue that OpenBSD is more secure but so is Trusted Solaris. Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days.

      You maybe right with your last sentence, but isn't it very much fun to laugh your ass off for Microsoft embarrassing itself with these kinds of security issues. :)


      Redmond folks should keep their mouths shut about greatly improved security, when these kind of exploits and issues surface once in a while. I just can't remember any even distantly similar security vulnerability in Linux all alone, ever. Somebody might want to prove me wrong on this, I'm happy to become enlightened.

    39. Re:really... by El_Ge_Ex · · Score: 1

      1. Users don't run Unix as root. Viruses have a very hard time attacking programs they have no write permissions on.

      Assumed knowledge, you are assuming that Every user of Unix knows about user permissions and ever user of Windows does not.

      2. Unix has a much longer history than Windows NT+. It's had more time for the holes and buffer problems and other stuff to be fixed. Linux essentially "lengthens" its short history because it has so many eyes looking at it.

      Actually, history can work against Unix. Imagine having to repeatedly patch over time for new machines. It's the patches that cause problems. Plus, the technology used in Windows NT has been around for about 15 years. It's not exactly 'new'

      3. The killer Unix programs (Apache, SSH, PostgreSQL, etc.) don't run as root either. So even if they get exploited, worms can't do much with their rights anyway.

      They run on Windows too. :)

      In Windows they are called Services and can have specific permissions assigned to them.

      Unix is just built better.

      Really? Which one? When you decide that realize there are at least ten others, and some aren't going to be built too well. :)

      Now quit the 'Holier than Thou' rants. Unix's GUI sucks (any of them, Aqua doens't count as being for Unix, yet). Give Unix a GUI that can pass the Grandmother test, then come back to me on how 'high and mighty' Unix is.

      -B

    40. Re:really... by Eric+Ass+Raymond · · Score: 1
      Accept it: *nix is inherently a more secure design.

      That is questionable. More likely there is an advantage to the people who set up and maintain the system. I readily admit that *nix systems that are harder to set up attract perhaps more professional and dedicated people.

    41. Re:really... by Anonymous Coward · · Score: 0

      No - the difference is that with Open Source products, you can in principle audit them yourself to check for security problems. Not so with closed source software.

    42. Re:really... by Omnifarious · · Score: 1

      Which brings me to the core of my posts. No, no, no. People should not stop using Microsoft software anymore than they should stop using free software, public domain software, shareware software, malware, spyware or any other kind of software. Telling people to stop using Microsoft software IS a call for a monoculture.

      You're wrong.

      The greater the diversity of OSes out there, the less likely any particular attack like this will be able to affect all of them. Right now, increasing diversity means dropping Microsoft. Microsoft accounts for a larger percentage of computers on the net than any other OS. Most (not all) people should drop Microsoft.

      Pointing at people and laughing at them and saying it's their fault for using Microsoft is perfectly appropriate, because it is. The same as if most farmers use the exact same corn, and some disease came and wiped it all out, but left the holdout farmer's fields intact. The holdout farmers are perfectly justified in pointing at the others and laughing at how they all use the same corn, and all got wiped out. They shouldn't all have used the same corn. It's wrong.

    43. Re:really... by Anonymous Coward · · Score: 0

      As I posted many times here, comparing Windows security to Linux security is like having to watch the Cincinnati Bengals & Detroit Lions play football, and pre-season footbal at that.

      Another thing left out of the discussion: even if you were to be hit with a *nix virus while not as root, the virus could take out your home directory. Precisely the directory I'm most concerned about.

    44. Re:really... by pyros · · Score: 1

      whatever. RedHat's default firewall settings have in fact been too secure for most average users (I believe the default firewall settings prevented using samba with any other networked machines, for example) in the last few releases. Also, services haven't been widespread enabled in RedHat workstations installs for a while. If you're talking about sendmail specifically, the default firewall blocks incoming smtp connections, and I think the default settings (implemented by RedHat) don't allow relay.

    45. Re:really... by Eric+Ass+Raymond · · Score: 0, Troll
      Ah, I see.

      It's the newspeak for the new millennium. "Free software" means free software - with the limitations imposed by GPL - and the "multiculture of operating systems" means multiculture - as long as Microsoft software is not involved.

      Thanks for clearing that up.

    46. Re:really... by Politburo · · Score: 1

      If you want to play the "I've seen.." game, where I work, users are *not* administrators, and the IT department is very wary at giving admin rights out, to the point of frustration. At least XP lets you change your own resolution without rights.

    47. Re:really... by freedommatters · · Score: 1
      er, perhaps it shows you don't understand my point.

      microsoft develops windows (or as near as damnit, they may licence some small parts).

      they are responsible for windows. period.

      redhat and all the other linux distributors don't develop linux themselves. they may contribute to the final product but no one company is 100% responsible for the software.

      that's the difference.

      so now, i'll repeat. either he didn't understand the difference between microsoft and the linux resellers, or he is a troll.

      and again, i didn't even mention linux in my original post!

      look forward (ha) to your well thought out response.

    48. Re:really... by The+Bungi · · Score: 1
      Upon upgrading the drivers for my 802.11b card (a linksys), I needed to be an administrator

      Yeah, I hate it when I have to do /sbin/su to run modprobe or something. It just sucks.

      I've also had trouble with CD burning (Nero) when not administrator

      Windows software is notorious for requiring admin permissions when they are not really needed. Blame it on the vendor (though to be fair a lot of Microsoft products also require that. They are getting better - as of Office 2K you don't need admin rights to even install it).

    49. Re:really... by Poltras · · Score: 1

      Wait a minute... (Hop in discussion) When you install Windows XP, when creating the admin account, it tells you it shouldn't be the account you would use your computer with it. When you create a new account, it asks you weither it should be "normal" or "user with power" account. User with power aren't admin, before you flame. They can install and remove programs, but not install services and such. Services can be installed with privileges only if you are admin, etc etc etc. Funnily, you find some stuff in the security doc of Windows, cut/pasted from *x. When a software become widespread, all of a sudden many users drop standards. Each user you add to a system, each times your system becomes dumber. I personnaly find that for a software with that many code lines, the bugs and holes are still pretty low. I admit I respect Unix (BSD at home) for security, but Windows is not THAT far behind. You can't blame a system to be dumb when the ones using it are. I've updated my computer a month ago for the security hole, and magically I don't have any virus problem right now.

    50. Re:really... by PeteyG · · Score: 0, Offtopic

      Translation: "I can't articulate an intelligent response to the point you made, so I'll just call you a 'troll' and see if it sticks with the mods."

      A classic troll response, if I've ever heard one! Ha!

      Just kidding.

      --
      no thanks
    51. Re:really... by MSG · · Score: 1

      apache parent process runs as root

      The parent process doesn't handle user requests, so there's not much you can do to exploit it remotely.

      sshd *always* runs as root

      Authentication is handled by a highly audited, very small portion of the sshd. All encryption/decription, terminal emulation, port forwards, and everything else is handled by a separate thread that's running as a non-privileged user. Once again, the practice is to limit the activities of the privileged process.

      It's not even that Win32 platforms don't provide these capabilities. They do. Application authors just don't use them. Application vendors are largely responsible for the remote exploits in Win32 platforms. Microsoft themselves are the vendor for many of those applications, and share the responsibility for disregarding the security mechanisms provided by the Win32 platform.

      so does postgresql

      It's already been pointed out that you're wrong.

    52. Re:really... by Mybrid · · Score: 1

      Hi!
      Happy Friday! I'm not a security expert. However, I have read security articles and MS always pales in comparison to any Unix flavor.
      Remember the Cisco virus a couple of weeks ago? What OS do you think all the Cisco routers run? What percentage of market share does Cisco have? Imagine, a world where Cisco routers ran on Windows? How often do you hear of Cisco worms? If Cisco ran on Windows?
      Fact is, when companies want something reliable and secure Windows is not the first choice.

      Cheers!
      -Mybrid

    53. Re:really... by pij · · Score: 1

      When I got my cable 18 months ago, roughly half of the port scans were at common Unixish services, mainly ssh, 111, 515. The other half was mostly a search for open proxies/SOCKS and some famous backdoors. This is skewed, my provider blocks http, ftp, smtp, telnet and perhaps other ports (I suspect SMB services are now off too).
      Nowadays the overwhelming majority of port scans are directed at typical MS ports and windows trojans: 135, 57, 1433, 17300.
      There are certainly more Windows boxes online at any one point than Unixish systems, however, I still believe this shift has something to do with Windows being easier to hack, and Windows users generally being less prepared against attacks.

    54. Re:really... by Kombat · · Score: 3, Insightful

      "[Unix] is *not* as susceptible as Windows is. Not by a large margin."

      Oh really? I'd just like to point out that while this bug is *attacking* one of MS's sites, it won't successfully *break in*. It was a mere 2 days ago that a hacker successfully broke into GNU.org and compromised the crown jewel of the Linux community.

      So who's more secure again? Don't be so quick to jump to Unix's defense. A lot more exploits are publicised for Linux than for Windows.

      --
      Like woodworking? Build your own picture frames.
    55. Re:really... by Anonymous Coward · · Score: 0

      What are you talking about man, have you ever done a clean install of Windows XP? After it's done going through the setup routine, on first boot, it asks who will be using this computer, and have a large number of text fields where you put your username. These users ARE, by DEFAULT, in the computer administrator class. We're not talking about after you've got your shiny new XP install and you go into the Control Panel to enable the Guest account and add some other people from the household, we're talking about what Windows does without asking.

      Not that I mind one bit, it's a pain in the ass to run Windows as a non-administrator. You can't even access any DirectX resources unless you're an administrator (Go ahead, try to play a game that uses DirectX on a Limited account, you won't be able to). Besides, I'm usually not in Windows enough to care about the security risk, nevermind the A/V and firewall.

    56. Re:really... by Omnifarious · · Score: 1

      I didn't say nobody should use Microsoft software. Just fewer. When they have 20-30% market share, I'll be happy.

    57. Re:really... by harvardian · · Score: 1

      2. Unix has a much longer history than Windows NT+. It's had more time for the holes and buffer problems and other stuff to be fixed. Linux essentially "lengthens" its short history because it has so many eyes looking at it.
      ...
      Unix is just built better. It has a longer history. I'll ceed that perhaps with a larger user base (pretend Unix has 90% market share) it would be a bigger target, but it is *not* as susceptible as Windows is. Not by a large margin.


      I wouldn't be so quick to jump to this conclusion. Even though there's a huge community working on open source code, plenty of companies stake their survival on the quality of their code (Microsoft included).

      Check out this story, for example. Some company called Reasoning did a code audit on Apache and found a defect density of .53 defects per 1000 lines of code, compared to an average .51 defect density for commercial products. Now, this was a review of Apache and not the Linux kernel, of course, but there's clearly going to be a correlation. I also think any reasonable person would agree that Microsoft's defect density probably isn't very different from the commercial average. Despite what you may feel about them, they certainly have some of the most qualified software engineers working for them.

    58. Re:really... by Anonymous Coward · · Score: 0

      More reasons why security(*x | *bsd) > security(MS)

      4. Unix/Linux/BSD don't run user applications and middleware as part of the kernel, like MS does with IE.

      5. More MS installations means more targets for malcontent script kiddies, so there are more crackers messing with MS OS's.

      rant. All these OS's suck because of buffer overflows, because c is too bare metal and/or lazily developed to perform any sort of memory protection. Granted, sometimes you want the extra performance you get by not running memory protection and just trusting the application to get it right. However, most of the time it's not worth the pain and you will have to do the memory protection in the software ANYWAY so it would be nice to have the compiler do it for you (ada style). It would be really cool to have a compile flag that tells the C compiler, "look, I'm an idiot, prevent me from overruning my buffers, smashing the stack, or allocing memory like an incontinent rhino" vs "I'm 31337, I meant to do that, don't hold my hand". That way the programmer could chose between "protected and a bit slower" or "unprotected and faster".

    59. Re:really... by whoever57 · · Score: 1

      Have you run any serious Windows version lately? Hint: I'm not talking about 95, 98 or ME. By default, you don't log onto them as the Administrator. Yeah, you can give yourself those privileges

      Pretty much everyone has to give themselves administrator privileges, otherwise they can't use a CD burner (on Win2k and XP, but not NT).

      The default is pretty much irrelevent if the default is useless!

      OK, they could "run as", for the burner, but that still requires that they know the adminstrator password, so they can then "run as" anything, or change their own login to have admin privileges.

      In my opinion, without the concept of setuid or setgid file permissions, Windows security model is a joke!

      --
      The real "Libtards" are the Libertarians!
    60. Re:really... by AirRock · · Score: 1

      Does booting from a Knoppix CD count as installing?

    61. Re:really... by AirRock · · Score: 1

      Almost off topic, i'm not sure if windows passes my Grandmother's test.

    62. Re:really... by cygnusx · · Score: 1

      Most old software for Windows (esp. those designed for Win9x, which had no security model) needed admin-level permissions to run on NT. Today, to meet "certified for XP" logo guidelines you have to ensure that users/power users can use your software without needing the admin password.

      Since 2000, all MS apps I can think of run quite happily as root. The problem is with third-party software (e.g. Visual Cafe never quite worked for "Power User"-class users on Win2000), but even this is coming down because of the "certified for xp" program, which makes it really easy for QA teams to benchmark their apps against a MS-supplied best-practices template.

      Windows 2000 and later can be hardened and secured quite easily. Head over to TechNet and read some docs instead of cribbing.

    63. Re:really... by AirRock · · Score: 1

      I'm still waiting for Adobe and macromedia to port to Linux so i can drop Windows as well.

    64. Re:really... by AirRock · · Score: 1

      Another reason they dont use windows is they can't mold it to their specific needs like they can do with *Nix. I'm also lead to believe that royalties (or whatever they should be called) would be less expensive using *Nix than windows.

    65. Re:really... by zulux · · Score: 1



      Disagree? Give a brand new machine to your parents, or grandparents and get them to install unix. See what happens, and if you have any hair left after walking them through.


      Mandrake 9.1 (with built in office suite) requires less that 20% of the effort than WindowsXP and OfficeXP require.

      Mandrake:
      Partition
      Insall
      Optionally Configre Network if Not DHCP
      Create Password
      Reboot
      Update

      Windows:
      Partition
      Reboot
      Format
      Reboot
      Install
      Enter 20 chard of serial number
      Install
      Reboot
      Optionally Configure Network if not DHCP
      Windows Update
      Install MS Office
      Enter 10 chars of serial number
      Microsoft Office Update
      Register Windows
      Register Office XP

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    66. Re:really... by Paelon · · Score: 1

      Erm...no, no that wouldn't be similar to /usr/bin. /usr/bin is the place where quite a few programs get installed, usually utilities, so it is similar to c:\windows or c:\winnt.

      IMO it's more similar to "Program Files" than either "Application Data" or "WINNT".

    67. Re:really... by acidtripp101 · · Score: 1

      I'm going to have to disagree with some of your post.
      I'll admit that all the *nix I use (*BSD, gentoo, slackware) is a pain in the ass to install, but I also know that some installs are EASY (once, I installed Redhat... hated it, but it was easy as hell... and that was like 2 years ago)
      But as far as Mr Joe Average (the porn adict who runs in root because it's easier) goes... thats BS for one reason... xscreensaver. I'm not kidding here, screensavers are a fairly big part of computers now, and not being able to run xscreensaver would cause people not to run as root.
      In all honesty, that's the reason I NEVER (well... post install/testing) run XFree as root... I hate xscreensaver complaining. I know it's not good practice to run X as root EVER, but I still would sometimes if it weren't for xscreensaver.

      --
      Not Free(as in beer). Free(as in "I'm free to beat you over the head for being a dumbass")
    68. Re:really... by Christianfreak · · Score: 1

      By that logic Apache would be the most compromised web-server since it has the most installations, but we all know that IIS has far more problems than Apache with security.

      I don't know about fines and what not but I think that it's clear (or should be) that Microsoft doesn't try to make its products secure, that is unless it thinks it will sell more, because they have a monopoly on the desktop, users don't know that other things exist so they keep on using the same products, and making excuses about "that's just how computers are" etc.

      Whereas IBM, Sun, etc. and especially the Open Source community put quality first and you don't see the same problems.

      Would their be more problems if there were more users? Sure but I still don't think it would be near the same kind of issue.

    69. Re:really... by deranged+unix+nut · · Score: 1

      Saying that Unix Users don't run as root is funny.

      I have seen a number of VAR configured systems (Just go find any system running Autologue, a POS accounting system used in auto parts stores, lumber yards, and some other businesses) where all users were logged in as ROOT, including the dial-in guests, and the root account had no password.

      People in general want their computers to be easy to use and don't care about security until their system is trashed. Windows or Unix, it doesn't matter much when the users don't care about security.

    70. Re:really... by conan_albrecht · · Score: 1

      They were also using their own FSF-written FTP server which ran as root. Mainstream FTP servers (ProFTP anyone?) don't. Their FTP server is *not* the default server included in Red Hat, Mandrake, Debian, or any other distros I can think of.

      In fact, most secure machines turn off FTP anyway (most distributions turn it off by default at the install). The only reason (IMHO) to use FTP is for anonymous FTP access. For anything else, SCP is a much better option.

      However, I will agree with you that Unix is much more apt to get broken into than Windows because of its remote-shell nature. On Windows you worry about viruses; on Unix you worry about hackers.

    71. Re:really... by conan_albrecht · · Score: 1

      Granted. If we want to be picky on this, I'll rephrase to /sbin/ and /usr/sbin/ as compared to c:\windows and c:\winnt.

      Same principle applies, though. Except for exceptionally-well-run, non-default Windows machines I seen some advanced people run, you can easily write to c:\windows, c:\winnt, c:\program files, c:\...(insert anything else here). Any of the above and you're hosed. I cannot understand why MS leaves these directories writeable (by default) version after version after version.

      On Unix the *only* directory you have write access to is your home directory, which shouldn't contain programs--especially root-type programs.

    72. Re:really... by vsprintf · · Score: 1

      And really that is the case, many billions of dollars were paid to Microsoft for defective software. When auto makers have a recall, they are required to fix the problem for you. With software you have to do it yourself, and if you don't its your fault. Then again if you do install the patch yourself and your machine breaks, its still your fault!

      Whoa, there. You want companies that sell software to be liable for problems their software caused? Where is the logic in that? The Dept. of Homeland Security uses Windows. What are you, some kind of communist or cyber-terrorist? We've got your user ID. :)

    73. Re:really... by Sprinkels · · Score: 1

      Nero allows you while installing to create a local group with the priviliges needed to burn a cd. Members of this group do not need te be administrator.

      For some reason this is not done by default...

    74. Re:really... by SmallFurryCreature · · Score: 1

      You are forgetting that all the newbie light linuxes, lindows for one run as root by default. The biggest problem however seems to be with windows opening ports and services with them wich are not neccesary. I got XP as my game machine. Scanned it from my linux workstation and it had port 135 open. But a router is between it so it should be safe. Anyway why is the port open? I obviously don't need it since the router blocks it anyway. This is the only reason unix can be better. It is setup usually by paranoid admins or distrubtion creators. Remember on the web they ARE out to get you.

      --

      MMO Quests are like orgasms:

      You may solo them, I prefer them in a group.

    75. Re:really... by OdinHuntr · · Score: 1

      Sorry, no, that bug was a bug in the Linux kernel itself. Local root exploit. GNU's mistake is that they allow local shell access to all GNU developers - and there are many of those.

      Don't get me wrong, I love Linux, but this was a legitimate (and terrible) problem. Honestly, I was more upset at the idiot rookie 2.4 kernel maintainer who waited for months to get 2.4.21 out the door.

    76. Re:really... by Anonymous Coward · · Score: 0
      So who's more secure again? Don't be so quick to jump to Unix's defense. A lot more exploits are publicised for Linux than for Windows.

      Well, consider that "Linux" covers a much larger set of services and software than "Windows." Not to mention many different distrubtions that are going to have their own individual security issues in many case. For example, I'm on the Debian security mailing list and most of the alerts are for packages I have never even heard of much less have installed.

      -matthew

    77. Re:really... by Anonymous Coward · · Score: 0
      1. Erm...no, no that wouldn't be similar to /usr/bin. /usr/bin is the place where quite a few programs get installed, usually utilities, so it is similar to c:\windows or c:\winnt.

      IMO it's more similar to "Program Files" than either "Application Data" or "WINNT".

      IMNSHO :) /opt and /usr/local/bin are similar to "Program Files", /usr/bin is "Windows"/"Winnt", and any sbin directory is similar to any "system" directory under Windows. They don't map directly, and there can be arguments for specifics (example /etc/X11, /etc, /etc/init.d, ... compared to the registry, and many of the other Windows directories already mentioned).

    78. Re:really... by pjrc · · Score: 1
      Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies alike as Windows is these days

      Approximately 1/3 of all websites are hosted by IIS/Microsoft systems, yet the majority of defaced websites have been among the smaller portion hosted on Microsoft.

      As linux-based marketshare grows, I predict that this well established trend will continue.

    79. Re:really... by wasabii · · Score: 1

      Good. Any service that could ever potentially be connected to the network, and cause the sort of problems we witness today with MSBlast, must be blocked. There is simply no other way. Even if Samba is listening, there have been Samba exploits!

    80. Re:really... by Anonymous Coward · · Score: 0

      I have to call you on this remark. The Mac has been around as long or longer than Windows (if you consider the earlier stages of it). Microsoft is the target of all these virii because of unethical business practices throughout its history. Unix has been around forever, and how many Unix virii have you ever heard of? Ever seen the movie "Pirates of Silicon Valley"? The targeting of Microsoft is because of a comment Bill Gates made to Steve Jobs when it was discovered that Microsoft had ripped them off -- "You just don't get it, do you Steve? It's not about who has the best software. It's about who gets theirs out first!"

      Now, I am NOT a Mac user. IMHO, everything before OSX SUX. I don't like the proprietary hardware, I don't like anything about a Mac, except for the way the OS LOOKS. Macs crash just as frequently as Windows machines, but Apple is constantly working to actually fix the problem. They weren't able to do it the way they were headed, so they used Unix to fix the OS. I find that very admirable -- "We can't seem to get this environment as stable as we want it, so let's abandon ALL of the work we've done for the last 15 years and start with a base that DOES work." MicroCRAP could still learn a lot from Apple, but Billy can't seem to keep his hand out of everyones' cookie jars.

    81. Re:really... by caluml · · Score: 1

      I think the whole root-below-port 1024 is stupid. What is the point of it? Mabe have an /etc/reserved.ports file, with tcp/22, udp/53, tcp/53 in it, etc that users aren't allowed to bind to. But needing root access to **only** bind to a port 1024 is just silly.

    82. Re:really... by Anonymous Coward · · Score: 0

      OS X only proves his point -- In order to make things easy, it sets up the default user with "admin" and wheel privledges.

      If you haven't had any problems, count it as luck, because there's been many many holes in OS X which could have been exploited.

    83. Re:really... by Overly+Critical+Guy · · Score: 0

      What a ridiculous rant.

      It's complete, 100% common sense that if you were able to magically give Linux the 90+ percent marketshare that Windows has, it will suddenly come under HUGE fire, hackers will be flinging shit at it left and right, and no doubt dozens of holes will be discovered that nobody knows about because the system isn't as "beta-tested" as Windows is.

      Second, didn't the last big Windows worm only affect people running MS SQL? What is that, 1% of all Windows installs? So despite the small number of computers which would be affected by this worm, it was still written.

      The typical Slashbot strategy. Completely make up a number from thin air that you haven't even looked up--typically illogical (1%???)--and then proceed to base your argument on it as though it is true.

      Microsoft had two announced holes last month, while Linux had nine. But there is a massive anti-Microsoft bias here at Slashdot, and everything they do is evil and wrong. Linux flaws only get reported when they're very major ones, like the filesystem-corrupting "turkey" release of the kernel, or the recent FTP hacking incident that people have been making excuses left and right for.

      Considering the incredibly huge marketshare and usage that Windows has, it is surprisingly durable and secure, and not as crackworthy as people make it out to be. I wouldn't be surprised if Linux would suddenly buckle under such a load if suddenly given that much. In fact, the only *NIX I would trust would be BSD, just based on reputation, though that's not saying much.

      You can't say Linux is as secure, because Linux isn't being run in as many real-world scenarios as Windows is, so you just can't know, aside from yammering heresay and anecdotal evidence.

      --
      "Sufferin' succotash."
    84. Re:really... by Anonymous Coward · · Score: 0

      > Given the same marketshare as Windows, Linux would be just as much targetted by the black hats and script kiddies

      Long before it got the same marketshare it would attacked by Microsoft funded script kiddies, if it isn't already ;-)

      But the real reason that Linux and BSD is more naturally secure is that it isn't a monoculture. There are hundreds of subtly different implentations and anyone can recompile their own copy of Linux with different options and make a specifically targetted attack fail.

      A buffer overflow, for example, relies on putting code into specific addresses in the program. One byte out, one bit out, and it fails - probably just crashing the program.

      With Windows there are tens of millions of machines with absolutely identical code, bit perfect, in the target.

    85. Re:really... by Daath · · Score: 1

      True, both the apache and the sshd *parent* processes run as root, apache launches child processes (those that serve requests) as another user (apache or httpd).

      Same with sshd - it spawns a new process in the account name of the user that logs on.

      --
      Any technology distinguishable from magic, is insufficiently advanced.
    86. Re:really... by pyros · · Score: 1

      You misunderstood, or purposely quoted only enough to support your statement. After upgrading, in order to use the drivers/utilities (to get an association with the access point and have networking access through the card), I have to be in the administrator group.

    87. Re:really... by Daath · · Score: 1

      Actually, history can work against Unix. Imagine having to repeatedly patch over time for new machines. It's the patches that cause problems. Plus, the technology used in Windows NT has been around for about 15 years. It's not exactly 'new'

      Windows NT was built on VMS which is 23 years old if I'm not mistaken ;)

      --
      Any technology distinguishable from magic, is insufficiently advanced.
    88. Re:really... by caouchouc · · Score: 1

      It's to stop a regular user from, say, binding to port 110 and grabbing user passwords with a fake POP3 session if for any reason you need to reload or take down your pop3 server.

    89. Re:really... by caouchouc · · Score: 1

      Oops. Hit submit too early.

      Ports 1-1024 are your reserved ports. They're standard so there's no confusion, and any services where it would be a bad idea to let a user bind to the port are assigned numbers in this range as their standard ports.

      As I said in example- POP3, where you would be entering authentication data. Or HTTP where your company's website resides and your reputation could be damaged by a malicious user hijacking port 80 to put up a defacement.

    90. Re:really... by caouchouc · · Score: 1

      Are you comparing a live hacker to a shoddily-written virus with a thuggish payload?

      A lot more exploits are publicised for Linux than for Windows.

      I don't find this anywhere near as reassuring as you seem to.

    91. Re:really... by Some+Dumbass... · · Score: 1

      Are you being serious or sarcastic?

    92. Re:really... by j0e_average · · Score: 1

      HEY!!!! I resent your comments!

      Or maybe I resemble them....I don't know -- now you've gotten me all confused...

      .

    93. Re:really... by i_am_nitrogen · · Score: 1

      Honestly... how many people can install Windows? If they can figure out how to install Windows, they can most definitely install LindowsOS (a breeze if you're installing it as the only OS), and probably install Mandrake.

    94. Re:really... by i_am_nitrogen · · Score: 1

      So, OCG, what were those two announced flaws, and what were those nine announced flaws? What subsystems? What software? All kernel flaws?

      Most flaws in Linux and other Unix-like operating systems are local exploits that require one to already have some kind of executable access to the system. These worms get themselves onto Windows boxes without such access, so-called remote exploits.

      There are cases where a flaw in a software program, such as wu-ftpd, combined with a local exploit in the kernel, will result in a remotely exploiatable situation, but rarely is the kernel itself remotely exploitable.

      Lumping all Linux-compatible software together (i.e. Apache, Sendmail, Wu-ftpd (why does anybody still use that?), ProFTPD, Postfix, Qmail, etc.) doesn't count. You need to break those nine flaws down and give details.

    95. Re:really... by Nogami_Saeko · · Score: 1

      Hmm... Doesn't do that on my systems and I just installed XP on my machine at work a few days ago.

      Windows:
      Partition
      Format
      Install base NTFS system
      reboot
      Optionally Configure Network if not DHCP
      finish installing XP
      reboot
      Windows Update
      Install MS Office
      Microsoft Office Update

      Granted I use XP Corp edition at work, but there's not nearly as much rebooting and installing as you claim. It rebooted twice, then was done.

      --
      "Nothing strengthens authority so much as silence." - Charles de Gaulle
    96. Re:really... by caluml · · Score: 1
      Hmmmm. The risks associated by needing to run the daemon as root (which is often done via setuid anyway) don't outweigh the benefits, I think.

      OK - solution. Binding to ports under 1024 may only be done by users in the priv group or something. In fact, grsecurity patches allow you to do this - and even stop outbound connections by group too.

    97. Re:really... by Overly+Critical+Guy · · Score: 1

      Lumping all Linux-compatible software together (i.e. Apache, Sendmail, Wu-ftpd (why does anybody still use that?), ProFTPD, Postfix, Qmail, etc.) doesn't count. You need to break those nine flaws down and give details.

      Yet people count Office, Outlook, etc. holes as "Windows flaws."

      --
      "Sufferin' succotash."
    98. Re:really... by caouchouc · · Score: 1

      I disagree. A properly constructed program like apache (which doesn't actually use its root process to interact with users or files) is no root-compromise risk. The risks of a race for the port by a malicious user and an embarassing defacement are far more serious to my company.
      As to your solution, what if one of the users in the group is malicious? Then you're back to square one.

      The ports 1-1024 bindable only by root is also a standard that must be adhered to or you risk breaking software, which is unacceptable in most business environments. Things like grsec's low-port group exist so you can choose to take that risk.

      So, just use grsecurity if you want it done that way. :)

      note: Some software developers also choose to bind to high ports and take the risk of a port race (eg: mySQL), which is of course entirely their own perrogative.

    99. Re:really... by Nine+Of+Mirrors · · Score: 1
      I cannot understand why MS leaves these directories writeable (by default) version after version after version.

      Hm. Are they? I don't know about XP Home, but I'm on a freshly-installed XP Pro here and members of the "users" group do not have write access to %windir% or %programfiles% unless someone explicitly granted them that right. They mustn't even peek into another user's %userprofile%. Same with W2K I'd guess.

      Then again new accounts (including the user created during installation) are administrators by default.

    100. Re:really... by zulux · · Score: 1


      Sound like you slip-streamed some patches

      On the OEM version of XP you have to reboot after Windows Update.

      My point ws that Mandrake is easier to install that the combo of XP/MS Office.

      I'm eagerly awating the day when OpenOffce becomes as polished as MS Office - my guess is that in 18 months it will be there - then the real blood letting at Redmond will begin.

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

    101. Re:really... by Nine+Of+Mirrors · · Score: 1
      I've also had trouble with CD burning (Nero) when not administrator.

      I don't know if that's still an issue, but you could run the Nero "BurnRights" tool to create a user group with, well, burn rights. http://www.nero.com/en/631940824944968.html

    102. Re:really... by i_am_nitrogen · · Score: 1

      Office, Outlook, etc. are all from a single vendor. Apache, Sendmail, Linux, etc. are all produced independently.

    103. Re:really... by caluml · · Score: 1
      I disagree.

      Well, that's what makes the world an interesting place :)
      Why does apache need to be run by root? Because it needs to bind to port 80. But why bother with that need for root at all? I am well aware that a program that binds to a port, and then drops all root privs is in effect just a normal user program.

    104. Re:really... by sootman · · Score: 1

      That is a factor, but the much bigger factor is the amount of people examining *nix code from a security standpoint, the way that application prics are set, running apps in user space vs. kernel space, etc. (that last one affects stability more than security, but if someone can crash your machine, isn't that almost as bad as taking control of it otherwise? down is down.)

      --
      Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
    105. Re:really... by Anonymous Coward · · Score: 0

      It ensures that nobody but root (ie: no potentially evil users) can start an http server on port 80. I don't know about you, but I got the gist of it in the first port.

    106. Re:really... by Some+Dumbass... · · Score: 1

      Sorry for taking so long to reply. I just moved.

      Anyway, based on the other comments you've made in this thread, it would appear that you were being serious. Okay, here's my analysis of your analysis.

      What a ridiculous rant.

      It's complete, 100% common sense that if you were able to magically give Linux the 90+ percent marketshare that Windows has, it will suddenly come under HUGE fire, hackers will be flinging shit at it left and right, and no doubt dozens of holes will be discovered that nobody knows about because the system isn't as "beta-tested" as Windows is.


      First, by using the "common sense" argument, you're simply dismissing my argument against this particular point rather than arguing against it. Translation: you have just said nothing. Second, according to another article on SlashDot right about now, some people believe that Mars is about to crash into the Earth. Needless to say, "common sense" isn't worth much. Many people don't have it at all, and even then people don't always agree on what the "common sense" answer is (see any political debate for an example of this). Third, you've presented speculation as fact. You said that if Linux had more market share then "bad things X, Y and Z" would happen. Based on what? What is the evidence for the scenario you presented? You're speculating without presenting any evidence for your position.

      Second, didn't the last big Windows worm only affect people running MS SQL? What is that, 1% of all Windows installs? So despite the small number of computers which would be affected by this worm, it was still written.

      The typical Slashbot strategy. Completely make up a number from thin air that you haven't even looked up--typically illogical (1%???)--and then proceed to base your argument on it as though it is true.


      First, the exact number doesn't matter. The point was that there were relatively few MS SQL installs listening on the Internet. This contradicts your claim that it is merely the large market share of Windows which makes it a target because a worm writer targeted a small subset of computers on the Internet with that worm (they just happened to be Windows boxes). Clearly you just didn't _understand_ this argument (it's always lovely to argue with people like that). Do you understand now? The exact percent doesn't matter, jsut the sense that it's a small number, like Linux desktop use.

      Second, you didn't present any evidence that my number (1%) was wrong. Don't complain about my lack of evidence or "illogical" argument when you're not willing to present any evidence yourself.

      Microsoft had two announced holes last month, while Linux had nine. But there is a massive anti-Microsoft bias here at Slashdot, and everything they do is evil and wrong. Linux flaws only get reported when they're very major ones, like the filesystem-corrupting "turkey" release of the kernel, or the recent FTP hacking incident that people have been making excuses left and right for.

      Okay, there are any number of problems with this paragraph.

      The biggest one is that you used the word "holes". What is a "hole"? I don't remember even one vulnerability in Linux which allowed remote execution of arbitrary code in the past month (or the past several months, as I mentioned in my previous post). This would be a bug similar in severity to the Windows RPC bug. In other words, you left out vital information which would have hurt your argument and adjusted your language to avoid raising the issue. Perhaps you simply don't understand the difference between local and remote vulnerabilities, what a buffer overflow is, or what priveledge escalation means. I've seen a lot of that lately - MS supporters who use terms like "hole" or "vulnerability" while failing to distinguish types, presumably because those words are the totality of the depth of their understanding of the issue.

      Other mistakes: Bugs patches does not equal bugs in existence (you argued this yourself in your

  14. Safe until.... by SirLantos · · Score: 0, Redundant

    ...they publish the address of the new site and then someone else writes a virus that attacks that site. Instead of putting a band-aid on the problem why not just fix it? Just my opinion, SirLantos

    --
    The flying hamster of DOOM rains coconuts on your pitiful city.
    1. Re:Safe until.... by Anonymous Coward · · Score: 0

      Instead of putting a band-aid on the problem why not just fix it?

      Really, they should have come out with a patch weeks ago .... Oh wait they DID. What exactly do you want them to do RIGHT NOW to handle a problem that they fixed and provided a patch for?

    2. Re:Safe until.... by SirLantos · · Score: 1

      Personally, I would prefer it if they REALLY tried hard to make Windows more secure so things like this wouldn't be so rampant.

      But, I can understand how difficult it is to make a program secure. There is no such thing as hack proof. BLAH BLAH BLAH

      Even if they put some a little more serious thought in to security issues, I think people wouldnt be as upset.

      Just my opinion,
      SirLantos

      --
      The flying hamster of DOOM rains coconuts on your pitiful city.
  15. Can Blaster find another way to attack? by Anonymous Coward · · Score: 0

    From what I understand windowsupdate.com is the target URL of the latest worm (msblaster). Now that this URL is no longer functioning, is there any other way that this worm can cause problems for Microsoft's servers?

    Was this the only action Microsoft could have taken to protect itself from the pending attacks? Was this some sort of last resort?

    Any information about the new worm and how it is affected by this URL change is very much appreciated.

  16. ran Linux? by Anonymous Coward · · Score: 2, Insightful

    netcraft goes by IP, so if the MS servers went down, someone else running Linux got the IP, then it could show up on Netcraft. it's happened to me, where my dns would point to some ip, but then I move apartments, and my net is down for a week, and during that week, netcraft says that my system was running Win2K... but I haven't had Windows in my home at all for about a year.

    but with MS, they probably were running Linux, and their IPs likely don't change like that. but you never know.

    1. Re:ran Linux? by windchill2001 · · Score: 1

      Take a look at the netcraft link. The linux box is not using any of the same IP's that microsofts server had used in the past. It is a completly different block. That means that this isn't from a reassignment of the IP. This is a result of the DNS record changing to point to a different system.
      Well just an observation.

      --
      -Windchill2001 The One, The Only, The Cold...
    2. Re:ran Linux? by Anonymous Coward · · Score: 0

      No you're right, microsoft.com is run though a cable modem in Bill Gates' apartment

    3. Re:ran Linux? by Coward+the+Anonymous · · Score: 1

      I highly doubt Microsoft's webservers are using DHCP and dnyamic DNS. The one Linux box was from Akamai. From one of the articles "Microsoft is already a customer of Cambridge, Massachusetts, company Akamai Technologies Inc., which operates a distributed worldwide network that can diffuse DOS attacks." So this one box was something used to protect against DOS's I suppose.

      --
      -- Jason
  17. windowsupdate.microsoft.com? by Anonymous Coward · · Score: 0

    Why would they bother taking windowsupdate.com down, if they left windowsupdate.microsoft.com up. Do they know for certain that none of the bugs are setup to attack both?

  18. WU didn't ever run on Linux by cscx · · Score: 1

    That's just an Akamai cache engine, duh.

    1. Re:WU didn't ever run on Linux by Anonymous Coward · · Score: 0

      Not real brave of them, but certainly smart.
      In fact, I would say that it was one their few smart moves except for aquiring a monopoly first, before trying to screw the customers.
      Now if they would just get rid of exchange and IIS.

  19. NetCraft stats by xrayspx · · Score: 5, Informative

    Take NetCraft stats with a Big Grain of Salt (big grains of salt, heh). If a site is "Akamized", as this one was, or is otherwise distributed, you'll see the OS of the front end, not what the site actually runs. You'll note that NetCraft lists "linux" for the Akamai site.

    1. Re:NetCraft stats by Soko · · Score: 1

      If a site is "Akamized", as this one was, or is otherwise distributed, you'll see the OS of the front end, not what the site actually runs.

      So it's Windows in the back end? Sounds about right...

      Soko

      --
      "Depression is merely anger without enthusiasm." - Anonymous
    2. Re:NetCraft stats by terrymr · · Score: 3, Insightful

      Yes but isn't the point that microsoft has chosen to protect it's windows server by putting it behind a load balancer running Linux ?

    3. Re:NetCraft stats by Anonymous Coward · · Score: 0

      And who says that MS has not switched to Running Apache in the same fashion that WalMart does. Keep in mind that MS still uses BSD/Solaris at hotmail, but they run a modified exchange up front as a proxy.

    4. Re:NetCraft stats by cant_get_a_good_nick · · Score: 1

      Technically it's not exactly a load balancer, the entire site isn't coming from Akamai, just some portions of the content. Akamai is typically used for large objects - large GIFs, music, video files - that get spikey use. You pay for the bandwidth used, when it's used. You don't have to pay your ISP for a huge pipe that occiasionally gets filled, and is usually idle. In my dotcom days, we built an ad firm off of this, the adserver was a single Dell box because it just threw out URLs, the real bandwidth was coming from Akamai.

      As far as "ha ha, MS uses Linux", there really isn't a lot of competition out there for that particular service. MS isn't an ISP, they're not in business to service websites. They chose Akamai because it was the best (or only company still existing) that did what it needed, it using Linux notwithstanding.

    5. Re:NetCraft stats by elmegil · · Score: 1

      One wonders if the goatse.cx man could do with windows to cut down the drafts.

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    6. Re:NetCraft stats by scumdamn · · Score: 2, Interesting
      MS isn't an ISP, they're not in business to service websites.

      Uh, *cough*MSN*cough* maybe they ARE an ISP but they contract to a bunch of other companies for their bandwidth/infrastructure.

    7. Re:NetCraft stats by Compenguin · · Score: 2, Insightful

      but if linux couldn't be used for anything worthwhile, as they claim, why are they trusting their website to a serving system based off of it?

    8. Re:NetCraft stats by BurritoWarrior · · Score: 1

      No, it isn't. Akamai is much more than simple load balancing. it is content caching and distributed networking around the globe, keeping your data closer to the end user.

      The Linux story, if you want one is that Akamai has chose Linux to do this heavy lifting for many of the biggest sites in the world.

  20. Well, at least Microsoft by Rorgg · · Score: 2, Funny
    Has a license to use those Linux boxes!

    [rimshot]

    Thanks folks, I'll be here all week!

    1. Re:Well, at least Microsoft by Anonymous Coward · · Score: 0

      *KABOOM* [gutshot]

  21. In other news... by GillBates0 · · Score: 4, Funny
    Computing is more important than any other part of our work. If we don't do this, people simply won't be willing--or able--to take advantage of all the other great work we do.

    Breathing is more important to us than any other activity. If we don't breathe, we will die.

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
    1. Re:In other news... by Attaturk · · Score: 1

      And if we do breathe, we die. We gotta get those free radicals out of the oxygen and computing-based research will let us do that... so computing must, by definition, be more important than breathing. =D

  22. Ahhh, the perfect security by Froze · · Score: 4, Funny

    1) Disconnect box from all external cords
    2) Encase box in several hundred cubic meters of concrete
    3) Surround concrete with meter thick lead lining
    4) Bury under radioactive waste in a geologically stable region
    5) Saturate the surface with nuclear land mines
    6) Curse MicrSoft, becase you still get hacked!

    --
    -- The morphemes of your disquisition are ascertainable, but they have eschewed an ambit of transpicuous exposition.
    1. Re:Ahhh, the perfect security by MlBruehlly · · Score: 1

      7) Curse profusely when you have to undo it all to reboot the box because of a BSOD crash.

    2. Re:Ahhh, the perfect security by Dukael_Mikakis · · Score: 1

      Indeed, tripwire has some posters that reference security holes and what ITs do to protect the network.

      Microsoft's strategy, however:

      SECURITY EXPLOIT(S): Using a known server name

      FIX: Move to different server

      Brilliant, Microsoft.

    3. Re:Ahhh, the perfect security by johnnyb · · Score: 1

      That isn't security, it's obscurity :)

    4. Re:Ahhh, the perfect security by thinkninja · · Score: 1

      You missed a step:
      2a) Wrap tin foil around your head.

      --
      "The number of Unix installations has grown to ten, with more expected." (Unix Programmer's Manual, 2nd ed.; june 1972)
    5. Re:Ahhh, the perfect security by PhxBlue · · Score: 1

      Neutrinos as TCP/IP packet carriers? I guess it could happen. . . :)

      --
      !#@%*)anks for hanging up the phone, dear.
    6. Re:Ahhh, the perfect security by stwrtpj · · Score: 4, Funny
      1) Disconnect box from all external cords
      2) Encase box in several hundred cubic meters of concrete
      3) Surround concrete with meter thick lead lining
      4) Bury under radioactive waste in a geologically stable region
      5) Saturate the surface with nuclear land mines
      6) Curse MicrSoft, becase you still get hacked!

      7) Profit?

      --
      Karma: Frotzed (mostly due to the Frobozz Magic Karma Company)
    7. Re:Ahhh, the perfect security by AkkarAnadyr · · Score: 1
      Dude, if you go to all this trouble, you can't use the machine at all -- it's the exact equivalent of a permanent DDoS - which was the aim of the k1dd13z in the first place.


      Curse MS, indeed. Their product produces so many gotchas that they've trolled you into DDoS'ing yourself, thought-virus fashion. The ultimate hack.

      --

      I bought this house and you know I'm boss
      Ain't no h'aint gonna run me off

    8. Re:Ahhh, the perfect security by Anonymous Coward · · Score: 0

      Methinks your internal network's humor server has been DDOS'd.

    9. Re:Ahhh, the perfect security by WNight · · Score: 1

      No it isn't. He published the entire algorithm.

    10. Re:Ahhh, the perfect security by Xeth · · Score: 1
      7) Profit?

      Only if you're Mirosoft.

      --
      If your theory is different from practice, then your theory is wrong.
    11. Re:Ahhh, the perfect security by Anonymous Coward · · Score: 0

      or simply remove all mains power from machine and every electrical appliance in a thousand mile radius.

    12. Re:Ahhh, the perfect security by AirRock · · Score: 1

      It's almost what the White House did for it's webpage, but iirc it was pointed to an IP address instead of name, so they just switched it to a different server, problem solved. Tho it wasn't the White House's fault.

    13. Re:Ahhh, the perfect security by EvilNTUser · · Score: 1

      "7) Profit?"

      No, sorry. The correct answer would be:

      7) ...
      8) Profit

      --
      My Sig: SEGV
    14. Re:Ahhh, the perfect security by Anonymous Coward · · Score: 0

      ehm.. shouldn't it actually be

      7) ???
      8) Profit

    15. Re:Ahhh, the perfect security by RenHoek · · Score: 1

      Knowing Microsoft, when you are done with step 5 the machine crashes, making you dig out the machine again to hit the reset switch :)

  23. It sure is a hell of a lot faster by Hamster+Lover · · Score: 4, Informative

    Went to check for updates today, just for the hell of it and the speed was a huge improvement over the old URL.

  24. Re:I think the windows update botton on the taskba by h0tblack · · Score: 4, Insightful

    They're obviously worried that something is in the wild that is hard-coded to attack WindowsUpdate.com, else there would be no point in abandoning that domain and moving to another.

  25. Sensationalism? by blincoln · · Score: 2, Informative

    Where in any of those articles does it say that MS is taking down windowsupdate.com? It's always redirected me to windowsupdate.microsoft.com.

    --
    "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    1. Re:Sensationalism? by Mryll · · Score: 0
      Where in any of those articles does it say that MS is taking down windowsupdate.com? It's always redirected me to windowsupdate.microsoft.com.

      It doesn't. windowsupdate.com doesn't resolve to an IP and perhaps never has.

  26. windowsupdate.microsoft.com by anotherone · · Score: 5, Interesting

    Not a huge deal, since the official URL is windowsupdate.microsoft.com . The start menu, Tools in IE, and Windows Help all have that address. The worm author was kinda stupid, he should have pointed it to microsoft.com or windowsupdate.microsoft.com.

    --
    Username taken, please choose another one.
    1. Re:windowsupdate.microsoft.com by Polo · · Score: 3, Funny

      Not a huge deal, since the official URL is windowsupdate.microsoft.com . The start menu, Tools in IE, and Windows Help all have that address. The worm author was kinda stupid, he should have pointed it to microsoft.com or windowsupdate.microsoft.com.

      darn...

      cvs co msworm.asm
      click. tap. clack. click.
      cvs commit -m 'fix url'
      make;make install

      ok, done. Thanks!

    2. Re:windowsupdate.microsoft.com by anotherone · · Score: 1

      n/p man viruses should be open source

      --
      Username taken, please choose another one.
  27. Man.... by frodo+from+middle+ea · · Score: 2, Funny

    that gotta teach a lesson to those lousy worm writters. Changing domain name, who whold have thunk , microsoft would come up with such an ingeneous solution.
    Take that you microsoft hackers, bet you are scratching your head now.

    --
    for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
    1. Re:Man.... by Interesting+Username · · Score: 2, Funny

      They are getting smarter, this time the IP isn't hardcoded.

  28. Permanently Secured == Permanently Offline? by Matrix272 · · Score: 5, Insightful

    So "Permanently Secured" now basically means "Permanently Offline"? Why didn't they just let the worm eat the domain? What's the difference, really? Whether they pull the plug, or the worm does it for them, it still means windowsupdate.com won't work...

    --
    "It's better to have a gun and not need it than need a gun and not have it." ~ Christian Slater, True Romance
    1. Re:Permanently Secured == Permanently Offline? by Anonymous Coward · · Score: 0

      ok, when you ante up for the bandwidth bill, lets let it happen.

    2. Re:Permanently Secured == Permanently Offline? by BrynM · · Score: 1

      I wonder if anything will happen if the worm can't resolve the domain name. Is there a second runner up?

      --
      US Democracy:The best person for the job (among These pre-selected choices...)
    3. Re:Permanently Secured == Permanently Offline? by Spackler · · Score: 1

      What's the difference, really?

      Huge difference. If they do it, they are proactive. If it is done to them, they are reactive. Although the sequence of events ends up being the same, they don't have half a million geeks pointing fingers at them because a worm took down their site. Of course, if it got on the news the other way, the report would say "The Internet was taken down by a worm".

      Oops, going off topic:
      When the news says "Internet Chat Room", why can't they just say AOL? Time Warner?
      When they say "Email Virus", why can't they just say MS-Outlook? MS-NBC?
      When they say "Internet Worm", why can't they just say Microsoft has another hole, what's up with Linux?

    4. Re:Permanently Secured == Permanently Offline? by MyHair · · Score: 1

      Why didn't they just let the worm eat the domain? What's the difference, really?

      If I understand correctly, the difference is that there won't be massive SYN floods from all over the internet because there will be no target. (I haven't RTFA; I don't know what the worm will do if it can't resolve the domain.)

      I was figuring on the internet coming to a screeching halt for a while Saturday, but this action may prevent that from happening.

      <Nelson voice>Ha ha!</Nelson voice>

    5. Re:Permanently Secured == Permanently Offline? by LineGrunt · · Score: 1

      Now we know what Microsoft means by "Windows is secure..."

  29. Here's the deal on Linux for windowsupdate.com by djh101010 · · Score: 5, Interesting

    They've given the windowsupdate.com site to Akamai to serve for them. Not a bad idea, actually, since Akamai has something like 15,000 webservers distributed around the world, to share the load.

    Of course, it's extremely amusing that they're paying to have their content served by a flock of 15,000 penguins. I'm a bit concerned for our own site this weekend, as we use akamai for our static content. It'll be interesting to see how my pageloadtimes are affected (if they are).

    Akamai is a great resource for dealing with huge spikes in webserver load - I guess you could say this qualifies as that.

    1. Re:Here's the deal on Linux for windowsupdate.com by mog007 · · Score: 0

      Akamai is a great resource for dealing with huge spikes in webserver load So much for /.ing windowsupdate.com when it comes back online, huh?

    2. Re:Here's the deal on Linux for windowsupdate.com by nlinecomputers · · Score: 1

      I think that DNS lookups to windowsupdate.com are allready being sent to dev/null so I doubt that you or any other akamai client will be affected. Local ISP will have to discard the packets before they ever hit the backbone.

      --
      Slashdot, home of supporters of free software, free music, and free speech.Except for Moderators that disagree with you.
    3. Re:Here's the deal on Linux for windowsupdate.com by nobodyman · · Score: 2, Funny
      Of course, it's extremely amusing that they're paying to have their content served by a flock of 15,000 penguins.

      Man, that's gotta be embarassing -- their ass is being saved by the OS they are trying to kill. Good thing they paid SCO for that Linux license.

    4. Re:Here's the deal on Linux for windowsupdate.com by xcomm · · Score: 0

      So do so have bought the rights with their SCO license or will M$ be sued as for using AKAMAIs Netfinity Linux box by there SCO serves.

  30. Saved? by PovRayMan · · Score: 4, Funny

    Last night I finally went to go upgrade from Windows Media Player 6.4 to 9.0 so I can test out those high definition WMP9 videos for once. I couldn't figure out why microsoft.com wasn't loading but now I find out it was because of a DOS attack.

    Now I'm thinking, was this intervention from a higher force to protect me from installing WMP9 or just odd luck?

    1. Re:Saved? by Anonymous Coward · · Score: 0
      test out those high definition WMP9 videos
      What? Those 10 second 50x33 pr0n movies just aren't cuttin' it for ya?
    2. Re:Saved? by C32 · · Score: 1

      Microsoft have a windows media 9 codec redistributable on their site which works with wmp6.4 (it's "unofficial", and doesn't download automatically in wmp6.4 like other codecs, but it works just the same)

    3. Re:Saved? by Anonymous Coward · · Score: 0

      In the great words of Morpheus...

      "Show me."

    4. Re:Saved? by Theranthrope · · Score: 1
      could you please provide a link?

      Finding even slightly "non-standard" stuff on the microsoft.com site is quite a chore.

    5. Re:Saved? by Valar · · Score: 1

      If by "higher force" you mean teh 1337 h4>0r v1r|_|5 writers, then I guess the answer is yes...

    6. Re:Saved? by Cow4263 · · Score: 1

      Two things about upgrading to WMP 9.0

      1st - Don't :P

      2nd - Media Player Classic has the look and feel of MP 6.4 but with more features, check it out.

  31. *PERMANENTLY* by devphaeton · · Score: 1

    That's a real strong word. We all know that PERMANENTLY is an impossibility.

    You don't believe me, see if you can find an RFC for it!

    --


    do() || do_not(); // try();
    1. Re:*PERMANENTLY* by CashCarSTAR · · Score: 1

      Well..if the site is down and never comes back up...

      I would say that's pretty permament:)

  32. Re:I think the windows update botton on the taskba by druske · · Score: 4, Insightful
    "...whats the big deal about cancelling windowsupdate.com? do you think anyone will notice, or care for that matter?"
    The virus writers will care. I'd be surprised if a version with a New Improved attack address hadn't already been launched, probably ignoring the semaphore which normally kept the worm from reinstalling itself on an infected machine. If this happens, Microsoft's initial countermeasure won't be worth much for long. Still, it was a necessary and sensible first step.
  33. not quite by joe_bruin · · Score: 5, Informative

    OS: Linux
    Server: Microsoft-IIS/6.0
    Last changed: 15-Aug-2003
    IP address: 213.161.82.33
    Netblock Owner: Akamai

    they did not switch their servers to linux, they used akamai's caching services to handle their massive bandwidth requirements. notice the server is still iis. this is an akamai box (linux) serving a cached copy of microsoft.com (windows/iis)

    $ host www.microsoft.com
    www.microsoft.com is an alias for www.microsoft.com.edgesuite.net.
    www.microsoft.co m.edgesuite.net is an alias for a562.cd.akamai.net.
    a562.cd.akamai.net has address 63.236.1.163
    a562.cd.akamai.net has address 63.236.1.160
    a562.cd.akamai.net has address 63.236.1.153
    a562.cd.akamai.net has address 63.236.1.139
    a562.cd.akamai.net has address 63.236.1.168
    a562.cd.akamai.net has address 63.236.1.147
    a562.cd.akamai.net has address 63.236.1.138

    1. Re:not quite by javatips · · Score: 2, Interesting

      No, technically, they are using Linux to serve the page faster that their Windows box is able to.

    2. Re:not quite by angst7 · · Score: 2, Interesting

      Of course, your right. But it's so much more fun to take the fact that microsoft.com was reported running linux by netcraft at face value. Besides, technically they are making use of linux within the chain of information delivery, and doing so of their own volition. I still kinda think thats worth giggling about.

      --
      StrategyTalk.com, PC Game Forums
    3. Re:not quite by terrymr · · Score: 2, Interesting

      Yes but by doing so they're protecting their Windows box from attack by putting it behind a linux proxy. I doubt microsoft had a problem with bandwidth.

    4. Re:not quite by Pharmboy · · Score: 1

      They ran Hotmail on Unix for years before changing it over. Remember, they purchased it, they didn't start it from scratch. Not that big a deal.

      --
      Tequila: It's not just for breakfast anymore!
    5. Re:not quite by joe_bruin · · Score: 1

      I doubt microsoft had a problem with bandwidth.

      you've obviously never had to depend on the msdn website for documentation in the middle of the day (PST).

    6. Re:not quite by RoLi · · Score: 2, Funny
      What's your point?

      The sorry fact is that Micrsoft's complete Internet infrastructure would immediately break down without Unix/Linux.

      Remember when microsoft was offline for half a week? They migrated their DNS-servers from Windows to Akamai(Linux)

      Now they migrated the whole load-balancing and caching system.

      The only thing left is their measly webserver-box, so it seems.

    7. Re:not quite by NanoGator · · Score: 1

      "Remember when microsoft was offline for half a week? They migrated their DNS-servers from Windows to Akamai(Linux) "

      Just remember, that's what Akamai uses. It's not like MS said "no, use the Linux boxes because ours suck." MS said "You have a service that is helpful to us."

      --
      "Derp de derp."
    8. Re:not quite by AirRock · · Score: 0

      It could also be said that Akamai's *Nix boxes are better than M$'s "Windoze" boxes, and M$ is admitting it by switching to *Nix

    9. Re:not quite by tshak · · Score: 1

      I doubt microsoft had a problem with bandwidth.

      Ya, they're only one of the top most hit websites on the Internet.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  34. A secured Windows is a dead window, eh? by Anonymous Coward · · Score: 1, Insightful

    And who says that BSOD are so bad.

  35. Gotto think fast by Anonymous Coward · · Score: 3, Funny
    Shit, now I've gotto think of something clever/insulting to say about Microsoft....it's 2:30 in the afternoon....and my great mind isn't too active either, after a heavy lunch.

    /. editors should give us some advance warning before posting demeaning stuff about microsoft/RIAA/SCO, so I have enough time to think about rude stuff to write up, before 300+ posts are posted.

    1. Re:Gotto think fast by Neophytus · · Score: 1

      Its called subscription.

  36. I can't wait by GoatPigSheep · · Score: 2, Interesting

    To see how much microsoft sues the person who wrote that worm, or if it's someone from a third world country, they might just take a nod to the US government and post a 25 million dollar dead or alive bounty.

    Whoever it is is in A LOT of trouble now.

    --
    GoatPigSheep, the 3 most important food groups
    1. Re:I can't wait by oohp · · Score: 1

      Well the author could have just written the worm and stfu. Very unlikely but it can happen.

  37. Re:Gates Memo repost - slowing... by otisaardvark · · Score: 5, Funny
    Today, in the developed world, we do not worry about electricity and water services being available.

    You have to give it to the guy; his timing is impeccable...

  38. Re:I think the windows update botton on the taskba by Anonymous Coward · · Score: 0

    It does take you to http://windowsupdate.microsoft.com. Got it from strings wupmgr.exe. So what the hell was windowsupdate.com for anyhow?

  39. www.microsoft.com not on Linux by jared_earle · · Score: 2, Interesting

    Just because netcraft is reporting www.microsoft.com running on Linux, it's unlikely that they ported IIS to it. What you're seeing is a Linux proxy; The webserver itself is still an IIS6 box running on Win32 behind Akamai's Ghost proxy/cache.

    We all know that when Microsoft run UNIX, they run FreeBSD.

    --
    -- Jared Earle | "There is no spork"
  40. So... by Flabby+Boohoo · · Score: 3, Interesting

    the Army, or any large organization with a large install base of MS boxes, does not use SUS?

    I started using it here about 6 months ago, it is the only way to go. I cannot imagine using Windows Update as an enterprise solution. One or two PCs at home sure, but SUS is free dammit.

    1. Re:So... by Anonymous Coward · · Score: 0

      Are you really that naive? SUS is uses IIS to dish up these updates. How insecure to you want to get? I'm an MCSE. I generally like Windows. I'm not a Linux fanatic but I'm the first to admit IIS has more holes than swiss cheese. It's the one service we won't run. I may be over reacting but I'd rather be safe than sorry. Why doesn't Microsoft use the power of Active Directory to give you the ability to push these updates to boxes?

    2. Re:So... by Flabby+Boohoo · · Score: 1

      Naive? Perhaps, but not enought to think that being an MCSE means puts you in a position of authority.

      Sure, the IIS is not the most secure, but it is behind my firewall and since it keeps all my workstations up to snuff, the integrity of one box is easier to maintain.

    3. Re:So... by Anonymous Coward · · Score: 0

      Come on. You still have to prevent a hack from inside the network too. Getting physical access to your network is generally not that hard in most companies. Security on your network is not only restricted to external sources. Network security starts with user education, to securing each box, securing the internal network, then the external connections. This is exactly why we see the problems with security that we do. You need to be systematic about securing you network and start from the ground up in securing information systems.

      FYI, I mentioned my MCSE just to let you know I wasn't an anti-MS crusader, not to use it as a status thing.

    4. Re:So... by LinuxTek · · Score: 1

      Pardon my ignorance, but what exactly is SUS? Google gives too many unrelated answers.

      --
      Signatures are supposed to be funny?
    5. Re:So... by Flabby+Boohoo · · Score: 1

      Microsoft's Software Update Service. Details here.

    6. Re:So... by Darth_Burrito · · Score: 3, Informative

      Software Update Services. It is Microsoft's free solution for managing the installation of critical updates across a network. As I understand it, you are basically running your own mini Windows Update service to which your clients subscribe. You can download updates on the server and roll them out if and when you want to. I think it has reasonably good scheduling features. All the Windows Update clients need to be updated to a new version, but I think this was already been sent out in older service packs.

      Caveats:

      Requires Windows 2000/2003 Server (for the server)

      Only updates Windows 2000/XP/2003 (Professional or higher?)

      Until recently (SUS sp1), you could not install the SUS server on a domain controller.

      I think it only installs critical updates, not recommended updates, and not 3rd party software... so (tear, sniffle) no euro conversion tool.

      Other than that, I don't know a lot about it either... but I did very recently start a job where I desperately need to deploy something like this. There's a lot of questions I have like how do you ensure the clients actually update? Is there any reporting? Are the updates pushed or pulled? Does anyone have any SUS stories good or bad?

      More info

      Server Download Page

      Random dated article found on google.

    7. Re:So... by tokul · · Score: 1
      I started using it here about 6 months ago, it is the only way to go. I cannot imagine using Windows Update as an enterprise solution. One or two PCs at home sure, but SUS is free dammit.
      But the server used by SUS is not free.
  41. This is not just about the worm by Anonymous Coward · · Score: 0

    A DOS attack has nothing to do with the OS of the server it is trying to block access to.

    The DOS attack last night had nothing to do with the worm or any security flaw what so ever.

  42. What took out Microsoft.com last night??? by TopShelf · · Score: 4, Funny

    At least we know where the DDOS attack didn't come from: New York, Detroit, Cleveland, Toronto, et al.

    --
    Stop by my site where I write about ERP systems & more
    1. Re:What took out Microsoft.com last night??? by Anonymous Coward · · Score: 0

      I told those idiots not to switch from Linux to Windows Server 2003, but would they listen? NO! So, power on, reboot, power off, power on, reboot, power off, etc. :-)

    2. Re:What took out Microsoft.com last night??? by Anonymous Coward · · Score: 0

      ha ha, i took down the power grid AND micro$oft, worship me!

      -zero c00l

    3. Re:What took out Microsoft.com last night??? by Wraithlyn · · Score: 1

      On the contrary, there was a guy posting to Slashdot from the middle of the New York blackout yesterday, with full 'net access through Verizon.

      So _obviously_, the blackout was a huge diversion to hide the source of the DDOS, and fool us all. Thank goodness for tinfoil hats.

      --
      "Mind, as manifested by the capacity to make choices, is to some extent present in every electron." -Freeman Dyson
  43. How to get Good MS PR by linuxislandsucks · · Score: 2, Funny

    A question ..

    Assuming that all old windows systems are unsecure or badly written..

    Would it not make sense to take 75% fo $45 billion and offere to replace hardware and update to winXp or longhorn to every MS custoemr worldwide?

    It would be the PR stunt of the century..

    --
    Don't Tread on OpenSource
    1. Re:How to get Good MS PR by Frostalicious · · Score: 1

      Would it not make sense to take 75% fo $45 billion and offere to replace hardware and update to winXp or longhorn to every MS custoemr worldwide?

      Uh...no? Because companies exist to make money, not give it all away?

    2. Re:How to get Good MS PR by pyros · · Score: 1

      except that this particular worm (blaster) only affects 2000 and newer. 95/98/ME are safe to this worm.

    3. Re:How to get Good MS PR by TClevenger · · Score: 1

      Yeah, except that XP is one of the vulnerable systems, whereas NT/95/98/ME are not.

    4. Re:How to get Good MS PR by fonetik · · Score: 1

      NT 4.0 is affected.

  44. Re:I think the windows update botton on the taskba by gusilu · · Score: 1, Interesting

    Do you think anyone will notice, or care for that matter?

    Well, isn't the last Microsoft virus supposed to "attack" windowsupdate.com tomorrow? That might be an explanation as to why they are changing this - they obviously don't trust their own users to keep their systems patched and/or behing firewalls ... oh, wait, maybe they don't trust their own systems and sysadmins to be able to deal with it!

    --
    Don't try to fix me. I'm not broken.
  45. And for the next worm... by LilMikey · · Score: 1

    Peon: "Bill, the XYZ worm will attack www.microsoft.com at mightnight!" BG: "Change the name of the company immediately! Do we know security or what?!" By 2010 they'll just be dropping network support from Windows.

    --
    LilMikey.com... I'll stop doing it when you sto
  46. Next worm by semanticgap · · Score: 1

    Will target windowsupdate.microsoft.com - what will they do then?

  47. next work is going to use goofle by javatips · · Score: 4, Interesting

    I predict (maybe this post will help a little :-( ) that the next iteration of the worm (or another one) will google up "windows update" and will attack the 3-5 bests results.

    Let's see what happen then... Microsoft is going to pressure Google to remove www.google.com from their DNS Servers ;-)

    1. Re:next work is going to use goofle by javatips · · Score: 1

      The subject should have read next worm is going to use google

    2. Re:next work is going to use goofle by Keeper · · Score: 1

      You're assuming that such an attack won't take down google in the process...

    3. Re:next work is going to use goofle by FedeTXF · · Score: 2, Insightful

      Google runs FreeBSD... Say no more. :-)

    4. Re:next work is going to use goofle by Anonymous Coward · · Score: 0

      would it use the ImFeelingLucky() function?

    5. Re:next work is going to use goofle by Anonymous Coward · · Score: 0

      I'll say plenty, liar. "Google employed thousands of linked PCs - one of the world's largest Linux clusters". From http://www.google.com/corporate/tech.html

    6. Re:next work is going to use goofle by Keeper · · Score: 1

      Google does not have infinite bandwidth, or infinite processing power. Say no more.

  48. cool title by pyros · · Score: 4, Funny
    Marc Maiffret, chief hacking officer for security software maker eEye Digital Security


    That is the coolest job title. I'd have to negotiate a gold plated machette as a hiring bonus for a title like that. And anyone working for me would be officially titled a Hacking Minion!

  49. Or point DNS to resolve to SCO.com ! by Anonymous Coward · · Score: 1, Funny

    NT

  50. Re:Gates Memo repost - slowing... by Asmandeus · · Score: 1, Redundant

    Trustworthy Computing is computing that is as available, reliable and secure as electricity, water services and telephony.

    With yesterday's event, I'm thinking those aren't such good references anymore.

  51. Quote from one of the articles... by Anonymous Coward · · Score: 1, Insightful

    "We are preparing," said Stephen Toulouse, security program manager for Microsoft's security research center. "We are working diligently to make sure that our customers can get the patch."

    We are doing anything and everything EXCEPT making sure that these Windows problems do not find their way to the user in the first place. That would cost too much, slow down the new releases of Windows (hey, it takes us years for new releases that are nuthin' but eye-candy, you wouldn't want us to find bugs, too?), and generally just hurt our bottom line. Can't have that!

    Well, the bottom line should take a big boost now.

  52. Re:I think the windows update botton on the taskba by the+idoru · · Score: 1

    whats the big deal about cancelling windowsupdate.com?

    it isn't, but what if the worm had been written to attack microsoft.com instead? would they redirect all of their traffic for that URL to microsoft.com.microsoft.com? it just seems like a hackneyed fix. they lucked out that the worm won't follow a redirect and that it was for a URL they could afford to surrender.

  53. Ironic? by Bandman · · Score: 4, Funny

    Today, in the developed world, we do not worry about electricity and water services being available.

    Maybe he didn't get the memo?

  54. About That Bill Gates Memo... by tds67 · · Score: 3, Insightful
    Quote the Gates:

    So now, when we face a choice between adding features and resolving security issues, we need to choose security.

    Apparently he changed his mind.

    Our products should emphasize security right out of the box, and we must constantly refine and improve that security as threats evolve.

    After it's too late, that is.

    A good example of this is the changes we made in Outlook to avoid email borne viruses.

    I must've been absent when that came true.

    If we discover a risk that a feature could compromise someone's privacy, that problem gets solved first.

    Since when are bugs called "features"?

    If there is any way we can better protect important data and minimize downtime, we should focus on this.

    Lip + service = $$$

    1. Re:About That Bill Gates Memo... by Chester+K · · Score: 1

      So now, when we face a choice between adding features and resolving security issues, we need to choose security.

      Apparently he changed his mind.


      Microsoft is all about security these days. Unfortunately they're bogged down under the weight of the operating systems they released before their big internal security push. It's a black eye for the company that Windows Server 2003 was affected by the RPC hole, but I can't really fault them for that... the RPC service is core functionality deep in the OS and slipped their audit. It's not as if Open Source software has never found bugs in previously audited code either.

      A good example of this is the changes we made in Outlook to avoid email borne viruses.

      I must've been absent when that came true.


      So when's the last time you saw an Outlook virus? (Trojan horse attachments aren't exactly Outlook's fault; and Outlook even does a decent job of blocking most of those at the door.)

      Lip + service = $$$

      FUD + Anti-Microsoft Rant = Karma?

      --

      NO CARRIER
    2. Re:About That Bill Gates Memo... by Idealius · · Score: 1

      The Outlook "Security Enhancment" refers to it automatically blocking .exe (and other files) attachments, both sending and receiving.

      In fact, the only way to send a .exe (while maintaining the .exe file extension) is to get a tool from Slovak called "Outlook Email Attachment Options"

  55. The next update sites... by TheOtherChimeraTwin · · Score: 0

    Look, we all know this is just a temporary solution, since the next worm will target the new web site. Microsoft has planned ahead with a series of new web sites that should be able to handle any future problems.

  56. So Gates sent out a memo on security... by Hawthorne01 · · Score: 1
    Gee, it seems just yesterday that all this was cleared up by a memo from Bill.

    In the words of Bullwinkle "this time, for sure!"

    --
    "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former."
  57. Funny thing is... by Anonymous Coward · · Score: 0

    If the network went down due to MS it will never be admitted.
    We are a society that is easy to attack (due to shoddy coding) and yet our government still supports it due to political connections. How funny.

  58. Blame? by wasabii · · Score: 1

    I don't know where I place the blame for MS's horrible track record with bugs. I think, initially, it falls to the users. The users are idiots, they don't know how to properly secure their systems. They don't know to firewall everything, inside and out, and disable stuff like RPC where it's not used. However, why don't the user's know this? Because MS doesn't want them to. MS wants Windows to be point and click and not involve thinking. I think that's where disasters like this start. People need to be educated about how to secure their systems. Making everything as easy as point and click without thinking does not help people to understand how a system works, and how it needs to be protected. XP's firewall should have been enabled by default, protecting EVERYTHING. If the User found something didn't work, then the system should explain why. MS makes it EASY to be unprepared.

  59. Re:I think the windows update botton on the taskba by Overly+Critical+Guy · · Score: 1, Informative

    I don't get it either. Slashdot says "future updates will come from a different domain" as if they always came from windowsupdate.com, which is completely false.

    --
    "Sufferin' succotash."
  60. Does that mean... by bersl2 · · Score: 1

    windowsupdate.com is up for sale?

    Eh, probably not. :(

  61. Most Coveted Job Title Ever by seanmeister · · Score: 2, Insightful

    Marc Maiffret, chief hacking officer for security software maker eEye Digital Security, said the amount of data sent from each infected computer would be small....

    Man, how would you like to put THAT on your resume? :-)

    1. Re:Most Coveted Job Title Ever by TheOtherChimeraTwin · · Score: 0
      Sure, CHO.

      Excuse me, but what is this job you held in 2003? CHO??
      Oh, that was just a step below CIO.
      Oh, very impressive indeed!

  62. Today, in the developed world by elinenbe · · Score: 3, Funny

    From the memo:

    "Today, in the developed world, we do not worry about electricity and water services being available"

    Well, at least some people don't have to worry about electricity...

    --
    -eric
  63. Fixing my own post by conan_albrecht · · Score: 0

    Sorry, I guess that's 3 reasons, not 2. :)

    At least I said (at least)!

    What was that statement about "you should have previewed"?

  64. When asked for comment, by Anonymous Coward · · Score: 0

    Billy G. could only say:

    "It's not about the bugs! It's not about the bugs!"

  65. Re:not quite - this is what I get. by packethead · · Score: 2, Informative

    host www.microsoft.com
    www.microsoft.com is an alias for www.microsoft.com.edgesuite.net.
    www.microsoft.co m.edgesuite.net is an alias for a562.cd.akamai.net.
    a562.cd.akamai.net has address 206.112.112.69
    a562.cd.akamai.net has address 206.112.112.71
    a562.cd.akamai.net has address 206.112.112.63
    a562.cd.akamai.net has address 206.112.112.64

    --
    .sig
  66. September's Memo by msblaster.exe · · Score: 2, Funny

    From: Bill Gates
    To: Microsoft staff


    Last month I sent out a memo. Well here is another one. It has come to my attention that people on the website www.slashdot.org make fun of me and how I run my business.
    On another note there is another Windows Update available at the url www.windowsupdate2.com please download this due to the fact there were major holes in the last update.

    -Bill

  67. -1 Cluelessness by Anonymous Coward · · Score: 0

    It will only fool the current worms, not future ones that will have the new machine names in them.

    So you expect them to do NOTHING now? They released a patch weeks ago, what else can you expect them to do to take care of an issue that is gonna crop up in less than 24hours? Your post is resorting to smoke and mirror tricks to appear to be insightful or interesting when in fact it is simply clueless.

  68. Sidechannel attacks by babbage · · Score: 5, Insightful
    Of course, this leaves them open to alternative attacks.

    For example, if someone hijacks or otherwise poisons some DNS servers, then all the traffic to windowsupdate.com will make it through to windowsupdate.microsoft.com anyway.

    Or, a future worm could be written to target & attack a variety of Microsoft servers.

    Or a future fowm could be written in such a way that the target is not part of the worm's code, but rather can be directed remotely somehow. This way, even if Microsoft tries to switch addresses, the person[s] directing the attack can just change the target.

    The real solution isn't to keep trying to dodge the bullet.
    The solution to become bulletproof.

    Even after all this time, Microsoft still doesn't seem to get that.

    Part of the reason Microsoft is such a prominent target is of course because it is so, well, prominent. Taking down (say) an FSF server doesn't raise nearly as many headlines (as this week's headlines will attest to). But I don't think that all of the problem here can be traced to how widespread Windows is -- while the Internet's clients are nearly all running Windows, a large fraction of the server architecture is running some Unix variant, and while there is of course some malware that targets *nix (Linux, Solaris, MacOSX, BSD, etc), the results never seem to be as catastrophic as the typical Windows outbreak

    To rip of Bruce Schneier's analogy from his security article in Atlantic Monthly a year ago, it seems to me that the what security mechanisms Windows has tend to be brittle, while those that the *nix etc world have tend to be pliable. That is to say, when a problem comes up with (say) Apache, the damage tends to be isolated. This is partly because each installation will be configured differently, with different features enabled or disabled, and partly because the server runs on a variety of systems, each of which may have different mechanisms for providing underlying security protections. On the other hand, IIS installations tend to be pretty homogeneous, and a flaw with one very well could be a flaw with all.

    That's not to say that IIS couldn't be just as secure as Apache, if not much more so. But part of Apache (etc)'s strength is it's heterogeneous nature -- people are able to tinker, adapt, mix & match components to suit their needs, and in the process this will also tend to protect them from catastrophic failure. Microsoft has actively resisted this kind of diversity -- witness their howls about having to come up with "thousands of versions of Windows" if some of the firmer antitrust penalties were put into force. Those thousands of permutations are, arguably, exactly what is needed: this will give their users greater choice, and it will make emergencies like this more rare.

    I don't get why they're so opposed to the idea.

    Maybe they've got cleverer plans than anything I can think of. I certainly wouldn't claim to be any kind of security expert. But if the best they can come up with is a change of address card, I can't help but wonder if they're fumbling in the dark here...

    1. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      They want one version to make support cheaper.

    2. Re:Sidechannel attacks by Anonymous Coward · · Score: 0
      Those thousands of permutations are, arguably, exactly what is needed: this will give their users greater choice, and it will make emergencies like this more rare.

      Then why do so many viri work against Windows 95 through XP?

      Apache (the core) isn't resistant to attack because it can be compiled and run just about anywhere. It's resistant because the developers assume that it *will* be attacked and they take that very seriously -- beyond adding features.

      Microsoft is under pressure to 'show value' by adding features, with security in the role of just another feature.

      (That, and Apache's code is open to review or abuse, and the act of making it work on multiple hardware and software platforms forces more design defects to the surface. After all, if you knew others would look at what you made and that they would be compiling it everywhere, wouldn't you be careful with your overall design as well as the code itself?)

    3. Re:Sidechannel attacks by babbage · · Score: 1

      Cheaper than a drastic scrapping & overhaul of their automatic update & security patching site?

      I would find such reasoning very surprising.

      That's not to say you're wrong -- actually you're probably right -- but this kind of thinking is very short sighted of them.

      One of these days they might even figure that out.

    4. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      Remote control the victim domain? Surely, you mean give away the virus writer.

      I'm sure the original writer didn't expect the virus to be so successful. I would point to MSN.com or Microsoft.com

    5. Re:Sidechannel attacks by babbage · · Score: 1

      Where there's a will, there's a way. Past malware has been writtn to listen to IRC channels, waiting for instructions for which targets to go after in DDOS attacks. I'm sure that it would be possible to do something similar with or without the help of IRC.

    6. Re:Sidechannel attacks by mborland · · Score: 1

      Parent--good post, many good points. One obvious alternative attack would be to have the worm look up the host of the update site from the infected client...instead of hard-coding the hostname or numbers, it determines the update host the same way the Windows Update client program does. (It must be easy to find this...a URL in the registry?) This way if MS changes the DNS records for WU, that would make it impossible for users to access Windows Update itself. So, you are right, as you say, "The real solution isn't to keep trying to dodge the bullet. The solution to become bulletproof." Well, close to bulletproof, at least.

      Your note about customization of security features is important. For example, I tend to compile & configure Apache to a pretty minimal number of modules. You can configure IIS to run minimally, but obviously you can't recompile it to be certain the functions are unavailable! The less code that is available to exploit...the better.

    7. Re:Sidechannel attacks by babbage · · Score: 4, Insightful

      I actually don't want to get into whether or not having source code access improves security. A lot of people firmly believe that openness lends to security (and I happen to agree with them, in general), but some of the arguments against source availability are pretty persuasive too. Let's not get into that right now.

      You write...

      Apache (the core) isn't resistant to attack because it can be compiled and run just about anywhere. It's resistant because the developers assume that it *will* be attacked and they take that very seriously -- beyond adding features.

      Well put. After re-reading my post again, I think you've done a better job of putting your thumb on Schneier's argumeent about the pliability of systems that have well designed security. The point, which I guess I didn't really explain well enough, is that a well designed system sags instead of buckles; it softens instead of shatters. Apache tends to sag & soften; IIS tends to buckle & shatter.

      No system can ever be completely resistant to catastrophic failure. I think that Godel's incompleteness theorem and Turing's halting problem are, in a way, proofs of this assertion: no matter how well any system is designed, there are always cases that fall out of the design scope, and will cause Interesting Failures.

      This can be a depressing insight. You will never have a perfectly safe system. Ever.

      You can respond to that in a couple of ways. One is to say "fuck it, we can't win, so why try"? Another way is to say "we can't anticipate what will happen, but we can try to compartmentalize the damage from certain problem classes." You could say that Microsoft has been moving to the second point of view here, but it's taking them an agonizingly long time to get there, while Apache/Linux/etc have long beeen designed from this point of view.

      Interestingly, and to go back to Schneier's excellent article again, this sort of thinking also comes up in real world security considerations. Some of our systems are brittle (the airlines), and single failures can have catastrophic results. Other systems tend to be plastic (the power grid), and catastrophic failures are rare -- because single failures are common, expected, and planned for.

      This is why I find all the bleating on by the newscasters & politicians that "the power outage was not the result of terrorism." Well of course it wasn't, this isn't the sort of attack that a small malicious party can pull off. Power stations go out all the time, but normally nobody ever notices. Indeed, it is very, very hard to deliberately bring down a power system: NATO spent a month bombing the power grid & computer netwroks in Yugoslavia, but they never managed to do much more than bring a city like Belgrade down for a few hours before power was restored.

      If you want to bring down a whole grid, the best way to do it is by plain dumb luck (or an overwhelming lack of luck, depending on your point of view :-). It was a random fluke that caused yesterday's outage, just as it was random flukes that brought down the grid in the last two major outages, in 1977 & 1965. (On the bright side, that suggests that the mean time between power grid failures may be stretching out... :-). (Incidently, the Presidential Report on the 1965 outage makes for fascinating -- and newly relevant -- reading material).

      (To get even further off track, this kind of thing is also why Bayesian spam filters are such a good idea: at the micro level, each filter tends to do a fairly good job of being able to classify each user's patterns. But at a macro level, everyone ends up with a unique profile, and spam crafted to circumvent one user's Bay

    8. Re:Sidechannel attacks by Chester+K · · Score: 1

      The real solution isn't to keep trying to dodge the bullet.
      The solution to become bulletproof.

      Even after all this time, Microsoft still doesn't seem to get that.


      I can guarantee you they "get it". New development at Microsoft these days undergoes more stringent security evaluation than I'm sure most companies do. But Microsoft has tons of unchecked software out in the world, and once the bullet's been fired, the only thing you can do is try to dodge it.

      We're not going to see a substantial improvement in the number of Microsoft-related security incidents until a substantial portion of the world moves to a Win2K3+ operating system.

      --

      NO CARRIER
    9. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      Such reasoning is not surprising because it looks good on paper. Undisclosed and unforseen risks like massive worm attacks are not put on paper and do not factor into the cost.

    10. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      Other systems tend to be plastic (the power grid)

      You haven't been keeping up with the cause of the blackout, have you? The power grid is incredibly brittle because deregulation has removed any incentive to build additional capacity.

    11. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      This advertisment brought to you by:

      Microsoft Corporation
      "The finest in treadmills since 1995"

    12. Re:Sidechannel attacks by babbage · · Score: 1

      If the power grid were "incredibly brittle", then we'd have failures like this all the time. But we don't. The last one of this magnitude was 1977; the other was 1965. That means that we went 26 years without a collapse, and 12 years before that.

      One way to interpret this is that we have a mean time between failures of 19 years. That's IMO superb.

      Another way to interpret it is that we have managed to almost double the MTBF figure, and so can expect that the next such event could be 50 years from now. That's even better, if maybe wildly optimistic.

      The pessimistic interpretation is that we were doing well before deregulation came along and screwed up our winning streak.

      Clearly this seems to be your interpretation, but personally I'm not so sure. While I don't think deregulation has been a good thing, and maybe it did contribute to this event, on the other hand I think that failures like this are inevitable.

      People can argue all week over what caused this -- and I have no doubt people will -- but the fact is that the facts aren't in yet, and it's all wild speculation. Politics aside, nobody really knows if deregulation deserves any blame for this, nevermind what portion of the blame (none / some / all).

      What is obvious to me is that this was an extraordinary event, but it was not the way the power system usually works -- or fails. Local outages happen all the time (especially if you've lived in Alabama, as I have), but the power companies are very competent at isolating the damage and restoring service promptly. System collapse is an edge case, not routine.

    13. Re:Sidechannel attacks by hacker · · Score: 1
      The real solution isn't to keep trying to dodge the bullet.
      The solution to become bulletproof.

      No, the solution is to remove the bullets from the gun.

    14. Re:Sidechannel attacks by Anonymous Coward · · Score: 0

      In the case of Apache/IIS, Microsoft did learn that lesson.

      In Windows 2003, IIS is not installed by default. When you install IIS no extra features are enabled at all and all unregistered extentions are completely blocked. Only simple static pages can be served. In order to add more you must install and enable manually. This mixes the environment up a bit.

  69. domain sitting by zapp · · Score: 1, Insightful

    I cant wait for some asshole to try and reclaim the windowsupdate.com domain after it's been abandonded (if it is actually fully abandoned) and suddenly find his site being hammered on the first day.

    --
    no comment
  70. Scary Vulnerability by rgmoore · · Score: 5, Insightful

    This strikes me as being a really bad thing:

    Windows Update works by adding an entry into the system registry every time it installs a patch. When users log on to the update tool, it scans their registry and offers them list of patches that have not yet been installed. Cooper said that this mechanism was found to be flawed.

    "We found that people had got the registry key for the patch, but not the file," he said, explaining that the error could be triggered by a number of reasons -- from an incomplete installation to a lack of system resources.

    They're missing a really big flaw, here, which is that this is horribly vulnerable to malicious behavior. There are already plenty of viruses and worms out there that make registry entries for one purpose or another. It seems to me that if you were exploiting a vulnerability for which a patch already existed it would be very easy to automatically modify the registry to make it appear that the patch had already been applied. This would make tracking which systems were vulnerable much, much more difficult. This would work particularly well if you were trying to make a stealth worm.

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

    1. Re:Scary Vulnerability by Mr.+No+Skills · · Score: 1

      You'd think it would at least be difficult or require specific action to write to the registry, since this is probably only something that needs to happen when installing software.

      I know I've worked on machines where you couldn't write to system areas of memory until you physically moved a key or switch on the processor. You'd think the registry would at least give some signal that it was being modified.

      For that matter, how come there's no process monitoring tools in the "task manager" in Windows. I hate when I see those cryptic EXEs running out there without an ability to examine what they're doing...

      --
      Sleep is for the Weak
    2. Re:Scary Vulnerability by rgmoore · · Score: 1
      You'd think it would at least be difficult or require specific action to write to the registry, since this is probably only something that needs to happen when installing software.

      Except that it isn't. One of the problems with the registry is that it's a vast, multi-purpose thing. Not only does it have records of vital stuff like what software you've installed, it also does much more mundane things like keep track of your preferences. Every time you change your desktop wallpaper, for instance, Windows has to update the registry. (In fact, changing the registry is the only way I know of changing the wallpaper for the logon screen.) There are restrictions on changing the registry- random users aren't allowed to change other users' preferences, for instance- but if a worm can get system privileges then it can alter anything it wants.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    3. Re:Scary Vulnerability by jpmorgan · · Score: 1
      It seems to me that if you were exploiting a vulnerability for which a patch already existed it would be very easy to automatically modify the registry to make it appear that the patch had already been applied.

      At which point the guys at Microsoft, if they have more than two brain cells, change the KB number of the patch and your brilliant plan becomes a waste of code and an easy way to detect infected systems.

    4. Re:Scary Vulnerability by kylef · · Score: 2, Informative
      There are restrictions on changing the registry- random users aren't allowed to change other users' preferences, for instance- but if a worm can get system privileges then it can alter anything it wants.

      Exactly! But what more can you do? I mean, if I get root access to a Red Hat box, I could corrupt the RPM database just as easily as a Windows virus could corrupt the registry. It's just a programmer's API, any way you look at it. If you have the intention and the permissions, you can screw up any OS.

      The registry is protected with ACLs just as well as your average access-controlled filesystem (NTFS), so complaining about it being "easy to modify" is irrelevant. Files are easy to modify too, if you have the right permissions. But you EXPECT the permissions to block stupid programs from messing with your files.

      Now I'm assuming someone is going to say, "But Windows users run as Administrator!" Well, if that's the case, then running a trojan horse or spyware app is their own damn fault. Running as Administrator all the time basically makes your NT system as secure as Windows 9x was.

    5. Re:Scary Vulnerability by Anonymous Coward · · Score: 0

      www.sysinternals.com

      There is a free tool called regmon here that allows you to monitor registry modifications in realtime.

    6. Re:Scary Vulnerability by fervent_raptus · · Score: 1

      Getting around that kind of worm would be simple...

      Microsoft could:

      1) Relabel the patch on windows update
      2) Update their scanning control to check for actual files instead of registry entries

      Both of these things could happen post worm release.

    7. Re:Scary Vulnerability by rgmoore · · Score: 2, Interesting
      But what more can you do?

      What you can do is to look in detail at the actual files that the update was supposed to contain. If the correctly named files with the correct MD5 hashes are in the right places, you know that the update has been installed correctly. Fortunately, RPM is actually able to check things like MD5 hashes to confirm that the files that were supposedly installed actually have been installed, and that makes the kind of corruption that would hide the truth much more difficult to carry out.

      I'll admit that in this case Microsoft is doing a good thing by releasing a more detailed scanner that will actually check to ensure that the appropriate patches have really been installed, rather than just taking the registry's word for it. But doing so is not a built-in part of the system the way it is for RPM.

      It's also imprtant to note that this is an advantage of Linux distributions not being a mono-culture. Corrupting the RPM database won't help you if the system that you've invaded is a non-RPM using system like Debian, Slackware, or Gentoo, each of which uses a different packaging system. It's not even clear how much it would help if you were invading a Suse or Mandrake system instead of a RedHat one, since the expected names of the packages would be different, too.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    8. Re:Scary Vulnerability by pavera · · Score: 2, Insightful

      sure, running as admin makes the NT box as insecure as 9x, but thats the point, by default ALL USERS ADDED TO WINXP are admin, all of them, and how many grandmas are going to go in and change their account type? How many parents? How many teenagers?? not many, the only ones who do are the ones who are gonna have the patches installed anyway. The permissions issue in windows is MS's fault for having entirely too wide open defaults.

    9. Re:Scary Vulnerability by Anonymous Coward · · Score: 0

      > You'd think it would at least be difficult or require specific action to write to the registry,

      Registry keys have permissions. In theory, you'd have to be Administrator to read/write the Windows Update values.

      But that's almost everyone. Oops.

    10. Re:Scary Vulnerability by Phil+John · · Score: 1

      However, what if the virus checks home to see if it should enter a new value into the registry?

      Now, you may say that "Well, their host would just shut down the site"...but now comes the interesting part, what if the virus includes some peer-to-peer code that allows the payload to be updated on one node, and then be sent to the others.

      A virus that could always stay one step ahead of the opposition. Virus scanners detecting it? No problem, send out an update that totally changes the files signature, gets rid of suspect registry entries etc.

      What you would then have here is the ability to release new payloads or even new viruses without needing to get them up to the critical mass of infections where it starts to snowball, that critical mass is already out there.

      --
      I am NaN
    11. Re:Scary Vulnerability by Anonymous Coward · · Score: 0
      The easy answer to that one: install Microsoft Baseline Security Analyser. It actually looks at the version numbers of various DLLs, etc., that are updated by the patches. If the version numbers are too old, it warns you that the patch isn't applied. If they're too new, it warns you that the patch may not have been applied (and you'll usually ignore that warning).

      I admin several Windows 2000 boxes. Each of them has this tool installed and used regularly. You can download it from Microsoft's web site.

  71. Re:I think the windows update botton on the taskba by anotherone · · Score: 1

    Gasp, slashdot's got something inaccurate about ms?

    --
    Username taken, please choose another one.
  72. Re:The FUD on here is amazing by Anonymous Coward · · Score: 0

    Microsoft products cost a lot of money. Linux is free. Both are vulnerable. Get over it.

  73. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 5, Informative

    I installed and ran the Microsoft BSA utility that scans your computer for updates (windowsupdate looks in registry only) per the link above. It found 4 problems that WindowsUpdate can't find, so I followed the links, to read about them.

    Problem is, when you click on the link to DOWNLOAD the actual patch for XP, it just redirects you to www.microsoft.com, so even their security tool is useless if you cant get to the files to manually install them. Fucking rediculous.

    --
    Tequila: It's not just for breakfast anymore!
  74. Re:I think the windows update botton on the taskba by spectral · · Score: 2, Interesting

    Going to 'tools, windows update' in internet explorer takes you to a redir site on microsoft.com, which attempts to forward you to windowsupdate.com NOT windowsupdate.microsoft.com .. even still (~3PM EST). you'd think they'd at least fix that if they were fuckin with the dns..

  75. Re:Gates Memo repost - slowing... by tarquin_fim_bim · · Score: 1

    You have to give it to the guy; his timing is impeccable...

    Timing being the essence of comedy........

  76. Re:I think the windows update botton on the taskba by PhoenixFlare · · Score: 1

    I had the same problem this afternoon, this link for the XP patch seems to work still, for the moment.

  77. Re:I think the windows update botton on the taskba by Overly+Critical+Guy · · Score: 0

    Um, it's called the W32Blaster worm.

    --
    "Sufferin' succotash."
  78. I just had to mention it... by SillySlashdotName · · Score: 1, Funny

    "Microsoft.com went down last night" - See? Microsoft really DOES suck!

    --
    Acts of massive stupidity are almost never covered by warranty. --me.
  79. What I really want by phorm · · Score: 1

    is a "companion" virus to update infected machines now that windowsupdate.com is no more. How about keeping the domain around, but either modifying the DNS server to point it at the IP of RIAA.org, or perhaps just a slight modification to the hosts file of local machines?

    If they think a slashdotting was bad, I'd love to see their server smoke after all the infected windows machines start saying "hello"

  80. While some people may want to cast aspersions on.. by Anonymous Coward · · Score: 0

    ...MS. I believe last night's power failure was not caused by a lightning strike or terrorists. I believe it was cause by a comet fragment hitting the power grid. Last night was just a small sampling of what is coming when Planet X arrives. It will rain oil and fire and water over the entire earth. Everything that depends on electricity will cease. Screw Bush, the Taliban or Saddam. It's not going to matter after Planet X is here.

  81. DOS or real traffic? by nolife · · Score: 4, Interesting

    I wonder if this "DOS" they claim to be suffering is really too many users actually trying to get updates for once. After all, the code in this virus is not set to DOS MS until the 16th so they can not blame it on that. I doubt they would ever admit to not being able to handle the load. I use MS update at least a few times a day and have been for the last year on various client machines. Sometimes I need 10's of updates from a fresh install, sometimes just a few driver updates or the recently released. I don;t have any specific stats but I have noticed a definate slowing of the update site when the blaster worm was announced and it is getting slower as the days go on, today it took over 5 minutes to get a sound card update that for the previous year, only took 10 seconds. Another time today it took about 60 seconds. DOS causing this? Maybe, but I would guess they are having a hard time providing the update service for everyone and do not want to admit it. I bet hundreds of thousands of people are running the update service for the first time ever and they need a lot of updates. This move of names and connectivity is probably a hidden attempt to get the stuff hosted somewhere else or split up the load more then what they are currently doing and make it appear it is for security reasons. Reading bewteen the lines here but the amount of work involved with name change of this nature is massive compared to the relative ease a virus writer can simply point to the new site. Does MS honestly think a name change will stop a DOS? I doubt it, but it fits into thier FUD compaign of increased security and that they are under attack.

    --
    Bad boys rape our young girls but Violet gives willingly.
    1. Re:DOS or real traffic? by theflea · · Score: 1

      Maybe so. Just in passing conversations this week, I clued in several people that patching your OS was at least as important as an AV suite (at least in my view).

      If one thinks about the enormous media atention this worm has brought, and the number newspaper articles saying "seriously--you need to do this", you might think that this could increase traffic to windowsupdate by 3x or even far, far more.

      Maybe its just a healthy slashdotting; maybe there's a lot of things happening along several fronts.

  82. Re:I think the windows update botton on the taskba by Anonymous Coward · · Score: 0

    Or should I say, it used to, I think.. I just tried it before posting, and it got to some funky redir address, and didn't work.. timed out. Then i punched in windowsupdate.microsoft.com, and it worked. now when I go to tools, windows update:

    it works immediately (i don't even see a redir address)

    Oh well.

    Ok, I closed IE and then opened it back up while I was waiting for the two minute rule to expire, and it again timed out while trying to hit the redir address:

    http://www.microsoft.com/isapi/redir.dll?prd=ie& cl cid=0x0409&pver=6.0&ar=ienews&os=N6

    So I put it in to mozilla, trying to easily see what headers were sent, it grinds away, does nothing. I refresh, and it goes to windowsupdate.microsoft.com. then IE does it. so I close it, open it up again, and .. well, now it works again. So maybe they just fixed the redir or something. who the hell knows, I'm sick of this :) anonymous cuz replying to myself is dumb

  83. Linux's worst threat... by Thud457 · · Score: 0, Troll

    Is that Microsoft starts writing software for the Linux platform. Thereby making Linux a big fat target for bugs, worms and viruses.

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  84. too easy to fix by recursiv · · Score: 1

    Just change the first five results on google to some page that explains it's only there to be taken down by the worm. Virus attack: incapacitated.

    --
    I used to bulls-eye womp-rats in my pants
  85. Not really... by AzrealAO · · Score: 1

    They've contracted their massive load balancing requirements to Akami, and probably don't give a shit what Akami runs to do their work.

    It's not like Billy G. called the Network guys into his office and told them to go stick their servers behind a linux proxy.

    They're just contracting a service, like Apple and several other companies do for high bandwidth projects. (Apple distributes most of the Quicktime Movie Trailers via Akami)

    1. Re:Not really... by terrymr · · Score: 5, Insightful

      I think given Microsoft's position on Linux that they shoud / would have researched the market to see if the service could be provided by a windows shop before signing a deal with akamai. It looks bad ... almost like saying windows isn't up to the task.

    2. Re:Not really... by lucifuge31337 · · Score: 1

      I think given Microsoft's position on Linux that they shoud / would have researched the market to see if the service could be provided by a windows shop before signing a deal with akamai. It looks bad ... almost like saying windows isn't up to the task.

      Please go find a clue. Do you think that there are no Junipers or Foundrys in Cisco.com's upstream? Does that tell you Cisco isn't up to the task? Hardly.

      Akami was chosen because it's the biggest and baddest, and can deploy on a the short schedule required for this project.

      --
      Do not fold, spindle or mutilate.
    3. Re:Not really... by Anonymous Coward · · Score: 0

      While it DOES look bad it actually makes sense in a wierd way. Hell MS admits as much in Mr. Gates's memo. Take it from this point of view. Lets say IIS DOES get compromised and it will, as will the others. Their whole patch system is not gone. There are other capable systems that can service stuff. Lets say Apache gets compromised. The other IIS web sites can still service up patches quite nicely. If they are doing it properly they are looking for a 3rd provider, just incase.

      I would call it reliablity in depth. Also if you read the memo he sent out. He gives not a rats ass about IIS vs Linux. He wants people to pick MS stuff because its a no brainer. It currently is not. He just made sure the WHOLE company knows it. He even said as much as 'its not up to the task'. He also said NO one is up to the task. Which I belive...

    4. Re:Not really... by Anonymous Coward · · Score: 0

      No offence, but unless you (very) recently just got on the net, started reading newspapers, or basically just started knowing your environment (what do I know, you might be from another planet), it's proven beyone any level of dubt they are not.

    5. Re:Not really... by tshak · · Score: 1

      It looks bad ... almost like saying windows isn't up to the task.


      Obviously you don't understand what Akamai does. Akamai is the premier global content distribution company. Almost everyone who's anyone uses them on the net. MS isn't sticking Windows behind some Linux proxy because Windows isn't up to the task. They are distributing content through a major network that has geo-routing capabilities with datacenters all over the world. It's irrelevant whethor or not Akami runs Linux.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  86. Who cares by bogie · · Score: 2, Interesting

    More importantly when will MS abid by their settlement and allow alternative browsers to be used with WindowsUpdate?(In my eyes that should be implied)

    Doesn't seem right that they are allowed to throw up a button for "Program Access and Defaults" while at the same time making sure you actually can't live without the products your trying not to use.

    btw, waiting and hoping that the automatics updates works is NOT an alternative. Except for those who never use non-critical updates(IE WMovMaker, WMP9 etc) or love being alpha testers for a company known to CONSTANTLY screw up their patches.

    --
    If you wanna get rich, you know that payback is a bitch
    1. Re:Who cares by tweek · · Score: 0, Troll

      I don't think that forcing a windows machine to use IE for windows update is a bad thing really. It uses activex VERY heavily. When was the last time Microsoft put out an activex plugin for Netscape? It's been YEARS.

      --
      "Fighting the underpants gnomes since 1998!" "Bruce Schneier knows the state of schroedinger's cat"
    2. Re:Who cares by Mostly+a+lurker · · Score: 1
      IE would not have been my choice of core architecture around which to build a system maintenance utility. That said, I think it quite appropriate that MS base something like Windows Update around something specific. What MS was (past tense) trying to do with Windows Update is intrinsically hard and you definitely want to minimise the number of variables you are dealing with. This is a very different matter from locking out competitive browsers for general Internet surfing.

      What I find very difficult to understand is how, with the amount of money MS has thrown at the problem, they can currently have such poorly designed implementations (multiple) for product updates.

  87. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 2, Insightful

    Adding more salt to the wound I guess. I have also noticed that if their servers are not properly operating, they will say there are no updates available, even when there are. I have confirmed this twice when I KNEW there was an update that was not installed on the laptop (sometimes i go two weeks without using).

    That is a pretty shitty way to handle a down server, by convincing your customers they are safe when they are not.

    --
    Tequila: It's not just for breakfast anymore!
  88. Microsoft's "Security" Record sucks but... by Eric+Damron · · Score: 4, Insightful

    the Linux community needs to concentrate on not becoming the next big security joke. Okay, it's fun to laugh at Microsoft's pathetic record.... Just a second... Muhahahahahah. I feel better now. But as Linux becomes more and more popular blackhats will put more and more attention into breaking our OS.

    We need to all make good design and operational decisions. Bad decisions like the one made by Lindows to run as root be default can lead to Linux having as bad a reputation as Microsoft.

    The Linux community is positioned to demonstrate to the world that Linux, not Windows, should be used anywhere that security is an issue. Let's not blow it.

    --
    The race isn't always to the swift... but that's the way to bet!
    1. Re:Microsoft's "Security" Record sucks but... by MicroBerto · · Score: 4, Insightful
      Many people are probably thinking about the kernel, but those guys are doing a relatively good job.

      What we really can't overlook are the popular distributions. They can't be putting in ridiculous defaults at startup. They shouldn't use too much beta software that's going to be running a lot. They need to keep pushing updates, and make it easy. And for the most part, I think we're doing pretty good. Learn from Microsoft's mistakes while you laugh at them.

      --
      Berto
    2. Re:Microsoft's "Security" Record sucks but... by RealAlaskan · · Score: 1
      ... the Linux community needs to concentrate on not becoming the next big security joke.

      True, but the situation isn't so bad for us as it is for MS. First of all, the developers have actual incentive to really fix problems, and fix them fast. At MS, the developers don't have any incentive to fix anything until sales tells them: ``This bug is costing us sales.'' The developers job then is to make sales go back up. Fixing the bug may not be the easiest option.

      Second, if security DOES become a big problem, we can start doing things like using libraries which are buffer-overflow safe (like libsafe, maybe?). This is available right now. People can start auditing critical stuff like glibc and the linux kernel for buffer overflows. There's a lot that our community can do (and should be doing!) right now, that MS just is never going to have the incentive to do. I'll bet there isn't anything like the kernel janitors working on the NT kernel.

      Finally, the easiest and the most important thing we can do is make sure that the newbie distributions have secure, sensible defaults. Things like using something other than sendmail, having services turned off by default, not accepting connections from anything but localhost, and so on. For the typical newbie, who hooks up one machine to the 'net via ppp or pppoe, this kind of security wouldn't be a problem. Someone who needs to make their machine part of a lan would have to learn enough to turn on some of these services, and open up the default firewall a bit, but that's not a bad thing.

      ... as Linux becomes more and more popular blackhats will put more and more attention into breaking our OS.

      The day is coming when we will have to be more secure out-of-the-box. Security is a process, and begins with a knowledgeable user. Starting with the services turned off, and making the user learn to turn them on as he needs them, will help with the user education, and make the OS more usable in the long run. After all, the better you know it, the better you can use it.

    3. Re:Microsoft's "Security" Record sucks but... by jc42 · · Score: 1

      Bad decisions like the one made by Lindows to run as root be default can lead to Linux having as bad a reputation as Microsoft.

      But ... but ... Lindows is supposed to be emulating Windows. Running as root is required to do this job. After all, imagine the criticisms from Windows users if they didn't do this.

      "What? I can't overwrite any file on the system unless I give some stupid root password (whatever that is)? They told me this would work just like Windows. They lied to me. I want my money back."

      MS's management has told us and told us: Windows users don't want security. They want capability. So give them the power to do what they want. It's just those outdated unix systems that limit what their users can do to their own machine.

      --
      Those who do study history are doomed to stand helplessly by while everyone else repeats it.
    4. Re:Microsoft's "Security" Record sucks but... by Eric+Damron · · Score: 1

      You raise some good points. Things do need to be mostly shutoff by default but we should provide an easy way to turn them on in a secure way. It's better that than have a user run a process that is insecurly configured.

      I don't agree that security begins with the user. I agree that no matter how secure a system is a moron can make it insecure PDQ. But let's not depend on the user. Most users will never be gurus and shouldn't have to be.

      I guess what I'm saying is: have most things turned off by default and have easy utilities to guide the less-than-a-guru user when that user wants to enable some part of the system that he knows nothing about. Let's do it for him and make sure that it's done right.

      I know a lot of purists will jump on me and say that we shouldn't make Windows-like wizards but just because we make wizards for the user doesn't mean that the gurus can't get under the hood and do things by hand if they really want to.

      --
      The race isn't always to the swift... but that's the way to bet!
    5. Re:Microsoft's "Security" Record sucks but... by RealAlaskan · · Score: 1
      When I was talking about making the user learn, I was thinking about bastille, which guides you through the process step by step, gives you the information you need to make decisions about each step, and tells you what it's doing to implement your decisions. I learned a lot from that.

      That's a pretty good start on ``... easy utilities to guide the less-than-a-guru user ...''.

      Distributions are a bit better now than they used to be about sensible defaults. I got started with RH6.0, and it had everything turned on. I didn't realize that for quite a while, and didn't figure out that it was a bad idea for a while longer, and didn't figure out how to fix it until quite a while later, when I installed Mandrake 6.1 or so, and ran bastille for the first time.

      Of course, I KNOW I didn't get rooted while I was running wide open: I wasn't on the net. No modem, no ISP, no problem.

      By the time I got a modem, I'd learned how to run bastille, how to look for signs of intrusion, and so on. I got rooted once, and had to reinstall. I figured that the problem was that upgrading Redhat (I was back to them by that time) was too much hassle, so I switched to Debian. No problems since.

  89. I've figured it out! by Anonymous Coward · · Score: 0

    Heres my suggestion to MS (and this is actually a serious one).

    Ever thought about peer to peer? integrated bittorrent or Kazaa style sharing would be a god send for the dissemination of huge patches like this.

    Food for thought

  90. You call a memo from January 15th 2002 timely? by AzrealAO · · Score: 1

    That's a pretty strange definition of impeccable timing if you ask me.

    1. Re:You call a memo from January 15th 2002 timely? by otisaardvark · · Score: 1

      OK, OK... poetic license... errr.... yeah... What, did you think I didn't RTA or something?

  91. Microsoft exploring different sources of revenue by JAgostoni · · Score: 1

    I wonder if the ad in the middle of the article is from ZDNet or actually in Bill's memo... (or course it was from ZDNet, but I wouldn't put it past Billy boy do drive advertisment dollars from his own employees)

  92. Re:I think the windows update botton on the taskba by PhoenixFlare · · Score: 1

    Yeah...You'd think they'd notify all the people like Symantec, Mcafee, CERT, etc. that've been posting the other links all week.

  93. Package Management by plankers · · Score: 3, Interesting

    Two thoughts here. First, package management

    Operating system version control has been a problem for Microsoft Windows for a long time. Especially with runtime software bundled with third-party applications (think DirectX), you need a clear way to identify what is installed on a machine, upgrade it while tracking dependencies, and easily remove it. InstallShield does this sort of thing -- why isn't it built into the operating system?

    Furthermore, most package managers provide a facility to verify the files that are running on the machine. While it isn't as conclusive as something like Tripwire, a simple "rpm --verify --all" will give you some insight into whether a system file has been replaced.

    Package management on AIX (and probably other UN*Xes, but I haven't used them) gives you the ability to roll back out of a patch that went wrong, too. While that is possible to some extent in Windows, a package management solution could make that very easy.

    And while we're at it, why isn't there a framework built into Windows to centralize patching of ALL products, not just Microsoft ones? Certainly the "Microsoft Update" that they are proposing is a good step, but why not build something that can check other vendors' web sites for patches? Couldn't such a framework be built so that when an application is installed it registers with the OS, and tells the OS where to look for updates for that specific product? Then when you run this "update console" or whatever, your local machine goes out to Microsoft, Symantec, Adobe, whoever, and checks to see if there are updates for EVERYTHING that is installed?

    The system could also be similar to Red Hat's update mirrors/satellite up2date server, where a corporate customer could set up a central update server, tell it where to get updates for all the products in use in their company, and then that server mirrors it. Then updating the client workstations (and servers) is something that happens in-house. Maybe it could even be smart enough to tell if a client machine hasn't been updated yet, and then when that machine is powered on it could update itself and reboot if necessary, all before the user is able to log in.

    These two things together could really put a dent in management for Windows machines. Sorry if this is sort of a ramble, I've been thinking about it for a while and it all just spilled out.

    1. Re:Package Management by SuiteSisterMary · · Score: 1

      If you a Win2K/XP network, use the intellimirror/SUS stuff built into and downloadable for Win2k server.

      If you're a more heterogenous windows network, use SMS.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    2. Re:Package Management by plankers · · Score: 1

      Agreed. Part of my argument, though, is that support for this has to be ubiquitous and built in to the OS, not a separate product like SMS. I don't want to pay more money to have Microsoft, or any vendor, keep me secure when I should have been secure in the first place.

  94. Re:I think the windows update botton on the taskba by TheGreenLantern · · Score: 1

    Maybe I just wasn't ever paying attention, but I don't remember the address ever being "windowsupdate.com"; it's alwasy been "windowsupdate.microsoft.com". At best there was some DNS redirection going on at some point perhaps.

    --

    It hurts when I pee.
  95. Two thoughts by LittleGuy · · Score: 2, Insightful

    1) M$ (and the media) hyped this security patch to the hilt, IMHO, because WU was the target. Other worm exploits that have been cited in the news can be prevented by patches that come out a year or two ago. It would be nice to have the other 30 or so patches released this year equally hyped.

    2) Re: WU says you're patched but you're not... I'm sorry, but nothing impresses me more than Shavlik's HFNetChkLT for Win2K, NT, and XP. SCan with this and then download the patch from the M$ Security Bulletins through Technet and install manually.

    --
    Mod Karma -1: I sed bad wurds. If I cep my mouf shut, I wud be at riyses.
    1. Re:Two thoughts by sdibb · · Score: 1
      SCan with this and then download the patch from the M$ Security Bulletins through Technet and install manually.

      I just tried doing that, but half the links on Technet redirected me to Microsoft's home page.

    2. Re:Two thoughts by jpmorgan · · Score: 1
      M$ (and the media) hyped this security patch to the hilt, IMHO, because WU was the target. Other worm exploits that have been cited in the news can be prevented by patches that come out a year or two ago. It would be nice to have the other 30 or so patches released this year equally hyped.

      Nice conspiracy theory. But you forgot that they were hyping the patch before the worm was released.

  96. It's still M$'s fault! by Thud457 · · Score: 3, Insightful
    "I don't like MS either, but this is blatantly unfair. MS did fix the gaping hole -- last month. The problem is that their customers didn't implement the fix, so they are taking reasonable precautions to avoid damage. Beat them up for the things for which they deserve, but not this."

    Because they've endgendered a "computing" culture where users are either: 1)ignorant about the need for patching, or 2) have been burned by fucked up M$ patches in the past and hence, don't keep up to date.

    "Fool me once, shame on you
    Fool me twice ...
    ...
    won't get fooled again
    "

    This country is overrun with idiots. I hope you reap the consequences of your actions. I spit on you all!

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    1. Re:It's still M$'s fault! by crawling_chaos · · Score: 1
      Weird that a site that's so high on "personal responsibility" in so many other areas completely abandons its ideals when the chance to bash Billy Gates comes up.

      You do realize that, by your reasoning, the RIAA is perfectly in the right in going after Napster et al, since they engendered a computing culture that promotes theft of service? And that's just one example.

      I wonder what your reaction will be the next time there's a big oops in your favorite operating system? I've seen apt eat more than a few machines myself, so don't think that the attitude you describe is unique to Windows users.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    2. Re:It's still M$'s fault! by Anonymous Coward · · Score: 0
      "This country is overrun with idiots. I hope you reap the consequences of your actions. I spit on you all!"

      Nice to see Peter Finch get moderated up to +4, insightful!

    3. Re:It's still M$'s fault! by caouchouc · · Score: 1

      by your reasoning, the RIAA is perfectly in the right in going after Napster et al, since they engendered a computing culture that promotes theft of service?

      That's "copyright infringement," not "theft of service."

      Copyright infringment is no less a bad thing, but calling it theft of service is just silly. You bent the example just a little bit too far to make your point, and it broke.

      I've seen apt eat more than a few machines myself

      I've never seen apt eat a machine. Of course, I also lay off the UNSTABLE branch because it's the UNSTABLE branch. This may or may not be related. :-P

  97. Re:The FUD on here is amazing by Greyfox · · Score: 1
    You're new around here, aren't you?

    You've nailed the problem down pretty well though. I'd require a license similar to the ham radio license to use the Internet, if I were Dictator of the World.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  98. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 3, Informative

    Going to 'tools, windows update' in internet explorer takes you to a redir site on microsoft.com, which attempts to forward you to windowsupdate.com NOT windowsupdate.microsoft.com .. even still (~3PM EST). you'd think they'd at least fix that if they were fuckin with the dns..

    You may not know this, but when you change an entry in DNS, it is not available to everyone for a while. This is due to caching (all ISP DNS servers are caching servers, of course). For instance, the AOL servers may have gotten the ip for the domain at 8am, and if it doesnt expire for 24 hours, their server will assume it is still at the same ip, so when an AOLer tries to go there (using AOL's DNS server) it will simply give that IP address, even tho it has changed. It wont go back to the SOA and check the serial number of the DNS entry to see if it is still valid until after it expires and someone requests it. So, it depends on the expiry of the DNS record before the change. My experience is that it takes 1 to 2 days for all the changes to fully propegate, and sometimes longer on some DNS servers if they override expiry.

    --
    Tequila: It's not just for breakfast anymore!
  99. Re:The FUD on here is amazing by Dan+Ost · · Score: 1

    The reason this is getting attention is because it's the first major
    security flaw in Windows Server 2003 which was supposed to be
    impenetrable being the first major OS released after the big security
    push my Microsoft.

    In addition to that juicy bit of info, this flaw is more interesting
    to talk about than most because of the worm. It's amusing to see such
    a clever worm thwarted by using the wrong domain name. Seems intentional
    to me.

    --

    *sigh* back to work...
  100. Re:I think the windows update botton on the taskba by Fishstick · · Score: 2, Informative

    The button on the taskbar is targeted to

    %SystemRoot%\system32\wupdmgr.exe

    which sends me to http://v4.windowsupdate.microsoft.com/en/default.a sp

    which appears to work just file. Didn't try it from IE tools menu, tho

    --

    There is much cruelty in the universe, John.
    Yeah, we seem to have the tour map.

  101. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 3, Insightful

    Microsoft is about to get into the AV business yet again. Keep in mind, MS does NOT consider those companies friends, rather they are competitors, so I can see MS letting them look bad with old links. That is not new for them.

    --
    Tequila: It's not just for breakfast anymore!
  102. Hey worm writers: IDEAS! by Ex+Machina · · Score: 1, Troll

    You guys should poke the registry key that indicates the patch status for the hole you are exploting So the patches, won't work.

    EVIL!

  103. MS memo is an advertisment by AmishSlayer · · Score: 1

    That "memo" looks more like an advertisment to me. Read it and see how much Bill gabs on and on about all the good things that Windows, .NET, et al provides.
    Even when security is there number one priority advertising is still their other number one priority.

  104. Interesting by Anonymous Coward · · Score: 0

    Why don't you now try to download the latest IE?

    I can holy hope as to what might happen.

  105. Windoze... by CoyoteGuy · · Score: 1


    So what happens when the worm writers get a clue, and write subroutines to do lookups on hostnames, and attack based on the translated host-to-ip address? It's not too hard to resolve windowsupdate.microsoft.com to whatever the root dns has listed, or for that matter any domain. A big enough worm, even with load balancing on its target, will still cause havoc on every routing device from here to Timbuck Two. I for one, would hate to be paying the bandwidth bill on the intended target.

    --
    Slashdot.. Land of nerds, trolls, and FlameBait..
  106. hehe... by Anonymous Coward · · Score: 0

    Maybe he didn't get the memo?

    That, or he didn't bother to RTFFP (read the fscking front page).

    Sure, don't read articles, but shit, alteast skim the OTHER slashdot story titles!

    1. Re:hehe... by Anonymous Coward · · Score: 0

      The quote is from Bill Gates' memo, not the submitter.

  107. windows worm OLE exploits might have broke power. by Giant+Robot · · Score: 2, Interesting

    Apparently the US National power grid uses "OPC"

    OPC stands for "OLE for Process Control"... (if you did some COM/DCOM windows programm you will be familiar with this).

    It's the same technology targeted by the W32.Blaster worm that is crawling around the web.

    It won't suprise me if some of those computers responsible for failover/grid isolation actually hung themselves on the worm.

    In case you don't know what the worm does, not much, but a side effect (because of sloppy coding) it causes the machine to restart very frequently (it also attempts to attack microsoft.com in a DoS attack, I guess that's why microsoft shut down windowsupdate).

    what do you think?

  108. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 4, Interesting

    they obviously don't trust their own users to keep their systems patched and/or behing firewalls

    I'm an XP user (among other os's) and I don't trust the average Windows user either. Not ragging, just a fact. My mom is one of them.

    My brother and I were joking around because mom asked him what she should do about "that new virus" (blaster). She asked him if unplugging the computer was enough, or if she needed to do more. I told him he should have told her to put the box in the refrigerator because everyone knows that viruses and germs won't grow when they are kept that cold. Yea, I know, slightly cruel, but I'm telling ya, she just MIGHT have done it if we could have kept from laughing.

    So its not an insult to Windows users, its just a fact: Most are interested in doing stuff with their computers and expect them to be like a toaster, just plug it in and never think about it again.

    Ironically, I bought my 67 year old mom the computer last christmas, she uses it every day, and she WAS smart enough to ask someone about it, more than I can say about a few /.ers , hehehe.

    --
    Tequila: It's not just for breakfast anymore!
  109. I noticed and cared by sirshannon · · Score: 1

    when I sent someone a link to http://www.windowsupdate.com this morning and there was no site there, I noticed and cared.

  110. Microsoft != reliable by Thud457 · · Score: 5, Funny
    "Actually, there are rumors that safety systems that would have prevented such widespread failure were running on Windows and were down because of blaster. "

    If those rumors are true, then the worm didn't cause the power failures, it just disabled the systems that would have prevented them. That this happened at around the same time is just a coincidence, - or maybe minor power failures happen frequently and were just prevented from spreading?

    Who the fuck runs mission-critical systems on Windows?!! HOMER SIMPSON?!!!

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

    1. Re:Microsoft != reliable by pyros · · Score: 4, Funny
      yes ... yes ... yes ... .. y ... <hmmmm> y ...

      <stupid filler to avoid the fscking retarded lameness filter>

    2. Re:Microsoft != reliable by pyros · · Score: 4, Funny

      redundant!? Guess I should have quoted the bit I was responding to (who runs windows on ...? HOMER SIMPSON ) The yes over and over being a reference to him running his mission critical system, where he just typed yes all day, until he figured out he could just hit y, until he set up that toy bird which leans forward and stands back up over and over. Man, I can't believe I had to explain that one.

    3. Re:Microsoft != reliable by mrjive · · Score: 1

      It would have been more appropriate to include a quote like...."Hey miss 'doesnt find me sexually attractive anymore,' I've just found a way to triple my productivity!"

      or....

      "I'll just have a tab....oh wait, no time for that now, the computer's starting!"

      --
      If you can't beat them, arrange to have them beaten. -George Carlin
  111. techie question by kisrael · · Score: 1

    I need to research this, thought someone might know off the top of their heads...
    Windows XP, I got hit by a trojan hiding as an .SCR, (yeah yeah, revenge of pr0n), a pretty nasty one that pulled crap like shutting down task manager as soon as I brought it up. I think it might have disabled windows update. is there a way to tell if it is actually disabled, and how to get it back?

    --
    SO YOU'RE GOING TO DIE: The Comic for Dealing with Death
    1. Re:techie question by J.+Patrick+Graves · · Score: 1


      If you ever get hit with a trojan horse that gains root, oops, I mean "administrator", priviledges, you should reinstall or go to a back-up.

      Unless you want your PC to be someone's b*tch , you need to press the "do over" button, i.e. do a system install or recovery and install the proper patches to prevent another root, I mean "administrator", comprimise.

      Even if the "known" exploit is reported to doing nothing harmful, there is no guarantee that you haven't been comprimised by a clever variant of the exploit. Any of the system programs could be replaced with a copy that opens a back door when it starts.

      Once you get comprimised, it's GAME OVER and some script kiddie OWNS you.

  112. I hope you are joking by stewby18 · · Score: 1

    Or that if you aren't, you neve work in a security field.

    Yeah, you get hit with a virus and the network slows down for a while, but the problem is solved for the future.

    For those who actually think that this is a good idea:

    • First, making any virus/worm that doesn't have unintended sideeffects is basically impossible. Virus writers don't have to care, but software vendors would.
    • Second, there are laws against distributing viruses; I doubt that MS could slip under the FBI's radar if they released a worm.
    • Last, as is pointed out every single time there is a story about patching, there are valid reasons to hold off on a patch. I don't think mission-critical windows servers would be much of a viable option if people had to worry about MS forcing potentially unstable patch installs. (Note to trolls: yes it is possible to run a stable, mission-critical windows server in some circumstances if you know what you are doing)
  113. Are Updates Secure by ScuzzyTerminator · · Score: 1
    Windows Update works by adding an entry into the system registry every time it installs a patch. When users log on to the update tool, it scans their registry and offers them list of patches that have not yet been installed. [From the ZDNet article]

    I'm curious. Does the registry entry include any security, or can any exploit set the registry to deceptively indicate that the host is already protected.
  114. Cooler title! by Anonymous Coward · · Score: 0

    Scott Renfro
    Paranoid Yahoo
    yahoo.com

  115. So now... by TomatoMan · · Score: 2, Interesting

    ...hackers will just point at http://windowsupdate.microsoft.com instead. Right?

    --
    -- http://frobnosticate.com
  116. This is sad... by TitanBL · · Score: 1

    "We found that people had got the registry key for the patch, but not the file," he said, explaining that the error could be triggered by a number of reasons -- from an incomplete installation to a lack of system resources.
    Microsoft did not respond to requests for comment on the Windows Update issue."

    When is Redmond going to realize that people do not have time for this kind of Mickey Mouse bullshit? All of those developers and resources and they cannot even ensure that you are patched when you use windows uodate...

    Then unable to keep their site up for their customers - they switch to linux. Gives a whole new meaning to 'Do more for less'.

  117. FIREWALLS WORK by AnalogDiehard · · Score: 1
    Last night at home, BlackICE caught MSBlast trying to launch. Twice.

    And I'm on a 56K phone modem. Took less than thirty seconds of connection before BlackICE prompted me.

    So I unplugged the phone cable and then configured BlackICE to block MSBlast forever.

    Then I checked my registry, drivers, and running applications for this maggot. No sign of it.

    After reconnecting, BlackICE detected and blocked attempts at MSRPC.

    Firewalls WORK.

    --
    Eternity: will that be smoking, or non-smoking? I Corinthians 6:9-10
    1. Re:FIREWALLS WORK by redstoner · · Score: 1

      You bet they do. I use ZoneAlarm's firewall and it caught that little bugger trying to sneak into my computer. HA HA MSBlast, you didn't get me sucka!

  118. MS Troubles by esdjco · · Score: 1

    Oh man this makes me feel good. As more and more of these happen soon the world will see MS as a company that creates inferior products with serious security flaws that are not addressed for months!

  119. Patent by Arpie · · Score: 2, Funny

    Will someone please patent something like this before micro$oft:

    "Method to prevent worm attacks by changing site hosting locations as many times as needed".

    This way they'll either have to fix the damn holes or pay up.

    I'm joking... but if someone wants to try and the USPO actually accepts it (not totally unlikely) just give me some credit, and some 10% of the profits will do. ;-)

    --
    /* TAANSTAFL */
  120. Re:windows worm OLE exploits might have broke powe by theflea · · Score: 1

    I'm frustrated that I've only heard people saying what "didn't" cause the power failure by the powers that be: It wasn't terrorism or the MS worm. So says the politicians and power grid experts. Of course, they also go on to say things like "I don't know what caused it--it shouldn't be able to happen".

    I also remember hearing months back that some functions of control for public utilities are taking place over the internet. Why not since its cheap and mostly reliable.

    Does anyone remember Homer's rhetorical query to lisa's sarcastic assessment of the killer robots at the amusement park..."Wonders, Lisa, or blunders?"

  121. Holy Misinformation Batman! by kevlar · · Score: 4, Informative


    WindowsUpdate.com did not, I REPEAT: DID NOT EVER Run Linux. The scan from Netcraft only shows that during a particular scan the DNS resolved to Akamai's web caching servers. So Puh-LEASE don't try to start misinformed rumors.

    Linux AkamaiGHost 15-Aug-2003 213.161.82.37 Akamai

    1. Re:Holy Misinformation Batman! by Anonymous Coward · · Score: 0

      Touchy aren't we? Relax. It's only a few billion per quarter.

      Derek

    2. Re:Holy Misinformation Batman! by Anonymous Coward · · Score: 0

      If a DNS resolves in the woods, does it still point to a host?

      If DNS says a machine is windowsupdate.com then, baring a DNS hack, that machine *is* windowsupdate.com. MS voluntarily chose to use Akamai, thus MS voluntarily chose to make make windowsupdate.com be a linux hosted domain.

      PS - Akamai is better named kapakai because they would not sell service to al-jazeera when their English site was being silenced by DOS attacks.

  122. On the Security of an OS.... by jmors · · Score: 1
    I have read over and over again from time to time, in various forums and posts, including here on /. that there is no such thing as a perfectly secure OS so is Misrosoft really all that bad or is it just that they are the most popular OS in use?

    There is one fundamental difference I would like to point out concerning Microsoft OS's vs Linux, BSD and other open source OS's:

    1. With an open source OS those who find security holes and exploits can also patch them themselves since the source code is available. With closed source/proprietary OS software you are at the mercy of the OS Vendor (Microsoft) to provide the appropriate patches when a security hole is discovered.

    2. You have to accept on blind faith that they knew what they were doing when they coded the patch and cross your fingers, hoping that the fix does not turn out to cause more problems than the hole reguarding the running of your system and sometimes essential third party software which you may depend on.

    Yes, it is true that security holes have been found (and patched quickly) in Linux and other open source variants. The major difference, at least to me, is that I have access to both the original OS code containing the bug/hole/problem as well as the code for the patch that fixes it!

    Yes I know that most /. readers already understand this!
    Just my two cents worth here.

    The Matrix IS real but I'm only visiting!

    --
    The Matrix is real... but I'm only visiting!
  123. Re:The FUD on here is amazing by Anonymous Coward · · Score: 0

    Microsoft products cost a lot of money. Linux is free. Both are vulnerable. Get over it.

    MS products only cost money if you pay for them. I've been using MS products for free (for educational purposes of course) without paying a dime to MS - except for Xbox Games. And they provide free patches also!

  124. Military Definitions of "Secured"... by Speare · · Score: 4, Funny

    Reminds me of the old military joke,

    • The reason the Air Force, Army, Navy and Marines bicker amongst themselves is that they don't speak the same language. For instance, take the simple phrase
    • "secure the building".

      The Army will post guards around the place.

      The Navy will turn out the lights and lock the doors.

      The Marines will kill everybody inside and set up a headquarters

      The Air Force will take out a 5 year lease with an option to buy.

    --
    [ .sig file not found ]
    1. Re:Military Definitions of "Secured"... by Anonymous Coward · · Score: 0

      the good and old military humor...
      I never get tired of this...

  125. Timing of Attack? by Cornflake917 · · Score: 1

    I'm thinking if the author of this worm would have made it attack the windows update site a few days ago, when the number of infected computers was at its peak, it would have caused a lot more damage. I'm sure most of us on /. would have figured a way to get the update from somewhere else (assuming WU gets taken out). But what about all the computer illiterate users who were too clueless to update their systems ahead of time in the first place?

    I think there would have been alot more problems if the author predicted the spread of the worm more accurately. Am I correct in assuming this?

  126. Well, News.com isn't _quite_ correct by ddtstudio · · Score: 1

    Apparently, at least from this report at eWeek, Microsoft's official story is that they took the site off-line intentionally to avoid the Blaster attack. Bolstering this is that the page was a redirect; however, discrediting their argument is the fact that getting to the same data is rather clumsy. You think they'd be able to have something better in place.

  127. Don't completely abandon WU.com by sahonen · · Score: 2, Insightful

    Put a locked-down box on windows-update.com that logs all the IP addresses it gets DOSed from, then trace them back to the actual users whose machines were compromised. Then revoke all of those users' XP licenses for being bloody stupid morons who don't know how to apply a patch.

    --
    Make me a friend and I'll mod you up
    1. Re:Don't completely abandon WU.com by wik · · Score: 2, Informative

      They already revoked access to WU for people who used pirated licence keys. As a result, there are plenty of XP installations which will never be patched. I believe this is reckless and self-defeating.

      --
      / \
      \ / ASCII ribbon campaign for peace
      x
      / \
    2. Re:Don't completely abandon WU.com by heli0 · · Score: 1

      " They already revoked access to WU for people who used pirated licence keys. As a result, there are plenty of XP installations which will never be patched"

      Not true. Only people who use the key that came out at the XP launch FCKGW-xxxxx-xxxxx-xxxxx-xxxxx are prevented from updating. If you use the key-gen that came out later then you can use WU.

      --
      Whenever the offence inspires less horror than the punishment, the rigour of penal law is obliged to give way...
    3. Re:Don't completely abandon WU.com by wik · · Score: 1

      Either way, it's a horrible policy.

      --
      / \
      \ / ASCII ribbon campaign for peace
      x
      / \
  128. Disk Operating System by Tired_Blood · · Score: 5, Funny

    While Windows was getting all the attention from their common creator Microsoft, DOS has secretly been waiting for its opportunity to strike at both.

    From the infoworld article:
    The company is cooperating with federal law enforcement officials to investigate the attack, which is the second successful DOS attack against Microsoft.com this month.

    Two successful DOS attacks this month. And what a sense of irony: revolt against the creator by manipulating "the favorite" to do its bidding.

    What's so hard about using a lower-case 'o'?

    --
    This is not my sig.
    1. Re:Disk Operating System by Anonymous Coward · · Score: 0

      revolt against the creator
      MS did not create dos!

    2. Re:Disk Operating System by Anonymous Coward · · Score: 0
      What's so hard about using a lower-case 'o'?

      This would require a journalist to do 10 or 20 seconds worth of research or to already be educated about the field they're reporting on. Therefore, it won't happen.

    3. Re:Disk Operating System by Mostly+a+lurker · · Score: 1
      What's so hard about using a lower-case 'o'?

      He was probably using MS Word and could not work out how to switch off autocorrect: DOS and Dos will be allowed, but DoS will be 'corrected' for you.

  129. mbsa by sdibb · · Score: 1
    I downloaded the MBSA (MS Baseline Security Analyzer), and it works pretty nice. It found 9 patches that couldn't be verified explicitly, with links to the URL on Microsoft's website of where to download the individual packages.

    The only problem, was that 4 of the 9 download links redirected me to http://www.microsoft.com/

    I heard to search the link on Google til I found the actual .exe to download.

    1. Re:mbsa by sdibb · · Score: 1

      Just rebooted for about the fifth time... After installing all of them, the scan still shows that there are still five unpatched vulnerabilities. Even the separate packages don't fix it.

  130. Re:I think the windows update botton on the taskba by Metasquares · · Score: 1

    Against a large and diverse enough DDoS, all the sysadmins in the world together can't deal with it. Microsoft did all that they really could do: remove the target address from the internet, so that the pings never reach their server in the first place. Of course, all it takes is a new variant of the worm targetting windowsupdate.microsoft.com to recreate the problem all over again - and unlike windowsupdate.com, Windows systems use windowsupdate.microsoft.com.

  131. Infoworld Article Contradicts itself! by Anonymous Coward · · Score: 0

    some users reported difficulty reaching [windowsupdate.com] Friday morning.

    "The windowsupdate.microsoft.com and download.microsoft.com sites, which distribute software updates to Microsoft customers, were unaffected by the attack, Sundwall said. Users continued to access and download software patches from those sites throughout the attack, he said."


    The quote is wrong. The previous sentence in the article contradicts the quote! windowsupdate.microsoft.com was too slow to do anything useful last night!

  132. Couldn't MS patch throught the hole? by Anonymous Coward · · Score: 0

    Seems to me that if MSBlast.exe could get in, Microsoft could program their own program that seeks the same vulnerability to get in and patch the system... I'm sure its in the license agreement somewhere, right? Hah.

  133. What? That's supposed to be informative? by Kynde · · Score: 2, Insightful

    This is a garden-variety buffer-overflow exploit of the sort that could just as easily still exist somewhere in Linux.

    Active Directory also provides a way to block this type of worm that *ix doesn't. There wasn't time to patch all of our servers during the outbreak, so one of the guys here implemented a group policy that prevents execution of msblast.exe and teekids.exe on any machine on our network. Once they're all patched, the policy can be removed really easily.


    Is this guy for real?
    This kind of am-an-admin-expert-because-i-have-two-boxes-at-hom e kind of talk should be left at score 1 or so, where it belongs, regardless of wether it praises or bashes M$ or *nix.

    That kind of "block" should not be suggested to other clueless admins! This is exactly why the worm got the 2nd generation where the filename had changed.

    (I'm trying real hard not to mention also the fact that you shouldn't make false claims like about *nix systems. You really think *nix systems, employed for thousands of users all over the world in thousands of universities don't have elaborate user policies that can be administered swiftly and efficiently? Thenagain you're probably just flaming/trolling...)

    (and even you forgot the penis32.exe, which btw is indeed a genius naming stunt! I do loathe the black hats, but every now and then I can't help myself admiring the simplistic beauty in some of their tricks. Thinking how many warning mails that never reached their target because mail filters grabbed them...)

    --
    1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
    1. Re:What? That's supposed to be informative? by zipadax · · Score: 1

      I think you missed the meaning of his post. He is not advocating the use of that particular AD trick by itself, I feel that what he was saying was if you don't have the patches installed, stop it from running with the AD, patch the systems, then take out the AD entry.

    2. Re:What? That's supposed to be informative? by blincoln · · Score: 1

      This kind of am-an-admin-expert-because-i-have-two-boxes-at-hom e kind of talk should be left at score 1 or so, where it belongs, regardless of wether it praises or bashes M$ or *nix.

      I'm work with an infrastructure that numbers in the tens of thousands, but we're not talking about me. As I said, one of my co-workers (who is much smarter than I am) used this as a stop-gap measure because it's humanly impossible for us to patch servers fast enough. It's not a perfect solution, but it will keep our network up in the interim. I figured it might do the same for others as well.

      I do only have one machine at home though, at least that's in use at all.

      --
      "...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
    3. Re:What? That's supposed to be informative? by Mostly+a+lurker · · Score: 1
      penis32.exe ... Thinking how many warning mails that never reached their target because mail filters grabbed them

      LOL ... I never thought of that.

  134. Troll much? by stewby18 · · Score: 2, Insightful

    Because they've endgendered a "computing" culture where users are ... ignorant about the need for patching

    Yeah, curse those bastards for making computers that are usable by people other than us techno-elite snobs.

    Many people simply have other things they care about more than patching their computer. If 95% of people used *NIX, would it have a reputation for being mostly secure? No, because people who don't care would still be the vast majority. Most people should know the importance of basic car maintenence: checking oil, tire pressure, anti-freeze, etc. Many, many people don't bother to do so. When they have problems, is it Ford's fault?

    1. Re:Troll much? by Prior+Restraint · · Score: 2, Insightful

      Most people should know the importance of basic car maintenence: checking oil, tire pressure, anti-freeze, etc. Many, many people don't bother to do so. When they have problems, is it Ford's fault?

      Your analogy is flawed. The product was defective when it left the manufacturer. The automotive analogy to a patch is a recall. The general public views recalls as an indication that Ford (or whoever) is at fault.

      Therefore, Microsoft is to blame.

    2. Re:Troll much? by RealAlaskan · · Score: 2, Insightful
      If 95% of people used *NIX, would it have a reputation for being mostly secure?

      Yes, because 95% of people can't administer a *nix box. They'd have to rely on pre-setup operating systems (just like they do now with Windows!). If those systems were Debian stable, they could be kept secure by a cron job (part of the default install, in this hypothetical situation) which looked like this:

      apt-get update;apt-get dist-upgrade

      If 95% of people used Debian stable, they'd be happy, just like they are with Windows, because they'd be using the same software everyone else is using, and having the same problems as everyone else.

      They wouldn't be having problems with buggy old software on unsecured boxes, and they wouldn't be having the same sort of problems with viruses, either.

    3. Re:Troll much? by (void*) · · Score: 1

      Cars do require that the driver get licenced before they can drive. Eventually, putting a computer on the net would require such a licence too. Has nothing to do with being snobbish, everything to do with the complexity of the instrument and the competency required to use it.

    4. Re:Troll much? by IM6100 · · Score: 1

      Since an automobile inherently consumes oil, leaks tire inflation pressure, consumes anti-freeze, the product is 'defective when it leaves the manufacturer.' Your criticism of his analogy is flawed.

      Try again.

      --
      A Good Intro to NetBS
    5. Re:Troll much? by IM6100 · · Score: 1

      The bandwidth suck that would result from 95% of the people on the Internet regularly running apt-get as you describe would be staggering.

      I won't go into the 'centralized lock-step authority' stuff inherent in your suggestion that everybody regularly and automatically update their OS software in a process they aren't even aware of.

      --
      A Good Intro to NetBS
    6. Re:Troll much? by James+Cole · · Score: 1

      You mean, when using Microsoft products, you are in constant need of patches, just like a car needs gasoline to run?
      I fully agree.

    7. Re:Troll much? by IM6100 · · Score: 1

      And the same is true of any Operating System.

      If you're not aware of that fact, you're asking for trouble.

      --
      A Good Intro to NetBS
    8. Re:Troll much? by Anonymous Coward · · Score: 0

      apt-get update fetches a small number of text files from your configured debian mirror.

      if the installer did something intelligent like ask where you are (so it can find a close mirror), the problem you describe would never exist.

      everybody *SHOULD* regularly update their OS and automatic measures are a VERY SMART way to do it. I'm sure you're the same fucking troll who would say 'well windows update has fixed this bug for a month' and say 'centralized lock-step authority' in the same fucking post.

      Fuck you and your fucking ignorant, high horse.

    9. Re:Troll much? by Anonymous Coward · · Score: 0

      yeah, curse those bastards for making computers that are usable only by imbeciles..

    10. Re:Troll much? by RealAlaskan · · Score: 1
      The bandwidth suck that would result from 95% of the people on the Internet regularly running apt-get as you describe would be staggering.

      It might be kind of hard on the debian mirrors. I'm sure that the problem could be dealt with.

      It wouldn't be nearly as bad as you seem to think: Debian ``stable'' means Debian ``never changes''. Except for security patches, and the once-every-year-or-two transition from Potato-->Woody or so, there would be essentially no load.

      I won't go into the 'centralized lock-step authority' stuff inherent in your suggestion that everybody regularly and automatically update their OS software in a process they aren't even aware of.

      You mean like when they use any recent version of Windows,and use the updates? Of course, they wouldn't get a less-favorable version of the licence with each new upgrade, they wouldn't get spyware added with each new upgrade and they wouldn't get their applications broken with each new upgrade. But other than those omissions, it would be just like the current situation.

      Folks seem to live with the current situation, either by never upgrading, or by upgrading and taking their lumps. I'm sure that the clueless could learn to find something else to complain about if their computers stopped breaking. The cluefull few could simply change the cron job from:

      apt-get update;apt-get -y dist-upgrade

      to

      apt-get update;apt-get -u dist-upgrade

      so that they can review the proposed updates. With stable, there's not much point in reviewing changes for a workstation. Changes are sure to be security patches, and pretty sure not to break anything.

  135. Mutations are guaranteed by theolein · · Score: 1

    I imagine that given that there are already variations that use names that will get blocked by kiddie protection filters and spam filters that block porno mails, that any attempt by MS to sidestep the domain name of WU will soon be nullified by the same people putting out the current variations.

    Although I'm aware that many users simply don't know how to patch their systems often or don't care, I am truly amazed at the sheer number of worms that do manage to get through, no matter what. I am even more surprised at MS' rather clumsy responses every time a worm gets through. Oh well.

  136. Re:I think the windows update botton on the taskba by PainKilleR-CE · · Score: 1

    The IE tools menu will eventually get you there, but it definitely seems to be taking a different route. Of course, this is the first time I've ever gone to Windows Update that way, I usually just type in http://windowsupdate. (hit down arrow, hit enter) if I have an IE window open or use the start menu link, both of which go to the same old windowsupdate.microsoft.com site.

    --
    -PainKilleR-[CE]
  137. Missing part of the equation by Iowaguy · · Score: 1

    Linux, BSD or other may not get as many attacks as windows does even wiht high market share. Karma does catch up with us all. MS has business and ethical practices that frankly, piss a lot of people off. "A wise philospher once said that anger, hate, fear, these are the ways of the dark side, and the dark side makes you strong."

    There are lots of huge companies. Even the occasional near monopoly. MS gets hit more than them. What goes around comes around.

    my two cents
    -Iowa

    --
    "He who laughs last, didn't get the joke."-Cap
  138. Re:windows worm OLE exploits might have broke powe by batkins · · Score: 2, Interesting
    Actually, it's called RPC (Remote Procedure Call). And the power grid doesn't use RPC (or OPC for that matter). No critical systems like that are run with MS software.

    Get a clue.

  139. Current Situation by JamesP · · Score: 1

    windowsupdate.com does not resolve: pinging or tracert does not work

    windowsupdate.microsoft.com works (asks for I.E. 5)

    microsoft.com no problems (thay have a nice link on how to stop the baster worm though...)

    Microsoft Instructions on "What You Should Know About the Blaster Worm and Its Variants"

    --
    how long until /. fixes commenting on Chrome?
  140. Hotmail.com down? by MoxFulder · · Score: 1

    Has anybody else noticed that hotmail has been down all day today? I haven't been able to login from my home computer (md.comcast.net) or work computer (umd.edu), or from a couple other Linux boxes at various points around the country...

    1. Re:Hotmail.com down? by dougnaka · · Score: 1

      just logged in, haven't heard this anywhere else... dont think it was down

      --
      My Linux Command of the Day site : LCOD
  141. strace - truss for windows 2000/XP by tekan · · Score: 1

    "Strace for NT is a debugging/investigation utility for examining the NT system calls made by a process. It is meant to be used like the strace (or truss) on linux and other unix OSes."

    http://razor.bindview.com/tools/desc/strace_read me .html

  142. Dear Jamie by Keith+Russell · · Score: 2, Insightful

    Interesting article. But did you have to be such an asshole about it?

    Yours truly,
    Keith

    P.S.: If your power is still out tonight, I hope this burning karma lights your path.

    --
    This sig intentionally left blank.
  143. No third party distribution of patches by Anonymous Coward · · Score: 5, Interesting

    Notably, Microsoft refused to give permission to ISPs to burn CD's or make floppies with the Blaster patch on them. I heard of one outfit that had their lawyer contact MSFT to make sure that they were kosher before giving them to customers. Microsoft refused. As it turns out, stating that the users could easily download the patches directly, even if they had the shutdown bug and were dialing in to download a 1.2 MB patch.

    I have no sympathy for MSFT getting DOS-ed. The fuckers deserve it, and they were hoist by their own petard. Sure, there is some nitwit out there that acted on as explout that was known for at least a month, but WTF? What is the problem with letting ISPs distribute the patch to fix this thing?

    The ISPs are burning time and support lines over it, bandwidth is getting hosed by the packets on the affected ports, filtering ports helps (but doesn't eliminate the problem). Essentially, third-party companies (ISPs) asked for permission to help put out this fire, and Microsoft gave them a big "fuck you" and I am somewhat gratified by the whole thing.

    Fuck you, Microsoft. Here's hoping you get more of the same.

    I might post the emails discussing the attempt to get authority to help spread the patches somewhere, but I'm not anxious to cause a slashdotting of my own weenie ISP's servers.

    1. Re:No third party distribution of patches by Mostly+a+lurker · · Score: 2, Interesting
      Notably, Microsoft refused to give permission to ISPs to burn CD's or make floppies with the Blaster patch on them.

      I had not heard this. Do you have any references? On the face of it, this could lay MS open to legal action by the ISPs for damages that could and should have been prevented.

    2. Re:No third party distribution of patches by GordoSlasher · · Score: 2, Funny
      From an article in a local newspaper
      In Colorado, Comcast and Qwest said customers who couldn't access the Internet bombarded the company with calls. The companies directed their customers to Web sites offering software fixes.
      That's some really useful advice for someone who can't access the Internet! Maybe they expect granny to drive to the web site?
    3. Re:No third party distribution of patches by Anonymous Coward · · Score: 0

      The isp-ceo mailing list at isp-ceo.com is where I saw it. The archives of the list at that site are not public, however. Try posting to the isp-wireless list because there is some cross-pollination, and there may be someone there who can point you to the person who was trying to get permission from MS.

  144. Why it actually "runs Linux" by dodell · · Score: 2, Informative

    And, if you read further about how Netcraft actually works, you will notice that they state that firewalls and other sorts of software can make it appear that a server's software is actually running on an OS that it would otherwise be impossible to run on. This is why you will find IIS running on Solaris, FreeBSD and Linux. Read first.

    1. Re:Why it actually "runs Linux" by dodell · · Score: 1

      Oh, and by the way, windowsupdate.microsoft.com and windowsupdate.com have always forwarded to that same www.v4.windowsupdate.com address. From where do you get this info!?

    2. Re:Why it actually "runs Linux" by mlk · · Score: 1

      But it still means Microsoft used a Linux-based firewall, instead of a Microsoft based one (what they had been using before hand).

      So still funny, but no as funny as them moving to a Unix/Apache web server.

      --
      Wow, I should not post when knackered.
  145. Breaking news tomorrow by the_one_smiley · · Score: 3, Funny

    The impending DDoS attack on Microsoft scheduled in the MSBlast worm was drastically mitigated by Microsoft's DNS shuffing, the diligent patching by systems administrators around the world, and the lack of electricity in several population centers. However, it was replaced by a much more potent DDoS attack by people checking to see if Microsoft's site was dead yet...

    --
    "Never put off for tomorrow what can be avoided altogether"
  146. Re:really... (repost formatted) by Poltras · · Score: 1

    Wait a minute... (Hop in discussion)
    When you install Windows XP, when creating the admin account, it tells you it shouldn't be the account you would use your computer with it.

    When you create a new account, it asks you weither it should be "normal" or "user with power" account. User with power aren't admin, before you flame. They can install and remove programs, but not install services and such. Services can be installed with privileges only if you are admin, etc etc etc. Funnily, you find some stuff in the security doc of Windows, cut/pasted from *x.

    When a software become widespread, all of a sudden many users drop standards. Each user you add to a system, each times your system becomes dumber. I personnaly find that for a software with that many code lines, the bugs and holes are still pretty low.

    I admit I respect Unix (BSD at home) for security, but Windows is not THAT far behind. You can't blame a system to be dumb when the ones using it are.

    I've updated my computer a month ago for the security hole, and magically I don't have any virus problem right now.

  147. Microsoft hosed their own update service! by KE1LR · · Score: 5, Informative
    Microsoft has a free tool called " SUS " which is a localized version of Windows Update - you run it on a W2K server in your enterprise and then redirect your clients to get their automagic updates from the local server instead of going to MS directly.

    The SUS server is supposed to synchronize itself (manually or automatically) with Microsoft's servers to get the latest updates, and you get a chance to approve them for distribution to clients. Not a bad idea, and it seems to work OK.

    However, the URL that's coded into SUS to synchronize with updates is -- wait for it -- a windowsupdate.com URL!

    Error Message:
    "Failed to download from URL 'http://www.msus.windowsupdate.com/msus/v1/aucatal og1.cab'. (Error 0x80072EFD: Unable to connect to the server.)"

    Anyone using SUS to update their client machines is now stuck with their current update set until Microsoft sets up a new site to sync with and documents how to change the URL that SUS uses to whatever one they come up with.

    Lame.

    1. Re:Microsoft hosed their own update service! by Hecubas · · Score: 1

      ARGH!!

      I just installed SUS this morning on one of my companies 2000 servers in order to update our 50 Win2k desktops in a controlled manner. I was thinking "Gee, MS is actually doing a good thing here".

      In any case, SUS is better than setting all those desktops to simultaneously flood our internet connection while trying to sync up with windowsupdate.com.

      ARGH!!

      --
      hecubas

      --
      Hecubas
    2. Re:Microsoft hosed their own update service! by Plug · · Score: 1

      50 Win2k desktops, you say?

      HFNetChkLT should be exactly what you wanted.

    3. Re:Microsoft hosed their own update service! by Mostly+a+lurker · · Score: 1
      the URL that's coded into SUS to synchronize with updates is -- wait for it -- a windowsupdate.com URL!

      This is amusing (and further embarrassment for MS) but should not take much to fix. There is a configuration option in SUS that allows setting of the synchronization server.

  148. Re:I think the windows update botton on the taskba by oohp · · Score: 2, Informative

    Well they bought a Romanian AV company called RAV. They used to have anti virus products for Linux and FreeBSD (to scan for wind0ze viruses of course), but no more now.

  149. Wow by Cyno · · Score: 2, Funny

    With Microsoft getting DOS attacks and viruses all the time one might begin to think that someone doesn't like them. Hrmm. Wonder who that could be..

  150. Microsoft Security Bulletin MS03-026 by Valiss · · Score: 3, Informative

    I don't know why this became a big deal. Ok, I lied. It became a big deal because of users who did not patch their systems (for whatever reason). But it isn't like this patch is new. It was originally posted on July 16, 2003. They just revised the bulletin because of the outbreak.

    From MS's site:

    Why have you revised this bulletin?

    Subsequent to the release of this bulletin Microsoft has been made aware that additional ports involving RPC can be used to exploit this vulnerability. Information regarding these additional ports has been added to the mitigating factors and the Workaround section of the bulletin.

    If I have installed the patch provided with the original bulletin, am I still protected?

    Yes. There has been no update to the patch itself, and the patch will still correct the vulnerability. This additional information is being provided to those customers who may require a temporary workaround until they can apply the patch.


    I wish I could make my friends, family, people I know read these security reports on their own, but they never do.

    --

    -Valiss
    1. Re:Microsoft Security Bulletin MS03-026 by Spy+Hunter · · Score: 1

      Oh come on. MS releases a new security patch every other day, if not more often than that. It's a royal pain to keep a Windows system updated, and it's not something that can or should be expected of someone who just wants to check their email three times a week, and visit a website now and then. And heaven forbid you ever get behind, otherwise you could end up with 60+ MB of patches to download. We recently bought a new computer, and once we brought it home I found that to just download the security patches that had come out since Windows had been installed at the factory took over 5 hours over our dialup! Is it any wonder there are unpatched systems out there?

      --
      main(c,r){for(r=32;r;) printf(++c>31?c=!r--,"\n":c<r?" ":~c&r?" `":" #");}
  151. Re:New CFO's? by Anonymous Coward · · Score: 0

    Maybe this has something to do with the recent announcement that EACH Microsoft division would have its own CFO!

    This is right out of Dilbert!

  152. An easier way to pay... by raygundan · · Score: 1

    Select and buy your favorite combination of solar, wind, gas generators, or whatever else your locale will support. Call the power company and tell them to disconnect you, and would they PLEASE get their damn wires and poles off your property.

    1. Re:An easier way to pay... by Cromac · · Score: 2, Interesting
      Select and buy your favorite combination of solar, wind, gas generators, or whatever else your locale will support. Call the power company and tell them to disconnect you, and would they PLEASE get their damn wires and poles off your property.

      It's definately something we've considered. Based on where our house is and living in the Pacific NW wind seems like may be our best option, fortunately windmills are getting more efficient all the time.

      I think I'll just leave PSE's wires in the ground and disconnect them at the box though. If they came to dig them up they'd sever my cable, phone and water lines for sure. :)

  153. Worms don't care about root by Admiral+Burrito · · Score: 1

    Worms, such as the latest one that attacks Windows RPC services, only need to make outgoing TCP connections in order to propogate. This does not require root access. The fact that network daemons under *nix don't usually run as root has no impact on worms; worms don't need root.

    Root access would be needed for viruses (that modify executables), more sophisticated worms that install rootkits to hide their presense (has that been done yet?), and human attackers that want to snoop around users files or sniff network traffic or install rootkits. A simple worm is one of the few cases where containing a compromise to a user account is not a major win.

  154. As Reliable as Electricity and Water??? by Anonymous Coward · · Score: 2, Funny

    However, even more important than any of these new capabilities is the fact that it is designed from the ground up to deliver Trustworthy Computing. What I mean by this is that customers will always be able to rely on these systems to be available and to secure their information. Trustworthy Computing is computing that is as available, reliable and secure as electricity, water services and telephony.

    Today, in the developed world, we do not worry about electricity and water services being available. "

    I guess Bill hasn't seen the news in the last 24-48 hours. I haven't seen a virus yet that can take down all systems in less than nine seconds. If the reliability of power is what Bill aims to achieve we (MS) admins will always have a paycheck...

  155. Slashdot, change your shameless plug now by Joe+Enduser · · Score: 1

    A new story will be posted soon, but subscribers get enough time to think about rude stuff to write up, before 300+ posts are posted.

  156. It's about the User by nonameisgood · · Score: 1

    To all of the programmers:

    User interface IS THE ISSUE.

    The Mac OS X implementation uses non-privileged user for all normal operations, then and ONLY THEN, does it propmpt for an admin password.

    Contrary to what you all think is right, I keep my more or less secured Linux box running as root user for one main reasons: I routinely (daily) install or modify systems USING THE X GUI, which does not allow me to shift on the fly to root and back for things like drag-and-drop of files.

    Call me crazy, but I thought this whole crazy computer thing was to make our lives easier, not to burden us with being our own little system administrator.

    Users will not accept systems which do not provide to them what they need (a word processor, a game platform, or whatever.)
    Don't blame the dumb user for the poorly made system or poorly written software - IT IS YOUR FAULT IF SOMEONE HAS A PROBLEM WITH YOUR PROGRAM.

    If you can't grasp that, it is obvious why software programmers aren't really engineers. (With apologies to those of you who do get it.)

    --
    Faith is the very antithesis of reason, injudiciousness a critical component of spiritual devotion. Jon Krakauer
    1. Re:It's about the User by Anonymous Coward · · Score: 0

      "The Mac OS X implementation uses non-privileged user for all normal operations, then and ONLY THEN, does it propmpt for an admin password."

      Funny.. last I checked Red Hat does do that.

      "Contrary to what you all think is right, I keep my more or less secured Linux box running as root user for one main reasons: I routinely (daily) install or modify systems USING THE X GUI, which does not allow me to shift on the fly to root and back for things like drag-and-drop of files."

      As I said.. try redhat.
      If the issue is a GUI file manager...

      Alt-F2 (shortcut for Run dialog in gnome)
      sudo nautilus

      And if you think your Linux box is "secure" when running as root.. you, sir, have quite a bit to learn about how operating systems work.

      "Call me crazy"
      No, I'll just call you ignorant and lazy.
      People like you are the reason worms and viruses are so widespread.
      Learn how to use your computer so the rest of us don't have to put up with all the worms flying out of your ethernet card.

      Someone who thinks they know how to run a computer are worse than people who know they can't. The ones who know they can't do go around giving people (wrong) advice!

    2. Re:It's about the User by nonameisgood · · Score: 1

      You don't read well do you? The whole point of my reply was that the interface must allow the typical user a useful computing platform. The typical user does what s/he must to function without worrying about overhead.

      You also don't understand that there are various levels of security...one of which is physical - to which I was referring. As for my kind being the typhoid Mary of computerland, let's lay the blame on a system design that misses several basic design concepts, such as reliability and maintainability.

      --
      Faith is the very antithesis of reason, injudiciousness a critical component of spiritual devotion. Jon Krakauer
  157. Bug rept: Pol0 suxxors by Anonymous Coward · · Score: 0

    Description: WTF? Your bugfix doesn't work! LOL!

    Repro steps:

    (1) Lauch msworm on a zombie farm
    (2) Use IRC bot to reset dates and trigger attack

    Expect:
    Moderate DDoS to slow down new site

    Observe:
    No effect.

    Note: Micro$oft has moved to a caching company to support this new domain. Akamai has bandwidth to burn and enuf points of presence that we'd have to take down the whole net to have an effect.

    Try again, Luser!

  158. Boasting Bill by cyberwave · · Score: 2, Interesting
    From Bill Gates' memo: "We have done a great job of having teams work around the clock to deliver security fixes for any problems that arise. Our responsiveness has been unmatched - but as an industry leader we can and must do better"

    Last time I checked, most everybody, on average, beats microsoft in terms of speed of security fixes. So I suppose unmatched, because Microsoft has been completelysurpassed.

  159. Palladuim & DRM by FedeTXF · · Score: 1

    Bill is setting up the mood for the industry to beg for palladium and DRM...

  160. Re:I think the windows update botton on the taskba by Anonymous Coward · · Score: 0

    The best way to do it is a few days before the actual IP address change, go in and set the TTL on the zone file to 15 minutes. Let that propogate to all of the cashing DNS servers. Then when you do update the IP address on your DNS server, the changes propogate to everybody within 15 minutes guaranteed.

    Of course in the interim, your DNS server will have a pretty heavy load. You probably don't want to keep it at 15 minutes for any longer than you need!

  161. Prepare to pay thru the colon by Archfeld · · Score: 5, Interesting

    Here in CA you have to fund the switch which allows you to feed from your supply to the lines, even if you don't EVER want to feed back, PG&E got some help in the legislation, this run s around 10K minimal. The CA government in its infinite wisdom also institutied a Farking tax on power feedback, in order to offset the cost of people leaving the system while it is so deep in financial trouble, so now even if you DON'T USE the power grid, you are required to pay a tax on the approx. amount you would use....Our rural neighborhood association just went through the governmental hoops to get this working...what a friggin nightmare.... Unless you have several hundred potential users, there is no way this is financially feasible thanks to our friends in government, always out to protect corporate interests at the expense of taxpayers freedom and choice.....

    --
    errr....umm...*whooosh* *whoosh* Is this thing on ?
  162. DoS of the /. Variety by mpeg4codec · · Score: 1

    Is anyone concerned that putting a link to the new [?] Windows Update site on the /. front page would cause a DoS in itself? Granted, the traffic woudln't be as great as the Blaster DoS, but the Slashdot Effect is pretty strong.

  163. No... by Anonymous Coward · · Score: 0

    7) Loss.

  164. MS Worms - walk in the park by Capt_Troy · · Score: 1

    How difficult can it be to write one of these things? You don't even have to be a hacker at all. all you do is.

    1) Wait for a MS critical update to come out.
    2) Write code to take advantage of the documented flaw. (take a month or two to write it, what the heck)
    3) release.

    Then all the yay-hoos that didn't upgrade their systems (when their computers probably told them to) get borked. if people would only apply security patches... ahh well...

    T.

  165. Software Update Services by Sprinkels · · Score: 1

    SUS = Software Update Services.

    With SUS you can use the automatic update feature of Windows 2k/XP/2k3 to download and install updates automaticly (or with your own approval for each update).

    It's kind of the Microsoft equilevant of "apt-get update && apt-get upgrade".

    It's based on the same protocol as Windows Update, so therefor it requires IIS.

  166. Re:I think the windows update botton on the taskba by Darby · · Score: 1

    they will say there are no updates available, even when there are. I have confirmed this twice when I KNEW there was an update that was not installed on the laptop (sometimes i go two weeks without using).

    I just cleaned up my friend's computer who got infected with blaster.
    I went to Windows update, and it said that he needed no updates which is, of course, false since otherwise he wouldn't have gotten infected in the first place.

    He's running XP home which has the auto update set to download patches but not install by default.

    So after some digging around I realized that Windows update was correct that there were no newer patches available for download, but he had never installed any of them, so it was wrong that none were needed.

    I wonder if something similar might have happened in your case?

  167. Re:The FUD on here is amazing by Anonymous Coward · · Score: 0

    "if I were Dictator of the World."

    That is what all you Cheney-neocons strive for, isn't it? To rule the world as a dictator?

  168. even windows has a hosts file by gregm · · Score: 1

    Why couldn't you just redirect windows.com to one of the ips they choode for their new service,using your hosts file or with your dns server?

  169. Re:windows worm OLE exploits might have broke powe by petwalrus · · Score: 2, Informative
    Actually this isn't so far off:

    http://www.matrikon.com/drivers/opc/whatisopc.asp

    OLE for Process Control (OPC) is a new technology designed to bridge Windows based applications and process control hardware. It is an open standard that permits a consistent method of accessing field data from plant floor devices. This method remains the same regardless of the type and source of data. Therefore, end users are free to choose the software and hardware that meets their primary production needs, without having to consider the availability of proprietary drivers.

    OPC components fit into two categories: OPC clients and OPC servers. A client is typically a data sink -- an application that uses data in some way, such as an MMI or SCADA package. A server is a data source -a device specific program that collects data from a field device, and then makes it available to an OPC client.

    and DCOM definately appears to be in the mix as well:

    http://www.opcfoundation.org/Downloads/White%20Pap ers/OPC,%20DCOM%20and%20Security.pdf

    Perhaps the lusers who are uneducatedly blaming the blaster virus aren't entirely wrong.

  170. Some Stats by Bruha · · Score: 1

    Curious using the scan tool on my network for dsl

    x.x.x.15: patched with KB823980
    x.x.x.4: unpatched
    x.x.x.12: connection to tcp/135 refused
    x.x.x.66: patched with KB823980
    x.x.x.18: patched with KB823980
    x.x.x.16: patched with KB823980
    x.x.x.21: connection to tcp/135 refused
    x.x.x.101: connection to tcp/135 refused
    x.x.x.109: connection to tcp/135 refused
    x.x.x.99: connection to tcp/135 refused
    x.x.x.85: connection to tcp/135 refused
    x.x.x.82: connection to tcp/135 refused
    x.x.x.131: unable to determine patch status; please investigate
    x.x.x.79: patched with KB823980
    x.x.x.73: unpatched
    x.x.x.80: connection to tcp/135 refused
    x.x.x.76: connection to tcp/135 refused
    x.x.x.74: unpatched
    x.x.x.78: unpatched
    x.x.x.135: patched with KB823980
    x.x.x.136: patched with KB823980
    x.x.x.105: connection to tcp/135 refused
    x.x.x.139: patched with KB823980
    x.x.x.142: patched with KB823980
    x.x.x.130: connection to tcp/135 refused
    x.x.x.147: connection to tcp/135 refused
    x.x.x.151: patched with KB823980
    x.x.x.162: patched with KB823980
    x.x.x.183: connection to tcp/135 refused
    x.x.x.166: connection to tcp/135 refused
    x.x.x.164: connection to tcp/135 refused
    x.x.x.200: connection to tcp/135 refused
    x.x.x.186: connection to tcp/135 refused
    x.x.x.203: patched with KB823980
    x.x.x.160: patched with KB823980
    x.x.x.171: connection to tcp/135 refused
    x.x.x.207: connection to tcp/135 refused
    x.x.x.208: connection to tcp/135 refused
    x.x.x.206: connection to tcp/135 refused
    x.x.x.205: connection to tcp/135 refused
    x.x.x.212: patched with KB823980
    x.x.x.225: patched with KB823980
    x.x.x.228: patched with KB823980
    x.x.x.221: connection to tcp/135 refused
    x.x.x.215: connection to tcp/135 refused
    x.x.x.237: patched with KB823980
    x.x.x.234: patched with KB823980
    x.x.x.226: connection to tcp/135 refused
    x.x.x.238: connection to tcp/135 refused
    x.x.x.243: connection to tcp/135 refused
    x.x.x.246: connection to tcp/135 refused
    x.x.x.254: patched with KB823980
    x.x.x.253: patched with KB823980
    x.x.x.224: patched with KB823980

    So about 1/10+- remain unpatched.

  171. The real reason? by Anonymous Coward · · Score: 0

    The real reason is either:

    Conspiracy A - Uncle Bill takes after Uncle Sam

    The blackouts were engineered by Microsoft as a preemptive strike against the vast quantity of infected ("terrorist") computers in the Northeast while it attempted to deal with the worm....

    OR:

    Conspiracy B - Some guy really desperate to hit Microsoft

    The worm author (or someone who really despises Microsoft) was a powerplant worker and sabotaged the systems so that all the infected computers in the Northeast would restart simultaneously as the power came back on, all attacking Microsoft at once.

    Conspiracy nuts, pick your story!

  172. Consider Novell's Zenworks by Anonymous Coward · · Score: 0

    but I did very recently start a job where I desperately need to deploy something like this

    Have a look at Novell's Zenworks. It has all the functionality you need, and Novell has the best security in the business.

  173. Re:I think the windows update botton on the taskba by subsolar2 · · Score: 4, Informative
    Going to 'tools, windows update' in internet explorer takes you to a redir site on microsoft.com, which attempts to forward you to windowsupdate.com NOT windowsupdate.microsoft.com .. even still (~3PM EST). you'd think they'd at least fix that if they were fuckin with the dns..
    You may not know this, but when you change an entry in DNS, it is not available to everyone for a while. This is due to caching (all ISP DNS servers are caching servers, of course). For instance, the AOL servers may have gotten the ip for the domain at 8am, and if it doesnt expire for
    You may not know this, but you are incorrect ... the redirection has nothing to do with DNS dns enteries propagating and everything to do with MS's web site/server. It's redirecting to the old URL and not the new one.

    -1 Overrated for that on a +5 post

  174. Re:I think the windows update botton on the taskba by spectral · · Score: 1

    That doesn't apply, it's a www.microsoft.com/redir.asp?blabla crap or something like that.. so if www.microsoft.com works, then they should have fixed that redir to do an http refresh to windowsupdate.microsoft.com immediately.

    They appear to have fixed it by now, as evidenced by the reply I made to my comment. yes, I know how DNS works. It's quite a pain when my friend's computer (which I mostly handle the admin tasks for) loses internet (business class RR in rochester sucks) and the DNS is fucked up for days. I might not have it set up properly or something, but I know about the time it takes to propogate :)

  175. What country are you from? by TheOnlyCoolTim · · Score: 1

    Because once you tell me I am going to do some research and you better be damn sure that your country has had uninterrupted power since the turn of the century.

    I am going to suggest that the U.S. alert the U.N. to put in place an emergency mission to provide you with a clue.

    Tim

    --
    Omnia vestra castrorum habetur nobis.
    1. Re:What country are you from? by Anonymous Coward · · Score: 0

      He's got a clue. Your past since the turn of the century is irrelevent. Your infrastructure is falling apart now and it's too late to do anything about it.
      It's attitudes like yours that allowed it to happen unchecked.

    2. Re:What country are you from? by Winston+Orwell · · Score: 1

      Well, who cares which is my contry ? (i'm not the anonymous coward any more, but the same guy). I can read, speak english and access the internet. And also, I have power at home to listen to some great King Crimson music. And I can assure you, I never had any ininterrupted power since I was born, and I pay something like 25 euros a month for it (much less than you, I guess). Well, you did't reply to any of the points I made. I can assume I am right. If you need some text explanation, I may find some time. Cheers

    3. Re:What country are you from? by Anonymous Coward · · Score: 0

      I wonder how many resolutions it would take for him to actually get the clue?

    4. Re:What country are you from? by Anonymous Coward · · Score: 0

      You didn't make any points. Even in a pitiful slashdot debate, your post looks feeble. Your whole post was just you making fun of the USA because one small fraction of it had a power outage.

      Filthy foreigner, you should learn to keep your stupid, uneducated mouth shut until one of your betters needs you to pull a cart or something.

    5. Re:What country are you from? by Winston+Orwell · · Score: 1

      Well. Uneducated, I can still speak another language (american). Are you at least uneducated ?

      There is less than 300M inhabitants in USA www.census.gov, and the british times estimates 50M of them can't have electricity. Thus the small fraction you're speaking about seems to be something like 16.67%. Not so small in my opinion. And this part that cannot have electricity counts for much more than 16.67% of the economical and political power of the USA.

      And you know, I remember than just last year, it is your silicon valley that couldn't turn on their computers because there was no electricity !! People said at the time that it was because California didn't do what was required to provide people with enough electricity, that it was just a local problem and couldn't happen elsewhere in USA...

      For your information, I did actually make some points. I would kindly and respectfully suggest you read my post again.

    6. Re:What country are you from? by Anonymous Coward · · Score: 0

      There is less than 300M inhabitants in USA www.census.gov, and the british times estimates 50M of them can't have electricity. Thus the small fraction you're speaking about seems to be something like 16.67%. Not so small in my opinion

      Don't forget to factor in the fact that this outage only lasted hours, maybe a day or two. And that's since what, the 70's? Lesee, what is one day out of 20+ years?...

  176. Forget about all that Gates bidness... by Durindana · · Score: 1


    and let's concentrate on the

    Lip + service = $$$!

  177. Right ON! by DesScorp · · Score: 1

    "Personally, I think we should (build) some new nuclear power plants...I personally wish the US would update it's power infrastructure, and I'd be willing to pay for it."

    You got it, pardner. This is one of those things where they could raise a tax somewhere, and I wouldn't complain about it. ESPECIALLY if it was for new nuclear plants. Environmentalists will be hysterical, but so what. Europe, which is supposedly faaar ahead of us in terms of civilization and good ideas, draws as much as 50 percent of its power from nuclear reactors in countries like France and Sweden.

    Not that I wouldn't mind some more natural alternatives. I'd LIKE to see things like advancing wind farm and solar panel technology. Bur right now no other alternatives will provide NEAR the power we need except for nukes or more fossil fuel powered plants.

    The grid is indeed horrendous and old, and President Bush himself said as much today, urging that it be upgraded.

    --
    Life is hard, and the world is cruel
    1. Re:Right ON! by darien · · Score: 1

      The grid is indeed horrendous and old, and President Bush himself said as much today, urging that it be upgraded.

      Despite this, I do think it actually should be upgraded.

  178. Re:Corrected link for Infoworld article by Anonymous Coward · · Score: 0

    The parent was modded Redundant, but I can't find any other comment with a working link. I notice the URL works for either infoworld.com or archive.infoworld.com but NOT for www.infoworld.com (which was the URL given in the main post); it just gives a "Not Found: Nothing matches the given URI" error. So somebody please either fix the main post by putting a working URL there, or at the very least mod up this comment's parent.

  179. Re:I think the windows update botton on the taskba by aWalrus · · Score: 3, Interesting

    That line of reasoning is hogwash, and part of the self-apologizing crap us Software Developers keep throwing out.

    It used to be that we could blame the users for running executables they receive via emails. We demanded common sense, and said that it was user error, not Software Developer error. This time, the mere act of being plugged into a network or the Internet is enough to get the computer infected. So what do we do? We say Damn those lusers because they didn't install their latest security patches!.

    That's a big, smelly load of shit. Systems administrators should be required to read bugtraq and keep their systems patched. Users should only show common sense. We can't ask them to do these things. There are people working with computers that actually use them as tools to do work, rather than as objects of worship, as we geeks do. They don't want to know about driver install woes or our petty flavour of the month.

    We should be bounds-checking our mallocs rather than demanding users take the time to fix the faulty products we put out.

    --
    Overcaffeinated. Angry geeks.
  180. Well thank GOD by Sevn · · Score: 1

    That Linux was there to save Microsoft. It's truly great that Microsoft could benefit from the incredible POWER of Linux to balance the load to one of their sites. Wow. I'm definitely going to give this Linux thing a try now since even Microsoft ended up having to use it. It must be incredible!

    --
    For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
  181. this is secure by Anonymous Coward · · Score: 0

    http://secure.opera.com

  182. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 1

    The best way to do it is a few days before the actual IP address change, go in and set the TTL on the zone file to 15 minutes. Let that propogate to all of the cashing DNS servers. Then when you do update the IP address on your DNS server, the changes propogate to everybody within 15 minutes guaranteed.

    Of course in the interim, your DNS server will have a pretty heavy load. You probably don't want to keep it at 15 minutes for any longer than you need!


    This is EXACTLY what I do, to the letter and to the minute. It works on 99% of caching servers (some are setup to override TTL, but they are rare). I run dedicated DNS servers, even tho the load is in the 0.02 range, mainly because of security, so the extra burden is not a problem. This also helps by having the extra capacity for an amatuer DOS attack.

    --
    Tequila: It's not just for breakfast anymore!
  183. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 1

    Twice I kept checking update over and over. Both times I tested it this way, within 30 minutes it magically found an update, so this tells me their servers were either overloaded and just telling me this to get me to leave, or they have a bug. My guess is they were at max load, and don't really care about security enough to just say "we are at max load". I guess looking good is more important that serving us.

    --
    Tequila: It's not just for breakfast anymore!
  184. Uhhhh, No by DesScorp · · Score: 5, Insightful

    "why would i want to help allievate the situation? hell, i get to have all my computers attack microsoft for free! and legally! wohoo! sick 'em!"

    I know (think) you're joking, but while we can moan all we want about how Microsoft should design software that's more secure, we can't do anything about existing systems. And windowsupdate was the fastest, easiest way for the non-tech public to protect and repair themselves. Those of you out there that view this impending attack and the shutting down of windowsupdate as a good thing are very shortsighted.

    Maybe you don't give a shit about all of those other users out there that use Windows. Maybe you're happy this is happening. Fine. But rest assured, it's not going to cause people to rebel against Microsoft, like many of you are hoping. There will be no enlightenment and mass exodus to Linux or BSD or OSX. This is going to get blaimed on "hackers". And we all know hackers hate God, hate America, root for Saddam, get pentagram tattoos on their foreheads....and use Linux. Pretty soon it'll be "yeah, I saw those Linux guys bragging on slashdot.org that they took windowsupdate down!"

    IBM's reps will be going "yeah, thanks heaps for the positive image, slashdotters.........fuckers".

    Make fun of people that run Windows all you want, but don't assist in, or support the disabling of one of their few effective means of defense.

    --
    Life is hard, and the world is cruel
    1. Re:Uhhhh, No by malfunct · · Score: 1
      Windows update didn't shut down, just the easy to remember domain name. The windows update service is still and always was running at windowsupdate.microsoft.com and windowsupdate.com was just pointing to the same servers.

      Your point is well taken, but windowsupdate is rather unaffected (the start menu icon still goes to the right place).

      --

      "You can now flame me, I am full of love,"

    2. Re:Uhhhh, No by k12linux · · Score: 2, Insightful
      it's not going to cause people to rebel against Microsoft, like many of you are hoping. ...This is going to get blaimed on "hackers".

      You got it! Fairly recently I noticed that nearly 100% of the time MS spins Windows problems this way. It's especially true with Outlook. Based on the spin in their press releases and KB articles, all security problems are 100% the fault of those evil hackers. MS on the other hand really isn't responsible for security problems because if it weren't for hackers there would be none.

      That's kind of like being a company who builds bank vaults made of wood instead of metal. After all, it's not their fault if it gets broken into. It's those damn bank robbers.

      What other industry would people put up with that type of logic?

    3. Re:Uhhhh, No by thesuperjason · · Score: 2, Informative

      This is going to get blaimed on "hackers". And we all know hackers hate God, hate America, root for Saddam, get pentagram tattoos on their foreheads....and use Linux.

      Unfortunately, this is (in my experience over the last couple of days) correct.

      Since the outbreak of blast, I've helped around 5 or 6 family members (you know the ones: "Um, you work with comupters and mine's broken. What do I do?) patch their home systems and remove the worm.

      "What was it?" they ask. "Well, it's this worm you see..." and before you can finish your sentence you get a barrage of "Why do these people do this??? Do they think it's fun???".

      "Who, Microsoft?" I ask.

      "NO! These bloody hackers!!! Where do they get off busting my into system. I wish they'd all get a life. Arseholes".

      Sigh... There's really no point explaining that it's because of MS that they have these problems. They don't have an alternative as they see it. Computer = Windows.

      TSJ

    4. Re:Uhhhh, No by Anonymous Coward · · Score: 0

      Rofl.

      Umm guys sorry to break this to you but it is the hackers fault.

      Yeah Microsoft screwed up but that doesn't give someone permission to exploit a mistake.

      Saying its Microsoft's fault is like saying a man, whose car was stolen because he left his keys in it, is his fault. Yeah he shouldn't have left his keys in the car but that mistake doesn't give someone permission to take it.

    5. Re:Uhhhh, No by Intrinsic · · Score: 1

      Who were the fools who modded this post up to Score 3 Insightfull?

      Some dumb ass windows users ?

    6. Re:Uhhhh, No by darien · · Score: 1

      And good luck to him when he takes that story to the insurers.

      There's such a thing as negligence, you know.

    7. Re:Uhhhh, No by thesuperjason · · Score: 1

      Sure hackers are breaking the law, but if you leave your keys in the ignition while your car is parked in a bad neighborhood, are you going to tell people on the bus on the way home how it was wrong of them to steal it?

      TSJ

    8. Re:Uhhhh, No by sql*kitten · · Score: 2, Insightful

      There's really no point explaining that it's because of MS that they have these problems.

      Rubbish. I expect you blame Ford for the existance of car thieves? Damn Ford, they should have used brick-proof glass in the windows!

      And it's not as if Linux has never been r00ted via sendmail or BIND, is it? MS Blaster is the same, it just propagates over DCOM.

    9. Re:Uhhhh, No by thesuperjason · · Score: 1

      I expect you blame Ford for the existance of car thieves?

      No, I don't.

      The point I was making is that the majority of end users (in my experience) tend to blame hackers and not Microsoft for security issues.

      I'm not saying I agree with their views, but that the problem is one of perception.

      (Did I really have to explain that?)

      TSJ

    10. Re:Uhhhh, No by Anonymous Coward · · Score: 0
      Rubbish. I expect you blame Ford for the existance of car thieves?

      But I would expect them to put a lock on the door and require a key for ignition. Especially when everyone else does it.

      And it's not as if Linux has never been r00ted...

      Nope, but when it's rooted, the people who wrote the compromized code blame code flaws and not the hackers. You don't see them acting like security is hopeless becaue there are hackers.

  185. Re:I think the windows update botton on the taskba by DavidTC · · Score: 1

    Who's this 'we'? Microsoft should be doing that, not us.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  186. ubiquitous devices should be secure PERIOD! by qoquaq · · Score: 1

    If a device becomes so ubiquitous that large scale damage could be done if a flaw exists the product should not be released if this flaw is known before release. We all know that testing of products before release can not find every problem. Major problems should be found. Imagine if a software house as a punishment for anti-trust violations (and majority market share) and broad reaching security flaws had to (by law) refund the purchase of terribly insecure software AND provide a free upgrade once all security fixes were in place .. imagine slower software release cycles by cathedral software houses .... imagine overall more secure products which still have to be easy to use ... imagine better software. It is schedules which kill cathedral house software not QA.

    --

    "They say travel broadens the mind, so I went over the falls in a barrel." -Thomas Dolby

    1. Re:ubiquitous devices should be secure PERIOD! by Anonymous Coward · · Score: 0

      cathedral software houses

      Yeah... You kind of killed your credibility as a possible level-headed, reasonable non-zealot right there.

  187. Typo... *"don't go around" by Anonymous Coward · · Score: 0

    s/do go around/don't go around

  188. The Plot Thickens by Anonymous Coward · · Score: 0

    A very reliable ( and of course, paranoid ) IT expert working somewhere in the southeast has said it is no coincedence that the power outage and the time that the "blaster worm" hit the east coast were so close. Microsoft's laid-back approach to securing it's commercial O/S product line may have cost us billions. But what the hell, he's got money to spare.

  189. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 1

    That's a big, smelly load of shit. Systems administrators should be required to read bugtraq and keep their systems patched. Users should only show common sense. We can't ask them to do these things. There are people working with computers that actually use them as tools to do work, rather than as objects of worship, as we geeks do. They don't want to know about driver install woes or our petty flavour of the month.

    I am not sure if you are suggesting I hire a sysadmin to manage Mommy's computer, or that she should not be expected to know how to do all this. My statement was that she doesn't, and shouldn't have to know about all that. Thats one reason i bought her a system with a sys restore disk, since I live 1300 miles away. To her its a game platform (casino games) and an email machine, so wiping it isnt the end of the world.

    If you are saying she shouldn't have to know this, wtf are you doing argueing with me? That was my point: Its not their fault that they are not experts at upgrading their computers. My brother and I were just enjoying making fun of her about it. Fuck it, she's my mom, I can pick on her if I want. I bought her the box.

    As to the "crap [you] Software Developers keep throwing out", ....yea, get your shit together, you guys suck. :D

    --
    Tequila: It's not just for breakfast anymore!
  190. License to connect by chrysalis · · Score: 1

    Internet is often described as a "highway".

    People are driving on it and they go where they want to go.

    On a real highway, everything works like a charm when these conditions are met :

    - people respect the driving laws.

    - drivers are mentally and physically ok, and they have a driving license.

    - cars are secure.

    When you violate these rules :
    1) You can make severe damage to yourself and to other people.
    2) You can say goodbye to your driving license and/or your car, you can have to pay a lot of money and you can go to jail.

    Now, how are things on the "internet highway"?

    Anyone can drive. Even people who absolutely don't know how to drive (ie. people don't patch their system, never heard about the netiquette, send HTML mails, etc) .

    Most people have a car that wasn't designed to drive on a highway (Windows is obviously something _not_ designed with security in mind).

    People don't even keep their car in a good state (no update) .

    As a result, when their car explodes, they happily make all other car explode as well.

    They are so many people violating the driving laws that it's a common practice that correct people tolerate.

    I receive hundreds of SPAM and Nimda virus every day, my host is scanned on ports 21 and 135 every minute, my web server receive IIS unicode attacks every hour. This is just "normal", and I can't do anything but ignore that, because this is how the "highway" is nowadays.

    Jesus. The fact that internet is a marvellous world where anyone can connect and express himself is great. But nowadays, it's nothing but a big mess and even careful drivers are hit by the silliness of people driving with broken cars and no license.

    --
    {{.sig}}
  191. Re:The FUD on here is amazing by Greyfox · · Score: 1
    I don't strive for it. I would be a completely unwilling dictator. But it would be for the world's own good. Most people are demonstrably lazy, stupid and completely unwilling to fight for the betterment of their world or the freedom of their children as long as they can have their things right now. And we are to allow these sheep rule the world through the sheer volume of their numbers? No, it's obvious that what the world needs is a mostly benevolent dictator who has the foresight to herd this flock to a better place. While it would be overly meglomanical to claim that I'm just the person for the job, I don't see anyone else who's given due consideration to all the issues and who is willing to implement the necessary policies.

    My goals as dictator of the planet would be as follows:

    1) The eradication of all superstitious behavior on the part of the citizenry, including all organized religion. Realizing that religious teachings can allow for the development of a more ethical outlook on life, an optional state sponsored religion involving Smurfs will be implemented.

    2) Immediate mandatory reversable sterilization of all citizens, male and female. A breeding license will be required on a per-child basis based on a set of criteria that will be enumerated in full once I ascend to power. In no manner will further growth of the population be allowed, until more resources can be obtained (see 3)

    3) Immediate and massive space exploration program, with a first goal being the terraforming of the planet Mars. With the world's economy behind me, this should be feasible before my death.

    4) Immediate and massive longivity and genetic improvement program, with an eventual goals of faster, smarter humans free of disease and immortality.

    5) Research into ways of increasing the wealth of all human beings, with the goal being that every man, woman and child on the face of the planet can have anything they want and only have to work at whatever they want to do. If all they want to do is sit in front of the TV, that's fine with me, but those people won't be front runners for the breeding licenses. I would settle for eliminating hunger and disease world-wide as an acceptable first step.

    Although I would have some other more minor goals, I believe those would keep me busy for the foreseeable future as I reshape the world in my image. Naturally such a system would be wide open for abuse by the inner core of the support system, but such abuses would be dealt with most harshly. Anyone working in the government would be required to adhere to strict ethical guidelines and failure to do so would cause them to forfeit all their organs to the state-run organ banks.

    I'll let you figure out how much of that is serious and how much of it is irony.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  192. C2? by LifesABeach · · Score: 0

    i thought it was C4 clearance, and that took years to get.

    1. Re:C2? by kjs3 · · Score: 2, Insightful
      i thought it was C4 clearance, and that took years to get.

      It's C2; there's no such thing as C4. C2 isn't terribly hard to get (lot's of auditing and doco requirements). However, since C2 isn't a particularly interesting or useful security classification except for marketing (DAC systems are strictly for unclassified environments), most vendors don't bother with it until they start selling lots of stuff into the gov/mil/intel areas.

      B-level secure systems are another story entirely.

  193. Re:I think the windows update botton on the taskba by aWalrus · · Score: 1

    I meant 'we' as in 'all Software Developers'. Although it's usually Microsoft taking the spotlight in these situations, the fact remains that their software has a very large installed user base and therefore is more prone to be analyzed and attacked. There's a lot more software out there just as insecure. It's just not attacked that often.

    And still, Security Oriented Programming courses are not a part of most Computer Science Curriculums, and we keep blaming these problems on everyone but ourselves.

    Microsoft doesn't magically materialize their sloppy programmers from dirt. They hire them FROM THE BRIGHTEST OF THE PACK. That's right. They go to Uni's, find the most promising students and hire them. And they're the ones giving us Blaster woes. Perhaps we should do something about this.

    --
    Overcaffeinated. Angry geeks.
  194. Re:I think the windows update botton on the taskba by Badanov · · Score: 1

    Yeah, a lot of users think a computer is like a Ronco product: Set it and forget it!

    --
    Dawn of the Dead
  195. Eeh, excuse me? by Jugalator · · Score: 3, Informative

    And now, the company has "extinguished" WindowsUpdate.com (future updates will come from a different domain). All this because of some Microsoft worm that triggers at midnight.

    If you're going to submit a biased article, at least get the facts straight. WindowsUpdate.com was never the primary WU domain, windowsupdate.microsoft.com was. They're just disabling the extra one that was never linked from the Windows OS.

    --
    Beware: In C++, your friends can see your privates!
  196. Re:I think the windows update botton on the taskba by aWalrus · · Score: 1

    I was referring more to the part of your post where you made fun of her not knowing if unplugging her computer was enough. We all tend to do that and rag on user ignorance, but we're becoming dangerously close to asking them to actually be on the level of sysadmins, and the whole computer as a tool paradigm kind of gets shot to hell at that point.

    As to the "crap [you] Software Developers keep throwing out", ....yea, get your shit together, you guys suck. :D

    I know. Damn us.

    --
    Overcaffeinated. Angry geeks.
  197. Re:I think the windows update botton on the taskba by malfunct · · Score: 1
    Common sense was plenty, my computer quietly downloaded the patch in the background days before W32.Blaster became a problem and asked me if I would like for it to install the patch. I said yes and Blaster didn't hit me.

    The problem is people are scared to death of "magic" inside a computer and we need to help educate them.

    That said a LARGE improvement in initial software quality would be good, especially changes in design that make it much more difficult for the worms and virii to get permission to execute on the machine in the first place would go a long way to solving the issue before its really an issue.

    --

    "You can now flame me, I am full of love,"

  198. Actually, by Sevn · · Score: 2, Informative

    :)

    A few of the german microsoft sites used to run Linux. Oh, and their "Switch to Windows" campaign server used to run Linux as well until everyone started picking on them. You don't have to get all huffy because Microsoft had to rely on the awesome power of Linux to save their bacon. They went with Akamai to load balance a site, and Akamai uses industrial strength Linux. So yes, inadvertently WindowsUpdate.com IS running on Linux. The scan from Netcraft was correct. So Sorry. Thank You For Playing. No rumors here. It's the honest to God's truth.

    --
    For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
  199. Re:I think the windows update botton on the taskba by jez9999 · · Score: 1

    Makes ya wonder why they didn't write the worm to attack microsoft.com doesn't it?

    It's ok, microsoft.com can take it.
    Can they? This is possibly 50% of machines *in the world*, at worst anyway.

    But people can just update... ... from windowsupdate.microsoft.com ?

    But we can just drop the domain...
    What, change the company name because of a DoS attack?

    Tricky one, isn't it? Looks like MS got let off.

  200. OT: Login desktop customisation by Anonymous Coward · · Score: 0

    Under XP, look under Control Panel - Accessibility Options. General box. Yes, those two little ones down the bottom that really shouldn't be there but were tucked in there because they didn't fit in anywhere else. Heh.

  201. Re:I think the windows update botton on the taskba by Anonymous Coward · · Score: 0

    That's because the version on their site is oooold. Microsoft didn't write MBSA - Shavlik Technologies did. Last I saw there was an MBSA version that could actually download the patches there. Looks like they took it shareware?

  202. Re:I think the windows update botton on the taskba by caluml · · Score: 1

    Next time, virus writers - microsoft.com - let's see them turn that one off ;)

  203. Um.. by firew0lfz · · Score: 1

    is it just me, or is nowhere in the article did it say that they were going to take down http://windowsupdate.microsoft.com? From the C|NET article, "Although Toulouse was mum on the specific steps the software giant is taking to prepare for the attack, Microsoft is advertising alternative ways to get downloads and information from its site. The company has put more than 10 links on its main Web site to send people to more information and alternative channels for downloading updates." Also, near the end of the article: ""I doubt Windows Update will go down," Maiffret said. "They have a big network, and it's very distributed."" Nowhere did I see anything about shutting down windowsupdate.com.. ?? And I'm at the site now, and it appears to be working fine. Did I miss anything?

    --
    Try not to let life get in the way of living.
  204. Re:I think the windows update botton on the taskba by Pharmboy · · Score: 1

    was referring more to the part of your post where you made fun of her not knowing if unplugging her computer was enough.

    I was making fun of her because she is my mom (remember how I even said she was smart enough to ask). She is also the first to tell you to kiss her ass. We play for keeps in my family. Most people would have trouble dealing with so much "in your face humanity". Really, it gets pretty wild, although it still sounds weird hearing your own mother refer to someone as a "fucking asshole". And no, they are actually upper middle class, lol.

    As to the crap you developers keep throwing out, remember, the first step is admitting you have a problem. Next is seek help among others with the same problem. ;)

    --
    Tequila: It's not just for breakfast anymore!
  205. Fuck. How can you tolerate this ? by Winston+Orwell · · Score: 1

    50 MILLIONS people that cannot heat their dinner or have a hot shower, airports blocked, wall street that cannot make business, the white house and the pentagon that survive on emergency power supply, as you pretend to be the richest and whealthiest country in the world ?

    How can you possibly tolerate this !! Don't you ask yourself any questions ??!?? Do you never think "is this normal, in 21st century as we spend 400+ billions dollars in your defense and big corporations don't pay taxes, is it normal I can't have light at home !!?!! Is this kind of failure acceptable ?? " Don't you ever wonder if in some other countries, things are different ? I remind you electricity has been discovered more than 100 years ago and we perfectly know how to transmit it safely.

    Don't you ever wonder where the fuck are your taxes and your electricity bills going to ??

    Please, open your eyes, don't be so dogmatic.

    What kind of freedom do you have, except walking in the dark ??

  206. change time by DoraLives · · Score: 1

    Which makes me wonder how much fun and games would have erupted had some Wiley Hackist been able to perform a similar trick, being sufficiently careful to conceal the payload (unlike the dingdongs behind this one), which would then have DDoS's something similarly large at midnight on the first day of the year 2000.

    --
    Is it fascism yet?
  207. Brightest of the pack? by moncyb · · Score: 1

    Brightest of the pack??? I stopped using MS products because they were the most shoddy, buggy, poorly designed pieces of crap I have ever seen outside of script kiddie shareware. If their programmers are the "brightest of the pack," then their management must be on crack to be directing them so poorly. MS is a screwed up company. I dealt with their crappy products for nearly a decade, so no one can tell me differently. Their security problems are just the tip of the iceberg. From their DOS print string function which used a dollar sign for termination[1] to Windows which would automaticly change settings to the wrong values because they think their three lines of code knows better than the user.

    [1] Yeah, you heard right a printable character, so if anyone needed to print a string with a dollar sign in the middle, they would have to print the first half of the string, output a dollar sign with a different function, and print the second half of the string. No wonder most programmers used the BIOS functions or direct access to the video card for display. They'd do it even where DOS would've been more appropriate. Don't even get me started about the bugs in the console functions. These are simple things any inbred script kiddie could do. They had years to work on them, yet DOS still had problems.

  208. Kinda like you should not have to keep your ... by Randy+Rathbun · · Score: 2, Insightful

    car in roadworthy condition, huh?

    I mean, what business is it of anyone else's if your brakes are bad, you have bald tires, and huge chunks of the car falling off as you drive down the street.

    1. Re:Kinda like you should not have to keep your ... by aWalrus · · Score: 1

      If your car is not roadworthy it lets you know. Tires vibrate, brakes make noises and other parts squeal. As far as I know, only Windows XP notifies you automatically when there are updates you need available. Even then, as evidenced by a link on the current story, it could fail during an update, not notify you, and tell you everything's ok. Then it would be the equivalent of a car that performs extremely well until you realize it lacks breaks (although none of the warning lights ever came up). Again: let's blame the users. They should fix my buffer overflow.

      All the things you mentioned are meant to fix parts of the car that wear out because of use. They are not meant to fix glaring defects that were there when the car was sold. And those involve rather large recalls and responsibility by the Company that produced the parts. Software companies can just slap a disclaimer on the box and they're home free.

      --
      Overcaffeinated. Angry geeks.
  209. BSA? by moncyb · · Score: 1

    Microsoft BSA utility which scans your computer? Methinks Pharmboy will get a visit from the stormtroopers tomorrow. ;-)

    Stormtrooper via megaphone says: "Alright everyone. Hands off the computers. This is a license audit!"

    1. Re:BSA? by Pharmboy · · Score: 1

      Microsoft BSA utility which scans your computer? Methinks Pharmboy will get a visit from the stormtroopers tomorrow. ;-)

      Stormtrooper via megaphone says: "Alright everyone. Hands off the computers. This is a license audit!"


      Lol, I have to admit, the name made parts of me pucker up, too. But as I move more and more to Linux, its nice to know that is less and less an issue. Bitching about constant updates, security holes, bad scripting, closed source and crashes are also becoming less and less an issue as well.

      The largest network I manage is only 15 clients and about 6 servers, but the whole licensing thing is really a consideration, not only for the expense of purchasing the licenses, but trying to keep up with what everyone else installs and keeping them legal. I do this as just a part of my job, alone. Linux is looking better and better every day.

      --
      Tequila: It's not just for breakfast anymore!
  210. Facts you won't see by Overly+Critical+Guy · · Score: 0, Flamebait

    Facts you won't see: Microsoft had 2 announced holes last month. Linux has 9.

    --
    "Sufferin' succotash."
  211. Not secured from the bug? by failedlogic · · Score: 1

    I thing the power outage did a good job of securing my computer for 24 hours.

  212. Re:I think the windows update botton on the taskba by Richard_at_work · · Score: 1

    Works fine here, go to "Tools > Windows Update" and I get a v4.windowsupdate.microsoft.com/blah/blah page which allows me to scan for updates, going nowhere near a windowsupdate.com site.

  213. Re:I think the windows update botton on the taskba by Transcendent · · Score: 1

    They're obviously worried that something is in the wild that is hard-coded to attack WindowsUpdate.com, else there would be no point in abandoning that domain and moving to another.

    Well duh....

  214. Article says not blaster worm by jeffbruce · · Score: 1

    The article says that the attack did not come from the Blaster Worm. I am not sure if I believe this.

  215. Re:windows worm OLE exploits might have broke powe by Mostly+a+lurker · · Score: 1
    It wasn't terrorism or the MS worm

    Probably true, but the authorities could be in denial. Remember the shuttle disaster. For the first few days, they said it definitely was not caused by the foam issue.

  216. Proof it was Windows' fault by commodoresloat · · Score: 1

    The BSOD (Black Smoke of Death).

  217. Everybody is missing the point by grozzie2 · · Score: 5, Insightful

    I think everybody is missing the point on this whole issue. Fact :- Blaster is a worm, who's payload was intended to dos windowsupdate.com, rendering it unavailable to the folks using it. Fact :- windowsupdate.com is 100% unavailable. Conclusion :- Blaster is the most successful virus/trojan to date. It didn't just cause a few hours of unavailability, it wiped the domain from existence. Not just any domain, but a prominent microsoft domain (high profile, big budget website) totally obliterated off the internet. Folks can say what they want, and argue about the politics of it all, bicker about who is responsible to update what, and whatever, but you cannot deny the facts. Blaster is head and shoulders above the crowd as a denial of service worm, the first to achieve a 100% success even prior to actually triggering. Say what you want folks, but this has got to go down in history as the most successful worm ever.

    1. Re:Everybody is missing the point by BuckaBooBob · · Score: 1

      So what does this mean in the long run? 1)A Variant will be out next week to target the new domain? (Yet another Short term solution for a long term problem) Or 2)Will MS Follow thier practice of security through obsecurity and not release the new domain name (to the public or the clients that need to know the domain to connect to it:))

      --
      Who needs WiFi when we can have Packet Over Sheep! http://datacomm.org/PoS-InternetDraft.txt
    2. Re:Everybody is missing the point by Fishstick · · Score: 1

      It's not a "new" domain. windowsupdate.com always just re-directed to windowsupdate.microsoft.com -- they just removed the DNS for this convenience address (probably temporarily at that).

      True, the next worm will probably just point to the real url (not sure why this one didn't?)

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    3. Re:Everybody is missing the point by raga · · Score: 1

      According to the one of the links in the story-line, the DDOS did not come from Blaster-infected machines.

      cheers- raga

  218. Hellooooo up there by LordLucless · · Score: 1

    It's already the sixteenth down here in the merry old land of Aus. We have computers too.

    --
    Just because you're paranoid doesn't mean there isn't an invisible demon about to eat your face
  219. Default XP Home user is admin by JimmytheGeek · · Score: 1

    You don't have to/aren't prompted to create an unpriviledged account.

    If the vast multitude of windows exploits are merely proportionate to market share, why is it that IIS has the bulk of web server exploits, the bulk of 0wn3d sites, and lags Apache in market share?

  220. If it were that easy to write a Linux virus by obdulio · · Score: 1

    Redmond would be releasing hundreds of them every month.....

    --
    PENAROL: Seras eterno como el tiempo y floreceras en cada primavera.
  221. Conspiracy Theory by Scoria · · Score: 1

    Perhaps an entity is attempting to mitigate every convenient method by which a Windows administrator or user can retrieve updated packages.

    Perhaps this entity has discovered another Windows exploit.

    Once the vendor distribution services (Windows Update, for instance) were rendered inaccessible, the hypothetical entity could then invoke its exploit. And, until the services were restored, every affected machine would remain involuntarily susceptible.

    Imagine the possibilites!

    --
    Do you like German cars?
  222. Who is next? by Anonymous Coward · · Score: 0

    Ok, windowsupdate.com is history:

    nslookup windowsupdate.com
    Server: localhost
    Address: 127.0.0.1

    *** No address (A) records available for windowsupdate.com

    Because someone spent a couple weeks writing a worm
    and convinced 200,000 computers to attack it. Rather
    than attempt to withstand the attack, Microsoft decided
    that the domain was not important enough to defend.

    What happens next week when someone modifies the worm
    (which will take hours/days instead of weeks) and attacks
    a more important domain (www.[yourcompanyhere].com)?

    Does anyone think they could have withstood an attack
    of this magnitude? (200,000 * 20pps = 4 million pps)
    By Akamai-zing perhaps.

    1. Re:Who is next? by Anonymous Coward · · Score: 0

      it would be trivial if an exploit added

      windowsupdate.com windowsupdate.microsoft.com

      to c:\winnt\system32\drivers\etc\hosts (win2k)
      or c:\windows\system32\drivers\etc\hosts (xp)

      on comprimised machines

  223. Microsoft Hatred by Anonymous Coward · · Score: 0

    i believe that if Microsoft Windows is compared to unixes, Windows are far more secure. Please see Mirosoft Hatred, the beginning follow down to MS hatred FAQ. Xah Lee

  224. Re:windows worm OLE exploits might have broke powe by deepfusion · · Score: 0

    To further add to the conspiracy take a look at some of the clients on the Power & Utilites - Client List page:


    ConEdison.
    Brooklyn Navy Yard.
    New York Power Authority.
    Brooklyn Navy Yard.


    matrikon.com

    While they market mostly monitoring tools that run on client-side Wintel machines, it still makes you wonder. I admit that I laughed when I first heard of people trying to make this connection, now it seems slightly less improbable.

  225. Re:windows worm OLE exploits might have broke powe by deepfusion · · Score: 0

    Opps,
    The last client in that list should have been:

    Orion Power - New York

    Sorry 'bout that. The point is all of those are players in the NY area black-outs. ( Brooklyn Navy Yard, at least the non-critical areas, was affected and they run their own grid.)

  226. Difference from Code Red by haX0rsaw · · Score: 1

    In 2001, after Code Red infected some 350,000 computers, it aimed a similar denial-of-service attack at Whitehouse.gov. Network administrators were able to move the site from the targeted Internet address and sidestep the attack. Moreover, despite hundreds of thousands of PCs flooding the Internet with data, local network outages didn't happen. The major difference here is that Code Red was targeted at an IP, Blaster is not, rather a domain.

  227. Now if only they would... by yelohbird · · Score: 1

    "extinguish" Windows

    --
    h-t-t-p-colon-slash-slash-slash-dot-dot-org
  228. Billy owes SCO? by Anonymous Coward · · Score: 0

    I wonder if Microsoft has cut SCO a cheque for the move to Linux?

  229. The memo... by d2003xx · · Score: 1

    IS TOO LONG!!

  230. Problem with your fact by Xandar01 · · Score: 1

    windowsupdate.com is about as useful as whitehouse.com

    Seriously though, windowsupdate.com was just a redirector for those who don't know the real URL (not quite the high profile-big budget website, but close.) Same thing goes for technet.com. Too lazy to type the real URL, MS conveniently provides a TLD URL based on what you're looking for.

    The automatic updates and windows update option in IE both connect to windowsupdate.microsoft.com.

    I'll grant you that 100% success for Blaster, but it's kind of silly if you takeout whitehouse.com when you were really aiming for whitehouse.gov.

    --
    Life moves pretty fast; if you don't stop and look around once in a while, you could miss it. -FB
  231. Past midnight now.... by blumpy · · Score: 1
    It's past midnight now, and I'm getting a strange message when going to http://windowsupdate.microsoft.com/

    "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. The latest version of Windows Update is available on computers that are running Microsoft Windows 98, Windows 98 Second Edition, Windows Millennium Edition, Windows 2000 (except Windows 2000 Datacenter Server), Windows XP, and the Windows Server 2003 family."

    That's how they plan to deal with the attacks? Just put up a simple html page? What if I wanna do an update?

  232. Re:What a fizzer! by grolschie · · Score: 1
    Uh... the site windowsupdate.microsoft.com, not only has it been available for most of today, but now also has the following text:

    Steps to Protect Yourself from the Blaster Worm

    To protect yourself from the Blaster Worm and its variants, users of the following products: Microsoft Windows(R) 2000 Service Pack 2 or greater, Microsoft Windows XP, and Microsoft Windows Server(tm) 2003, should install "MS03-026: Security Update for Windows XP (823980)". Microsoft Windows NT4 users are also vulnerable and should click here for more information.

    Users of Windows 2000 RTM or Windows 2000 SP1 should upgrade to the latest service pack and then install "MS03-026: Security Update for Windows XP (823980)".

    Your computer is not vulnerable to the Blaster Worm if either of these conditions apply to you:

    If you have already downloaded and installed the security update that was addressed by Security Bulletin MS03-026. The MS03-026 update will not be listed on Windows Update in this case.

    If you are using Microsoft Windows 95, Windows 98, Windows 98 Second Edition (SE), or Windows Millennium (Windows Me).

    For more information click here. Windows Update is looking for available updates... 0% complete


    Man, this virus's payload was a real fizzer!
  233. Re:What a fizzer! by grolschie · · Score: 1
    D'oh! Just after I hit the submit button, the site now just shows nothing but this:

    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.

    The latest version of Windows Update is available on computers that are running Microsoft Windows 98, Windows 98 Second Edition, Windows Millennium Edition, Windows 2000 (except Windows 2000 Datacenter Server), Windows XP, and the Windows Server 2003 family.


    That'll learn me!
  234. link... by WiseWeasel · · Score: 1

    Here ya go: M$'s WMV 9 codec for WMP 6.4 & 7.0 Gotta give the credit to Google for locating the site...

    --
    "I like systems, their application excepted", George Sand (French)
  235. Social DOS by Ashok · · Score: 1

    The most 'impressive' denial of service going on here is the social one. Get a lot of folk out there that are manually trying to get patched, all together and it's going to cause a hell of a spike on whatever machines service the update. This is aided slightly by some good meeja stories.

    Removing the DNS for windowsupdate.com is one thing but windowsupdate.microsoft.com looks a lot like toast right now. That could be because there are variants of the worm, I suppose, but I'd wager it's the monkeys at keyboards.

    Imagine if they didn't have the best part of a month to patch and a week to prepare for the ddos. How about an hour or so to code for a new exploit and 15 minutes for it to propagate? Patching isn't going to save anyone if that sort of thing ever because commonplace.

    --
    ash
    ... You can call it a wizard once it can do bloody magic
  236. Never saw an article so clearely wrong by fulgan · · Score: 1

    Well, not since april's fool, anyway...

    1/ Nothing besides a couple of "helpful suggestions" on public mailing lists states that windows update might change URL.

    2/ If you look at the netcraft grph, you'll see that the "linux" entry isn't the MS web site, it's a MS-owned IP. What it simply shows is that, for some times, Netcarft's probes where not served directly ba MS's servers but by Amakai's cache. Simple as that.

    3/ ALL the articles and web pages are missquoted: they usually specifically say the OPPOSIT of what's stated in the /. summary. Even the part about WU downtime being due to the worm.

    I would suggest permanently baning the poster from ever submitting news again. Remember folks: it's not because you WANT it to be true that it is true.

  237. spybot by Anonymous Coward · · Score: 0

    add spybot to the list.

    I use spybot, zone alarm, avg anti-virus, mozilla, mail via yahoo (excellent free anti spam protection), and never use IM or anything by Micrsoft except the operating system itself (e.g. no IE, no outlook,etc)

    I've tried a few free anti pop up products; all work good but none work great.

    oh, and turn off ALL automatic upgrades.

  238. newsflash by Anonymous Coward · · Score: 0

    There are rumors that the NY power blackout was caused by a worker from Springfield Nuclear Power Plant, from sector 7G. The workers name is assumably Homer Jay Simpson. Owner of the plant Mr. Montgomery Burns hasn't stated anything to the press yet. Our reporter was chased away from his property by fiercious hounds :)

  239. Re:I think the windows update botton on the taskba by Anonymous Coward · · Score: 0
    We should be bounds-checking our mallocs rather than demanding users take the time to fix the faulty products we put out.
    There is a solution for that right here:

    http://bstring.sf.net/

    You want to know that sad thing? Microsoft has 3 very well known ways of dealing with buffer overflow that their own developers do not use:

    1. MFC's CString class
    2. STL's std::string
    3. A length guarded C library called SafeString.

    Each one of these exposes a usage that completely protects from buffer overflows on string manipulation (including input.) Microsoft VC++ has access to all 3 APIs. MS has no good excuse for having lame string based buffer overflows anywhere in their code.

    Yes, string manipulation is not the *only* situation where buffer overflows can happen, but its clearly the most prevalent. And if a string library is augmented with full binary string capabilities (i.e., dropping the '\0' termination condition) then you can use a buffer-overflow safe string library for more tasks, most importantly -- *ALL INPUT* tasks.
  240. Poor mans DOS... by Lispy · · Score: 1

    A link on Slashdot...;-)

  241. Put in some 400MW Solar IIs by Colin+Smith · · Score: 1

    That's life, the gas turbines are cheaper.

    However you could make more use of the Solar II Solar thermal stuff mentioned in slashdot a few weeks ago. They produce power period as the aircon requires it and they reckon they can scale the technology to 400MW.

    --
    Deleted
  242. Huh? This has been trivial for decades. by Colin+Smith · · Score: 1

    onall "find / -name msblast.exe -exec chmod a-x {} \;"

    Where onall is a trivial shell script wrapper round rsh, ssh or whichever equivalent you use.

    --
    Deleted
  243. Apologies to Rod Stewart by Megaslow · · Score: 1

    Let me tell you about a place, somewhere up in Redmond way
    where the people are so gay, patchin' the night away
    Here they have a lot of fun, puttin' worms on the run
    Oh man you'll find the old and young patchin' the night away

    Here's a man in evening clothes, how he got here I don't know
    but oh man, you ought to see him go, patchin' the night away
    He's getting ready to reboot, he just installed a service pack
    Oh man, there ain't nothing like patchin' the night away

    Feel much better

    Here's a fellow in blue jeans, who's fighting with an older box
    reloading Windows 2000, patchin' the night away
    Man you ought to see him go, patchin' to the rock and roll
    Here you'll find the young and the old patchin' the night away

    They're patchin', patchin', everybody's doing great
    They're patchin' man, patchin', they're patchin' the night away
    Patchin', you know they're patchin', patchin' the night away
    They're patchin', patchin', man patchin' the night away

    Here they have a lot of fun, puttin' worms on the run
    Oh man you'll find young and the old patchin' the night away
    Here's a man in evening clothes, how he got here I don't know
    I don't know but man you ought to see him go
    Patchin' the night away

  244. Ferrets? by sean.peters · · Score: 1

    Well, there's no shortage of weasels in the administration...

    Sean

  245. Windows Update service was *not* taken offline.. by chrisleonard · · Score: 1

    I'm really surprised that they actually took windowsupdate offline.

    Just to clarify (though I think you understand this), they unregistered the windowsupdate.com domain, but did *not* take the Windows Update service offline.

    The windowsupdate.com domain was only a "redirector" domain anyway. The service itself is hosted at windowsupdate.microsoft.com, but apparently the worm-burners weren't very clever on this point, and they pointed at the redirector domain instead of the real thing. This let Microsoft retire the redirector as part of a defense against this particular worm. I'd say MS is just being opportunistic, because basically very few people ever used windowsupdate.com to get to the Windows Update service anyway. For example, if you click Tools | Windows Update in IE you are sent to windowsupdate.microsoft.com, not to windowsupdate.com.

  246. windowsupdate solution...akamai. by generic · · Score: 1

    windowsupdate.microsoft.com canonical name = windowsupdate.microsoft.com.edgesuite.net.
    window supdate.microsoft.com.edgesuite.net canonical name = a822.cd.akamai.net.
    Name: a822.cd.akamai.net
    Address: 63.208.194.73
    Name: a822.cd.akamai.net
    Address: 63.208.194.97

    makes sense to me.. add 15,000 servers to your pool.
    They should have done that the first time around.

    --
    Microsoft aggravates my tourettes syndrome.