Slashdot Mirror


FBI, Pentagon Talk to MS about XP Hole

(eternal_software) writes: "The Associated Press is reporting that the FBI and Defense Department are talking to Microsoft about the serious flaws found in the XP operating system. As we all know, the most recent flaw allowed any XP machine to be hijacked simply by connecting it to the internet. The government is getting involved because of growing U.S. concerns about risks to the 'net as a whole." In fact, the FBI would like you to go a bit beyond the MS patch. davecl points out the updated page put out by the National Infrastructure Protection Center about this vulnerability as well.

132 of 405 comments (clear)

  1. Just a thought by peripatetic_bum · · Score: 4, Interesting
    First we hear rumors that al-queda may have hacked into windows,

    now we see the Gov't take a special interest in

    the latest XP hole.

    Dont know about you, but I am really dont know what to think?

    --

    Sigs are dangerous coy things

    1. Re:Just a thought by MagikSlinger · · Score: 2

      I'm sure it's just coincidence. The more likely reason is due to the hightened state of security, the FBI is less tolerant of MS's sloppy security holes.

      --
      The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
    2. Re:Just a thought by colatek · · Score: 5, Insightful

      I have to agree with the the one post on the site I linked to above. Microsoft knew about the security hole in XP for 5 weeks yet they continued to tout it as the most secure system ever. I believe it was irresponsible of them not to at least inform the government about this bug. Heck, I think they should have gone as far as tell the consumers. The whole thing tells me that Microsoft cares nothing more than their bottom line (yes I know that they are a business, but this could be a national security issue). I think that there is criminal negligence here. I think there is grounds for consumer fraud. I for one am going to write the states attorney and ask them what stance they are going to take on this issue.

    3. Re:Just a thought by Syberghost · · Score: 2

      I think it's even worse than how you present it:

      A witness says that Al-Queda deliberately set out to leave back doors and security holes in XP.

      XP then has the worst hole of any Microsoft OS, ever.

      The FBI suddenly has a lot of questions. They damn well should.

    4. Re:Just a thought by nels_tomlinson · · Score: 3, Interesting
      I believe it was irresponsible of them not to at least inform the government about this bug. Heck, I think they should have gone as far as tell the consumers.

      Given that AOL can afford to stuff the mailboxes of the entire US with CD's, Microsoft ought to be able to afford a replacement CD for their paying customers. Instead, they expect you to risk further compromise by going online to get a patch.


      They wouldn't even admit that there was a problem until the Washington Post held their feet to the fire. Must be nice to know Uncle Bill cares about his customers ... It's even nicer not to be one of his customers.

  2. hmmm...interesting by metrix007 · · Score: 4, Insightful

    the fact remains, ms code *can* be secure, obviously just not xp, good to see them getting their act togethor

    --
    If you ignore ACs because they are anonymous - you're an idiot.
  3. XP patch is broken by Anonymous Coward · · Score: 5, Funny

    MS XP patch disabled network card on my computer!

    I guess the computer is really safe now.

  4. did anybody notice this.... by Merik · · Score: 3, Interesting

    "Microsoft explained that a new feature of Windows XP can automatically download the free fix, which takes several minutes, and prompt consumers to install it. "

    thats really messed up that and scary

    (Hmmm.. magic latern)

    --

    --

    What is the sound of this sentence?

    1. Re:did anybody notice this.... by sporty · · Score: 3, Insightful

      This isn't such a bad feature if you think about it. Well, if it did it like OSX did, I'd be happier, but I can't say that XP does. It should prompt and then dowdnload if affirmative.

      But that's my humble opinion, which isn't as scary or so scary or whatever...

      --

      -
      ping -f 255.255.255.255 # if only

    2. Re:did anybody notice this.... by Alien54 · · Score: 4, Funny
      "Microsoft explained that a new feature of Windows XP can automatically download the free fix, which takes several minutes, and prompt consumers to install it. "

      Nevermind that such an exploit could also be used to do just the same thing and send people off to download a "patch" form a psuedo MS site.

      Suddenly people are taking seriously the idea that MS can present a problem for national security, when this was dismissed as a trollish comment before.

      The fantasy is the unlikely end result with Bill Gates and buddies being arrested for treason for the software. yes it is just a fantasy. ,p.But isn't Xmas the time of year for dreams? ;)

      --
      "It is a greater offense to steal men's labor, than their clothes"
    3. Re:did anybody notice this.... by mESSDan · · Score: 3, Informative

      No, it is a part of XP, in the system properties, it's called Automatic Updates. It's also available in Win98/ME through the Critical Updates program you can get through Windows Update. You can turn it off at will.

      --

      -- Dan
    4. Re:did anybody notice this.... by Corgha · · Score: 2
      "Microsoft explained that a new feature of Windows XP can automatically download the free fix, which takes several minutes, and prompt consumers to install it. "

      thats really messed up that and scary


      Yeah, scary like apt-get.

      Then again, at least MS patches are signed, which makes things not quite so easy to trojan. (Yeah, signatures aren't everything, I know.) Unless, of course, you don't trust MS not to trojan their software, in which case why are you running it?

      Auto-update systems are good, so long as they prompt the user, which it appears XP's does.
    5. Re:did anybody notice this.... by TandyMasterControl · · Score: 5, Insightful
      Not that I necessarily think that the XP auto-updater is a bad thing; I haven't come to a conclusion for myself yet.

      Whenever you log in on your XP system (of course, no password in XP-home at least) a flurry of packets fly off to Mord- er Microsoft and to the OEM you bought the system from. You have no way of knowing the content of that communication. Since it's all closed source,no one can comb through it for vulnerabilities or trojans like they could for the code for apt or rpmfind. A typical user has no way of knowing that the communication is even taking place at all unless they are running something like tcpdump on the network.

      Does that help?
      Basically, when you buy XP you are wittingly or unwittingly complicit in your own surveillance. You have given your consent in principle, to be spied upon because you were sipping your morning coffee while XP talked to the higher authorities about you. You looked away and sipped instead of yanking the cat5 out. I say in principle because we've seen that all the consent required for this government to violate your Constitutional rights is that you and others do not resist it with force. Though no one posting here can say for certain what passes through this security hole now, neither can anyone deny that, with a hole like this opened in your systems, a hole which everyone is being conditioned to accept as normal, a feature of their OS, there is literally NO LIMIT to the severity of your insecurity. While you're sipping that coffee, the convenient updater can convert your computer system into a telescreen into your private thoughts, business plans, governmental policies, and so on without end, no matter where you live and what flag you salute. It used to be that spyware was an annoyance foisted on the public sporadically by marketers. Now with XP, spyware connects a government approved monopoly to your most trusted communications and private papers. You don't have to be an anticapitalist socialist or a government hating libertarian to understand that at some level the distinction between a government approved monopoly and an agency of that government is essentially null, or so small it's not worth discussing. (Or maybe someome could point out examples to me where ATT told the government it would not cooperate in its counterintelligence efforts against antiwar protestors and civil rights leaders in the 1960's)

      Between the 2 of them, Windows XP users have poor Goatse-man beat by a painful mile for the infinite elasticity of their holes. I have no doubt that the Feebs and Dept.of Deathdance have a million things they'd like to talk over with MS in that regard.

      --
      Johnny Quest has two Daddies.
    6. Re:did anybody notice this.... by innocent_white_lamb · · Score: 2, Interesting

      Nevermind that such an exploit could also be used to do just the same thing and send people off to download a "patch" form a psuedo MS site.

      Probably not as easily done as it appears on the surface. I suspect (though I could be wrong) that there would be some kind of key-signing of the update patch that's done by MS and then checked by XP before installing the same.

      Or maybe not. This is, after all, Microsoft. But still, it seems an obvious precaution to me.

      --
      If you're a zombie and you know it, bite your friend!
  5. But they don't see MS as the problem, I bet by MagikSlinger · · Score: 2

    How much you want to bet that no one sees this as a problem with Microsoft? One can only hope this emboldens the anti-trust crusaders and their cause.

    --
    The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
    1. Re:But they don't see MS as the problem, I bet by mpe · · Score: 2

      Here in the US, the power of government over large corporations seems to have almost completely disappeared. Karl Marx wrote of the "withering away of the State" as being a result of communism. It seems however, that it is not really necessary to have a communist system for that to happen. Now that some very large corporations are out from under the control of the US (so-called) "government", will individuals be able to achieve their own freedom?

      Probably not since this "withering away" of power appears confined to exercising power over US corporations. Indeed the US federal government is currently seeking to increase powers over it's citizens, visitors and colonial subjects. Also it's ability to wage war is quite formidable.

  6. Trust us! by robinjo · · Score: 4, Interesting

    Microsoft has known for five weeks that XP had a serious security hole. They didn't do anything to warn customers who bought XP during that time. They just kept telling how XP is so secure.

    It's unbeliavable what Microsoft can get away with. I don't think the hole and the patch are the important issues here. I'm shocked how Microsoft can lie to the whole world for five weeks and people still trust them.

    Microsoft should have withdrawn XP and fixed it. Expecially as they don't even have any serious competitors. What they showed was that they don't care about the safety of their customers. They just want to make money no matter what.

    1. Re:Trust us! by uchian · · Score: 5, Interesting

      Microsoft should have withdrawn XP and fixed it. Expecially as they don't even have any serious competitors. What they showed was that they don't care about the safety of their customers. They just want to make money no matter what.

      In my opinion they should _STILL_ withdraw it and fix it.

      By this, I mean that they should recall every vulnerable CD off of shelves, and send everyone who they know has bought one a new copy that is already patched.

      Computers bought with Windows XP preinstalled should have the offer of being recalled to have the patch applied, and everyone should be sent an updated recovery disk.

      Why? Because otherwise, 90% of computers out there, run by the technologically clueless population will never get this patch applied.

    2. Re:Trust us! by Masem · · Score: 5, Insightful
      Remember that Microsoft wants to push a security model in which new bugs are reported only to the vendor and possibly a NDA-signed security group, and then in 'sufficient time' ( There's a part of me that says, ok, this type of reporting for a bug with this amount of security implications is probably a good thing, as if the bug was reported before the patch was available, you'd already have 'owned' XP boxes out there before MS had the patch. In the fashion they approached it, the amount of damage to XP (or other OSes) boxes will be minimized.

      But I feel there MUST be some preannouncement on such bugs, even if the details are minimal. Whenever you work on something, you cannot expect that someone else in the world is not also working on the same thing, but not for the same purposes. In the case here, eEye, the group that found the bug, was looking for it for purposes of good, but I would not expect that someone else, maybe a malicious group, was also narrowing in on the bug 5 weeks ago when eEye reported it to MS. (And then you have to add cyber-espionge that might have garnered that info for themselves?). In the 5 weeks it took MS to verify the bug and develop and test the patch, that other group might have caught up and started 'owning' boxes already. A preannouncement of the bug, simply outlining the effects, and any short-term security measures, would have prevented that group from having any significant harm on the boxes if they did exist.

      I know from a previous discussion that many sysadmins, when a new bug is discovered, want to know all the details up front so they can test the bug before and after fixing on their systems. This is understandable, but I think in the cases of bugs that can affect a significant large number of systems, such as this XP bug, that limited disclousure is better. I think a key step that could be done is institute a small group of trusted security people; bugs that are found are reported to the vendor and to this group. A person(s) from the group verifies the bug and puts out a digitalled signed statement that this bug exists, and that certain steps can be taken to correct it. Because of the status of these people, if they claim to have verified the fix, then that should be considered to be truthful, and thus limiting the need of sysadmins having to have full details to test it themselves. After a short period (no more than 6 weeks), the full details should be released, regardless if a patch from the vendor was available or not. That way, the limited disclosure lets the sysadmins know there's something going on and there's step they can take to prevent problems, and it gives the vendor time to fix the problem before that information falls into the hands of malicious people.

      --
      "Pinky, you've left the lens cap of your mind on again." - P&TB
      "I can see my house from here!" - ST:
    3. Re:Trust us! by Toraz+Chryx · · Score: 2, Insightful

      And how exactly will that help all the machines that are already setup? and may quite possibly have the automatic patch checking disabled?

    4. Re:Trust us! by kresmoi · · Score: 3, Funny

      Isn't this the point where the government should be stepping in to do somethi...oh wait. nevermind.

    5. Re:Trust us! by eggz128 · · Score: 4, Funny

      Why? Because otherwise, 90% of computers out there, run by the technologically clueless population will never get this patch applied.

      Yes they will. Thats what the auto updater is for. It downloads the patch in background while the technologically clueless user is browsing, then prompts them to install it by asking them "We send you this update in order to have your advice".

      You can guess what the standard response will be.

    6. Re:Trust us! by uchian · · Score: 2, Interesting

      Hmmm... Great. But we still get a race between the autoinstaller downloading the patch, and the attacks from the all new improved Code Red XP which isn't out yet but which I guess there are at least one or two versions of being written in back bedrooms the world over.

      If I recall, on average I was getting one attack every fifteen minutes from Code Red. So how long does this patch take to download? Especially since it's happening in the background, I guess that means it takes a lower priority over a users normal browsing.

    7. Re:Trust us! by Oily+Tuna · · Score: 2, Informative

      You can disable UP&P and SSDP before connecting. Instructions for doing this can be found by non-internet means.

      net stop ssdpsrv
      net stop upnphost

      --
      Mmmmmmm ... sushi.
    8. Re:Trust us! by budgenator · · Score: 2

      when a new bug is discovered, want to know all the details up front so they can test the bug before and after fixing on their systems.
      All of the links I've followed was a little light on details, which leads me to believe this vulnerability is pretty low level in the kernal stuff. Patches to fundemental kernal services can have far reaching side-effects, in short a patched WindowsXP would be basicaly a new OS compaired to an unpatched Machine; and all existing security testing is out-the window and you start from scratch.

      I think that they should be forced to burn a CD and mass mail them to consumers/ and display them at software outlets. It should contain there precious patches, and tutorials on computer security starting at newbee level. Gee how would have thought that the ease-of-usage features of M$ software might lead to security vulnerabilites.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    9. Re:Trust us! by Anonymous+DWord · · Score: 2

      If you know enough to disable automatic patch checking, I'd assume you have your reasons, and probably keep abreast of things on your own, in which case you already know about this patch.

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    10. Re:Trust us! by staeci · · Score: 3, Insightful

      I don't know about anyone else I if I was writing trojans/virii etc for XP the first thing it would do would be to disable auto-update and make sure that it stays off.

      --
      'Welcome to Rivendell, Mr. Anderson...'
  7. Serious Stuff by smooc · · Score: 2, Informative

    Although I refuse putting a Windows box directly on the internet (and btw neither a linux-box) even for home use, I know a lot of people who do.
    Especially all the unaware homeusers like my landlord for example. For systemadmins it already difficult to keep up to date with all the patches even with the various *update programs, at least they are firewalled

    And yet they (the homeusers) are the most vulnerable!

    And Microsoft proclaimed this was its most secure OS ever.

    --
    - In Memoriam: Jeroen de Bruin (1972-2004), bye bro
  8. Follow the EEC Lead. by Beautyon · · Score: 3, Offtopic
    The British and German govermnents have both realized that Open Source software is the way to go for many reasons, and are now deploying these superior solutions (or planning to) across all departments.

    What the makers of Linux distributions must do is concentrate on usability (and by extension consistency) and further refining their installers so that anyone off of the street can choose and then run Linux as painlessly as they have done with all the different windoze generations.

    Ximian are the closest to making easy to use tools that even my Aunt Grace (70) can use. A fully blown distribution from Ximian would be "most welcome" to use parliamentary language.

    --
    ATH0 Bitcoin: 1DnwFLXczVZV8kLJbMYoheUrpqHesjxrSi
    1. Re:Follow the EEC Lead. by joebp · · Score: 2
      The British and German govermnents have both realized that Open Source software is the way to go for many reasons, and are now deploying these superior solutions (or planning to) across all departments.
      Yeah, it does look that way when the UK government plans to buy 500,000 copies of Windows XP.
    2. Re:Follow the EEC Lead. by dbarclay10 · · Score: 2, Troll

      I won't comment on the "usability" of the desktops other than to say that almost all desktops under *nix that I've used(KDE, GNOME, plain 'ol Sawfish or IceWM) are extraordinarily easy to use. They're hard to learn(well, maybe not KDE and to a lesser extent GNOME), but they're absolutely amazing to use.

      Be sure to seperate "ease of use" from "ease of learning" :) Windows is easy for almost everyone to learn, because almost everyone has had exposure. But it's a bitch to use.

      I *will*, however, comment about installations. You're on drugs. It's that simple :) Mandrake is *easier* to install than Windows. Go ahead and try it. The installation is smoother, all hardware is autodetected, everything is just EASY. Windows installation isn't nearly so nice. I'm not saying it's their fault - after all, Windows is almost always preinstalled. They really havn't had much motivation to make a really kickass installer.

      --

      Barclay family motto:
      Aut agere aut mori.
      (Either action or death.)
  9. Microsoft's in trouble . . . by Anonymous Coward · · Score: 2, Funny
    . . . the only backdoors in Windows XP are supposed to be the ones negotiated in the antitrust "settlement."

    ~~~

  10. all rightey then! by Jburkholder · · Score: 4, Interesting

    Microsoft explained that a new feature of Windows XP can automatically download the free fix, which takes several minutes, and prompt consumers to install it.

    I must be living under a rock because this is the first I've heard of this. XP just starts downloading files without any action from the user? Does anyone beside me feel uncomfortable about that?

    1. Re:all rightey then! by lseltzer · · Score: 2, Informative

      three options, and it asks you which you want:

      1) download updates automatically and ask the user whether to install them
      2) notify the user automatically that updates are available and ask them whether to download and install them
      3) none of this

    2. Re:all rightey then! by Bodero · · Score: 2

      You must be under a rock. Windows ME had Automatic Update Notification too.

    3. Re:all rightey then! by Bodero · · Score: 2

      Well, the default install has it do that (in XP, at least). It doesn't require you to run it, it gives you the option to "Remind Me Later" (with options like 30 minutes, 1 hour, 1 day, etc) and "Install". You can configure it to just check for updates and not download them too. Or, if you wish, you can just turn them off and search for patches yourself.

    4. Re:all rightey then! by Bodero · · Score: 2

      You don't need to buy a product to know what's new and what's not, especially if you're going to criticize the 'new' feature.

    5. Re:all rightey then! by Jburkholder · · Score: 2

      Yes, I know about critical update notification. What I didn't know is that it is able to download files on its own and then prompt you to install later. My experience with critical update (win 98) was that it pops up and asks if you want to do the update or be reminded later. If I said 'yes', it would *then* start downloading the update and prompt you to start installing once the dl was finished.

  11. the arrogance by kubla2000 · · Score: 4, Insightful
    The arrogance of microsoft is astonishing.

    I honestly and truly hope that the US government brings them to their knees about this. That's wishful thinking, I know. However, two statements in particular in the Yahoo! article surprised me:

    1. Microsoft declined to tell U.S. officials Friday how many consumers downloaded and installed its fix during the first 24 hours it was available.
    2. Microsoft also indicated it would not send e-mail reminders to Windows XP customers to remind them of the importance of installing the patch.

    The reasons for point 1 are quite clear though. Acting on point 1 would indicate what a fiction the sales figures for XP really are.

    Point 2 is more difficult to fathom... perhaps they're hoping people won't notice? Why on earth, other than their disdain for non-corporate users, wouldn't they send out the reminder? Or even a reminder stressing the improtance of installing the auto-updater?

    1. Re:the arrogance by hacker · · Score: 5, Insightful
      1. Microsoft declined to tell U.S. officials Friday how many consumers downloaded and installed its fix during the first 24 hours it was available.

      The reasons for point 1 are quite clear though. Acting on point 1 would indicate what a fiction the sales figures for XP really are.

      Or that 2 million copies were sold, and 9 million people required the patch.

      Point 2 is more difficult to fathom... perhaps they're hoping people won't notice? Why on earth, other than their disdain for non-corporate users, wouldn't they send out the reminder? Or even a reminder stressing the improtance of installing the auto-updater?

      I can give you several reasons:
      • The longer a problem exists, the more support calls they will get to address it. Support calls to Microsoft are not free. Read: coffers.
      • The longer a problem exists, the more time they have to sell product that is vulnerable to it (see 1. above)
      • The longer a problem exists, they more they can milk their training program and create a new MCSE test for "Securing the Enterprise", or some such drivel.
      • They can't probably email everyone that purchased XP, because the piracy for it has gone through the roof. Every-single-person I've spoken to (more than 2 dozen) that have XP installed tell me that they pirated it. Nice going, Microsoft, that was a good plan.
      • Wasn't the whole point of XP and the "online ease of installation" supposed to automatically send you fixes?
    2. Re:the arrogance by tcc · · Score: 2

      >>1. Microsoft declined to tell U.S. officials Friday how many consumers downloaded and installed its fix during the first 24 hours it was available.

      >The reasons for point 1 are quite clear though. Acting on point 1 would indicate what a fiction the sales figures for XP really are.

      Funny, my first reaction was "they won't tell how many ACTUALLY downloaded the patch versus the number of sales" That way they wouldn't have to tell the fbi that after 24 hours only "5%" (fictionnal number) were patched, this goes without saying that it would make their fast "security"-patching model look terribly bad in practice (even if good on paper).

      --
      --- Metamoderating abusive downgraders since my 300th post.
  12. Huh? by Fat+Casper · · Score: 2
    Several experts said they had already managed to duplicate within their research labs so-called "denial of service" attacks made possible by the Windows XP flaws. Such attacks can overwhelm Web sites and prevent their use by legitimate visitors.
    Another risk, that hackers can implant rogue software on vulnerable computers, was conidered more remote because of the technical sophistication needed.

    Now IANASK (script kiddie), but isn't implanting "rogue software" a critical step in getting a DDOS up and running? It'd be nice if tech journalists knew a little about what they're reporting, especially the ones who get their paychecks from MS. On the other hand, it'd be nicer if coders knew a little more about what they're doing- especially the ones who get their paychecks from MS.

    --
    I spent a year in Iraq looking for WMD and all I found was this lousy sig.
    1. Re:Huh? by jsarek · · Score: 2

      Not in this case. The DDoS attack method they were talking about was using the XP exploit to force MANY replies to a PnP(plug and play)device message, from MANY machines, by simply sending the correct info to specific ports on any XP/Me/98 machines. Spoof the return IP where that info is supposed to go, to the IP of your most hated web page for example, and boom, instant DDoS attack that is amazingly anonymous, and would probably be very effective.

      The only "hard" part would be tagging a bunch of XP machines on cable or better to be used for the attack.

      This should scare you.

      High skill level black-hat types getting system access on all machines running XP worldwide shouldn't scare you quite as much, but that is also THEORETICALLY possible through this hole.

  13. National/International Security Concerns by ackthpt · · Score: 5, Informative
    Utterly fascinating that the DoJ (FBI) is looking into these flaws for the difficulty exploits could cause people, after basically letting M$ off the hook in the monopoly punishment phase. Hope the states prevail, and if you haven't written your opinion in (to the court), here's another reason why monopoly for a universally adoptedand used O/S is bad.

    Public comment is invited within 60 days of the date of this notice. Such comments, and responses thereto, will be published in the Federal Register and filed with the Court. Comments should be directed to Renata Hesse, Trial Attorney, Suite 1200, Antitrust Division, Department of Justice, 601 D Street NW, Washington, DC 20530; (facsimile) 202-616-9937 or 202-307-1545; or e-mail microsoft.atr@usdoj.gov. While comments may also be sent by regular mail, in light of recent events affecting the delivery of all types of mail to the Department of Justice, including U.S. Postal Service and other commercial delivery services, and current uncertainties concerning when the timely delivery of this mail may resume, the Department strongly encourages, whenever possible, that comments be submitted via email or facsimile.

    After all the blather and FUD from Redmond, they again pushed a product out the door with great media hype which is again unsecure. It would be so ironic if Microsoft were punished for this kind of negligence after getting a slap on the wrist. I don't expect that to happen though.

    --

    A feeling of having made the same mistake before: Deja Foobar
  14. Nonsense by ackthpt · · Score: 3, Funny

    This is the DoJ (FBI) we're talking about, they want to thank Bill personally for keeping them all busy and employed during these uncertain economic times. Also, I'm sure there's a card with a box of chocolates on the way to Redmond from McAfee.

    --

    A feeling of having made the same mistake before: Deja Foobar
  15. "You guys promised us..." by Jacco+de+Leeuw · · Score: 4, Funny
    "... that this backdoor would not be found for at least 2 years after this Bin Laden thing blows over!!"

    "Yeah, but those eEye guys didn't want to be on our Security-Through-Obscurity team! And we had all these great goodies for them!"

    --
    -------
    Warning: Slashdot may contain traces of nuts.
    1. Re:"You guys promised us..." by snake_dad · · Score: 2
      "... that this backdoor would not be found for at least 2 years after this Bin Laden thing blows over!!"

      I hear you.. However, this ofcourse is just the obvious leak that was supposed to be found real quick. The Official FBI Approved Backdoor (OFAB) will not be found until two years after Bin Laden is blown up :)

      to e-mail me, please remove all yourclothes

      viezerik... :P

      --
      karma capped .sig seeking available Slashdot poster for long-term relationship.
  16. It's to be expected... by jmichaelg · · Score: 3, Informative

    ...that security will suffer when you make an os too easy to use. It's an age-old tradeoff: security vs. ease of use. Moreover, with more features comes more complexity and with more complexity come more security holes.

    Don't want to check to see if there's a patch needed for your OS? Don't worry, we'll have the OS check for you. We can't guarantee that your computer will be talking to our servers when it downloads the patches but hey! it'll be automatic! Come to think of it, we can't even secure our own servers so we're not too sure what you'll be downloading even if you are talking to our servers but hey! - it's automatic!

    I can't think of a better argument for limiting the services an os provides than this fiasco.

  17. Re:They need to mind their own buisness by ackthpt · · Score: 2
    Who even told the FBI and Pentagon about the Internet?


    The DOD was instrumental in forming the basis of the internet, DARPA-NET


    Man, I remember when it was a secret network.


    No. No you evidently don't.

    --

    A feeling of having made the same mistake before: Deja Foobar
  18. Re:Just a thought/Microsoft a target? by texchanchan · · Score: 5, Interesting

    MagikSlinger is almost certainly right about this. However, if there is a terrorist group out there which was organized and sophisticated enough to carry out another large-scale, imaginative attack (which I doubt), Microsoft might be on their list for these reasons:
    - It's American, and a symbol of American characteristics such as innovation, which is in itself hated by reactionaries.
    - It's extremely visible.
    - Its market dominance could be perceived as "imperialist" or culturally imperialist by people who think like that.
    - It's a center of wealth and therefore, in puritanical minds, of evil decadence.
    - It could be thought of as a "vital organ" of the American economy by someone who doesn't realize how decentralized the American economy is.

    Arguing against an attack on Microsoft is the idea that it's causing enough trouble for the US by itself, but this concept is probably beyond the reach of most fanatics.

  19. FBI might have warned them.. by jsse · · Score: 2

    with all these blackdoors already 'embedded' in the OS...

    would make project Magic Lantern useless and idiotic.

  20. UPNP is all about handling NATed devices by weave · · Score: 5, Informative
    I haven't seent his mentioned much, but UPNP is all about handling NATed devices. There is a UPNP SDK developed for Linux, but until someone builds a useful kernel module out of it, Linux users are SOL (or maybe they are fortunate).

    Why care? Well, I found out after installing MSN Messenger that most of the features are useless behind a NATed network unless your router/firewall understands UPNP. Of course, Microsoft ICS and Servers understand it. I was getting frustrated since I couldn't use MSN messenger except for messages behind my home linux firewall. ICQ features like file transfer work fine by port forwarding the necessary ports or using a kernel module for it.

    So, here's the interesting bit. UPNP works by telling the other client on the other end what your private IP address is. Microsoft's docs say this is necessary for the other client to be able to find out how to talk back to you. I think this is stupid. The other end of an MSN connection just needs to look at the source IP in the packets it receives and just send there and hope the owner of the IP knows what to do.

    However, UPNP apparently knows how to handled multiple chains of NAT networks, kinda like I guess an old fashioned UUCP bang path. Problem is, it seems like one can modify that "bang path" to route return packets to false places. Can you say DDOS?

    So I sent a rant to my friends about this on December 10, and about how UPNP is a security hole waiting to happen according to posts I read out of google searches...

    Here's my rant...

    I read the tech article about msn messenger and NAT devices. In order to do pretty much anything beyond chat, you can't be behind a NAT device unless that NAT device is a Microsoft device.

    Basically, it suggests installing Windows ICS for home users and corporate users should use a 2000 server for NAT and msn's extra features will work.

    Fuckers...

    ICQ works just fine behind a NAT. They are basically just trying once again to leverage one product to sell another....

    Their explanation is that the client must send its IP address to the other user so it knows where to send files, audio, video, etc, and since it's got a private IP, it screws up. So it needs to query the NAT device for what ITS IP is. But that's really stupid since there is already a connection open for chatting and all the other client has to do is look at that connection for the source IP and use that instead and everything else would just work....

    Someone on a newsgroup said this is another security hole waiting to happen. Basically, it's trusting client for security. I send a connection to your msn messenger client and tell it what IP to send its stuff to? What if I send it the IP address of someone I am trying to DOS? Arrgh...

    They'll never learn...

    Microsoft claims UPNP is a universal open standard. It'd be interesting to learn more about its origins and who is really controlling development of it, security of it, etc. Microsoft claims all manner of peripheral vendors will be supporting it.

    Is the concept itself as flawed as it seems, or is this just yet another case of Microsoft's implementation of something being flawed?

    1. Re:UPNP is all about handling NATed devices by weave · · Score: 3, Informative

      Sorry, bad link in my comment above. The UPNP Linux SDK is at upnp.sourceforge.net

    2. Re:UPNP is all about handling NATed devices by Robber+Baron · · Score: 2

      But isn't that because most NAT devices currently will only route port-specific traffic to a single, specified private IP? How else are you going to be able to specify which machine behind the NAT gets the traffic intended for it? MAC? IP? The sender's gotta know which machine behind the NAT gets the traffic and the NAT's gotta know where to route it to, and current NATs aren't all that smart. I'd prefer it if they'd come up with something other than private IP's, because that's slightly more info than I'd care to share. I'd rather see a system where a session cookie is created when the person logs on and use a router that can distinguish cookies, but they aren't giving us that option are they?

      --

      You're using her as bait, Master!

    3. Re:UPNP is all about handling NATed devices by weave · · Score: 2
      I'm behind a Win2000 box doing NAT, and MSN Messenger's features don't work. I don't know what the hell you're talking about.

      Don't bitch at me. Go read the Microsoft tech note on the topic and deploy the recommended Microsoft solution at your site as documented there.

    4. Re:UPNP is all about handling NATed devices by Corgha · · Score: 2

      Basically, it's trusting client for security.

      Microsoft has sort of a history of this. With Terminal Services, they log the IP address the client gives the server, instead of doing a getpeername() or something. (See this Bugtraq post.)

      You've got to wonder what they are smoking. Maybe they're stuck back in the DTP/FTP days (1970s and '80s), but the nature of networking sure has changed since then, and wise programmers learn from the mistakes of the past.

      Anyway, you want to talk protocols that break horribly with NAT, let's talk IPSec's out-of-band key-enchange mechanism. Grrrrr.

      Am I the only one that thinks that long before IPv6 becomes common, everyone + dog will be behind NAT? Even when IPv6 becomes common, will the ISPs really give home users the 48 bits they're supposed to? Making protocols that work with NAT is not that hard, and as you point out, is better for security than some of the alternatives.

      Grrrr. Thanks for reminding me of all this suppressed anger regarding stupid protocols. :P

    5. Re:UPNP is all about handling NATed devices by swb · · Score: 3
      Is the concept itself as flawed as it seems, or is this just yet another case of Microsoft's implementation of something being flawed?

      I think the MS implementation is the problem, not the concept. Most people get a bee in their bonnet about this because they think it breaks the NAT "security" model.

      Problem is, NAT provides security because it breaks routing, not because it is a security system by itself. That someone has come up with a routing/networking technique that keeps NAT's address translation ability *and* provides inbound connection capabiltiies is really pretty cool.

      However, because NAT has traditionally provided the secondary benefit of security to the interior network, any system that implements a way to connect to interior networks through NAT should provide at least three security models:
      • No interior access. Should be the default setting as it most closely matches the behavior expected from traditional NAT
      • Interior access to specific defined machines. Like current static NAT mappings.
      • Full interior access. Should require manual intervention to achieve this state.
    6. Re:UPNP is all about handling NATed devices by Salamander · · Score: 2
      In the case of MSN messenger I assume that the client keep some sort of a connexion open with the central messenging server.

      Yeah, that scales really well. Requiring that people leave outbound connections open to centralized servers for weeks at a time just so they can receive notification when events happen is just really bad design. Revealing internal IP addresses is also bad. Fortunately, SOCKS already solves enough of this problem to be useful (though it has its warts) and is supported by most programs that need to do this sort of thing.

      --
      Slashdot - News for Herds. Stuff that Splatters.
    7. Re:UPNP is all about handling NATed devices by inburito · · Score: 2

      This is assuming that you mean a remote sender who already has an established connection with the client..

      You need to go no further than gnutella to see that this has already been implemented. In gnutella these are called push requests.

      So you have a communication protocol for the established connection that includes commands for the server(sender) to ask the client to open an additional connection.

      If you meant running a server behind nat I should ask you to stop smoking whatever it is that you smoke..

  21. An analogy with the biological world by Ryu2 · · Score: 5, Insightful

    In epidemiology, one of the mitigating factors of the spread of any disease is simply the diverse genetic makeup of the targeted population.

    The opposite to this is what's called a monoculture, where one particular genetic structure is present in the large majority of the population. Such situations will usually not last long, beacuse once something is found that affects that population, it spreads quickly and decisively.

    With Windows having such a large share of the market as it is, could this be considered the electronic equivalent of a monoculture? Would one major virus or security flaw cause much more damage to the net than otherwise would have happened, because of the homogenity of the net's computer systems in terms of OS?

    Whether the king is Linux or Windows or MacOS, or..., is having a near monopoly market share ofany one OS a good thing in light of this philosophy? Hmm. GFood for thought.

    --
    There's 10 types of people in this world, those who understand binary and those who don't.
    1. Re:An analogy with the biological world by NumberSyx · · Score: 3, Insightful

      Windows is Prostitute and Microsoft is her Pimp. The Pimp wants the Prostitute to be easier and more accessable and doesn't want to inconvience the John by making them use a condom, so naturally the Prostitute is going to get a few diseases. The Pimp will want to keep the disease a secrect, but will also want the Prostitute to keep working. So she is going to spread the disease around alot before it gets treated.

      --

      "Our products just aren't engineered for security,"
      -Brian Valentine,VP in charge of MS Windows Development

    2. Re:An analogy with the biological world by mpe · · Score: 3, Insightful

      With Windows having such a large share of the market as it is, could this be considered the electronic equivalent of a monoculture?

      Actually a monoculture of clones.

  22. Cracking spree holidays? by Zarathustra.fi · · Score: 3, Insightful

    I'm thinking new computers that have been bought this Christmas as presents. I wonder how many of these computers are preinstalled with Windows XP. As we speak, these computers are all wrapped in gift papers; who will patch them? Do people even have time to do anything else except get prepared for the big day? And are people aware of the severe security flaw?

    Probably quite many of those computers go to people who are going to have it as their first computer. And what are they going to do first? Turn it on. And probably, go online with it..

    And the crackers will be waiting for the easy prey.

    --
    __
    Zarathustra.fi
    Modern man has no goal, no aim, no ideals.
  23. Reminds me of the Simpson's episode .... by wift · · Score: 3, Funny

    where Burns and Smithers goes through high security steel doors, scanning stations, gates and end up in the control room that has a old screen door to the outdoors in it allowing a stray dog in. Seems to me that sums up Microsoft's entire security structure.

    bonus karma points to anyone who correctly identifies the show number.

    "Oh for christ sake"- Montgomery Burns after discovering a stray dog in his XP like high security control room.

    --
    ....... Thus ends my attempt at wit or whatever
  24. You know by ASIO · · Score: 3, Interesting

    This would be a damm good way to get Magic Lantern on a whole lot of systems.

    This was mentioned earlier, but now the FBI is pushin it as well, Coincedence??

    --
    On the other hand, you have fingers :)
  25. Re:Way to go FBI by Anonymous Coward · · Score: 4, Funny

    Why buy a CD? Using this bug, you can install Mandrake remotely to all Windows XP systems connected to the internet.

  26. frustrated FBI by WildBeast · · Score: 3, Insightful

    They failed to protect the country from terrorists and now they're trying to rebuild their reputation among the population by getting involved in the Internet. Th

    Looks like MS isn't the only one with good marketers :)

    1. Re:frustrated FBI by WildBeast · · Score: 2

      I'm not blaming them, au contraire. I said it before and I'll say it yet again, destruction is way easier than creation.

      Even though FBI's job is security, they can't prevent all crimes from happening.

      That said, their's no reason to blame MS either.

  27. Does it? by barzok · · Score: 3, Informative

    I set up an XP Home Edition box on 12/14 and after installation, went to Windows Update. Found a dozen (4 critical, 4 non-critical) updates waiting for me.

    1. Re:Does it? by killthiskid · · Score: 2

      I like critical update (I maintain 24 machines at a university, very good users). I have my users trained to properly to use windows update.

      It's not always enough.

      But what kills me is when I do a virign Win98se install.

      You'd think one critical update would be enough, but at my last count there are critical updates for the critical update 4 layers deep.

      So if a person reinstalls windows, does a critical update, and then thinks they are safe, they are wrong.

      They need to go back a few more times.

  28. comment from a former Microsoft developer by AdamBa · · Score: 4, Insightful
    There was two bugs reported here. One in SSDP that makes it possible to use XP to launch denial of service attacks, one that is reported as a buffer overflow.

    So what is up with those buffer overflows...do Microsoft developers hate users and not care about quality? Well, no. It only takes one buffer overflow in the whole system that hundreds of developers have worked on, to make it vulnerable.

    At Microsoft the ultimate way people are valued is at review time when bonuses, stock options, and raises are awarded. Do developers get hosed for leaving buffer overflows in? Well, not as of when I left (April 2000). But maybe that will change, slowly.

    Eventually you have to stop accepting excuses like "Gee code is really complicated and I thought I was being careful" or "we really tried to think through this design" and recognize that essentially every buffer overflow comes from being lazy as a developer, or not accounting for what kind of garbage packets can come in off the net. If Microsoft starts emphasizing that you can be fired for leaving a buffer overflow in, then things might change. Of course it's a little unfair, there is no doubt lots of clunky code in there that just doesn't happen to expose an externally exploitable buffer overflow (and merely crashes the system or something), but you start emphasizing the necessity to go over things with a fine-tooth comb to prevent buffer overflows, it will improve all the code.

    Because although there may be a few cases where someone really tried to check boundary conditions and just did it wrong in the code, in most cases developers are just being lazy about writing the code robustly to begin with. Plus if you have some code to prevent this and you write it wrong, you haven't tested your code properly anyway.

    More ruminations at this osopinion article.

    - adam

    1. Re:comment from a former Microsoft developer by satch89450 · · Score: 5, Insightful

      So what is up with those buffer overflows...do Microsoft developers hate users and not care about quality? Well, no. It only takes one buffer overflow in the whole system that hundreds of developers have worked on, to make it vulnerable.

      It takes only one buffer overflow in the whole system that any number of developers, from one to one million, have worked on to make it vulnerable.

      It doesn't matter how careful you are. Zero defects at the individual level is a pipe dream. The goal of software quality assurance is that you test code to determine whether it conforms to the specifications with no astonishing side effects. Structured implementation (use of safe libraries, re-use of validated code) can reduce the effort and increase the quality of code.

      Want to eliminate buffer overflow? It's easy. Just write a routine ONCE that sucks up characters and puts it into a buffer, debug the corner cases ONCE to ensure you can't go beyond the boundaries, and use that routine for all your work, without exception. Not even when marketing comes in and says "Hey, you didn't come out on top in performance when HAL Magazine ran their tests!" Oh, and your QA people have to actually try to execute some kind of buffer overflow as one part of their suite of test cases...

      When a buffer overflow is discovered "in the wild," you find out the source of the buffer overflow and take appropriate action -- against the coder and against QA as well. You have to show these people that you MEASURE them by this sort of stuff.

      By the way, don't forget that code should check for attempts to go "outside the box" by using unusual character sequences like ".." in URLs, too. Again, write a single block of code that does the job right, test the hell out of the corner cases, and use that code, without exception.

      A Google search yields some interesting approaches. I would like to see the adoption as part of the ANSI definition of the C language an extension to the STR* library routines that are length-safe, such as the STRL* routines found in NetBSD; see the man page and the discussion in the Secure Programs HOWTO.

      Don't kid anyone. Buffer overflow can be avoided, by putting in place the proper process and discipline to do the job right.

    2. Re:comment from a former Microsoft developer by AdamBa · · Score: 2
      Of course they can be avoided with proper coding. You hardly need a separate function...to check for a basic buffer overflow you need to know the array in question, how much data can fit in there, and how much data is attempted being stuffed in there. If you have those 3 things, you can just put an if() in the code.

      So it's not a question of not being able to do it, it's a question of not doing it. That's what I meant about hundreds of developers...one bad egg can spoil everything.

      Consider this article about the problem. Jim Allchin is quoted as saying, "We have gone through all code and, in an automated way, found places where there could be buffer overflow, and those have been removed in Windows XP." The automated way is things like PREFIX that I discuss in the osopinion article I linked to above (the big cleanup was done right after Windows 2000 shipped, thus the results appeared in Windows XP). But as I pointed out, you are still dependent on a developer having the will to really investigate the PREFIX report, honestly admit that a problem could be there, and go to the trouble of fixing it, rather than just try to hand-wave explain why it won't occur.

      It's really hard to blame this on the test/QA team (even if they work in an environment with more enlightened development/test relationships than Microsoft). How many bad packets do you have to blast at something before hitting a vulnerability, if there is one? This kind of problem is *so much* easier to catch when the code is being written, or even via code review, than it is by experiment in a test lab. This is the kind of thing a developer really should be able to find when they are testing just their code. The lab can handle all the wierd interactions between different pieces of code.

      Unfortunately when you have millions of lines of code, like Windows XP does, it is mind-numbing to go through all of them looking for this kind of thing. So now the barn door is open and the buffer overflows have escaped into the code, and they will have to be rounded up one at a time by being found "in the wild" as you put it.

      - adam

    3. Re:comment from a former Microsoft developer by satch89450 · · Score: 2

      You hardly need a separate function...to check for a basic buffer overflow you need to know the array in question, how much data can fit in there, and how much data is attempted being stuffed in there. If you have those 3 things, you can just put an if() in the code.

      And just how many opportunities for making a mistake are you introducing with that viewpoint?

      "If you have those three things, you can just put an if() in the code." True. Of course, you have to avoid an off-by-one boundary problem, you have to test against the length of the right array (I've done that one myself), you have to get the right index or pointer or whatever...in short, there are LOTS of ways of screwing up even with the right facts.

      And in a million lines of code, there WILL be screw-ups, even with the best people.

      Unfortunately when you have millions of lines of code, like Windows XP does, it is mind-numbing to go through all of them looking for this kind of thing. So now the barn door is open and the buffer overflows have escaped into the code, and they will have to be rounded up one at a time by being found "in the wild" as you put it.

      I maintain a software engineer worty of the title would recognize just how stupid relying on code review alone is to catch something this important, and would instead prefer to reduce the number of opportunities for error by using a common routine where possible. Not to mention reducing the complexity of the coding of the parent routine, so that coding, testing, reviewing, and debugging effort are reduced.

      In your work, how are you measured? I'm measured by how much code goes out the door marked "sold" without technical support calls.

    4. Re:comment from a former Microsoft developer by AdamBa · · Score: 2
      "If you have those three things, you can just put an if() in the code." True. Of course, you have to avoid an off-by-one boundary problem, you have to test against the length of the right array (I've done that one myself), you have to get the right index or pointer or whatever...in short, there are LOTS of ways of screwing up even with the right facts.

      Most of that you have to get right just to pass it to a function. And how is the function written...does it expect to be told the length of the buffer including or not including a final '\0'? Is the second argument the allowed length and the third one the length to test, or vice versa? The key is taking the time to have the code check and having a mindset that this is something you need to guard against...how you do it is much less important.

      Now it is true that Microsoft is very bad at sharing code between groups. How many times has strlen() been reimplemented because someone didn't like the one in the standard library? And the same is true of methodology.

      You should understand that this UPNP code doesn't sound like it was done by the core NT team (here comes my bias as a former NT kernel developer). I can picture Steve Ballmer screaming five years ago about how hard it is to just stick a printer on the network and have it be discovered...so out of that comes the "Universal Plug and Play" team. Probably they are somewhere under Windows Me since that group is more consumer-focussed than NT/2000/XP. But of course they need a little piece of code that runs on XP. So some random person writes that code, maybe they are in the NT team, maybe not, maybe their code is run through PREFIX, maybe not. But when the code runs, it's got system-level access and can be used as an exploit. Meanwhile who is testing that code...probably a UPNP test team that is mostly focussed on some big matrix of machines and OSes and hardware devices, making sure that each device is detected by each machine and OS. Where in there is anyone going to test for buffer overflows in the XP code...nowhere is the answer. And if the XP team says, "in order to include code with XP you need to do all this stuff to verify it," the answer is probably "go away, we need to get UPNP working ASAP" (ironically, since UPNP is now going to be disabled on so many XP machines that when the hardware comes out next year, the whole scheme won't work anyway). I'm making some guesses here, but I bet the truth is pretty close to this. So there you have it hackers, find some piece of code that runs at high privilege on XP, but also involves some code that has to run on 2000 and Me and etc. and has enough external issues to distract a test team...that is where you will find your buffer overflow exploits.

      In your work, how are you measured? I'm measured by how much code goes out the door marked "sold" without technical support calls.

      When I worked at Microsoft I was not measured this way, which is unfortunate because it should be a component of the evaluation. We were evaluated on some combination of how much code we wrote, how respected we were in the team, and how many hours we worked. OK it was more than that, but the key is reviews were done every 6 months and once they were done they were never revisited. So questions like "how has this code held up after a year in the marketplace" never figure in someone's review. Maybe if Microsoft gets sued over an exploit and forced to lay out its engineering procedures in court, then it will get serious about penalizing developers for leaving around exploitable code.

      Plus you couldn't actually fire someone for leaving in a buffer overflow. Although technically Microsoft employs people "at will" and can fire them at any time for any reason or no reason, in fact to avoid lawsuits they have an elaborate procedure of putting people on probation, which usually just results in them leaving for another group within Microsoft. If they actually fired someone for a buffer overflow the person would sue and bring in all these experts to talk about how hard it is to catch every one etc.

      - adam

    5. Re:comment from a former Microsoft developer by sphealey · · Score: 2
      I can picture Steve Ballmer screaming five years ago about how hard it is to just stick a printer on the network and have it be discovered...so out of that comes the "Universal Plug and Play" team.
      In other words, a capability which has been a core function of Novell Netware for 7 years. Too bad Microsoft didn't copy that while it was busy copying the worst features, and ignoring the best features, of Novell networking, eh?

      sPh

  29. Why Many Hate Microsoft... by weave · · Score: 4, Insightful
    The reason many hate Microsoft is because they are just so damn arrogant. You can't put yourself up on a pedestal and not expect people to look at you closely. It's the same phenomenan as some of those televangelists. They are casting themselves as holy men all the while fleecing their followers and screwing teenage secretaries.

    I remember when NT 4.0 came out (they were fairly low key with NT 3.x) and Microsoft claiming it was far more secure than UNIX and you wouldn't have buffer overflows because the source was closed and people couldn't find them even if they existed.

    I also remember many years ago them claiming NT was more secure and showing the number of submissions of security holes posted to Bugtraq (before NTbugtraq) there were for UNIX vs NT (back when nothing serious ran on NT and no one really cared less about it to look for holes).

    Now they want their code running in everything, including acting as firewall devices. I find this so fucking funny I could just split a gut. You're going to protect machines running code "x" by installing a device running much of the same code "x" to protect those machines from the world?

    I just find it a bit frightening. The entire world running on code from one manufacturer that is not open to public review. I'm even more surprised that foreign governments are so trusting of it.

    You know what's scary? We just bought an EMC disk array and had to give it an IP address for management. Did a port scan on it. WTF? It's listening on netbios ports. Use smbclient to take a gander at it and low and behold....

    Domain=[AZBYCXDWEVFU] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]

    Workgroup Master
    AZBYCXDWEVFU CLARIION_SPB

    I call EMC and they say "Oh, the new clariions run a stripped down NT kernel in their service processors." :-( Joy... my SAN is now trusted to that super sekure Microsoft code. At least I can block it from the world through my router which, for now, is running non-Microsoft code...

    Can you imagine the harm one could do with a hole in THAT? The financial world survived WTC through redundancy and real-time mirrors of data kept in far flung locations. There are disaster recovery data centers where entire warehouses are filled with machines just waiting to kick in during a crisis. So now you have your storage area networks themselves controlled by Microsoft code. Just exploit the hole-of-the-week to get your code inside a corporate or government firewall, seek out these storage networks running NT kernel code, trash them, take out the primary and backup locations. Chaos.

    1. Re:Why Many Hate Microsoft... by mpe · · Score: 2

      The entire world running on code from one manufacturer that is not open to public review.

      Quite often exactly the same code. So you have a monoculture of clones. Which is even more dangerous than a regular monoculture.

  30. Surprised this happened now by phillymjs · · Score: 2

    Since the government these days seems to be all about protecting innocent corporations from us evil individuals, you'd think something this would have happened after, say, the second "ILOVEYOU"-style worm brought corporate mailservers around the country to a screeching halt-- during an administration that was actually prosecuting Microsoft for its monopolistic misdeeds.

    But now the Republicans are in office, and faced with a real conundrum: what do they do when one mega-corporation is selling dangerous, unsecure products to all the other mega-corporations? Because that's who they're thinking about here. If it warmed the cockles of your heart that the government was concerned for all those consumers who ran out and bought XP, you're delusional-- they're worried about seeing more shit like this once XP gets widely adopted in the corporate world.

    ~Philly

  31. You really think that'll work? by barzok · · Score: 3, Insightful

    You're saying that the same people who "need" the auto-updater because they're clue-deficient will know to do this? These people are sitting ducks.

  32. Re:Just a thought/Microsoft a target? by Enahs · · Score: 2
    Of course, we won't mention similarities between Windows and MacOS.

    I wouldn't expect that level of imagination from people who name themselves after Star Wars characters. ;-D

    --
    Stating on Slashdot that I like cheese since 1997.
  33. I watch too much Law and Order... by weave · · Score: 2
    You want to get a witness to cooperate. Threaten to throw them away for a long time with trumped up charges, then plea bargain them back out on the streets in return for their cooperation.

    Want to get government backdoors in the OS that runs almost every computer in the world? Threaten the company with trumped up charges which will ruin them for life, then cut deals with them so they can return to business as usual in return for their cooperation.

  34. Re:Yet another link to MSNBC by Enahs · · Score: 2

    Except that MSNBC is the most openly critical newssite, when it comes to MS. I suppose they think it gives them journalistic credibility to be so openly critical of their parent company. ;-)

    --
    Stating on Slashdot that I like cheese since 1997.
  35. How is That a TROLL? by budgenator · · Score: 2

    A big part of the 'ploit seems to revolve around M$ trying to do a "hardware detect" over the LAN to load the proper OS or third party "drivers". They are suprised that network boundries are primarily psycological, so their ease-of-use feature leaks out into the internet and causes security problems.
    Linux® on the other hand demands much more standards compliance and relies less on "drivers" to provide translation layers and introduction of security and or performance problems.

    And I agree, I just did a WindowME® install a few months ago, on a freshly formated hard-drive SuSE has blown Windows out of the water for a couple years on ease of install, auto-detected hardware not to mention ease of use. I do disagre with modern Linux desktops being hard to learn, for the same functionality as windows its about the same or easier to learn, but you can do alot more on the desktop in *nix than windows. (I like the way jaws drop when I change screen resolutions, and jump back and forth between six different screens and have twenty differnt apps running at the same time, from windows users.)

    --
    Apocalypse Cancelled, Sorry, No Ticket Refunds
  36. Buffer Overflow as a Decoy to bigger hole by lildogie · · Score: 3, Insightful

    Even the FBI is crying "buffer overflow," following in Microsoft's footsteps to divert attention for a designed-in security flaw.

    It makes sense, from the perspective of a defensive Microsoft. "Buffer overflow? Who hasn't slipped up once or twice and had a buffer overflow bug? We have our code scanners routing out the last one or two of these bugs, they'll all be gone soon and we'll all be safe."

    The bigger gaff is that they designed the OS to say "hack me" (or words to that effect) whenever some other device--any other device--asks to fondle, as it were, the OS's drivers. That this is a huge security exposure is obvious to anyone who is old enough to remember the early days of hacking. Some hotshot designers at Microsoft, (probably with degrees in marketing, not computing) designed this "hack me" feature into the OS intentionally.

    Now they have the attention of the NIPC/FBI. Even FBI agents (who, over the last 10 years, gave new meaning to the term "anti-intellegence") know that on Christmas day, millions of un-patched XP OS's are going on line, in the same 24-hour period. The hackers will be waiting to stick their electronic -er-fingers in those exposed UPNP ports and leave behind a little deposit.

    Maybe, maybe not, the FBI realizes that some of those systems will have time-delay bugs planted in the pre-patched OS's. Then, downloading the patch will produce the false security that keeps the spirit of the XP season alive throughout the coming year.

    The silver lining? Corporate PHB's, the holy grail of Microsoft marketing, will lose confidence in any of Mr.Bill's claims of reliability and security, once and for all. XP was supposed to be the one-size-fits-all OS, from palmtops to corporate web front-ends to data warehouses. (not that it was the first attempt at this unification by Microsoft, or even their competitors.) Even the golf-buddy execs are going to remember the day when the FBI started pushing patches to the monopolist's holey flagship.

    Did anybody notice, last year, when Bill Gates started to cut the cord to Microsoft? He did see the big fall coming, you know. Not as stupid as we make him out to be, eh?

    1. Re:Buffer Overflow as a Decoy to bigger hole by rlowe69 · · Score: 2

      The bigger gaff is that they designed the OS to say "hack me" (or words to that effect) whenever some other device--any other device--asks to fondle, as it were, the OS's drivers. That this is a huge security exposure is obvious to anyone who is old enough to remember the early days of hacking. Some hotshot designers at Microsoft, (probably with degrees in marketing, not computing) designed this "hack me" feature into the OS intentionally.

      Deja vu? This reminds me of Outlook virii. Can someone remind me why my e-mail program has the ability (or need for that matter) via Visual Basic to DELETE THE CONTENTS OF MY HARD DRIVE? Stupidity, plain and simple. Secondarily it is absolutely terrible marketing-driven software engineering.

      I've said it before and I'll say it again: If you are designing for Joe Public, you have to keep in mind how ignorant Joe Public may be and PROTECT HIS ASS.

      --
      ----- rL
    2. Re:Buffer Overflow as a Decoy to bigger hole by kcbrown · · Score: 2
      The silver lining? Corporate PHB's, the holy grail of Microsoft marketing, will lose confidence in any of Mr.Bill's claims of reliability and security, once and for all. XP was supposed to be the one-size-fits-all OS, from palmtops to corporate web front-ends to data warehouses. (not that it was the first attempt at this unification by Microsoft, or even their competitors.) Even the golf-buddy execs are going to remember the day when the FBI started pushing patches to the monopolist's holey flagship.

      Methinks you have far too much faith in corporate PHBs. Why should they lose confidence in Microsoft for these security blunders when they didn't lose faith over things like the countless Outlook viruses, or the IIS vulnerabilities, or the MS-SQL problems? No, just like every other time, they won't blame Microsoft -- they'll blame their own IS guys.

      And I'll tell you why: because they know that they can't sue Microsoft, and they have to "successfully" place the blame somewhere.

      Microsoft is popular with them not because it can be sued, but because the PHBs are sheep that follow the herd wherever it goes. They'll think Microsoft is the greatest thing until enough others think otherwise. In short, it's a self-perpetuating problem that will only be fixed when the economics of going with another solution instead of Microsoft means the difference between surviving as a business and failing as a business.

      If Microsoft does things right, the PHBs won't have that kind of economic incentive until it's too late and they really don't have any choice of where to go anymore.

      --
      Use 'slashdot stuff' in the subject line in any email you send me if you want to get past the spam filter.
  37. Re:Monopoly has serious security implications by flacco · · Score: 2
    This discovery highlights the dangers of the monoculture that comes with the de facto systems monopoly.

    Beat me to it. "Monoculture" - I think we should be hearing a lot more about this word. It's not just a marketplace issue.

    --
    pr0n - keeping monitor glass spotless since 1981.
  38. Of course they can't by phillymjs · · Score: 2

    Microsoft marketing: "Windows XP is the most secure and crash-proof OS ever!"

    Microsoft EULA: "...but if it turns out not to be, tough titties on you for trusting us when we said it was. You can't sue us, because you agreed you wouldn't at install-time. And we think we can afford better lawyers than you, anyway. So neener neener neener!"

    The no-liability stuff in license agreements, I'm sure, began life with the noble purpose of protecting companies from getting hit with lawsuits by morons who should have known better, or greedy individuals just out to screw a company out of a quick million. Typical of everything it does, though, Microsoft has twisted the purpose of the EULA into its current form-- that of a "lawsuit-proof vest" used to prevent people or companies with, in many cases, very valid beefs about Microsoft products, from taking them to court over it, and allowing Microsoft to push crap on us with impunity and just shrug when we get bitten by bugs or security holes.

    Imagine if other companies did this. What if you had to agree to a EULA on a train ticket before boarding the train, then then the train derailed because the operator was high on crack and speeding around a curve, and you wound up in a wheelchair for the rest of your life? You'd probably never take the train again. But what about companies who have to spend large sums of money on antivirus software and on employees who have to stay late to undo the damage done by the Outlook/Windows Virus/Worm of the Week. They just accept it and keep on using the same shitty software.

    If it were possible to sue the living fuck out of Microsoft over these bugs and security holes, I think Microsoft QC might get a little budgetary upgrade. But nobody wants to be the first person to test the validity of the shrinkwrap/disk envelope/click-to-be-bound-by-it EULA in a court of law.

    ~Philly

    1. Re:Of course they can't by snake_dad · · Score: 2

      Just an idea... Might I sue them, if somehow I suffer damages if the internet is brought on its knees via this leak? Like if my hypothetical online shop went bellyup as a result of a major hack of millions of XP machines? I never installed XP, so I didn't agree to anything. IANAA (American), but let's assume that I am :)

      --
      karma capped .sig seeking available Slashdot poster for long-term relationship.
    2. Re:Of course they can't by phillymjs · · Score: 2

      Once again, the "you can't afford lawyers as good as ours" comes into play. Good luck proving in court that you were put out of business by a DDoS attack via XP machines taken over by the UPnP exploit. Microsoft's sharks will poke holes in your server and firewall logs and probably ultimately get the court to fine you for wasting everyone's time.

      ~Philly

    3. Re:Of course they can't by mpe · · Score: 2

      The no-liability stuff in license agreements, I'm sure, began life with the noble purpose of protecting companies from getting hit with lawsuits by morons who should have known better, or greedy individuals just out to screw a company out of a quick million

      Does anyone know where this entered into software? Maybe way back to when IT involved contractors custom writing software for much larger companies.

  39. Re:Just a thought/Microsoft a target? by fanatic · · Score: 3, Informative
    Microsoft might be on their list for these reasons:

    How about the biggest reasons:
    • They hire lots of foreign programmers, (see their support for H1B visas) making them pathetically easy to infitrate
    • they neither know nor care about security - never have, never will, couldn't fix it if they wanted to because their corporate culture is 'features, Features, FEATURES!'
    --
    "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody
  40. Federal Criminal Charges.. by 3seas · · Score: 2

    Federal Criminal Charges need to be brought (and not dropped) against Microsoft in this case.

    This way the Government can come to a settlement with MS where those who were harmed by the hole can't sue MS.
    Along the lines of the deal struck between the tobbacco industry and government.

    Seriously, with all the digital rights issues going, certainly the compromise caused by such a hole but without
    criminal legal action against mircrosoft is only going to tell people that lady justice doesn't have her blindfold on.

    Thats' a serious problem! Assisting criminal activity knowingly.....

  41. People won by robinjo · · Score: 2, Funny

    I think the full implications of what MS has allowed to happen is going to felt more and more as real users suddenly understand that MS basically does not care about its users.

    Look at

  42. Sophistication? by SIGFPE · · Score: 2
    Another risk, that hackers can implant rogue software on vulnerable computers, was considered more remote because of the technical sophistication needed


    And of course technical sophistication is so rare that the chances of finding but one person in the world both able and willing to exploit it is...about 99.99%

    --
    -- SIGFPE
  43. Careful what you wish for by Gorimek · · Score: 2

    The arrogance of the US government is far bigger than M$'s. When they take over, things usually do not get better.

    1. Re:Careful what you wish for by Malcontent · · Score: 2

      In this case MS bitch slapped the most powerful nation on the planet like a 5 year old stepchild. It's clear the govt is no longer in charge of anything anymore so don't worry. The real worry is when the social security agency or medicare will pull an "enron" and screw a few million people.

      --

      War is necrophilia.

  44. Re:Can't get through? Different patch mirror sites by SuiteSisterMary · · Score: 2

    I'm sorry, but if you can't be bothered to find the configuration setting that tells Windows not to ask for confirmation, you have no business making any sort of judgement on it's usability or worth.

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  45. M$ Security problems web log? by Gorimek · · Score: 2

    If it doesn't already exist, someone should create a web page with all the big M$ security problems described chronologically. Just listed in the order they were discovered with 1-2 lines about what they do.

    It would be a neat place to refer people to who don't believe that M$ is a security problem.

  46. Built-in firewall protects? by SilentChris · · Score: 2

    Does anyone know if XP's built-in firewall protects these ports?

  47. Re:Just a thought/Microsoft a target? by fwr · · Score: 2

    Yes, with minimizing you have to keep moving your mouse down to the bottom of the screen, or transferring between using the mouse and using the keyboard. Plus, it looks cooler. Besides, when was the initial code on the new GNOME/KDE apps/controls that you say look like XP started? Was this before or after Windows XP was first released to testers? Kind of makes you wonder who is copying who, right? Just because Microsoft comes out with a "finished" product before GNOME and/or KDE does not necessarily they started working on said product before GNOME/KDE...

  48. faking out the XP user by Alien54 · · Score: 2
    I suspect (though I could be wrong) that there would be some kind of key-signing of the update patch that's done by MS and then checked by XP before installing the same.

    I am sure that someone could human engineer the error messages. and since they would actually never go to MS, but maybe to some Bogus Site, like Microsoft-security.com some folks could be fooled by this. I am thinking of the Pay-Pal Scam that was running around a few days back, using simple email. It wouldn't be that hard for people who were expert to fudge something to send a user to La la land, with appropriate dialogs, disclaimers, etc. etc.

    --
    "It is a greater offense to steal men's labor, than their clothes"
  49. RAW sockets by CAIMLAS · · Score: 2

    I might not be completely clued in here, but wouldn't such a devistating, overall vulnerability be contributed to WinXP's implimentation of RAW sockets? Or am I not correct in my understanding of the full control extent that RAW sockets allow?

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
  50. The AG of MD by Ho-Lee-Cow! · · Score: 2
    http://www.oag.state.md.us/

    Maryland Residents should be writing our dear Mr. Curran, explaining the problem in simple terms, explaining that making users go into the internet for the patch is not sufficient for dealing with this faulty product, and demanding to see the OS recalled and a fraud investigation initiated.

    Might want to copy the DoJ, even if Ashcroft is a sell out to Redmond.

    Here's your chance, Maryland! Do us all proud.

    --
    In space, no one can hear you moo.
  51. If XP is most secure, imagine other Windows'! by roman_mir · · Score: 3, Funny

    ``This is the first network-based, remote compromise that I'm aware of for Windows desktop systems,'' said Scott Culp, manager of Microsoft's security response center. ``Every Windows XP user needs to immediately take action.'' He called it a ``very serious vulnerability.''

    ``This is the most secure version of Windows we have ever released,'' said Culp, adding that complex software ``will always fall short of perfection.''

    http://dailynews.yahoo.com/h/ap/20011220/tc/micr os oft_hackers_7.html

    1. Re:If XP is most secure, imagine other Windows'! by PMan88 · · Score: 2, Funny

      "This is the most secure version of Windows we have ever released"

      that says a lot

  52. Significance by 90XDoubleSide · · Score: 2
    The real reason this is of significance is because it is finally giving MS some very bad press for their security blunders.

    Now, of course there will be dozens of MS apologists on this thread, and you can do a lot of apologizing about this bug, after all they got a patch out before there were any known uses of the exploit, and on the other hand this vulnerability leaves your computer more wide open than almost any that have come before, but I'm not interested in taking that debate any further, as that is what the rest of the thread is about.

    The reason I think this story has become significant is because this bug is actually getting reported by large news organizations. Slashdot might run an article every time some script kiddie finds a new hole in IIS, but when is the last time you heard about that on your local news?

    This bug, however, has actually been featured on all the big news organizations, thanks to the government statement. I saw a two-minute piece on it on CNN and a 30-second piece on Fox News, both feturing the governments warning that the patch would not be enough and everyone should disable UPnP on their machine. Flipping by CNN Headline News, I noticed the headline at the bottom, "Win XP hyper-vulnerable to hackers."

    It is getting people to be concerned about security that will get something done about it; security isn't a selling point right now. When was the last time you saw an OS (besides OpenBSD) listing security as its top feature?

    So think what you will about the impact of the bug itself, our government should be applauded for once for finally getting the media spotlight on security.

    --
    "Reality is just a convenient measure of complexity" -Alvy Ray Smith
  53. OT/Funny McAfee Story by 90XDoubleSide · · Score: 2
    Also, I'm sure there's a card with a box of chocolates on the way to Redmond from McAfee.

    Anyone else got to see the demo version of McAfee ActiveShield installed on new HP systems? One of my friends called me over one day because he said his antivirus had found a virus on his computer. I told him just to hir repair and if that didn't work, hit delete, then he told me there were no repair or delete buttons.

    When I went to look at the problem, I saw ActiveShield had popped up a dialog, "McAfee ActuiveShield has detected an infection in this file somefile.mp3.vbs VBS/Love Letter." With a button that took you to the McAfee website where you could remove this virus using McAfee online for "only 39.95." After getting him NAV, we found that it had infected every eligible file on the system (about 23,000), and LoveLetter of course overwrites the original files.

    I found his restore disks and went back to my Power Mac.

    --
    "Reality is just a convenient measure of complexity" -Alvy Ray Smith
  54. Gov shouldn't be using MS anyway by MrResistor · · Score: 3, Informative
    That statement isn't meant from the point of view of OSS zealotry (although I certainly have some feelings in that direction), but because the NSA has never rated an MS product as being secure in a networked environment. Part of the NSA's job is to issue information security recomendations, which other agencies are then supposed to use when putting together their systems.

    IIRC, NT at some point was rated secure when not networked.

    --
    Under capitalism man exploits man. Under communism it's the other way around.
    1. Re:Gov shouldn't be using MS anyway by SuiteSisterMary · · Score: 3, Informative

      An OS is never rated secure; a system is rated secure. That includes OS, hardware, programs running, and physical setup, amoung several other things. Note that most standard UNIX systems are immediately disqualified from the first 'secure' rating of C2 because they tend not to have ACLs, amoung other requirements.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  55. Ford/Firestone - make the effort by mgkimsal2 · · Score: 2

    Well, Ford might have thought "we can't possibly get ahold of everyone who has this problem, so we won't notify anyone".

    MAKE THE EFFORT. If people aren't registered with a valid email (and check it occasionally) that's their problem.

  56. We all know that Microsoft lies, but... by edunbar93 · · Score: 5, Insightful

    This is a really, really, really big one. It should be in the newspapers. Microsoft has claimed some time ago (free karma to the one who posts a link) that closed source, for-profit software and operating systems are more secure because the company can actually *hire* people to do security audits of the source code, whereas open source developers aren't motivated to do it because it's really boring, and there's no glory in it.

    Now, we all know that OpenBSD has proved them wrong, by proving not only that open source developers *want* to do hardcore security audits of the source code, but that doing hardcore security audits on source code prevents security holes from being released into the wild. OpenBSD hasn't had a remotely exploitable security hole in the default install in FOUR YEARS! Windows XP has been in release for for all of about two months, and already there's a major security exploit found.

    This proves by Microsoft's OWN ADMISSION, either they do not hire people to do the hardcore security audits they say they can, or if they do, they can't do it as well as the volunteers who "obviously" don't do it at all because there's no monetary motivation to do so.

    With lies like this, Microsoft couldn't get into a Better Business Beurau if they paid each of its members a billion dollars.

    --
    "No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
  57. Maybe there's another bug.... by cathryn · · Score: 2, Insightful

    >THE FBI'S National Infrastructure Protection >Center said that, in addition to installing a >free software fix offered by Microsoft on the >company's Web site, consumers and corporations >using Windows XP should disable the >product's "universal plug and play" features >affected by the glitches.

    If the FBI wants universal plug and play off, it sounds to me like there's another security hole there. Why else would they request this? Isn't Microsoft policy to keep these things quiet until they are fixed? They depend on no one knowing about the problem to keep machines safe. But, maybe for the FBI, especially with the terrorism situation, who might have critical data on XP machines, this thin line of defense isn't quite good enough.

    --
    http://junglevision.com -- Shamus for Gameboy
  58. You lazy bastards by Anonymous+DWord · · Score: 2

    http://www.google.com/search?q=xp+hole
    Results 1 - 25 of about 63,500. Search took 0.44 seconds.

    1) Microsoft issues patch for "serious" XP hole - Tech News

    The flaws were discovered by Aliso Viejo, Calif.-based security company eEye Digital Security and reported to Microsoft about six weeks ago, said Marc Maiffret, eEye's chief hacking officer.

    It's in the first fucking link on Google. Or was that too difficult?

    --
    "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
  59. Re:The Blue Nowhere by Anonymous+DWord · · Score: 2

    Basically the story was about a hacker Wizard(not lotr type) who could root your system whenever you went online, and you wouldn't be aware of it. This guy would then use info from your computer to kill you.
    Now I here XP can give up System control simply by having you go online!


    Isn't that what The Road Ahead is all about?

    --
    "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
  60. Re:Can't get through? Different patch mirror sites by SuiteSisterMary · · Score: 2

    I won't make any comment as to your intellegence, but if you can't figure out 'right click on the recycle bin, and unselect 'display delete confirmation dialog' and hit 'ok' or, in other words, right click, left click, left click, left click, then you might just be having a problem of some sort, even if only a complete and utter bias against Microsoft that causes you to make unreasonable assertions.

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  61. And then there's open sockets.... by Sara+Chan · · Score: 2
    The open-sockets DDoS hole, first railed against by Steve Gibson, should also start to rear its head. Microsoft previously claimed that Windows XP security was so superb that the required (zombie) programs wouldn't be able to run in the first place--that is, Windows XP machines would be safe from external forces running malicious programs!


    Perhaps the script kiddies were waiting until people got new PCs for Christmas.

  62. Re:Can't get through? Different patch mirror sites by SuiteSisterMary · · Score: 2

    Different design philosophy, and different intended end result. You pick the tool for the job, not the job for the tool.

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  63. Re:Symbol of innovation? by Some+Dumbass... · · Score: 3, Insightful

    Yes, but how much does Microsoft ADVERTISE that they are innovative. How many times do you think the word innovate shows up on www.microsoft.com?

    Exactly. Microsoft does occasionally innovate. Having to click twice on a menu entry in the menu bar to get all the options is an innovation! It's a lousy one, but still...

    The real problem with MS is, as you said, their Real Innovations:Advertised Innovations ratio. It's pretty low. It's not that they're not creative, they're just not as creative as they say they are. If a person acted like that, you'd call them "full of themselves". You probably wonldn't like them very much either :)

  64. yes, there are some tools by AdamBa · · Score: 2
    Read the osopinion column I linked to above which discusses the 60K number (although oso seems to be dead right now). Basically there are some tools to find suspicious code (but not fix it), but they are still subject to human error/arrogance. Things like BoundsChecker have been used at Microsoft but I don't think it works on kernel-mode code which is where the best buffer overflow exploits can be found.

    - adam

  65. One OS To RULE them all. by ImaLamer · · Score: 2

    One OS To Rule Them All,
    One phone-home to find them,
    One OS To Bring Them All,
    And with a security hole bind them...

    ...PAY ME HEED MY GOOD USERS,
    FOR THIS IS A STORY,
    OF CRACKERS AND HACKERS, OF CODERS.
    A WONDEROUS TALE YOU SHOULD KNOW,
    FROM AN AGE NOT TOO LONG AGO,
    BEFORE LINUX WAS THE MEASURE OF THINGS.
    WHEN THE NET GENTLY MURMURED
    HER SONG TO THE USERS,
    AND THE FLAWS GENTLY WHISPERED ITS PART;
    WHEN THE MICRO STOOD TALL,
    AND IS STILL KNOWN TO ALL,
    BY HIS WEAKNESS AND UNCARING OF DATA.

    More?

    Three OS's for the BSD-kings under the sky,
    Seven for the Linux Kernel Team in their halls of stone,
    Nine for Apple Men doomed to die,
    One for the Bill Gates on his dark throne
    In the Land of Redmond where the Bugs lie.
    One OS to rule them all, One OS to find them,
    One OS to bring them all and in the darkness bind them!
    In the Land of Redmond where the Shadows lie.

    "This is the Master-Flaw, the One Bug to rule them all.
    This is the One Bug lost many weeks ago,
    to the great weakening of its maker's power.
    Now, he greatly desires to have it again,
    - but he must NOT get it"

  66. NTFS Journaling by _Sprocket_ · · Score: 3, Informative


    How much longer has Windows (NT) had a journaling filesystem than Linux?


    My understanding is that NTFS' journaling was rudimentary at best. It hasn't been until its recent incarnation (introduced with Win2k) that its managed anything close to a true journaling file system.
  67. Re:XP auto-update wins. by Webmonger · · Score: 2

    Actually, I too have McAffe auto-updating, but it's running on a Linux server. Every night, a cron script sucks down the latest definitions using wget.

    While McAffe runs on Linux, it doesn't do much for Linux users. The reason it's there is to filter mail for Windows viruses. There would be no point in making a similar product for Linux.

  68. Re:OK, M$ is getting stupider by johnnyb · · Score: 2

    piss-poor quality? Yeah, I guess that's why Windows is used on more than 90% of desktops and that MS Office is so popular.

    ****

    You don't see McDonald's winning any product-of-the-year awards, do you? That's because the business behind McDonalds works so well, not the product itself. Just like Microsoft.

  69. Did you say "Free Karma"? by Dog+and+Pony · · Score: 2, Informative

    Hehe. Worth a try, I guess. Here is one link about that very thing:

    You are welcome. :)

  70. Re:A different analogy... by Kris_J · · Score: 2

    Actually, it's more like a dealer selling you a car that doesn't have any locks then asking you to leave it outside their dealership while they take their time getting 'round to it. Chances are everything will be fine by the time they've installed the locks, but will you ever really be sure?

  71. Re:Just a thought/Microsoft a target? by jacobito · · Score: 2

    Exactly what statistical possibility of infiltration are you referring to? And why would foreigners on a work visa be more statistically likely to commit acts of espionage or terror than American citizens? I'm ready and waiting to see the logic behind that claim.

    I think that the poster was playing on the recent claim that the Al Qaeda had planted malicious code in Windows XP, and to the average American's fear of Muslims and Arabs, and yes, I think that his post was a manifestation of the latent American racism and xenophobia that bubbled back to the surface following the September 11 attacks. Or perhaps you think that he was alluding to the fifth column of white Canadian programmer-terrorists in the software industry? Seriously, who are you kidding?

    Talk of racism, whether overt or not, makes me uncomfortable too (after all, it should), but it's better to discuss the topic openly and candidly rather than blowing smoke and making excuses.

  72. A poor analogy, roaches as monoculture success by xixax · · Score: 2

    Most of our oil deposits come from vast monocultures of algae called stromatolites, basically cells that photosynthesise and spend no effort on defending themselves. This worked swimmingly until snails arrived on the scene and ate the algae. You still get stromatolites today, but only in really salty places where snails cannot dwell.

    Stromatolites were especially susceptible to predators because they made no effort to defend themselves. With network connectivity becoming more pervasive, more previously isolated Windows boxes spew services to any network they can reach.

    After millions of years OTOH, Roaches are still everywhere. This is because the suckers are robust and paranoid and therefore hard to kill. Even if you do kill one roach, it is quickly replaced.

    Monoculture is only a part of the ecology.

    Xix.

    --
    "Everything is adjustable, provided you have the right tools"
  73. Re:Just a thought/Microsoft a target? by Malcontent · · Score: 2

    "It's American, and a symbol of American characteristics such as innovation, which is in itself hated by reactionaries. "

    Well I would not use the word innovation but yes it's an american symbol

    "It's extremely visible. "

    No doubt.

    "Its market dominance could be perceived as "imperialist" or culturally imperialist by people who think like that. "

    or maybe they are sonvinced there are back doors planted in it by the CIA or NSA or some such organization. Certainly I wouln't put it past them.

    "It's a center of wealth and therefore, in puritanical minds, of evil decadence."

    i think when most people in the world look around and see the abject poverty they live in and the constant misery they are forced to put up with they might resent obcene wealth and flamboyant lifestyles elsewhere don't you? Certainly somebody can use this as a recruitment tool.

    "It could be thought of as a "vital organ" of the American economy by someone who doesn't realize how decentralized the American economy is."

    This argument was put out my microsoft during the anti trust trial. MS (and their lapdog politicians) frequently argued that breaking up MS would disrupt the economy and harm the country. I heard a guest on the O'Reilly factor (I forget his name right now be he is a very vocal critic of the democats and clinton) blame the recession on clintons pursuit of MS. The Idea that harming MS would harm the economy of the US was broadcast far and wide by everybody from executives of MS to politicians. I suppose it would not surprise me if some terrorists believed it.

    --

    War is necrophilia.

  74. OK, bad example by AdamBa · · Score: 2
    I should have said something like, "is prevented from causing problems by other parts of the code" or "is never uncovered by users."

    - adam

  75. Re:Just a thought/Microsoft a target? by fanatic · · Score: 2

    Oh you're so right. (the rest of his post was massively sarcasm "agreement" with mine.)

    I understand where you are coming from in attacking my post, but let me ask you: how many of the 19 hijackers were Canadian or British or ANY ethiicity other than Middle Eastern, most notably Egyptian and Saudi Arabian? While we shouldn't prejudge, that's not the same as saying we should put on blinders and not more carefully investigate members of specific groups. You may deride this a 'racial profiling' - I call it common snese.

    --
    "that's not encryption - it's a new perl script that I'm working on..." - from some Matrix parody