Slashdot Mirror


Microsoft, Monocultures, Security FUD & Other Fun

techiemac writes "Dan Geer, who has been mentioned on Slashdot before due to his warnings about Microsoft's "monoculture" has just been written up by AP for his warnings about the widespread use of Microsoft products and the serious security flaws that are being discovered. This story is quickly becomming big news (Yahoo is currently carrying it on their front page). For those who don't know, Dan Greer was fired from @Stake Inc for his criticism of Microsoft (they are a big client of @Stake Inc). " Somewhat related, there has been interesting reaction pieces on ORA and OSDN to a recent, some say ill-informed article run on DevX.

40 of 509 comments (clear)

  1. MS Open Source Is Fertile Ground for Foul Play by anandpur · · Score: 5, Funny

    Now part of MS Windows source code is open on Internet so is "MS Open Source Is Fertile Ground for Foul Play"

    1. Re:MS Open Source Is Fertile Ground for Foul Play by syn3rg · · Score: 5, Interesting

      I hope no FOSS developers look at that source. It could "taint by association" -- which makes me wonder if that wasn't the real reason for the release. MS now realizes the fight is over source code. By releasing (through an agent: Mainsoft) the source they can now claim injury if similar methods appear in FOSS.

      --
      The contents of this message have been doubly encrypted by ROT13
    2. Re:MS Open Source Is Fertile Ground for Foul Play by swb · · Score: 5, Interesting

      You're totally right, but it'll be hard for a lot of people to not look at it. I say this tongue in cheek, but people will slow to look at a car wreck -- why not the "Windows" source code? Plus these are highly curious people.

      I think the better encouragement is not to *keep* the source code. It would be quite difficult for MS to "prove" that any given developer had seen the purloined source, barring the conspiratorial notion that MS is running false-flagged IRC channels and web sites and collecting evidence on who is grabbing it. But not keeping a copy of it (which would be illegal anyway), they remove the easiest proof that they have been tainted by it.

    3. Re:MS Open Source Is Fertile Ground for Foul Play by tuba_dude · · Score: 5, Funny

      I don't mean to put too much of a damper on this intellegent discussion, but I really enjoy the association of Windows' source code with a car wreck.

      --
      "The government of the United States is not, in any sense, founded on the Christian religion."
    4. Re:MS Open Source Is Fertile Ground for Foul Play by Kilobug · · Score: 5, Informative

      As I said in the news about the source code leakage, this is a false fear, the same one MS uses about the GPL "do not read GPL code or you'll never be able to write commercial code afterwards".

      Copyright is _NOT_ patent. You can read copyrighted work and then write something similar by yourself. Copyright does not protect ideas, structures, algorithms or data formats. Copyright protectes the actual code - copy/pasting or recopying Windows code into Free Software would be disastrous. Reading Windows source code to understand protocols or formats and then writing your own Free implementation is not.

      Of course, you're not allowed to have windows source code at first, and you can be sued for having it. Not for writing source code with the knowledge you gained for it; the same way that reverse engineering is fordbidden in US, but if you use reverse to write Samba or a XFree driver, Samba or the driver will be legal. You can be sued if it's proven you used reverse, but your code will not.

    5. Re:MS Open Source Is Fertile Ground for Foul Play by Anonymous Coward · · Score: 5, Informative

      Reverse engineering is NOT illegal, you just have to do it carefully. Various companies do it ALL THE TIME. You have one group decompile the program or take apart the device. They then write a specification for the device based on what they learned (bonus points if it's a school). This specification is given to a middle layer which then passes it on to the programming team. The programming team writes code to match the spec they got from the middle layer. The code is no different from what they would write if the spec was simply made from scratch, in fact, the programming team is never told that they're working from a reverse engineered spec. All you have to do is make sure that no one from the decompile team has contact with anyone from the programming team and you're good to go.

      If absolutely nothing else, you can do the reverse engineering in the UK, where reverse engineering is explicitly allowed by law. The law even says that regardless of EULA terms, you can decompile software.

  2. I guess ... by fewnorms · · Score: 5, Funny

    ... the old adage "No one ever got fired for choosing Microsoft" is true after all. Look what happens when you actually try speaking ill of the beast...

    --
    Veni, Vidi, Velcro!
    1. Re:I guess ... by banzai51 · · Score: 5, Insightful

      Wonder how Slashdotians will feel when they fully explore the anti-monoculture philosophy and realize it means keeping Microsoft rather than eliminating it and creating a new monoculture?

    2. Re:I guess ... by fewnorms · · Score: 5, Interesting
      And here I thought all this time it was "No one ever got fired for choosing IBM".
      You are correct of course, but I think the saying should be changed to "No one ever got fired for choosing $MONOPOLY", which would be true. From personal experience I can tell you people in my enviroment actually have been fired for suggesting/choosing a hardware/software solution which is not industry standard and 10 times more expensive.
      Luckily, the climate is changing, but it is ever so slowly...
      --
      Veni, Vidi, Velcro!
  3. They still don't get it by archeopterix · · Score: 5, Insightful
    Microsoft, which denies pressuring @stake to fire Geer, says the comparison between computers and living organisms works only so well.

    "Once you start down the road with that analogy, you get stuck in it," said Scott Charney, chief security strategist for Redmond, Wash.-based Microsoft.

    Charney says monoculture theory doesn't suggest any reasonable solutions; more use of the Linux (news - web sites) open-source operating system, a rival to Microsoft Windows, might create a "duoculture," but that would hardly deter sophisticated hackers.

    True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible. Without a Microsoft monoculture, he said, most of the recent progress in information technology could not have happened.

    Microsoft still want us to believe that the only way to integrate is to run One System (theirs) everywhere. They don't get (more precisely: don't want to) common open standards and protocols.

    And they are wrong about "duoculture". Linux, having many parties behind it(many distros, different kernel versions) has much mure internal variety than all versions of Windows out there.

    1. Re:They still don't get it by DangerSteel · · Score: 5, Interesting
      >>Microsoft still want us to believe that the only way to integrate is to run One System (theirs) everywhere. They don't get (more precisely: don't want to) common open standards and protocols.

      And not only do they want us to run thier OS, they want to make sure you are integrating thier Office, and collaboration (think .net) programs. To get the full value of Windows. I think I got enough "full value" of windows on my users machine affected by Blaster last fall...

    2. Re:They still don't get it by tomstdenis · · Score: 5, Insightful

      You could argue all the levels at which windows boxen are patched counts as "diversity" ;-)

      KIDDING!!!

      The article does miss a more important point that they do touch upon [sadly I'm siding with MSFT here...] is that "if you don't fence in the crops deer will eat it all".

      A stupid windows user will be an even more stupid linux user. Sorry to tell y'all this. Them the breaks.

      What's worse is distros like Redhat which feature binary updates are totally not scalable. Gentoo is one decent approach but requires a hell of a lot of patience to get going [and update when things like KDE pop up].

      All in all, MSFT sucks for being slow with updates and for using proprietary standards. Most OSS sucks for being hard to configure [for newbies] and occasionally slow/tiresome to deal with.

      So moral? Update as much as you can, don't run every binary you find, use a virus scanner [keep it up to date] and use a firewall. Heck even the stupid WinXP firewall is sufficient to protect users from most default settings virii [e.g. messenger virus, etc].

      Tom

      --
      Someday, I'll have a real sig.
    3. Re:They still don't get it by passthecrackpipe · · Score: 5, Insightful

      Dude, you must have ducked the last time somebody started swinging the old cluebat around. "Them's the breaks" indeed.... a stupid windows user makes for a very good linux user. You fail, just like MS, to differentiate between machine user and machine admin. While a stupid windows user has full admin access out of the box to all his settings, config, hardware setup etc. a linux user does not. Simply by virtue of most of the distro's making a point of creating a seperate root account during setup, and explaining why, ensures you shield the user from the most common types of mayhem (s)he can create. The "stupid" user has to really go out of his/her way to actually screw things up bigtime, something they usually don't really set out to do.

      --
      People who think they know everything are a great annoyance to those of us who do.
  4. Once... by flewp · · Score: 5, Funny

    Once I thought I had mono. They took a culture and it turns out I just had Windows.

    --
    WWJD.... for a Klondike bar?
  5. Interesting spin ... by Anonymous Coward · · Score: 5, Interesting

    ... on why the Microsoft monoculture is so important; from the AP article:

    True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible. Without a Microsoft monoculture, he said, most of the recent progress in information technology could not have happened.

    Really? Could someone more familiar with Microsoft and their products kindly give me examples?

    1. Re:Interesting spin ... by Airconditioning · · Score: 5, Interesting

      If Microsoft decides to support a product, piece of hardware, or whatever out of the box with their next version of Windows, that piece of technology starts to become very popular. That technology then gets refined and maybe, later on an integral part of a computer system.

      USB comes to mind but I think Apple beat them to it?

    2. Re:Interesting spin ... by Anonymous Coward · · Score: 5, Interesting

      USB comes to mind but I think Apple beat them to it?

      Let's start a bit earlier... can you say
      mouse
      GUI
      5 1/4" floppies
      cd-rom
      post-script printing
      true-type/open-type
      Firewire
      and the list goes on

  6. I hope he's wrong ... by Anonymous Coward · · Score: 5, Insightful

    As much as I dislike the company, there are too many critical systems that are relying on Windows Servers. The release of a kernel crippling virus or worm could result in loss of human life.

    1. Re:I hope he's wrong ... by Anonymous Coward · · Score: 5, Informative

      I call bullshit. Give me one example.

      I work as a consultant in Health IT and I'll give you 5 that I've found in my travels.

      1. Pharmacy systems
      2. Allergy interaction checking systems
      3. Dietary system, wrong or delayed diets can kill a patient
      4. Workstations in the ER that have access to critical applications and patient charts
      5. Workstations that communicate with the ambulence and med chopper teams

  7. Open for exploit by downix · · Score: 5, Insightful

    A great example of what can/will happen with the Microsoft monoculture can be found in the potato blight of Ireland. For those that lack any historical reference here, Ireland had a booming population due to the introduction of a nice, hardy breed of potato. For years, everything was going great, everyone had food, the potato became the staple of the diet. Everyone ate potatos, it is estimated to have been between 20-40% of all food consumed during this period.

    Then a viral attack that affected only this particular breed of potato struck. Within less than a year, whole crops failed, the economy collapsed as people literally starved to death.

    Yet, other breed of potatos were completely unaffected. It wasn't the reliance on potatos that was to blame, it was the reliance of one strain of potatos that was Irelands achilles heel.

    That is our economys achilles heel, Windows.

    --
    Karma Whoring for Fun and Profit.
    1. Re:Open for exploit by Spacejock · · Score: 5, Funny

      So, what you're saying is that Debian Potato is a bad idea?

  8. Great Microsoft quote by Anonymous Coward · · Score: 5, Funny

    "Once you start down the road with that analogy, you get stuck in it," said Scott Charney, chief security strategist for Redmond, Wash.-based Microsoft.

    One you start down the road with it, you get stuck in it. Sounds like a perfect description of the lock-in aspects of their products, though I think "Roach Motels for your data" is catchier.

  9. not the first time... by ThaReetLad · · Score: 5, Informative

    This is not the first time that A. Russell Jones has made controversial claims about Linux on DevX. At the end of august last year this story was run here on /. where he claimed that there should be a standard desktop for Linux.

    --
    You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
  10. Re:Rememebr folsk the def for monoculture by Anonymous Coward · · Score: 5, Funny

    Clippy: "It looks like you are trying to write..."

  11. Hah! by arvindn · · Score: 5, Insightful
    True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible.
    But this is exactly what open source buys you! The diversity of thousands of operating systems. Several distros, several versions of each, custom configurations, choices in every application space... put all these together and you increase diversity a thousandfold. Easily. There's really a powerful analogy between open source and biological structures, because the code is out there in the wild. Splitting, mutating, recombining. Forking, patching, merging. No two systems are exactly alike. A software ecosystem. Enormous complexity and diversity, enormous robustness and strength, extremely high rate of progress. Linus often makes analogies to evolution when explaining kernel hacking. That's no coincidence.

    Diversity != incompatibility. One standard, many implementations. What the M$ guy says is pure FUD.

  12. unsound refutation from MS by tverbeek · · Score: 5, Insightful
    [MS mouthpiece] says monoculture theory doesn't suggest any reasonable solutions; more use of the Linux open-source operating system, a rival to Microsoft Windows, might create a "duoculture," but that would hardly deter sophisticated hackers.

    This neglects that fact that Linux itself has internal diversity that makes it less vulnerable to "disease".

    It's also not necessary to have "thousands of different operating systems" to gain some resilience. If (for example) half of all computers were Type A and the other half Type B, the rate of transmission of type-specific malware would be slowed dramatically. It wouldn't prevent pandemics, but it would slow them down.

    --
    http://alternatives.rzero.com/
  13. The real problem is... by Noryungi · · Score: 5, Interesting

    I have thought about this whole monoculture thing recently, and here is my take on it...

    Microsoft made a conscious decision, a long long time ago, to make sure that everything in its Office applications (starting with Word) would be scriptable with VBA. And that the VBA scripts would have access to the entire underlying OS.

    At the time, it made perfect marketing sense: the king of word processors was Word Perfect, and it offered advanced scripting functions. Microsoft had to duplicate this functionalities if it wanted to kick WordPerfect ass and establish Windows and Word as the desktop champions. And it worked -- when was the last time you used WordPerfect on your PC?

    The only problem is, of course, that Windows security (3.x was a single user, single task operating system) was absolutely broken from the very beginning. After all, if you are the only user on your machine, you don't need a lot of security, do you? Wrong. You may need a different kind of security, but you still need some sort of framework to protect your resources. Windows never provided any kind of security at all.

    Then came the Internet. And, with it, a virus transmission vector of incomparable speed. The rest, as they say is history. Microsoft never bothered to create proper security and, because it completely ignored the Internet before 1995 (remember the Gates memo?), they were caught unprepared by the hordes of yahoos who write VBA viruses. VB is easy to use, viruses are easy to program in VB and, thanks to MS stupid decisions, they were allowed to run wild.

    In effect, most users and sysadmins are, today, paying the price of a marketing decision: Microsoft decided to design VBA, all the while ignoring the research that proved that application scripting needed to be severely limited and controlled. Emacs LISP scripts and shell files in the UNIX world were prohibited a loooooong time before VBA was even created.

    They kicked a competitor out of the field and, in doing so, created more problems for themselves (and for us!) than they solved...

    --
    The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
    1. Re:The real problem is... by tverbeek · · Score: 5, Funny
      when was the last time you used WordPerfect on your PC?

      (At the risk of being modded -1, Overly-Literal)

      10:37pm, yesterday.

      --
      http://alternatives.rzero.com/
  14. We suggest you reboot... by emtboy9 · · Score: 5, Insightful

    You know, there was, at one time, a long running joke about Microsoft tech support. The answer to any problem, according to MS support (and I heard this directly from them on more than a few occasions) was "We suggest you reboot to fix this problem" OR, Shut up and re-install.

    And now, here is the "Chief Security Strategist" for MS saying (regarding the monoculture analogy) "Another difference: computers can be unplugged from the network and rebooted; organisms cannot."

    So, is he really implying (God I hope not) that most exploits can be solved by unplugging the computer from the network and rebooting???

    I hope not, and maybe its just the way the AP story was written, but it sure sounds like a dismissal of most of the Windows security flaws.

    --
    "Our funds have never taken part in toxic or death spiral convertible financings of any sort" -BayStar's managing partne
  15. The trouble with diversity by rqqrtnb · · Score: 5, Interesting

    Without a doubt, online security is a major concern. The idea of monoculturism may be applicable to the computer industry due to the prevalence of MS operating systems. This, of course, assumes everyone has the same version of an MS operating system, with a single, universal exploitable flaw. The fact that not everyone has the exact same operating system nor the exact same component and software configuration tends to undermine the argument of 'monoculture' somewhat more.

    However, diversity of computers fosters a much higher learning curve to a machine that is already far more complex than 80% of the people using them understand. I'm a proponent of unity in the field of computers in that the UI of any OS should be the same as EVERY OTHER UI. This promotes a uniform learning curve for everyone so that learning one machine or OS does not restrict a person to that particular product or platform for life.

    People want to learn as much as they need to - and not have to constantly relearn it - in order to do the things they want to do with the computer. Imposing 'bio-diversity' on the operating systems of the world will only create sub-monocultures between which comparability issues and cross learning would be difficult for most to handle unless the UI for each system is essentially the same.

    I'd REALLY like to see Linux be available to anyone without having to have any knowledge of Unix protocols, have the same driver support and always be able to run ANY program regardless of the original OS requirements without having to constantly tweak everything into compliance. If anyone knows a way of doing this, or if it's already been done and you know how, PLEASE post it here.

  16. Solution: Multi-OS Boxes by G4from128k · · Score: 5, Informative

    One solution to the monoculture problem is multi-OS architectures in which a single process is executed on multiple independent codebases within each box.

    On high-reliability systems (Space Shuttle & X-29 flight controls), multiple redundant subprocessors attempt to compute the same answer. If the subprocessors get different answers, the majority-rules and the system logs the exception. If each processor ran independent code, then exploits of any one codebase would be detected and disinfected. A multi-system with one exploited/infected codebase would continue running while ignoring the output of the infected subprocessor.

    The system would still have some vulnerabilties. Simultaneous attack on a majority of the codebases might succeed in redefinig the majority to suit the malware. Also, codebase independence is very hard. More than likely several codebases might share the same fault (e.g. a buffer overrun bug). Attacks on the overseer/majority-rules system might also succeed. Finally, if the standard has an exploit (e.g., decrypting WiFi WEP), then all codebases implementing the standard are vulnerable.

    The biggest downside is bloat and cost. But at least it would give people a reason to buy the latest greatest chips from Intel, AMD, IBM, etc.

    --
    Two wrongs don't make a right, but three lefts do.
  17. i hate this ... by torpor · · Score: 5, Insightful

    different operating systems, which would make integrating computer systems and networks virtually impossible.

    This is such utter bollocks I can't even handle it.

    The reason integration is difficult is because it is made difficult by those who do it.

    It has nothing whatsoever to do with 'operating systems'. It seems to me that 'operating systems' don't mean what they used to mean ... in the good ol' days, an "OS" was all you needed in order to get some basic work and programming done on some hardware.

    Nowadays, it seems that an "OS" == "all the crap I think I'm gonna need one day, bundled into a single directory structure".

    If the OS is doing its job then integration is not impossible, it is 100% feasible and easy.

    An OS which doesn't do its job, doesn't allow integration. Its very telling to me that Microsoft choose to redefine the task of an OS rather than actually make their OS do the job its supposed to do.

    Integration between OS's is supposed to be easy. That is what an OS is all about, after all. Maybe someone should tell that to the 'gurus' from Redmond that mouth off about operating systems all day long ...

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
  18. Re:For those who don't know... by Anonymous Coward · · Score: 5, Informative

    If you read the paper that was published, listened to any of the news accounts (including the conference call press conference), and read CCIA's disclaimers, you would know that he made it perfectly clear that this was something he was doing on his personal time, and had nothing to do with @stake. He went pretty far to disclaim any @stake connection to the paper.

  19. Re:cant deny msoft does good things also by Anonymous Coward · · Score: 5, Insightful

    I can deny it.
    What has microsoft actually created that anyone is intested in?

    The browser? no Netscape developed that.
    Graphic interface? No Xerox and Apple developed that
    digital music? no MP3 and Napster developed that
    Plug and Play? no Apple developed that
    desktop publishing? once again Apple
    multitastking? Unix
    desktop video? Amiga
    DOS? bought from another company

    Perhaps MS developed some business apps, but I suspect that eveything in the Office suite was developed by some one else first.

    Please give me some examples of any tech, that is worthwhile, that MS pioneered. I think virii and adware are the only techs that MS truly owns.

  20. Limited Genetic Diversity by Phoe6 · · Score: 5, Interesting

    Nature deals with breakdowns in a complex system with evolution, and a very important part of evolution is the extinction of particular species. It's a sort of backtracking mechanism that corrects an evolutionary mistake. The Internet is an ecology, so if you build a species on it that is vulnerable to a certain pathogen, it can very well undergo extinction. By the way, the species that go extinct tend to have limited genetic diversity. -Atrributed to Bill Joy - Had preserved in my Blog Dan Greer's writings bear the same too.

    --
    Senthil
  21. Open Standards can kill MS anyway by newdamage · · Score: 5, Insightful

    In the long run (think the next 10-25 years), Microsoft will be forced to go along with open standards or get left behind as Open Source picks up more momentum. As IBM, Novell, large countries, and other big gorillas put their weight behind Linux and Open Source, the standards they use could become "the standard". This isn't going to happen likely anytime soon, but it definately has to start with the corporate world. If XYZ Inc. decides to use Open Office and Linux to save money (and we know businesses aren't doing anything radical to save money these days), and suddenly their employees must use it, guess what software package could end up on their home computers? As I said, it's not going to be a fast process, but it is possible.

    --
    ce n'est pas un Sig.
  22. M$ tight integration could cause more harm ... by verrol · · Score: 5, Interesting

    than good. yes, this is not a new idea, but the fact that M$ continues to do it is to me, evidence that they are not serious about security.

    Last week a client of mine wanted me to do some work on his computer and to remove M$ IM on WinXP. You try it, it will tell you that WinXP depends on some functionality of IM. What? The OS needs this crummy application you can get for free somewhere? If that is really true, then no wonder their system is so freaking vulnerable to all kinds of things.

    just about anyone who write large software knows that u have make it modular design and if possible striving independent modules as possible to reduce risk and propagation of faults. consider this, even after the trial, M$ still continues to bind unrelated OS functionality with applications. Apps and OS services are completely different.

    while M$ tries to give you a big bloated piece of software with OS and THEIR apps tightly integrated. look at what the people doing micro-kernels are doing. they are trying to make the kernel as simple as possible (hence easier to debug, understand, etc.). Then, the OS services are just apps (again, very independent form each other--though they may use the services provided by the other). but their is no need for that particular app, just any app providing that service. .v

  23. Re:Apple's worse by Nexum · · Score: 5, Interesting

    I have to disagree, Apple dropped certain technologies when they were replaced by superior ones, and were thus 'not that useful any more.'

    PC manufacturers dropped certain technologies when they were finally perceived not to be useful any more.

    Apple can act as the gentle motivational herder, because they have complete control over their flock, as long as they make sure they replace the things they phase out with generally superior technologies, and they have (floppy > email, legacy ports > USB).

    PC manufacturers have no choice, as there is less unity and it is human nature to be wary of new things, and to want to stick to what is tried and tested. In this scenario where it is impossible to move the flock forward as a whole (as the direction of the industry is dictated by many) it must first be shown and proven that the newer technology is superior.

    So I would hardly call this scenario a 'blunder' on Apple's behalf! Quite the opposite in fact - I'm sure it was of great benefit to both Apple and their users to make a swift concerted step forward.

    --

    This sig has been deprecated.
  24. is not monoculture, is evolution. by cabazorro · · Score: 5, Insightful

    Q:What is the single protocol used by all computers
    connected to Internet in the world?
    A: IPV4
    Q:What is the single mail protocol used by all
    computers connected to the internet?
    A: SMTP
    Q:What is the single protocol used to search the
    Internet and exchange most information over the
    Internet?
    A: HTTP
    According to evolution, diversity is the
    consequence of adaptation.

    Specialization, Mutation, Adaptation.

    Adaptation is the
    consequence of a changing environment. A
    changing environment is the consequence of a
    finite amount of resources and competition.
    The Internet in it's current stage resources are
    plenty and competition is little.
    Internet is currently in the specialization
    stage. The Internet has not being forced(YET) to
    depart from it's standard protocols (mutate) to
    survive an attack.

    Forcing diversity (by mandate rather of natural
    competition) not only makes the system less
    robust, it slows down evolution.

    --
    - these are not the droids you are looking for -
  25. Nothing new by jkabbe · · Score: 5, Interesting

    Monoculture (or, the problems associated with it) are not a new concept. When I was studying at U of Mi in 1992-93 (or thereabouts) we discussed the internet worm in my system administration class. The instructor pointed out that U of M was only moderately affected because of the variety of Unix systems comprising the network. The lesson was that a diverse network makes one less succeptible to attack affecting a single platform.