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.

509 comments

  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 DebianRcksLindowsLie · · Score: 2, Insightful

      I'm glad to see whistleblowers getting some press. This is EXACTLY what we need to advance the free & open source movement!

      --
      More whistleblowing in my sig.

    5. Re:MS Open Source Is Fertile Ground for Foul Play by Short+Circuit · · Score: 4, Interesting

      Well, a car wreck is convenient to look at. (You're driving right past it.) ... I would have to look for the source code, which I'm not even going to bother to do.

      Besides, if you want to see Microsoft code, use their Visual C++, and get the step into/step over keys backwards. It's easy to accidentally jump inside the cout statement, for example.

      And anybody elses code? If you can read assembler, wait for it to GPF. At the college I work at, MSVC++ used to snag any crash and throw it up on the screen as x86 assembler code. (I seem to remember that happening to Netscape 4.x a lot.)

    6. Re:MS Open Source Is Fertile Ground for Foul Play by cybergrue · · Score: 2, Funny

      It would be quite difficult for MS to "prove" that any given developer had seen the purloined source
      Simple, they could borrow a trick from SCO and say "It would be impossible for the FOSS developer to do X unless they had seen the M$ code." Unlike SCO, MS will have competent lawyers backed by even more money.

    7. 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.

    8. Re:MS Open Source Is Fertile Ground for Foul Play by pantycrickets · · Score: 1

      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.

      Yeah, because trying to sue a bunch of kids who live at home and are working on never-to-be projects on sourceforge is much better than the business model they've got now?

      Take off the tinfoil hat billy, and step away from the conspiracy theory.

    9. Re:MS Open Source Is Fertile Ground for Foul Play by Anonymous Coward · · Score: 0

      Bravo for getting the joke.

    10. 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.

    11. Re:MS Open Source Is Fertile Ground for Foul Play by Xenographic · · Score: 1

      True--I'm not going anywhere near that code, however interesting it might be to read.

      Once upon a time, one line of one answer of mine was worded oddly and someone else said almost the same thing. I couldn't prove I was innocent. I suffered.

      There's no way in hell I would so much as allude to the possibility that I might peek at that code. I never want to touch that damn code.

      Besides, my ISP disconnects me regularly, and I couldn't download fast enough to ever get the whole thing.

    12. Re:MS Open Source Is Fertile Ground for Foul Play by swb · · Score: 2, Interesting

      Simple, they could borrow a trick from SCO and say "It would be impossible for the FOSS developer to do X unless they had seen the M$ code."

      And how well has that worked for SCO so far? It'd be easier for MS to do what's often been claimed about the SCO code -- deliberate insertion to claim copyright violation.

      What you claim *may* be true for code like WINE or Samba, which has to work very closely with Windows, but I'd imagine those developers long ago got careful about what code they inserted and what they exposed themselves too. It'd be harder for something like Sendmail or another application which which is written to follow a public spec or standard.

    13. Re:MS Open Source Is Fertile Ground for Foul Play by Kilobug · · Score: 2, Informative

      Thanks for the clarification about reverse in the US, I didn't know that.

      For UK, it's true, but not only for UK, most European countries (including France and Germany) have similar laws: reverse engineering is allowed for interoperability, whatever the EULA says.

      The same was done for the European patents directive: the version that was voted by the European Parliament includes a specific clause allowing to bypass patents for interoperability reasons.

    14. Re:MS Open Source Is Fertile Ground for Foul Play by Anonymous Coward · · Score: 0

      http://www.kuro5hin.org/story/2004/2/15/71552/7795

    15. Re:MS Open Source Is Fertile Ground for Foul Play by Anonymous Coward · · Score: 0

      Learn to use H TML, you damn PHP/MySQL scriptkiddie!

    16. Re:MS Open Source Is Fertile Ground for Foul Play by dubious9 · · Score: 2, Interesting

      Hmmm... it's hard to say this here, but I think Windows is the product of some of the world's greatest programmers. They just had their hands tied because of management who extoll features over stability and security. Furthermore Redmonds Exec's suffer from the "I want mine to be special" way of implementing and using standards.

      Windows does what it was designed to do very well: be an operating system for the masses. Its headaches are caused by managerial nearsitedness and monopolistic practices. Disclaimer: IANA microsoft employee, or even a windows programmer, I run linux and develop cross-Unix (HP,SUN,Linux) software, but still I feel somebody has to give Microsoft developers some credit.

      --
      Why, o why must the sky fall when I've learned to fly?
    17. Re:MS Open Source Is Fertile Ground for Foul Play by BigBadBri · · Score: 1
      And what a stupid article that was.

      The author seems to think that in a situation requiring security, not only could someone nefarious get the contract to install the systems, but that any department that didn't have an independent security audit following the installation would be a very silly department indeed.

      And if I wanted to tweak any system (closed or open) to make it more vulnerable, it would be as easy as pie - but equally easy for a competent security auditor to pick up.

      In short, he's just spreading FUD, and pretty ill-informed FUD at that.

      --
      oh brave new world, that has such people in it!
    18. Re:MS Open Source Is Fertile Ground for Foul Play by DunbarTheInept · · Score: 2, Offtopic


      Reverse engineering is NOT illegal, you just have to do it carefully.

      The DMCA has changed that. Now all some company has to do to make it illegal to reverse engineer their code is find a way to tie it to the topic of encryption somehow, and then *bam* reverse engineering it is now illegal. (consider DeCSS).

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    19. Re:MS Open Source Is Fertile Ground for Foul Play by James+Lewis · · Score: 1

      Don't worry, I put it on a USB keychain and shoved it up the you know what. Somehow it's very poetic...

    20. Re:MS Open Source Is Fertile Ground for Foul Play by DunbarTheInept · · Score: 1

      I don't believe the conspiracy theory either, but you should at least have the politeness to criticise people for what they actually are arguing about instead of some strawman version of it. The fear wasn't that MS would try to make money from OSS developers by suing them for alleged copyright infringement, but tht MS would kill OSS competition by doing so.

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    21. Re:MS Open Source Is Fertile Ground for Foul Play by Dillusionary · · Score: 1

      I don't get why reverse engineering is illegal, for god sake you are taught this from your elementary school days, its called algebra.

    22. Re:MS Open Source Is Fertile Ground for Foul Play by ozbird · · Score: 1

      The timing of the Windows source "release" is highly suspicious. SCO's lawsuit - claiming that Linux contains "stolen" code - appears to have been dealt a knockout blow by Novell. Now Microsoft "stolen" code appears on the Internet... It doesn't take an Einstein to join the dots.

    23. Re:MS Open Source Is Fertile Ground for Foul Play by Syberghost · · Score: 1

      Unfortunately, there have already been exploits released based on information gleaned from that code. So, at first glance and as far as the understanding of the man in the street goes, it serves Microsoft's point.

      Of course, the counter-argument that the cognoscenti all "get" is that if the source had been open since day one, none of those bugs would have made it to the "beta" releases. Joe CEO doesn't understand that, however.

  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 queen+of+everything · · Score: 2, Informative

      And here I thought all this time it was "No one ever got fired for choosing IBM".

      --
      "Wisdom is not a product of schooling but of the life-long attempt to acquire it." -Albert Einstein
    3. 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!
    4. Re:I guess ... by __past__ · · Score: 1

      It seems that the prototypical Linux geek thinks that Debian, Gentoo and Fedora are plenty enough of deversity. At least their understanding of portability indicates that.

    5. Re:I guess ... by Jerf · · Score: 4, Insightful

      OpenBSD, FreeBSD, NetBSD, OS X, varients of Linux so dissimilar they are just barely the same operating system, revived BeOS, the HURD, and the continuing divergence of existing operating systems and potential availability of new ones (Plan 9 may have largely failed but where it failed others can succeed (hint: driver support)) is an odd definition of "new monoculture".

      (Heck, every Linux install has the potential to be a potentially new OS; my kernel is most likely the only kernel exactly like it in the world, as as I use gentoo, even a lot of the support programs are customized and potentially unique. I've tried five or six binary vulnerabilities that Linux programs are vulnerable to, and while several managed to crash my computer, not a single one of them has resulted in privilege escalation or anything meaningful, because my system is so different at the binary level from anybody else's. Even to the extent that Linux is a monoculture I've not suffered the price of living in a monoculture.)

    6. Re:I guess ... by Anonymous Coward · · Score: 0

      Huh? If Windows was completely obliterated, we'd still have Mac, Linux, FreeBSD, OpenBSD, Plan9, QNX, etc.

    7. Re:I guess ... by telbij · · Score: 4, Insightful

      Linux/Unix hardly runs a risk of becoming a monoculture, it's too easy to specialize. Regardless, talking about eliminating Microsoft is meaningless. If they get knocked back to 50% marketshare then their quality will improve and we won't need to hate them so much. The problem is the monopoly, the symptom is the software.

    8. Re:I guess ... by Anonymous Coward · · Score: 0

      I've not suffered the price of living in a monoculture

      Nor gained the benefits.

    9. Re:I guess ... by Tom · · Score: 1, Interesting

      Nah, you missed on the biology comparison.

      When M$ finally dies the well-deserved and overdue death, we can still have a lot of diversity without them.

      Let's see:

      Linux (dozens of distros)
      *BSD (several variants)
      MacOS
      Solaris and other *nixes
      Plan9 and other obscurities

      I'm not so sure anymore if I can count properly, but that sounds a lot more diverse to me than:

      windos (some variants)
      uh, whatever those freaks nobody cares about use

      --
      Assorted stuff I do sometimes: Lemuria.org
    10. Re:I guess ... by M1FCJ · · Score: 1

      That's %MONOPOLY% for all those cmd/bat wizards...

    11. Re:I guess ... by southpolesammy · · Score: 3, Insightful

      [Disclaimer: For the record, I'm a Solaris bigot and a Linux zealot.]

      That being said, I don't have that much of an issue with the Windows OS itself. Including it as another tool in IT's belt to be used in specific situations is a good thing to have.

      The problem I have is the predisposition of Windows' advocates to have tunnel vision with respect to the use of said tools. IMHO, Windows is a square peg and every problem is a hole of varying shape that possibly needs to be modified to fit that peg. Couple this with a marketing engine that is second to none in the IT world, and you end up with the situation that Geer describes in which 95% of the desktops and perhaps 50% of the servers in the world are vulnerable to individual bugs and attacks. IOW, just one nasty bug can wipe out nearly the world's entire IT infrastructure because of the lack of genetic diversity.

      Please note -- I'm not knocking Windows itself as an OS. As I mentioned before, it fits in certain situations. I am specifically targetting the misguided directions of our IT management, programmers, and the Microsoft marketing departments that have put us in this situation. This is yet another human problem -- not a technological one -- and one that could have been, and can yet be fixed.

      --
      Rule #1 -- Politics always trumps technology.
    12. Re:I guess ... by Anonymous Coward · · Score: 0

      Sorry, but you have to look at 'monoculture' a little differently. I can sum it up in one example.

      How many of those operating systems use Apache? On how many of them does the base source packages compile and run?

      Monoculture appears in many different ways. First-to-market, at least in the computing industry, is damn powerful. Sure, Apache itself is held to a much higher standard than the Microsoft monoculture (not to mention Open Source, and auditable/fixable/etc) but a single Apache weakness can possibly effect over half the webservers on the 'net.

      (and yes, I do understand that said weakness would need to be exploited in different ways on different OS'es, I still wait for the day that worms are arch-independent, or at least smart enough to attack different platforms differently)

    13. Re:I guess ... by Anonymous Coward · · Score: 0

      Do you really believe that when (not if) Linux becomes the OS of choice that Joe Sixpack will be rolling his own kernels on his Walmart-bought system?

      He won't. He'll do what he does now with the computers he buys, just accept whatever is loaded on it as long as it works.

      The Joe Sixpacks out there outnumber Linux geeks by about 4 or 5 orders of magnitude. They will create a monoculture naturally due to the "But all my friends run Lindows" factor. This is not a software issue, this is human nature.

    14. Re:I guess ... by NanoGator · · Score: 2, Interesting

      "The problem is the monopoly, the symptom is the software."

      That problem is over-inflated here on Slashdot. Microsoft has proven time and time again that they cannot simply make a monopoly out of everything it touches. (XBOX, PocketPC, UltimateTV, etc...) Worse, their popular products have deficiencies that the OSS Community has addressed. Their biggest enemy isn't Microsoft, it's lack of awareness. Follow IBM's lead: Get some commercials on TV. Start a "Advertise Linux" fund. Get the PHBs out there who sign expense checks to understand that it's not just some hobbyist project that couldn't possibly be taken seriously like Microsoft's business products.

      Don't be so quick to dismiss what I'm saying. Microsoft is creating opportunities left and right for you guys (blaster, MyDoom, etc), and you're doing a terrible job of taking advantage of them.

      --
      "Derp de derp."
    15. Re:I guess ... by Jerf · · Score: 1

      Anonymous coward says: How many of those operating systems use Apache? On how many of them does the base source packages compile and run?

      This was what I was getting at when I said I've run several exploits against my machine and none of them did what they were supposed to do. Yes, two or three of them were Apache but while they worked on the stock RedHat box I tried it on, my Gentoo box summarily terminated the Apache process. Bad, yes, but nowhere near as bad as a full-scale intrusion.

      Even if "Linux" dominates, you've still got "Red Hat", "Debian", "SuSE", a handful of others that can be called popular, a lot that can't be, and the meta-distros like Gentoo where each install is its own distro. To answer one of the other anonymous cowards who replied, yes, Joe Six-pack may get a relatively-popular Easy-Windows-Like-Linux install that is like every other Easy-Windows-Like-Linux, but that exact distro won't ever be 90% of the market.

      (Also, a lot of getting Linux onto such a system will help the *BSDs and other UNIX-like OS's, since it's mostly desktop and infrastructure work, so I'd expect if Linux-on-the-Joe-Sixpack-Desktop takes off, BSD won't be far behind. Once Linux opens the doors, there's going to be a lot of people trying to get through it.)

    16. Re:I guess ... by Zeinfeld · · Score: 1
      ... 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...

      The result might have been different if Microsoft had not been the largest customer of Geer's employer. The management were probably wondering which of their other customers Dan would be attacking next.

      The other problem is that the statement itself did not hold together at all well and does not do Dan or the other authors very much credit. Biological viruses adapt to their environment through random variations and the survival of the fittest. Computer viruses are designed and the designers are constantly trying to improve them.

      The virus problem existed long before there was anything like a monoculture. We had viruses on the loose since the days of the Apple II. The first Internet 'virus' the Moriss worm was actually a multi-platform virus. It attacked Sun and Vax platforms. It used several attack mechanisms.

      In these days of virus toolkits it would not be dificult to design a multi-platform virus. The driving force is not the monoculture, its the fact the attackers swap their tools through the Internet.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    17. Re:I guess ... by shotfeel · · Score: 1

      That problem is over-inflated here on Slashdot. Microsoft has proven time and time again that they cannot simply make a monopoly out of everything it touches. (XBOX, PocketPC, UltimateTV, etc...)

      What version are these things? Seems it generally takes MS about 3 major revisions before they start to take over. It wasn't until Windows 3 that MS had a "good enough" GUI to shut Apple out, it wasn't until IE 3.0 that they had a "good enough" browser to close the door on Netscape...

      Give them a little more time. Unfortunately, very few companies can afford to burn money until their version 3 product comes out before they start to see a return. That's one of the advantages of having a monopoly.

    18. Re:I guess ... by NanoGator · · Score: 1

      "What version are these things? Seems it generally takes MS about 3 major revisions before they start to take over."

      Name one product besides Windows, Office, and Internet Explorer where Microsoft has a monopoly. I don't mean market lead, I mean monopoly.

      --
      "Derp de derp."
    19. Re:I guess ... by nojomofo · · Score: 1

      How many do you need??? That's 3 areas (only if you count office as 1 area (not "work processing", "spreadsheets", "presentation software", etc) in which you freely admit that they have a monopoly.

    20. Re:I guess ... by rixstep · · Score: 0, Redundant

      OpenBSD, FreeBSD, NetBSD, OS X, varients of Linux so dissimilar they are just barely the same operating system

      Oh PUH-leeze.

    21. Re:I guess ... by NanoGator · · Score: 1

      "How many do you need???... you freely admit that they have a monopoly."

      Derrrrr. Go back and read the context of my post. The general point is that you guys go crying monopoly without generally realizing what the nature of it really is. The fact alone that MS only has 3 monopolies means that they don't have the power that it assumed they do. It means that the market said "We like this product over the rest" and they became a de-facto monopoly. (Note: That comment does not mean they didnt' do some nasty stuff to contribute to it. So spare me the tired "Oh but they arm twisted resellers etc." arguments. They're not terribly relevant in this particular case.) That means that a.) Their hold on the market is vulernable and b.) You cannot blame Microsoft on your failings.

      If the OSS Community would understand these points, they'd suddenly discover that their uphill battle isn't as steep as they've made it out to be. That's the point of my post, not whether or not MS should be broken up or not. Save that for somebody who cares.

      --
      "Derp de derp."
    22. Re:I guess ... by rixstep · · Score: 1

      If they get knocked back to 50% marketshare then their quality will improve

      That is definitely not a given. And the web is growing up. It's perfectly possible for MS to implode, and for the web to leave MS behind. Big ships take a long time to turn.

    23. Re:I guess ... by denks · · Score: 0

      New monoculture?

      We will have Debian, Gentoo, Red Hat, Mandrake, Slackware, Suse, .......

      --

      I am Monkey, the Great Sage, equal of heaven!
    24. Re:I guess ... by Anonymous Coward · · Score: 0

      1. The grandparent can't spell.

      2. The grandparent is dead wrong. These operating systems are VERY much alike.

      3. The grandparent needs to get hit hard with a cluebat.

      4. Some moderator is even worse off.

    25. Re:I guess ... by HogynCymraeg · · Score: 0

      I'd fire them!

    26. Re:I guess ... by qtp · · Score: 1

      How many of those operating systems use Apache?

      You mean including Windows, all of them can, but there are fare more webservers available for Unix like systems than there are for Windows. Thttpd, wn, Thy, Roxen, Fnord, Dhttpd, Caudium, Bozotic, Boa, and AOLserver are all available in Debian in addition to Apache. Most of these are IPv6, ssl/tls, and cgi capable. They all have their strengths, and they all are being actively maintained. Most of these will operate as a drop-in replacement for Apache for most sites.

      You are correct that most of the web servers on the net are Apache installations of one type or another. Most sites do not need or use all of the features that Apache offers, but install Apache anyway. Sound familiar? They are still thinking in traditional market terms, instead of looking at what is available to them. They treating Unix as if it were Windows, but if an cross-platform Apache-specific worm were to affect them adversely, there will be alternatives available to them that they would not have on Windows.

      The point is that Unix like operating systems offer greater variety of more services in more implementations than Windows does or ever will. There is more room for fault tolerance, more methods available, and more capability to find new solutions to new and old problems (including security) in Free Software than any company or group of companies is capable of providing.

      --
      Read, L
  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. Re:They still don't get it by geoff+lane · · Score: 1
      You could argue all the levels at which windows boxen are patched counts as "diversity"

      It's not such a dumb idea. Many hacks rely on knowing exactly where to plant some nasty code on the stack or elsewhere within the program. If a binary provides the same functionality but with a different code and stack layout it's almost as good as having a different OS.

      OTOH, not blindly executing anything that appears in your inbox is probably a better form of protection

    5. Re:They still don't get it by wud · · Score: 0, Flamebait

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


      I think mac should make a cheap computer, with an ad campaign that asks "Were you stupid enough to get an email virus?"

      I suggest linux desktops be setup ahead of time by big companies (hp,dell,etc.) and don't give the user the admin password unless they pass a basic knowledge quiz. Most users just need Konqueror, Gaim, and Open Office.

      --
      wud
    6. Re:They still don't get it by mwood · · Score: 2, Insightful

      Of course, if the programmers who build network buffers on the stack were all shipped out to Hamburger U. and replaced with people who think before they code, it would be a lot harder for malware authors to diddle the stack, wouldn't it?

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

      Why on earth would an organization wanting secure desktops give their users full admin access? That goes for Windows and Linux. There is *no* reason that a corporate user needs to have an admin account. Exactly like on Linux, limiting Windows users to a non-privileged account greatly limits the damage that they can cause.

      --
      You just come along with me and have a good time. The Galaxy's a fun place. You'll need to have this fish in your ear.
    8. Re:They still don't get it by Anonymous Coward · · Score: 0

      Almost everybody has been putting out binary updates: M$, Redhat, Suse, Sun, SGI, HPUX. I think past history has shown that it can scale reasonably well. If everybody wants to download 3gig at the same time it's a problem, but just updates shouldn't be.

    9. Re:They still don't get it by squiggleslash · · Score: 3, Funny
      I think mac should make a cheap computer, with an ad campaign that asks "Were you stupid enough to get an email virus?"
      I hardly think you can sell a product by insulting your potential customers.

      Oh, wait...

      --
      You are not alone. This is not normal. None of this is normal.
    10. Re:They still don't get it by sphealey · · Score: 3, Insightful
      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.
      While the first part of Charney's statement makes for an interesting discussion starter, the second part is absolutely side-splitting. Could Microsoft finish adding the basic capabilities of Multics, TOPS-20, and Netware 3.11 into its systems before it starts claiming ownership of all innovation in computer technology? Please?

      sPh

    11. Re:They still don't get it by Anonymous Coward · · Score: 0

      Actually "duoculture" (more generally, "oligoculture") does afford a measure of protection. This is one of the reasons why farmers often grow different crops interlaced.

    12. Re:They still don't get it by rah1420 · · Score: 2, Insightful
      True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible.


      Which begs the question of whether you need "true diversity."

      My slightly uneducated guess is that semi-true diversity would work just fine. After all, think of it this way: with simply one other computing platform to choose from, you've just increased the number of options you have by 100%.
      --
      Mit der Dummheit kämpfen Götter selbst vergebens.
    13. Re:They still don't get it by E_elven · · Score: 1

      >It's not such a dumb idea. Many hacks rely on knowing exactly where to plant some nasty code on the stack or elsewhere within the program. If a binary provides the same functionality but with a different code and stack layout it's almost as good as having a different OS.

      We could expand on this idea and create a software production system where instead of printing the image on a CD, we run the image through a random co-dependent bug inserter and then publicize these undocumented features. This way, no two systems would react exactly the same to a given virus or other attack, and all the evil hackers would soon get bored and get decent jobs.

      --
      Marxist evolution is just N generations away!
    14. Re:They still don't get it by overturf · · Score: 4, Insightful

      > 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

      Realistically, this is only true if the stupid windows user adds himself to the admins group (or signs in as administrator) and the linux user does not. It's just as possible for someone to always logon as root in linux or to add root permissions to their daily-logon account in linux as it is to do the equivalent in Windows!

      The only way your comment makes sense is if you're not distinguishing between the myriad versions of Windows that are out there. Windows 98, sure... you were able to easily spork the entire computer -- 6 years ago. Windows 2000 and XP give you all the power you need to not make your daily-logon account an admin by default.

      Imagine the uproar on Slashdot if Windows apologists showed up here (every day) posting things like "Linux has a local root exploit" and provided a link to some Redhat 5.2 hack from 6 years ago. Come on.

    15. Re:They still don't get it by goatan · · Score: 0
      A stupid windows user will be an even more stupid linux user. Sorry to tell y'all this. Them the breaks

      Yeh but window starts of with everything open and ready to be abused regardles off XP's firewall (which seems to stop more legimet code than malicoiuse code and is no substitute for a real firewall) Where as Linux comes with everything closed.

      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

      Your average stupid windows user is not going to do this where as you average stupid linux user shouldn't need to. However when comes to using the OS your spot on but when it comes down to it your stupid linux user is better protected by default than your average windows user.

      "if you don't fence in the crops deer will eat it all".

      A shoddy fence with holes in it is no fence at all also deer/hackers are rather good at getting over fences as with real life the best way to stop deer and other vermin from eating your crops is to kill (arrest for the hackers) them fences are an expensive ineffective and lazy solution and so is hidding your source code rather than making it secure in the first place.

      --
      Saying Apple is better than MS is like saying Botulism is better than rabies.

    16. Re:They still don't get it by starshot · · Score: 0, Redundant

      The default setting after using the XP installation program is for the initial user to be an "Administrator". No locks or controls or permissions whatsoever. At least 90% of Windows users are not going to bother to change that setting. And why should they? They dont know why they wouldnt want to be "in control" of their own computer, even if they have no idea what the hell their doing.

    17. Re:They still don't get it by Cramer · · Score: 1
      • limiting Windows users to a non-privileged account ...
      No it doesn't. Have you looked at the filesystem permissions after a default windows install? (assuming there are any... FAT doesn't support access rights) The whole system is open for "Everyone". A great deal of (stupid) software requires admin rights to even run -- I've ran into that one several times.
    18. Re:They still don't get it by Cramer · · Score: 1
      • ... provided a link to some Redhat 5.2 hack from 6 years ago
      Ok. In that case, the link would only be useful if someone was still running an unpatched RH 5.2 -- this is very unlikely. However, there's a fair chance the 6 year old Windows hack will still work on the most modern Windows versions.

      There in lies the difference... Linux (UNIX) fixes their mistakes and move on. Microsoft ignores everything until the bug crashes a small country. (I know first hand, they don't give a shit about people reporting bugs in their products.)
    19. Re:They still don't get it by Shalda · · Score: 2, Insightful

      Au contraire, a Windows machine can be secured as well as a Linux box. The problem I encounter that keeps me from locking down my users' desktops is many of them need to run older poorly written pieces of software that expect local admin privs. If your users wanted to run something on Linux that required they be logged in as root, you'd have the same problem. I realize there are lots of options (sudo, etc.) and Widnows has some equivalents, but training users to use them just isn't worth the effort.

    20. Re:They still don't get it by Cramer · · Score: 1

      Maybe you need a few more whacks yourself :-)

      There is no difference between "machine user" and "machine admin". Only companies and large orgainizations will have an "Administrator" to fill the role of "machine admin". In every household in suburbia, there's no differentiation -- the person(s) using the box maintains it.

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

      "machine user" and "machine admin"

      ARE THE SAME FUCKING THING ON A HOME PC.

      As for modding the kernel you have to have root privileges to mod your /boot or your /lib/modules dir [or at least it SHOULD be root only otherwise what's the point?].

      The truth is you have to login as root to admin then as your user to use it. hence the name "user". You can't admin a box from a non-root account without chmod 777 all of your dirs/files in which case what's the point?

      So the clueless newb will either run linux as root or login as root and install everything they see under the sun [re: virii]

      Thanks, you fail it.

      The solution is really smarter users. They have to know what a root account means and how to use it properly otherwise you need automation which we know is often exploitable.

      Tom

      --
      Someday, I'll have a real sig.
    22. Re:They still don't get it by Sepper · · Score: 1

      Then again, with current market economics, it's 'better' to come up with a solution that 'mostly works' then one that is perfect.

      This is exactly why Microsoft is the dominant force in computing: Their stuff 'Mostly work' and is available NOW, as with alternatives(Apple,Linux, BSD, etc) which 'works' but not necessarily with what you want to...

      So it's marketably (is that a word??) 'Better' to come up with a 80-90% solution NOW than a 99-100% latter if you want to capture the market.(Unless we speak about critical real-time OS)

      Think about it: that is why we are seeing the 'Outsourcing to India' Trend: they make good enough software to capture a market segment without costing too much...

      If we want to compete with thoses forces we need to come up with better design method to come up with 'Great' software in the same time 'good enough' can be built... We all know how these 'good enough' solution are A PAIN to debug several versions later, but if you don't come up with SOMETHING you won't be able to capture the market...

      I know it's a bit Offtopic but it's this 'cheap'+'good enough' attitude that gave Microsoft their market share in the first place... and the Monoculture we see today...

      --
      I live in Soviet Canuckistan you insensitive clod!
    23. Re:They still don't get it by tomstdenis · · Score: 1

      You sir are all wrong.

      I use WinXP on my laptop with the firewall turned on. I can use all the normal apps I used to use [www, usenet, imap, smtp, ym and msn]. On the bonus side when I plug into the school network it stops all ICMP from others and blocks out the services I normally leave running [file sharing which I only use at home but am to Lazy to turn on and off].

      As for the virus scanner, at some point your average windows user will because a linux user [or macos or whatever]. They'll expect binary installers, binary patches, binary blah. So in the long run you will still need a virus scanner. Cuz even if a virus can't run as root it can still do a lot of damage. Hint: if you always login as your user [not root] then a virus could wipe out all of your work. A virus could still bind to ports>1000 and act as a DDOS zombie, etc...

      The real security crux here is the user. If they use any other os like they use linux then they're screwed. Now don't get all pissy at that. You might have your own users [not root], a patched up SSH, latest cvs kernel, etc, etc, etc.

      Good for you. You sir are not representative of what the average windows user would do with linux.

      Tom

      --
      Someday, I'll have a real sig.
    24. Re:They still don't get it by cayenne8 · · Score: 1
      The trouble is....that some people DO need admin...and it takes an 'Act of God' to get it...at least on Win. As an Oracle DBA...for installs and such, I need Admin. privs...and installing clients on other machines.

      On the Unix side...it is easier...the admins can easily give us the rights we need to install, script and run Oracle/apps. Fine grain privs. on the Unix side is a wonderful thing...but, and this is just from my experience..Win doesn't have as fine a grain control...and admin. is needed for so many things, if it touches the registry...

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    25. Re:They still don't get it by tomstdenis · · Score: 1

      WinXP comes with the firewall turned on by default. That means it blocks out quite a few virii.

      Sure the first thing you have todo with a WinXP [even SP1] install is download 80MB of patches [school network helps here] but once you get the patches + virus scanner + turn off html/attachments in MSOE you're pretty much safe.

      I've been using this setup in school for five months and have yet to have the slightest problem. Even in blaster infected labs [stupid ass dumb students bring their HD caddies home and get infected!!!]

      Tom

      --
      Someday, I'll have a real sig.
    26. Re:They still don't get it by jedidiah · · Score: 1

      This is only due to the fact that most consumers have become accustomed to poor security practices from Monopolysoft over the last 20 years. Microsoft doesn't only produce poorly engineered products, they also help perpetuate bad computing culture.

      Although, quite often the novice WinDOS users are not infact their own administrators. WinDOS is not quite as easy or simple as M$ propaganda would lead one to believe.

      Then there's the whole notion of "sandbox" that suddenly goes by the wayside with the WinDOS security mentality. Such security policies can even be transparent to the common boob.

      Bad habits are hard to break. However, the stakes are quite high at this point.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    27. Re:They still don't get it by tomstdenis · · Score: 2, Insightful

      For someone who has been around slashdot so long [user # 10000] you are by far the most "full of /.'ty goodness" person I've ever seen. You spew vile "anti-MS" without a second thought.

      I dunno where you get your facts but most people I know admin their own windows boxes. Most newbies I know either ignore updates or attempt them theirselves.

      There is no "sandbox" in either OS though. At some point you have to run as super to install updates. That will be your point of vulnerability. Sure Linux [and all other Unix like OSes] benefit from having a non-root "sandbox'ed like" user but that doesn't stop them from running viruses as their user [e.g. DDOS zombie, wipe all their files, etc].

      The point isn't that Windows is insecure it's that most users don't setup/use their computer properly. Changing the OS won't really solve this problem.

      Tom

      --
      Someday, I'll have a real sig.
    28. Re:They still don't get it by DrugCheese · · Score: 2, Interesting

      A stupid window user could be a fenced in stupid linux user. Under Linux you NEED to supply the root password to do anything remotely dangerous to the system. Proper configuration of the system and the GUI could lead to the user only being able to get to and run those applications they need.

      I'm speaking from an IT perspective, if I could switch all the people I support from windows to linux .. no more headaches. No more 'oops I've resized my desktop when I was trying to change my background' or 'I don't know what I did I was in the control panel trying to uninstall this game ...' No, they open their linux menu and get the 4 choices of the 4 programs they need to get their job done. Oh this user doesn't need web access to complete their tasks ... they don't get web browser access and look at productivity soar!

      Linux can be made to be idiot proof and beyond.

      Linux can be dumbed down so a 2 year old can use it. I know, I have a 2 year old living with me, after I log him in he can use the mouse and click on the 4 different icons on the desktop (the only 4 accessible things to him) to hear the 4 seseme street characters sing.

      Windows is dumbed down to the kindergarten level. Even if you're an IT wizard using XP, you're using an interface written for a 5 year old.

      --
      *DrugCheese rants*
    29. Re:They still don't get it by CmdrGravy · · Score: 1

      I often need to request Admin rights to my machine because without them I can't set up any ODBC connections or install most of the software I need to do my job.

      It's a fair point that most corporate users don't need to do this but I do on a regular basis which is a pain in the neck since it seems to take 3-4 days for them to grant me the necessary access.

      I'm sure Linux has a better system of permissions which would allow me to install the programs I need and modify those aspects of the system configuration which I need to modify.

    30. Re:They still don't get it by tomstdenis · · Score: 1

      Except redhat pulled downloads from the free users. Which essentially made them "fucked".

      At least with gentoo if a mirror backs out it's not the end of the world [if gentoo.org did it would suck though but would be manageable].

      So binary updates for free OSes are not always freely available

      --
      Someday, I'll have a real sig.
    31. Re:They still don't get it by SlashDread · · Score: 1

      Not only that, they want you to look at MS content and MS premium content too.
      Pretty soon we will have MSNews, and well call it "independant". Oh wait.. scrap that.
      "/Dread"

    32. Re:They still don't get it by Anonymous Coward · · Score: 0

      "A great deal of (stupid) software requires admin rights to even run -- I've ran into that one several times.

      Right on! Preach it bro! Linux has NOTHING like that. OOo doesn't run as root! XFree86 doesn't run as roo... errr... hmm...

      Ok, nevermind. Nothing to see here, move along.

    33. Re:They still don't get it by Anonymous Coward · · Score: 0

      I use Mandrake, so this may not apply to other distro's, and if it does not, then I think they should take the idea and implement it.

      Most average users will set up to run a graphical interface, as the shell screen scares the hell out of them. On the Mandrake gui login, there is no root logon icon/entry to select. The user has to log on as a user.

      Most apps that require root privileges to run ask for the root password, making things like installing software or configuring the network available when required.

      Even if a browser/email vulberability is exploited, the malware would only run in the user space, and not trash the whole system. There would be no way for a spyware app to hijack the browser, or set the sockets to a porn dialer.

      I know someone will say that a user can log on at the shell as root and type startx, but as I said earlier, the average user will avoid a shell as much as possible.

    34. Re:They still don't get it by Meddel · · Score: 1

      Actually, both Windows and Linux offer you better solutions, but that's beside the point. The point is that you're clearly in the very small minority that legitimately needs admin access. Clearly someone is going to need it. It's just that the folks running exclusively Word and Outlook aren't those people.

      --
      You just come along with me and have a good time. The Galaxy's a fun place. You'll need to have this fish in your ear.
    35. Re:They still don't get it by Meddel · · Score: 1

      You're right that there is software out there that requires admin rights to run. It should be pretty clear that this isn't Microsoft's fault, though. If corporations demand software that runs as a non-priviliged user, they're going to get it.

      As for filesystems permissions on default installs, the whole point of this thread is that it can be locked down, not that the defaults are bad.

      --
      You just come along with me and have a good time. The Galaxy's a fun place. You'll need to have this fish in your ear.
    36. Re:They still don't get it by DotNetGuru · · Score: 2, Informative

      On the Unix side...it is easier...the admins can easily give us the rights we need to install, script and run Oracle/apps. Fine grain privs. on the Unix side is a wonderful thing...but, and this is just from my experience..Win doesn't have as fine a grain control...and admin. is needed for so many things, if it touches the registry...

      Unfortunately you've got this exactly backwards.

      Ok, let's start with the Unix permission model: r/w/x for user, group, or everyone. That's it w/o adding additional software.

      Windows uses ACLs by default, so you can say only Joe and Sally have access to this (with no relationship between Joe and Sally). Eg, and administrator could setup a %ProgramFiles%\Oracle and let you install anything you want below it. You could also create groups of course, and put Joe and Sally into the DBA group.

      As for your registry needs admin access, this is completely incorrect. Registry access is fully ACLed just like file access (and just like so many other things in NT: threads, mutexes, pipes, services, printers, etc...). Now, you can't put permissions on an individual value but you can put permissions on the keys. So, again you could be given the proper permissions necessary to modify the portions of the registry you need to.

      There are tricky parts on the registry. For COM objects for example you need to update the key HKCR\CLSID and probably HCKR it's self. You'd need to setup it up so that your account has these permissions: Query Value, Create Subkey & Enumerate Subkeys. That'd let you insert values, and the pre-existing CREATOR OWNER value gives you full control of the subkeys you created. Now you can add any new COM objects to the system, but you can't delete/edit the ones that are there.

      So in NT you have one security model that applies to a diverse range of objects throughout the entire system. In Unix you have users, groups, and access control on files. This almost works very well in Unix because "everything is a file" - the only problem is not quite everything is a file (is a process a file? a thread? are the posix threading APIs and objects files? how about the entries within a config file? are those file? - unfortunately the answer to all of these is NO).

      So I think in practice you'll find that NT's security model is not only more finer grained in the permissions that can be handed out, but is also more fine grained in the objects that can have access control applied to them.

    37. Re:They still don't get it by Meddel · · Score: 1

      As the other response mentioned, it sounds like the problem here is your admins. Windows gives you a rich built-in set of permissions tools. In particular, everything from Windows 2000 on has ACLs on just about everything you could hope for, in the default install.

      I ran a big handful of Linux and Solaris systems at school, and we always had to install ACL software for filesystems separately. Has that been fixed?

      --
      You just come along with me and have a good time. The Galaxy's a fun place. You'll need to have this fish in your ear.
    38. Re:They still don't get it by Anonymous Coward · · Score: 0

      Or you could just yell at the stupid students the way you flame people on usenet, and they'd never bring infected machines on the network again!

    39. Re:They still don't get it by mpe · · Score: 1

      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.

      A similar argument is Microsoft implying the "integrated applications means the coding for these applications needs to be intermingled. Effectivly deliberatly writing "sphagetti code".

    40. Re:They still don't get it by TheFrood · · Score: 1

      Microsoft, which denies pressuring @stake to fire Geer, says the comparison between computers and living organisms works only so well.

      What??????

      Wasn't it Ballmer that was talking up that weird "ecosystem" thing awhile back? You know, where he said "Open source software has to be part of the ecosystem", and what he really meant was "Open source software should be the prey that we can snatch up and eat and turn into our own proprietary fecal matter."

      And now they say that the biological analogy "only works so well".

      TheFrood

      --
      If you say "I'll probably get modded down for this..." then I will mod you down.
    41. Re:They still don't get it by mpe · · Score: 1

      You fail, just like MS, to differentiate between machine user and machine admin.

      This appears to be a deliberate idea of Microsoft's. So that they could use marketing slogans about not needing (expensive) admins to manage Windows systems.

      While a stupid windows user has full admin access out of the box to all his settings, config, hardware setup etc.

      In many cases Windows applications actually need this in order to work. With such programs continuing to be written. Not only have Microsoft not really got a handle on the separation of "user" and "admin" third party Windows application writers havn't either.

    42. Re:They still don't get it by cayenne8 · · Score: 1
      "...and don't give the user the admin password unless they pass a basic knowledge quiz. Most users just need Konqueror, Gaim, and Open Office."

      No emacs?

      :-)

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    43. Re:They still don't get it by spitzak · · Score: 1

      That's like claiming that the hundreds of thousands of creatures on Earth are unable to eat each other. Like somehow being different requires them to be different right down to their amino acids.

      They are grasping at straws now. They know they are wrong.

    44. Re:They still don't get it by mpe · · Score: 1

      Why on earth would an organization wanting secure desktops give their users full admin access? That goes for Windows and Linux. There is *no* reason that a corporate user needs to have an admin account.

      The reason that this is likely to be the case with Windows is software which requires elevated privileges in order to run. It need not even be old software (written originally for Win9X) it could just as easily be software written by developers who always run as admin.
      This dosn't tend to happen with Linux, since programmers tend to understand that it is a bad idea, it isn't that obvious how to make every user "root", any program which refused to run without privileges it didn't actually need would be fixed PDQ, unix type systems have the concept of setuid/gid executables, etc.

    45. Re:They still don't get it by gad_zuki! · · Score: 1

      Windows nt-based does exactly this when you set the permissions to user. No going outside your profile directory, no installations of anything that isn't completely local, etc. You can tighten it by editing group policy too.

      The problem is that users have to be taught abut safe computing, and restricting admin/root access is just one step in the process.

    46. Re:They still don't get it by DavidTC · · Score: 1
      Open Office doesn't run as root, dumbass.

      As for xfree....my God, the GUI runs as root normal! Why, that's so much worse than Windows, where the GUI runs in kernel space.

      Not to mention that there are ways of not running xfree as root, like running it on a framebuffer. Granted, it won't be as fast, because it doesn't have direct hardware access...but there's logically no way to give an application direct hardware access and still have it be 'secure', because direct hardware access is itself a security risk.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    47. Re:They still don't get it by mpe · · Score: 1

      You're right that there is software out there that requires admin rights to run. It should be pretty clear that this isn't Microsoft's fault, though.

      Given that Microsoft also produce the development tools and the documentation they may be part of the problem here.

    48. Re:They still don't get it by Anonymous Coward · · Score: 0

      I agree that MS is missing the point, as are some others. Mr. Greer is not suggesting that a single OS implies a monoculture (I haven't read his paper, though). Instead, I believe it is the association between executables that causes a monoculture. For example, the "ties" between IE and Outlook. In an effort to make things easier for the end-user by "tying" different software together, MS has created a monoculture environment. Linux doesn't generally have these types of interworkings between executables.

    49. Re:They still don't get it by mpe · · Score: 1

      This is only due to the fact that most consumers have become accustomed to poor security practices from Monopolysoft over the last 20 years. Microsoft doesn't only produce poorly engineered products, they also help perpetuate bad computing culture.

      In some cases it's even to the point of promoting really daft ideas as being positive

      Although, quite often the novice WinDOS users are not infact their own administrators. WinDOS is not quite as easy or simple as M$ propaganda would lead one to believe.

      This even applies to many "home" systems.

      Then there's the whole notion of "sandbox" that suddenly goes by the wayside with the WinDOS security mentality. Such security policies can even be transparent to the common boob.

      As well as the possibility of their being transparent to badly written applications.

    50. Re:They still don't get it by mwood · · Score: 1

      Sorry, a 90% solution is okay for pencils but totally unacceptable for parachutes. The tremendous cost of the consequences of such design decisions shouts (to me, anyway) that the product is *not* "good enough".

    51. Re:They still don't get it by Cramer · · Score: 1
      • As for filesystems permissions on default installs, the whole point of this thread is that it can be locked down, not that the defaults are bad.
      No it isn't. Without a very diligent and cluefull admin, a windows system will almost never be secured to same extent as a UNIX platform. Out-of-the-box is what's being looked at... windows makes nothing secure and even makes the user an admin; UNIX secures the filesystem (almost everything is owned by root and not writable by anyone but root) and never creates more than one "root" user.

      Given the hassle of using a windows system without admin rights, almost no one uses a non-admin account. Only in a large company does the hassle become worth the pain... jump through hoops to do things or let 10,000 idiots screw up the desktop they require to do any work?
    52. Re:They still don't get it by zurab · · Score: 2, Informative
      Realistically, this is only true if the stupid windows user adds himself to the admins group (or signs in as administrator)


      Except that you are wrong. The user that is created when you first launch Windows XP always has administrative privileges by default. So, a "stupid windows user" actually has to remove himself from administrators group and set up a separate account with more limited privileges, and then always use that account. I don't know anybody who has done this, or even is aware that there are more security risks if they don't.

      Besides, most windows users (and even many apps written for them) still view a Windows box as a single-user system. i.e., when I use Linux, I can't arbitrarily store my files outside of my home directory without becoming root or another user. In contrast, most Windows users that I know, store their files all over the place under C:\, D:\ or whatever.

      I'm not sure, if even MS decided to take administrative rights away from the default user, how many apps that would break or not be able to run under that user at all due to lack of privileges to read/write outside your home directory. Maybe, by the time Longhorn comes around, I am guessing, it won't be as much of an issue.

      Windows 2000 and XP give you all the power you need to not make your daily-logon account an admin by default.


      I don't know how many are running Win2K, but, again, XP default user has administrative privileges. You retract a little from your previous statement - yes, XP gives you "power" to create a user with less rights, but how many Sixpacks do it? I don't know of any.
    53. Re:They still don't get it by jtev · · Score: 1
      True, to an extent, however if the system asks for an adminstator/root password that's sorta like a sign that says "Magic lives here, tread carefully" It's not going to stop users from doing stupid things, but it will at least let them be aware that what they are doing may be stupid or at least potentialy dangerous. User education from geek friends can substantialy reinforce this. So, let's enumerate the ways in which Linux handles this better
      • Linux/Unix software is designed to be run as an unprivliged user
      • Most "user" Linux distros encourage/force the creation of at least one non root user
      • The install programs on those same distros explain why a non-root user is desireable
      The most important of these points is the first one, that the software is designed to work in a non-privleged environment. This is not a jab at Windows but rather at Windows software and Windows culture. Yes, it is posible to secure down a windows computer, however it's much easier to secure a Linux computer and retain functionality. Remeber that Unix has had multi-user functionality for over 30 years, and GNU has been re-implementing Unix for 20 years. The Linux kernel is 10 years old, Maybe when Windows has been Multi-User for 20 years or 30 years there will be less software that requires admin privleges.
      --
      That which is done from love exists beyond good and evil
    54. Re:They still don't get it by DrugCheese · · Score: 1

      They'll still have a taskbar, a system tray, a start menu button.

      I think you can only trim MS windows so much. I've worked in unix environments that after logging in I've had two icons - one to open up the program I needed and another for a calculator app.

      I just don't think windows comes close to being as scalable on either end that linux can be.

      --
      *DrugCheese rants*
    55. Re:They still don't get it by CatPieMan · · Score: 1

      "Integration" is one of the new keywords in the military. This means that one plane (for example) can extend its radar using a nearby ship, plane, tank, ground based installation, etc, for any purpose it desires. Or, have a large squadron of planes (all the same model, lets say) where half have air-to-air, and the other air-to-ground missles. The air-to-air's can mix in the formation and provide all of the cover that is needed, while some can fly higher and farther in front, and the bombers can launch smart missiles using their radar.

      For a pilot, the Blue Screen of Death is exactly that.

      Therefore, integration is possible without MS products.

      -CPM

      --
      ---You're all I need, When the water runs deep, You're all I need, Now I cry my soul to sleep -- Collective Soul, Needs
    56. Re:They still don't get it by inode_buddha · · Score: 1

      Umm, my current Fedora install uses ACL's and IIRC they had them in RH9 too. See man (5) acl, setfacl, and getfacl. Also note that both distros install libxattr and libacl.

      --
      C|N>K
    57. Re:They still don't get it by gnu-generation-one · · Score: 1

      "So the clueless newb will either run linux as root or login as root and install everything they see under the sun"

      Huh? How did you figure that one out?

      (a) You can't easily login as root. It's not listed on the login screen with other users, and if you tried, you'd get a bright red background with warning notices on it, and a lot of programs would refuse to run.

      (b) You can't easily create a user with access to do random deletion stuff. Adding privileges to a user, or making the file permissions more lenient, is a complex task that requires a lot of reading to find out how to do. You don't get the "make this user an administrator" checkbox on the new-user screens.

      (c) What exactly are you expecting them to install? Double-click on bonzai buddy from a web-page? Yeah, nice one "file type application/MSWindows, what would you like to do with this file [save] [open with wine]" I've not yet seen a new linux user who doesn't spend the first six months poking around the list of preinstalled applications, seeing what they do.

      There's quite a difference between clicking "power user" on a Windows installation, and ignoring the many, many warnings that a Linux distro gives you if you try to do something stupid on installation. Most of the people with a shiny new Linux computer will have had it setup by a friend who explains what admin mode is, why they shouldn't use it, and who to call if they think they might need it.

      "Thanks, you fail it."

      Ah, the distinctive battlecry of a wannabe expert. "I've got my MCSE, gonna be a CTO someday..."

    58. Re:They still don't get it by Sepper · · Score: 1

      I was taking about the main Microsoft market: Personnal computers. Sorry for not being precise enough.

      You are right, 90% is NOT good for parachutes... or the critical system that helped take down the power grid... Or Beagle 2... Or any system asking for a Real-Time Os for that matter. Imagine your car's OS running Ok, 90% of the time, rest of the time, it would put on break. not good. Yet those are the type of thing we see everyday with computer software.

      If you want another exemple of 'good enough': I am not an English native speaker. I learned English as a Second Language (necessary when you're working with computers). I'm sure my comments are never grammaticaly correct, but It's still 'good Enough' for Slashdot.(I'm trying hard to make progress... honest!)

      Only if Microsoft's product where perfect, would a monoculture prove OK. Unfortunatly for us, people are more interested in look and feature then actual stability. Think about it, what is the first thing you look for when you see a new software? Screenshots!

      I think there is matter for reflexion here

      --
      I live in Soviet Canuckistan you insensitive clod!
    59. Re:They still don't get it by rixstep · · Score: 1

      A stupid windows user will be an even more stupid linux user

      No. Totally wrong. Explain why OS X is so 'out of the box secure' that even the FBI recommend them.

      Linux _can_ be insecure, but a few config changes can remedy that easily, and then your stupid Windows users can be as stupid as they want and it won't matter.

      The stupidity to focus on here is not end-user stupidity, but Microsoft stupidity.

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

      Realistically, this is only true if the stupid windows user adds himself to the admins group (or signs in as administrator) and the linux user does not.

      But you're only scratching the surface, and you know it. Security is a lot more than access to the root account. No point in going into detail, as it's bloody obvious.

    61. Re:They still don't get it by Anonymous Coward · · Score: 0

      their are two many speling errars in parant. i cant raed it,

    62. Re:They still don't get it by Apathetic1 · · Score: 2, Interesting

      Too bad the first user that signs in is an admin by default in XP Professional. Quite a few programs I've run across won't work unless you're signed in as an administrator.

      Giving yourself root permissions (at least on OpenBSD) still requires you to use sudo or su to execute a command using those permissions.

      *shrug*

      --

      My username does not make me Apathetic. It's irony, get it?

    63. Re:They still don't get it by Trepalium · · Score: 1
      This might all work fine for a program you write yourself, and know exactly what permissions it requires. This does not work for a program that was designed by a company that foolishly assumed the security semantics of Windows 9x. Does this program require the "Load and unload device drivers" right? Will it be altering values under HKCR? Will it try to write to something within the %windir% directory? What about the application install directory? This is the problem.

      In the UNIX world, running as a non-privledged user is the norm, and as superuser the exception. In the Windows world, running as Administrator is the norm, and as a limited user the exception. So, regardless of how fine-grained the security is on UNIX, it seems simpler to set things up for non-privledged users to do whatever it is they need to do. SetUID programs are another advantage on UNIX, where you don't need to have a username/password to increase privledges for running a specific program. You can run programs, 'as a different user' on Windows, but you need the username/password to use that feature.

      Then there's the behaviour you can expect from applications running on each platform. UNIX apps tend to default to writing to ${HOME} unless running as superuser, and there's well defined places you can expect these things to access. In Windows, you can't always be sure of where an application might want to write to. Some even have the gall to insist on writing to files hidden in the %windir%, or one of it's subdirectories. Few UNIX applications would ever insist on being about to write to /usr, /bin, /lib or /sbin, because that's simply not where application writable files go. /var and (to a lesser extent) /etc are where those type of files are supposed to be.

      --
      I used up all my sick days, so I'm calling in dead.
    64. Re:They still don't get it by nautical9 · · Score: 1
      The solution, available as default in any semi-modern distro (and even base KDE or Gnome (or MacOS X for that matter) installs), is to ask the user for the root-password only when they go to install a system-wide app or patch or config change. A little pop-up appears, they type it in, that single program runs as root, whilst the user is still logged in their own non-root account.

      It's one extra semi-annoying step, but I doubt most SixPacks will encounter it very often, as they don't typically tweak a system every few hours like us admins do.

      Now of course, a trojan or worm that exploits a user-level hole to get executable priviledges could do the exact same thing to escalate itself, and most Joe SixPacks will unwittingly enter the root password without a moments hesitation, but that's a problem common across ALL operating system.

  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?
    1. Re:Once... by Anonymous Coward · · Score: 0

      This one time, I thought I was programming in .NET for a whole year. Turns out I was using Mono. (with apologies to Wayne & Garth from "Wayne's World")

  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 Anonymous Coward · · Score: 2, Insightful

      Yes, for example, a UDP worm that hit every infectable host withing 15 minutes of release would have been impossible.

      Additionally, we would not have such robust technologies as "Intrusion Prevention Systems". as there would have been no demand for it.

      and my skills as an information security professional would be less in demand if we all ran *BSD.

    2. 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?

    3. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      I must agree to a certain point.

      I for one cut my teeth on DOS, Windows 3.1 and Windows 95. From there it went on to UNIX. I would be willing to be most people started with Microsoft's products even if they now dispise them.

    4. Re:Interesting spin ... by gmuslera · · Score: 4, Funny

      Antivirus could be considered an information related technology?. All a market that could been starving and barely advanced without the gentle Microsoft colaboration.

    5. Re:Interesting spin ... by GoldMace · · Score: 1

      Although choice may be good in some respects, the fact that everyone uses the same thing is good in other respects. One can ask his neighbor if he doesn't know how to do something. Most documents are in the same, albeit proprietary, formats.

      If there truly were thousands of operating systems, it would also be quite hard to just go to a store and buy additional hardware or software that is guaranteed, or even likely, to work.

    6. 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

    7. Re:Interesting spin ... by ab762 · · Score: 1, Funny

      Yeah, without Microsoft products, Al Gore couldn't have invented the internet.

    8. Re:Interesting spin ... by torpor · · Score: 1

      I think its rubbish, personally.

      Microsoft have held back the industry. They have not pushed it forward.

      We could've had cheap, ubiquitous computing a loooooong time ago. MSX would've given it to us.

      Who stopped that? Microsoft.

      There isn't a single 'innovation' from Microsoft which wasn't thought of 10 years earlier in some other camp. Show me one single Microsoft innovation to have come out of their so-called R&D labs, which we couldn't have engineered/designed/implemented 10 years earlier ... there just isn't one ... and no, I'm not trolling, I honestly can't think of a single MS 'invention' which wasn't already feasible in the context of the rest of the industry.

      All MS innovate is theft of others technology ...

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    9. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      Bob!

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

      > Although choice may be good in some respects, the fact that everyone uses the same thing is good in
      > other respects. One can ask his neighbor if he doesn't know how to do something. Most documents are
      > in the same, albeit proprietary, formats.

      Looking at the consumer electronics industry I'd say this argument doesn't hold.

      My neighbor can easily ask me how to do a certain thing with her CD player/DVD player/video recorder, while hers use an entirely different internal; operating system then the ones I own.

      What they do is comply with a common set of standards regarding media, and offer enough similarity in operation for as far as the user is concerned.

      > If there truly were thousands of operating systems, it would also be quite hard to just go to
      > a store and buy additional hardware or software that is guaranteed, or even likely, to work.

      How interesting. Why is this possible when it comes to other complex consumer electronics then?
      I can buy a sony dvd player and connect it to a panasonic TV set without any trouble, and it is very likely to work, and in quite a few cases guaranteed to work.

      You make the same mistake as microsoft, you are confusing standards with implementations.

    11. Re:Interesting spin ... by Minwee · · Score: 2, Insightful

      Blaster. Welchia. Beagle. MyDoom. Swen. Without the support of a microsoft monoculture, none of these important systems could have been developed, nor would they have enjoyed the popularity they do today.

    12. Re:Interesting spin ... by Ernest+P+Worrell · · Score: 1

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

      Visual Basic, ADO, and Access are good examples. They all allow for extremely fast creation of simple information systems. This allows for CHEAP custom solutions that would not be possible without these technologies. No, they're not "real" programming languages, but they get the job done.

    13. Re:Interesting spin ... by fwarren · · Score: 1
      Before I ever took my first hit of DOS, I had done the following:
      1. TRS-80
      2. Tandy Color Computer
      3. Commodore PET
      4. Commodore VIC-20
      5. Commodore-64
      6. Timex Sinclar
      7. Texas Instruments TI-99
      8. Atari-16
      9. Apple-II
      I had even used CP/M before doing any DOS.

      The big thing Microsoft/IBM did for me was allow employers to have the need to hire people who could operate computers.

      --
      vi + /etc over regedit any day of the week.
    14. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      Sure the mouse, but with how many buttons?

      (Laugh nerd, its a joke! ;-])

    15. Re:Interesting spin ... by killmenow · · Score: 3, Insightful
      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?
      Well, look at it this way, without Microsoft, we probably wouldn't have any of the following: Think about it: If Microsoft produced superior products and didn't try to "0WN" you, a lot of those wouldn't exist.
    16. Re:Interesting spin ... by GoldMace · · Score: 1

      >My neighbor can easily ask me how to do a certain >thing with her CD player/DVD player/video recorder, >while hers use an entirely different internal; >operating system then the ones I own.

      And how many of your neighbors still have VCR's flashing 12:00?

      There is no need for the controls on every VCR, or anything else, to be slightly different. I'd rather have a common interface. You are correct, the implementation details do not necessarily have to be the same, however the controls on non MS OS's and software are not the same either.

      I used to have a car stereo that for some insane reason, to change the station you had to hold in the knob for 5 seconds and press the 3 button instead of just turning the knob, like EVERY OTHER CAR RADIO. God, that was so annoying having to tell everyone that ever tried to change the station in my car.

      Whether you guys like it or not, MS is the standard, if you differ from it, you make it difficult for non-geeks to use. MS actually would have even more dominance if they would stop altering the GUI themselves as well. People, in general, don't like change.

    17. Re:Interesting spin ... by killmenow · · Score: 1

      One "innovation" nobody else could have engineered/designed/implemented 10 years earlier (or later) ...

      Microsoft Bob!

      Thank you, thank you...I'm here 'til Thursday...

    18. Re:Interesting spin ... by Cereal+Box · · Score: 1

      First you say...

      There isn't a single 'innovation' from Microsoft which wasn't thought of 10 years earlier in some other camp.

      Then you say...

      Show me one single Microsoft innovation to have come out of their so-called R&D labs, which we couldn't have engineered/designed/implemented 10 years earlier

      So basically you went from "EVERYTHING Microsoft has done was done by someone else at least ten years ago" to "anything that Microsoft has done that I can't directly show someone else having done first I can simply say 'well someone COULD have done it at least ten years ago'." Make up your mind. Or is this just your copout for when someone inevitabaly shows you something that Microsoft has done that no one was doing, or could have done at least ten years ago?

      Here's one: anything Microsoft is doing that's XML-related. No XML ten years ago, so no one else could have done it!

    19. Re:Interesting spin ... by E_elven · · Score: 1

      A) Is this good or bad? All those people could have spent their time better.
      B) Why would there not be OO, Evolution or Mozilla? The others offer some form of access or emulation, but these are just programs.

      --
      Marxist evolution is just N generations away!
    20. Re:Interesting spin ... by asynchronous13 · · Score: 2, Insightful

      True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible

      I think the appropriate analogy here would be the early days of railroad. It used to be that each train company had their own standard for the width of the rails. The train engines and cars from one company could not fit on the rails from a competing railway.

      Obviously, it would be *impossible* to connect the entire country by rails unless a single company owned all of the tracks.

    21. Re:Interesting spin ... by killmenow · · Score: 3, Insightful

      A) I will make no value judgement. Good or bad is up to the individual to decide.

      B) Evolution is specifically designed to "be like Outlook" It has a look/feel about it that mimics Outlook. Basically, Open Office, Mozilla, and Evolution (and a number of other apps) simply try to be a better widget than Microsoft's version. If Microsoft had chosen to release Office for platforms other than Windows & Mac, and had chosen to play nicely instead of trying lock-in via file-format (and the 3 Es), most of these products wouldn't exist now or would be much less developed because there'd be much less motivation to have them.

      All that aside, I was simply attempting to be witty through the clever use of irony. Microsoft says basically, "If not for us, we wouldn't have so much innovation..." and I agree. If not for their sub-optimal products, draconian licensing, underhanded tricks, etc., many of the really awesome and cool technologies we enjoy *wouldn't* exist...but that's not because Microsoft made them. Microsoft just made them possible and (by their own actions) inevitable.

      And I find that ironic, and funny...but this needn't be mod'ed as such.

    22. Re:Interesting spin ... by torpor · · Score: 1


      Microsoft is an 'also-ran' in the XML game. XML is not Microsofts innovation - they're only using it.

      "derivative" != "innovative"

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    23. Re:Interesting spin ... by ObiWanKenblowme · · Score: 1

      here is no need for the controls on every VCR, or anything else, to be slightly different

      Except maybe for personal preference. Some people prefer Sony's implementation, some people prefer RCA's, some people prefer Panasonic's, etc. Even if this wasn't true, you're still overlooking the benefits you get from not having every product of a kind come from a single company. That's one of the main reasons people tend to not like monopolies (or monocultures) - not because they're bad, but because with more producers/developers/providers the products will be in competition and become better.

      --
      Obvious exits are NORTH, SOUTH, and DENNIS.
    24. Re:Interesting spin ... by pantycrickets · · Score: 1

      So since they weren't innovated by linux developers, should any of those things ever have been supported by Linux? I don't get it.

      I don't get a lot of the hypocrisy on Slashdot. Monoculture is bad, but Apple is good?

    25. Re:Interesting spin ... by Sique · · Score: 1

      Ten years ago we called it SGML, and XML is still fully expressable with SGML syntax.

      --
      .sig: Sique *sigh*
    26. Re:Interesting spin ... by Cereal+Box · · Score: 1

      Microsoft helped create the XML standard. They weren't the only ones to do it, true, but they are on the Working Group nonetheless. So it's not fair to say they're only using it.

      I'm interested to hear who you think can claim XML as their innovation if someone on the WG can't do so!

    27. Re:Interesting spin ... by nelsonal · · Score: 1

      MS point is that developers can work on pretty marginal programs for a very small subset of users because there is a platform will expose those programs to all of their audience. A quick example:
      Imagine two worlds one with a dominant OS with 90% market share and the other with three large OS each with 30% share. Both worlds have 100 million users. Let's say a company wants to develop some software that will cost $15 million (plus 3 million porting costs) and only 0.1 million people will want to use (it's engineering software for an auto component or somehting). If they develop it in the first world they spend 10 million on development and nothing on porting. They sell their 0.1 million copies at $200 each and make $5 million. In the second world they spent $21 million ($15 on dev and $6 on porting would lose $1 million, so they choose not to make the software.
      While I picked those numbers to make the point, you can see the major benefit of a monoculture (standard platform) is development of very low use software. This is the reason MS makes so much money, they extract a bit of the proceeds for offering the dominant platform, and why the internet scared them so much. Netscape was making noises about becoming the development platform of the future, when software would be run on a server. Look at an internet games site that requires a Java client as an example of that all you need is a compatable client to run the games, your OS no longer matters. Other developers can build game servers that interact with the clients and you have a new standard. They killed netscape to keep control of the applicaion platform, this is all over the DoJ finding of fact.
      Of course an alternate (and likely more secure approach) would be an agreed upon standard platform could also be a standard set of APIs that many OSs implement allowing software to be run on all of them, in the manner that JAVA or pdf allow somehting to work on many platforms. This is why linux scares them now. And why they are trying to develop .NET as an alternate applications platform for the future.

      --
      Degaussing scares the bad magnetism out of the monitor and fills it with good karma.
    28. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      Life sure would be a lot less interesting for those with an itch to scratch. In this case, Microsoft is the itch ...

    29. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      So obviously we need a M$onopoly to implement standardized protocols like TCP/IRC/SMTP/SSH/HTML/SHTML/ etc...

      What a load of crap! Someone is buying into the MacroShit ideology that only they can properly implement industry standards, designed by cooperartive efforts, and ignored by M$ to keep a lock on those ignorant enough to believe their Park Avenue division.

    30. Re:Interesting spin ... by ajs · · Score: 2, Informative

      True in a humorous way to a point:

      Ximian Evolution -- Certainly the look and feel is outlookish, but unified calendar / contact / task / email clients are old hat, and far pre-date Outlook. Outlook just had (arguably) the best UI, though it was often quirky and hard to use. One of Evolution's best features, though, is its virtual mailbox handling which is a hybrid of VM (Emacs) and mutt handling.

      Mozilla -- This one Microsoft had nothing to do with, though they did push Netscape's development cycles, that was just competition, not a reaction to MS' closed products per se. Mozilla is the child of Netscape and Netscape was a re-implementation of Mosaic from scratch... interestingly Microsoft's IE is a descendent of another Mosaic variant: Spyglass.

    31. Re:Interesting spin ... by llywrch · · Score: 1

      > 5 1/4" floppies

      I thought Apple pioneered the use of 3-1/2 inch floppies. I guess this proves I'm not an expert on that hardware.

      Geoff

      --
      I think I see a trend here. Maybe for them it really would be easier to muzzle the entire internet than to produce p
    32. Re:Interesting spin ... by gnu-generation-one · · Score: 1

      "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?"

      Sure, no problem:

      (*) Outlook viruses
      (*) Macro viruses
      (*) Information leakage in documents
      (*) Adware
      (*) Spyware
      (*) Shareware
      (*) Compulsory product registration
      (*) End user licensing
      (*) Windows messaging
      (*) AOL users
      (*) Popup windows? (or was this Netscape?)
      (*) MS-Word documents
      (*) Software patents
      (*) Palladium
      (*) Web-pages that only work on Internet Explorer
      (*) J++
      (*) ActiveX controls
      (*) A choice of operating system for your new computer: "Windows98 or WindowsME"
      (*) Computers capable of powering battleships
      (*) A generation of office workers who need "retraining" to use OpenOffice
      (*) Talking paperclips
      (*) Steve Ballmer

    33. Re:Interesting spin ... by WuphonsReach · · Score: 1

      I think the appropriate analogy here would be the early days of railroad. It used to be that each train company had their own standard for the width of the rails. The train engines and cars from one company could not fit on the rails from a competing railway.

      In other words, the railroad companies agreed on a common standard with regards to the width of the rails, tunnel clearances, etc. Without designing in "incompatibilities" (e.g. switches that only worked with a particular engine model).

      Integration is easy when products follow a published standard. It's as close to plug-n-play as it's possible to get without having to get sucked into a monopoly's monoculture.

      --
      Wolde you bothe eate your cake, and have your cake?
    34. Re:Interesting spin ... by Anonymous Coward · · Score: 0

      and while apple supposedly invented all these things, what was xerox doing? From memory, these aren't all apple things. I had a mac originally, and as soon as I realised I had to take it to THE apple approved service agent (only one in town, imagine what that does to prices) it was time to chance, apple tried to ensure its monopoly, and got smacked for it, alot of the schools heree changed to non apple machines because of it

    35. Re:Interesting spin ... by waldoiverson · · Score: 1

      don't forget laser printers

  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 tb3 · · Score: 4, Insightful

      I call bullshit. Give me one example. The Windows EULA specifically says that there is NO WARRANTY with the software. Who would be stupid enough to run a mission-critical, not to mention life-critical system on such a shaky foundation?

      --

      www.lucernesys.comHorizon: Calendar-based personal finance

    2. Re:I hope he's wrong ... by Radon+Knight · · Score: 4, Insightful
      there are too many critical systems that are relying on Windows Servers.

      But this is just foolish. Doesn't Microsoft explicitly say that Windows is not to be used for critical systems? There are special (i.e., non-mainstream) operating systems which are expressly designed for use in critical systems so that the problems caused by worms, etc. doesn't happen. If someone dies because of a Windows worm, it's the fault of the programmer who made a bad choice of the embedded system.

    3. Re:I hope he's wrong ... by Pofy · · Score: 2, Insightful

      > The Windows EULA specifically says that there
      >is NO WARRANTY with the software.

      And that would matter HOW, if the law of a country would say otherwise? In many countries one simply can't get away from responsability through contract terms like that.

    4. 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

    5. Re:I hope he's wrong ... by andreMA · · Score: 3, Insightful
      "Life critical" is relative. You're not going to find Windows running air traffic control systems, controlling raadiation exposure for cancer patients, or operating switches on a railway.

      You will likely find them doing things like maintaining records of drug allergies, insurance coverage, etc. If those systems fail, people will hopefully fall back on manual records (assuming they exist in an accessable format), but that will introduce delays in treatment and admissions, which might well indirectly result in deaths.

    6. Re:I hope he's wrong ... by GoofyBoy · · Score: 3, Informative

      "the Slammer worm knocked out 911 emergency telephone service in Bellevue, Washington."

      http://www.salon.com/tech/feature/2003/12/16/bla st er_security/index_np.html

      --
      The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
    7. Re:I hope he's wrong ... by InfoVore · · Score: 2, Informative
      Give me one example.

      Ok, I'll bite. How about the USS Yorktown shutdown in 1997. A Windows NT bug crashed their engine control system and required that they be towed to port. Dockside repairs took several days. You can get the full story here.

      Had this happened in a battle, it would have likely resulted in loss of life and probably the ship.

      --
      "These laws they're passing won't even compile anymore, let alone execute." - anon
    8. Re:I hope he's wrong ... by Anonymous Coward · · Score: 1, Insightful

      Safety critical systems that could kill people if virus-infected.

      Power management systems.

      Telephone systems.

      Traffic light central schedulers.

      Food shipment order systems.

      All of these are frequently (and alas, unfortunately!) Windows based. Oh, you only asked for *one* example and I gave you four? Whoops....

    9. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      The release of a kernel crippling virus or worm could result in loss of human life.

      [examples]

      The worm wouldn't be the cause of the deaths. It would be a symptom of the real cause - incompetence. Nobody should be installing Windows on these types of systems. Period. Even Microsoft will tell you that.

    10. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      A Windows NT bug crashed their engine control system and required that they be towed to port.

      Actually, it was a divide-by-zero bug in the application software, not an OS failure. Whoever wrote the application software for the military was to blame, not Microsoft.

    11. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      Gotta love slashdot. The parent (blaming Microsoft for a 3rd-party application induced failure)gets modded way the hell up, but the explanation that it was actually not MS' fault stays at 0.

    12. Re:I hope he's wrong ... by dacarr · · Score: 1

      They may not have manual records to fall back on. Garbage in, Gospel out, anyone?

      --
      This sig no verb.
    13. Re:I hope he's wrong ... by Anonymous Coward · · Score: 1, Informative

      I was in IC in '99 for some heart stuff, and the monitor system was NT based. Centralized at the nurses station, with remote wireless monitoring.

      Damn thing would beep when my heart rate went below a threshold value, which happened only when I slept. Long night.

      Derek

    14. Re:I hope he's wrong ... by Glytch · · Score: 2, Funny

      Please let me know the general geographical area where you work, so that I can plan future vacations accordingly by not venturing anywhere within a thousand kilometers.

      Thank you.

    15. Re:I hope he's wrong ... by Chris+Burke · · Score: 1

      Actually, it was a divide-by-zero bug in the application software, not an OS failure. Whoever wrote the application software for the military was to blame, not Microsoft.

      Wrong, it is Microsoft's fault. The application cause a divide-by-zero fault. Windows NT failed to properly handle that fault, and died. It is Microsoft's fault. There is no excuse for an operating system being brought down by a divide by zero error in an application.

      --

      The enemies of Democracy are
    16. Re:I hope he's wrong ... by spectecjr · · Score: 2, Informative
      Ok, I'll bite. How about the USS Yorktown shutdown in 1997. A Windows NT bug crashed their engine control system and required that they be towed to port. Dockside repairs took several days. You can get the full story here.

      Had this happened in a battle, it would have likely resulted in loss of life and probably the ship.


      Nice attempt at FUD there, skippy. It's a pity you're misinformed and ignorant of the true facts.

      In a letter to the "Comment and Discussion" department, published in the Aug 98 Naval Institute Proceedings, page 22, Captain Richard T. Rushton, then-CO of Yorktown, categorically states:
      "The Yorktown was never towed as a result of any Smart Ship initiative. During my command, we lost propulsion power twice while using the new technology. Each time, we knew what caused the interrupt and were underway again in about 30 minutes. The September 1997 incident was caused by incorrect data insertion by a well-trained crewman. The Yorktown returned to port using two FFG-7 emergency control units that specifically had been requested by me, and supported by other commands as a risk reducer. We knew there were some risks in the engineering development model propulsion-control system installed under a rapid prototyping development effort. The bottom line: The data field safeguards found in production-level systems were not installed yet in the Yorktown by intention, until complete wring-out was accomplished.""


      Or this one: http://www.cs.virginia.edu/~survive/NEWS/news003.t xt

      "On Sept. 21, 1997, the Yorktown experienced what the Navy called "an engineering LAN casualty" [GCN, July 13, Page 1]. A systems administrator fed bad data into the ship's Remote Database Manager, which caused a buffer overflow when the software tried to divide by zero. The overflow crashed computers on the LAN and caused the Yorktown to lose control of its propulsion system, Navy officials said.

      The Navy CIO Office is trying to determine whether the crash was caused by the software application, NT or some other problem.

      "So far, it doesn't seem like it's an NT issue but a basic programming problem," said deputy CIO Ron Turner, who is in charge of the inquiry."

      "Between July 1995 and June 1997, the Yorktown lost propulsion power to buffer overflows twice while using the new Smart Ship technology, said Capt. Richard Rushton, commanding officer of the Yorktown at the time of the failures. But in each incidence the Yorktown crew knew what caused the failure and quickly restored systems, Rushton said. "NT was never the cause of any problem on the ship," Rushton said. "The problems were all in programs, database and code within the individual pieces of software that we were using."


      http://www.gcn.com/archives/gcn/1998/november9/6.h tm

      ""Now that we know what can happen, we've realized how to bring the system back quickly," Petty Officer 1st Class Phillip Cramer said. "All we have to do is change the zero to any number, and everything comes right back up.""


      So all in all, it doesn't sound like the system crashed to me... You can't bring back a dead system by changing data in a field. You can't even change the data if the system is down.
      --
      Coming soon - pyrogyra
    17. Re:I hope he's wrong ... by spectecjr · · Score: 1

      Wrong, it is Microsoft's fault. The application cause a divide-by-zero fault. Windows NT failed to properly handle that fault, and died. It is Microsoft's fault. There is no excuse for an operating system being brought down by a divide by zero error in an application.


      Do some research. The OS wasn't brought down, as proved by the fact that they could bring the entire system back up by merely changing the zero in a single field to any other value.

      --
      Coming soon - pyrogyra
    18. Re:I hope he's wrong ... by Wedge1212 · · Score: 1

      This is very true. The company I admin for sells a perpetual inventory system for private pharmacies. Our entire system is based off Dell Power Edge Servers running Windows 200x. We do this because 99.9% of the people we sell to use MS products. Secondly the hosiptals we sell to have to admin the server once we sell it to them (we dont want to be responsible for their security and I'm sure they'd wrather have it that way). Thirdly and probably the most important is the pharmacy techs using the Client. They're just average users and its all they know. Its very very scary to see what hospitals consider "security" on these workstations. When we ship the boxes they're in a default state (minus the administrator account being disabled and a temporary account being made). Usually when we go out to a site to work on the system these boxes are in that default state. Its sad they dont tighten security on these boxes. I'd hate to see how they security is on the SQL server. But back to the point....These are mission critical systems for a hospital. If they lose this system it can slow down the drug distribution process and that can be catostrophic at critical times.

      --
      See Sig! See Sig Zig! Zig Sig Zig!!!!!
    19. Re:I hope he's wrong ... by Ivan+Karamazov · · Score: 2, Informative

      Last I knew, the New York Stock Exchange ran on NT. Also, I happen to know that many airline dispatch systems run on NT as well. I've never heard M$ say not to use their OS.

      --
      "The struggle itself toward the heights is enough to fill a man's heart. One must imagine Sisyphus happy." Albert Camus,
    20. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      Windows NT failed to properly handle that fault, and died.

      No, it didn't. Windows NT kept running. The application controlling the ship died. It's like blaming Microsoft when a bug in Mozilla crashes Mozilla.

    21. Re:I hope he's wrong ... by pavera · · Score: 1

      I have lots of times.
      Once when developing a VB frontend to SQL server the server crashed and erased a bunch of data (we had backups) I called MS to talk about the crash and figure out what had caused it, I told them what I was trying to do and they said "Oh, you shouldn't be using SQL server in a critical environment, its not designed for that"

    22. Re:I hope he's wrong ... by mingot · · Score: 1

      Then they should use the backups, perhaps. If they're stupid enough not to have those on Windows are they going to suddenly become smart enough to get with the program when they install Linux?

    23. Re:I hope he's wrong ... by Chris+Burke · · Score: 1

      The Yorktown's Standard Monitoring Control System administrator entered zero into the data field for the Remote Data Base Manager program. That caused the database to overflow and crash all LAN consoles and miniature remote terminal units, the memo said.

      From this article linked by granparent or something.

      Since my recollection of the USS Yorktown failure stems from back when it actually happened, I'll admit the crashing of NT is a detail I may be incorrect on. I do remember being quite clear at the time that it was in fact an application fault and subsequent operating system failure, but again that was six years ago.

      I was unable to find a link that explained the situation in more (technical) detail. If you have a link that would indicate specifically whether the operating system of the computer running the database software was still alive or not after the crash, then that would be helpful. Otherwise the issue remains unclear.

      --

      The enemies of Democracy are
    24. Re:I hope he's wrong ... by Cramer · · Score: 1

      Use of uncertified systems in "life supporting systems" is against the law. (grounds for malpractice, revokation of certifications and licenses, and even dissolution of a medical practice -- hospital, private practice, clinic, etc.)

      Pharmacy systems in a hospital can always fall back to pencil and paper tracking. #2 is a problem, however, doctors should not be relying entirely on computer systems as their knowledge base. #3... how many days do you think people are going to go without food? #4... see above. Anything in the ER is a "life support system". #5... umm, that's called a radio. (yes, they'll lose remote bio-telemetry. but that's why there are trained medics in the chopper.)

      [I've worked around medical systems before. It's a f'ing pain in the ass.]

    25. Re:I hope he's wrong ... by tb3 · · Score: 1

      There's nothing in the article to say that the servers that were knocked out were running Windows. It's more logical to assume they were UNIX servers that were over-whelmed by the Slammer traffic.
      Of course, this is Bellevue, so they could be dumb enough to be running Windows Servers connected directly to the Internet, courtesy of their dear friends next door in Redmond ...

      --

      www.lucernesys.comHorizon: Calendar-based personal finance

    26. Re:I hope he's wrong ... by Bob+Davis,+Retired · · Score: 2, Informative

      If you actually read the Windows EULA, you'd see that Windows is not to be used in critical systems the failure of which could result in loss of life.

      I'd say that the moron who deployed such systems (YOU!) is more responsible here than Windows itself.

    27. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      And let's not forget that Battleship (or whatever it was) that was left stranded at sea due to the Windows system that was running it. In the wrong situation that could mean the death of the entire crew.

    28. Re:I hope he's wrong ... by jsebrech · · Score: 1

      The worm wouldn't be the cause of the deaths. It would be a symptom of the real cause - incompetence. Nobody should be installing Windows on these types of systems. Period. Even Microsoft will tell you that.

      Hmm, I'm not sure of that. They claim their stuff is suited for mission critical systems. Though, if they ever sell a system, and that sale leads to human deaths because of flaws in it, even their eula isn't going to save them. That's manslaughter.

    29. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      If MS is running a critical system, then the company is showing a lack of critical thinking.

    30. Re:I hope he's wrong ... by mellonhead · · Score: 1

      "5. Workstations that communicate with the ambulence and med chopper teams"

      "#5... umm, that's called a radio. (yes, they'll lose remote bio-telemetry. but that's why there are trained medics in the chopper.)
      "


      I think the first poster was referring to Computer Aided Dispatch Systems. They're the computers that operators enter calls with incident details into for dispatchers to send the appropriate response.

      Yes, they can "go to paper" when the system crashes, but calls do get lost/delayed when this happens.

      Agencies across the country are currently using/implementing Microsoft products for these systems.

      In addition, many if not all emergency radio systems are going from the old push the button on the console set up to touch screens. As in, touch screens running on computers using Microsoft products for these systems as well.

    31. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      You're not going to find Windows ... operating switches on a railway.

      Rumor has it that it's running the entire unattended rapid transit system in Vancouver.

    32. Re:I hope he's wrong ... by Average_Joe_Sixpack · · Score: 1

      Pharmacy systems in a hospital can always fall back to pencil and paper tracking.

      Manual order entry (or "down time procedures") is slow, given to more errors and delays patient treatment.

      #2 is a problem, however, doctors should not be relying entirely on computer systems as their knowledge base.

      A BIG problem, which is one of the reasons 100k people die a year from medical errors. If a patient is allergic to iodine, then that info will be stored in the system (often from a prior visit) and referenced against any RX or diet (ie .. no eggs) that is ordered. Take away that system and you'll have to rely on the Pharmacist, dietician and doctor catch the possible interactions ... if they are even aware that the patient has such an allergy.

      #3... how many days do you think people are going to go without food?

      You mean how many hours can an unconscience-seriously ill patient go with out a tube feeding, when that patient needs nourishment to fight off a life threating fever?! Unfortunatly, neglect does happen. Take down a dietary, pharmacy or lab system and you'll suddenly overwhelm the staff with manual processes. This will lead to delays or neglect.

      #4... see above. Anything in the ER is a "life support system".

      Ditto #5... umm, that's called a radio. (yes, they'll lose remote bio-telemetry. but that's why there are trained medics in the chopper.)

      Literally seconds count! Keeping track by radio is a delay.

    33. Re:I hope he's wrong ... by ealar+dlanvuli · · Score: 1

      ED registration is not considered a "life support system."

      --
      I live in a giant bucket.
    34. Re:I hope he's wrong ... by spectecjr · · Score: 2, Informative
      Since my recollection of the USS Yorktown failure stems from back when it actually happened, I'll admit the crashing of NT is a detail I may be incorrect on. I do remember being quite clear at the time that it was in fact an application fault and subsequent operating system failure, but again that was six years ago.

      I was unable to find a link that explained the situation in more (technical) detail. If you have a link that would indicate specifically whether the operating system of the computer running the database software was still alive or not after the crash, then that would be helpful. Otherwise the issue remains unclear.


      Here you go:

      http://www.gcn.com/archives/gcn/1998/november9/6.h tm

      The Yorktown last September suffered an engineering LAN casualty when a petty officer calibrating a fuel valve entered a zero into a shipboard database, officials said. The resulting database overload caused the ship's LAN, including 27 dual 200-MHz Pentium Pro miniature remote terminal units, to crash, they said.

      The petty officer, who has since left the Navy, fed the bad data into the Remote Data Base Manager, a Standard Monitoring Control System application. SMCS, developed by Canadian Aviation Electronics Inc. of Toronto, allows sailors to monitor the ship's engineering and propulsion plant for potential casualties.

      The system provides troubleshooting data and normally indicates whether a valve is open or closed without requiring calibration. But something went wrong.

      "There was a problem in that this one valve was closed, but SMCS wasn't indicating it as such," said Cmdr. Eric Sweigard, the Yorktown's commanding officer. "So this petty officer started playing with the data.

      "This was the only time it occurred, and since then there have been some changes made to prevent it from happening again," he said.

      SMCS managers are now aware of the problem of entering zero into database fields and are trained to bypass a bad data field and change the value if such a problem were to occur again, Sweigard said.

      "Now that we know what can happen, we've realized how to bring the system back quickly," Petty Officer 1st Class Phillip Cramer said. "All we have to do is change the zero to any number, and everything comes right back up."
      --
      Coming soon - pyrogyra
    35. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      Here is Steve Jobs stoty saving 58 lives every year by speeding booting time on mac by 5 s. Imagine how many peopple's last words were "why did't I save my document..." before they got a stroke when the system crashed...

    36. Re:I hope he's wrong ... by InfoVore · · Score: 1
      Nice attempt at FUD there, skippy. It's a pity you're misinformed and ignorant of the true facts.

      Not FUD, just relaying a story from the press illustrating a potentially deadly Windows problem. It was offered in good faith to illustrate the point that OS problems (not just Windows) could have potentially deadly consequences. Thank you for adding further very informative references to what actually happened.

      Misinformed? No more than everyone else who heard the original story, and only to the extent that I did not find other explainations for the incident.

      Ignorant? Sure. That's not a failing, its merely a correctible condition.

      Calm discussion is one thing. Slinging FUD accusations is another.

      --
      "These laws they're passing won't even compile anymore, let alone execute." - anon
    37. Re:I hope he's wrong ... by Cramer · · Score: 1
      • ...one of the reasons 100k people die a year from medical errors...
      Enter one chicken and one egg. This is a double edged sword. People make mistakes because they are people. They also make mistakes because they are relying ever more on computer systems to do their job (read: "dumbing down".) I miss the days of the old country doctor (all of my childhood doctors have passed on.) Let's face it, wholesale medicine accounts for a lot of these deaths.
    38. Re:I hope he's wrong ... by Yeti7226 · · Score: 1

      So a virus like blaster can be lethal!

      Scary tought.

    39. Re:I hope he's wrong ... by Aku+Head · · Score: 1
      I work on pharmacy systems and other hospital computer systems. They are all Windows based. If you were an executive that needed to develop a new, large GUI-based project, what OS would you use? You can easily assemble a large group of Windows programmers. All of your field personnel are trained in Windows support, not linux. There's really no choice here.

      I think that it is disengenuous of Microsoft to drive all other competitors from the marketplace and then cover their ass with a little disclaimer about how you shouldn't use their product if it is for something important.

    40. Re:I hope he's wrong ... by Chester+K · · Score: 1

      Ok, I'll bite. How about the USS Yorktown shutdown in 1997. A Windows NT bug crashed their engine control system

      From the article:

      The Yorktown's Standard Monitoring Control System administrator entered zero into the data field for the Remote Data Base Manager program. That caused the database to overflow and crash all LAN consoles and miniature remote terminal units, the memo said.

      That's not a Windows NT bug, that's an application bug. Blaming Windows for that makes just as much sense as blaming Ford for drunk drivers.

      --

      NO CARRIER
    41. Re:I hope he's wrong ... by Anonymous Coward · · Score: 0

      "But this is just foolish. Doesn't Microsoft explicitly say that Windows is not to be used for critical systems?"

      Yeah, but it also says not to copy it and give it to all your friends...

    42. Re:I hope he's wrong ... by rixstep · · Score: 1

      it's the fault of the programmer who made a bad choice of the embedded system

      You mean the suit. Suits make choices, and suits make bad choices. Programmers keep their noses clean and try to get home early for dinner.

  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?

    2. Re:Open for exploit by faitaccompli · · Score: 1

      And the result was 10s of thousands of drunk Irishmen hitting our shores... ...thankfully they brought along wonderful Guinness...ah, Guiness...

    3. Re:Open for exploit by cperciva · · Score: 2, Informative

      So, what you're saying is that if there's a plague of worms attacking Windows systems, we shouldn't export non-Windows systems to England?

      Remember, there was lots of food being grown in Ireland during said famine; but it was being exported to England.

    4. Re:Open for exploit by sk8king · · Score: 1

      I think I read something about this on Slashdot not too long ago. Specifically, the potato breed was called the 'lumper'.

      And as for starving to death, it wasn't just a few people, it was millions over a few years.

    5. Re:Open for exploit by Fulcrum+of+Evil · · Score: 4, Interesting

      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.

      And the next year, the Irish planted the same crop. Why? Because that's all they could afford - the English were taxing them to death.

      --
      "We returned the General to El Salvador, or maybe Guatemala, it's difficult to tell from 10,000 feet"
    6. Re:Open for exploit by Anonymous Coward · · Score: 1, Informative

      Actually, other crops were grown, it's not like there was nothing but potatoes as far as the eye could see. They were just the tenant farmers' staple. The other crops were exported under armed guard.

    7. Re:Open for exploit by Wanderer2 · · Score: 1

      Wandering off topic, but the parent is slightly misleading. It wasn't so much taxes as tariffs, rent and general poverty.

      The Corn Laws, which were tariffs on imports on wheat and grain, were incredibly unpopular throughout Britain as they raised bread prices. The very poor Irish tenant farmers (who paid their rent by working on farms for the landowners) couldn't afford to buy much food over that which they grew themselves on their small plots of land. Meanwhile, the owners of the farms (most of whom were English/Scottish/Welsh colonists or their descendents) sold their produce to mainland Britain (as other posters have said).

      So you had the silly situation of an area exporting food whilst its people starved. The British government repealed the Corn Laws the year after the famine started, but this was not enough for the starving families who still couldn't afford to buy bread, unless they were prepared to give up their tenancies and join a workhouse.

      The government was a) clueless at first as to how wide-reaching the famine was and b) convinced that letting 'the market decide' would alleviate the problems. As supposition a was completely wrong, b was never going to work. Whatever your personal feelings about free-trade v government intervention, the scale of the famine meant that government intervention was required in this case. The tenant farmers simply could not afford to buy enough food, as it was still too expensive.

      <trite slashdot conclusion>So monoculture plus governmental stupidity can result in very bad things.</trite slashdot conclusion>

      Note. Whether the system of rich landowners and penniless farmers would have existed at the time without English/British colonisation is something I don't know enough about to comment on. This is a disclaimer to avoid a flame-war!

      --
      I say we take-off and slashdot the site from orbit... it's the only way to be sure
    8. Re:Open for exploit by Ziviyr · · Score: 1

      Potato is getting old, most Debian users would rather take Woody.

      --

      Someone set us up the bomb, so shine we are!
    9. Re:Open for exploit by rixstep · · Score: 1

      Uh - so people are safe from Internet attacks, even when running Windows, as long as they vary their diet?

      And does this make sense? Think of the Italians: has anything ever wiped out their spaghetti crop? No. The argument is full of holes.

  8. Rememebr folsk the def for monoculture by linuxislandsucks · · Score: 0, Interesting

    Remebr folks the def of monoculture is not being properly use dhere..

    Monoculture refers to a system(ie culture) in which you have like micro systems(cells)..in other words the micro and macro systems are integrated together and this is the reason why infections are so effective!

    Now in PCs for examepl unix like systems are not in the whoel a monoculture whereas MS windows is..why?

    Becasue the infrastruce to produce the micro system in this case the OS is different between MS and Unix like systems and different between Unxi flavours!

    If all unix flaours were using the exact saem kenrel architecture, development model, and etc yes than it woudl be amonoculture..

    Alot of educated bioligists and computer professionals are getting this def worng..

    Lets think a little , shall we?

    Of course if youa re readin my blog, (shareMe Technologies), then you already know I liek to think and reason through problems, trends, and etc... :)

    --
    Don't Tread on OpenSource
    1. Re:Rememebr folsk the def for monoculture by IamGarageGuy+2 · · Score: 1, Interesting

      How many typos can you possibly have in one comment? This may be a very intelligent comment but it is lost because most people will not read it for what it is but try to understand it through the typos. Not saying you have to spellcheck, but at least take a look at what you are typing.

      --
      Stay tuned for new sig...
    2. Re:Rememebr folsk the def for monoculture by Anonymous Coward · · Score: 0

      Of course if youa re readin my blog, (shareMe Technologies), then you already know I liek to think and reason through problems, trends, and etc... :)

      But not enough to spell check or hit the preview button? Gotcha....

    3. Re:Rememebr folsk the def for monoculture by Yaa+101 · · Score: 1, Funny

      Now only a spell checker...

      Sorry i could not resist...

    4. Re:Rememebr folsk the def for monoculture by Anonymous Coward · · Score: 5, Funny

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

    5. Re:Rememebr folsk the def for monoculture by DataCannibal · · Score: 0, Offtopic

      Of course if youa re readin my blog, (shareMe Technologies)

      No thanks, my eyes and brain hurt too much after trying to read through all your typos.

      --
      No but, yeah but, no but...
    6. Re:Rememebr folsk the def for monoculture by Anonymous Coward · · Score: 0

      Remember, folks, the def. of monoculture is not being properly used here...

      Monoculture refers to a system (i.e., culture) in which all subsystems are of the same kind... in other words (even though they don't need to be integrated with each other at all) they share the same flaws; anything abusing one such flaw could abuse the same flaw in each and every subsystem, and this is the reason why infections are so effective!

    7. Re:Rememebr folsk the def for monoculture by Physics+Dude · · Score: 1

      Seriously, when I initially saw the subject line, I honestly thought it was in German and skipped over it. :)

  9. 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.

    1. Re:Great Microsoft quote by gryphokk · · Score: 1

      I love that!

      It specifically applies to my complaint about people using Powerpoint for graphics -- then expecting me to do something professional with these graphics.

      I've always referreed to PP as a graphics dead-end, but Roach Motel for your graphics -- now that's a metaphor!

      --
      And you, madam, are very ugly. In the morning, I shall be sober.
  10. 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
  11. Fan-Out is the Killer by G4from128k · · Score: 3, Insightful

    It's not just monoculture that makes viruses spread so quickly. The fact that any computer can send something to any computer is bad. The fact that any computer can send something to so many computers is terrible.

    Even if Linus drives Microsoft products into the minority, infections would still quickly reach Microsoft machines (or machines of any leading platform). Furthermore, under non-monoculture conditions, the dilution of virus writers on any one platform would probably be matched by the dilution of anti-virus resources on that platform. Even under non-monoculture conditions, we'll still have fast-spreading infections.

    Connectivity is the real driver of infection.

    --
    Two wrongs don't make a right, but three lefts do.
    1. Re:Fan-Out is the Killer by andreMA · · Score: 1
      under non-monoculture conditions, the dilution of virus writers on any one platform would probably be matched by the dilution of anti-virus resources on that platform
      Assuming the relative inherent security of any of the common platforms to be equal (debatable at best), diversification still carries the major benefit that no single attack can cripple things as badly. Even if the total number of attacks annually increases (and the total machines impacted remains relatively flat) as we move to a more diversified computing culture, the damage will tend to be more spread over time and hence can be managed more easily.
    2. Re:Fan-Out is the Killer by goon+america · · Score: 3, Funny
      It's not just monoculture that makes viruses spread so quickly.

      It's Outlook. (Only about 30% joking)

    3. Re:Fan-Out is the Killer by kfg · · Score: 4, Insightful

      The question is not so much how fast a virus spreads, but what percentage of the computer population is affected at any one time, and what function does that percentage play in the workings of the whole.

      If I have a Windows box and a Linux box sitting side by side, each able to perform all the critical functions of the other, then a virus has to effect them both at the same time for me to lose functionality. When Blaster hits the Windows box I'm free to take it offline to clean it up. Vice versa for a *nix worm. Personally I add a Mac into the mix for three way security.

      This doesn't mean I can't get hit by a virus. It means that a virus can't take me down. And that's the point. Not that infections don't spread, but that infections are genetically specific. Your email worm targeted at a Windows address book, can't even find the address book on my Linux box. The mutt exploit is worthless against my Windows box. The Mac just keeps chugging along, mostly because no one cares to waste time writing a virus for a system even more obscure than Linux (That would be OS8 for those Mac heads about to pounce on me for saying that Macs are popular).

      Resilience through diversity, not absolute immunity.

      KFG

    4. Re:Fan-Out is the Killer by Anonymous Coward · · Score: 0

      No. By reducing some of the large-company corporate drive that is exerted on the programmers themselves, they would release more stable and backwards-portable code. And by dis-entangling the Office suite from the underlying Windows environment, and the additional entanglement of Internet Explorer that has occurred, you'd yield a system more vulnerable to minor failures due to mis-matches but more robust against system-wide failures.

    5. Re:Fan-Out is the Killer by MrHanky · · Score: 1

      Correct. But a virus will only spread to vulnerable hosts, and if the ratio of vulnerable hosts is large, the chance of it connecting to such host is larger than if its more likely the virus will be sent to hosts that can't be infected. After all, bandwidth isn't unlimited, and neither is CPU power. Spreading the virus will be slower, and not potentially as devastating, since fewer hosts would be affected as well.

    6. Re:Fan-Out is the Killer by Anonymous Coward · · Score: 0

      When Blaster hits the Windows box I'm free to take it offline to clean it up.
      This is exactly what I am doing - I have three machines: Win and Lin amd mac. Win is 98% off-line. Friend of mine told me to get rid of it, but I won't: If I would, my other boxes would need reinstalations instead, but I do not wont to mess them up.

  12. One word... by snake_dad · · Score: 3, Funny

    Clippy!

    --
    karma capped .sig seeking available Slashdot poster for long-term relationship.
  13. Proved us wrong by dazaris · · Score: 1

    Microsoft, which denies pressuring @stake to fire Geer, says the comparison between computers and living organisms works only so well.

    Another difference: computers can be unplugged from the network and rebooted; organisms cannot.

    Damn, just when I thought there was something to this monoculture thing everyones been talking about.

    1. Re:Proved us wrong by FictionPimp · · Score: 1

      computers can be unplugged from the network and rebooted; organisms cannot. Are you so sure? Take the blue pill.

  14. ...picking /self off floor by mrpuffypants · · Score: 0, Interesting

    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. ...and that's right when I fell out of my chair laughing. And before my morning Dew, no less!

    1. Re:...picking /self off floor by Anonymous Coward · · Score: 0

      News flash, zealot: Microsoft is the reason why there still is a commercial software industry. If Linux was the dominant platform, every programmer would be unemployed and socialism would be widespread.

  15. What Microsoft doesn't want is *Standards* by Ghoser777 · · Score: 4, Insightful

    Really. Look at all the Linux. BSD, and the other *nix distros and all the software that runs between them on different platforms with different packaging systems. I think it's messy at best, but in a world with more than one *major* operating system, the solution is standards.

    Look at the automobile - tons of competing car companies making different cars, but they all have some standardized equipment customized in a little different way not to radically change the entire experience. Open standards would kill Microsoft (or at least knock them off their behemoth perch), and they know it.

    It's sort of the idea that Federal action is better than State action - why worry about 50 different actors doing their own thing (hint: innovating) when the federal government can just fiat whatever they want.

    Matt Fahrenbacher

    --
    James Tiberius Kirk: "Spock, the women on your planet are logical. No other planet in the galaxy can make that claim."
    1. Re:What Microsoft doesn't want is *Standards* by hachete · · Score: 2, Informative

      Oh yes it does. But only if it can own the standard:
      http://www.pbs.org/cringely/pulpit/pulp it20040212.
      html

      And it if can't own the standard, then it will make the standard as complex as possible as to deter enterance - I give you SOAP as a first exhibit.

      h

      --
      Patriotism is a virtue of the vicious
    2. Re:What Microsoft doesn't want is *Standards* by E_elven · · Score: 1

      SOAP, more appropriately named COUP, or Complex Object-technology Usurping Plot.

      --
      Marxist evolution is just N generations away!
    3. Re:What Microsoft doesn't want is *Standards* by Ernest+P+Worrell · · Score: 1

      Open standards would kill Microsoft

      This is exactly why Microsoft is so afraid to open up its Office Document Standards, you know, like using XML or something instead of their closed DOC,XLS standard.

      They so know that if they were to open up the CLR of their .net Technology, and like, allow people to write their own CLR languages, their stock would plummet.

      /sarcasm

    4. Re:What Microsoft doesn't want is *Standards* by tarnin · · Score: 1

      "Look at the automobile - tons of competing car companies making different cars, but they all have some standardized equipment customized in a little different way not to radically change the entire experience. Open standards would kill Microsoft (or at least knock them off their behemoth perch), and they know it."

      Worse example ever for this. You are proving MS's case with this. Automobiles are like MS actually. Each part is close to the same as others but not close enough. You think I can take a starter out of say a Yugo and put it into a F-150? Not likely. They my kinda work the same but are whole different.

    5. Re:What Microsoft doesn't want is *Standards* by mingot · · Score: 1

      They so know that if they were to open up the CLR of their .net Technology, and like, allow people to write their own CLR languages, their stock would plummet.

      Um, people can write their own CLR languages. Quite a few have. Hell, they even let Borland play.

      Perl

      Python

      FORTRA

      More FORTRAN

      SmallTalk alike (SmallScript)

      Mondrian

      Pascal

      Scheme

      Mercury

      Eiffel

      Oberon

      Cobol

      Ya know what's annoying? Having to type in a bunch of random crap at the end of a message because slashdot does now seem to like having a low number of characters per line.

    6. Re:What Microsoft doesn't want is *Standards* by Ernest+P+Worrell · · Score: 1

      You must have missed the /sarcasm line? ;-).But still, very interesting. I didn't realize there were this many (as I only use VB/C# and once COBOL).

      Office2003 can save files using XML format, but does not do so by default to ensure backward compatability. Within a few years, the default will be changed to XML.

    7. Re:What Microsoft doesn't want is *Standards* by mingot · · Score: 1

      Whoops, I was having an MS Zealot knee jerk moment.

    8. Re:What Microsoft doesn't want is *Standards* by hachete · · Score: 1

      SOAP: it's not Simple and it's not Object-oriented. It's just a crock a shit. And I have to use it. I feel sick.

      h.

      A sig before seven is worth two in the bush.

      --
      Patriotism is a virtue of the vicious
  16. cant deny msoft does good things also by earthstar · · Score: 2, Funny

    dont u think , despite the security flaws ,msoft in a way helping the big inet with their products (in a small / big way).Can anything in this be 100% Good--without error /mistake? i think mistakes and flaws happen every where-from cars,govts etc

    1. 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.

    2. Re:cant deny msoft does good things also by Anonymous Coward · · Score: 0


      Hi Bill, i got your voicemail message about meeting on this "slashdot" anti microsoft place, glad you showed up, like the screename :)

      ok see you in the meeting later

      Paul

    3. Re:cant deny msoft does good things also by primus_sucks · · Score: 1

      Yes, MS shows us how not to design an OS.

    4. Re:cant deny msoft does good things also by geoffspear · · Score: 1

      Uh, yeah, Netscape invented the web browser several years before they existed. And don't even get me started about how horrible it was back in the days before the MP3 format was invented by Napster... Computers couldn't play music at all!! Idiot.

      --
      Don't blame me; I'm never given mod points.
    5. Re:cant deny msoft does good things also by gmuslera · · Score: 2, Insightful
      Perhaps MS developed some business apps, but I suspect that eveything in the Office suite was developed by some one else first.

      Maybe Lotus, Wordperfect and Borland? I remember an ad from Wordperfect that listed the "whats new" of Office 95 or 97, and on the side they put the year since WordPerfect had it, all several of years before, even a lot in the 80's.

      Most of their "innovations" were copying (good examples above), licensing (i.e. ms sql->sybase) or buying (vbasic, frontpage) technology from others.

      But of course, we can deny the hand of MS in all their derived products. Now we can be hacked/infected reading email, having a database accesible thru internet or opening a spreadsheet, things that before was calified as impossible or a joke.

    6. Re:cant deny msoft does good things also by Chris+Burke · · Score: 1

      I think virii and adware are the only techs that MS truly owns.

      Viruses and adware could perhaps be attributed to MS. The ascendence of virii, on the other hand, I think can safely be attributed to people without an adequate dictionary.

      --

      The enemies of Democracy are
    7. Re:cant deny msoft does good things also by spectecjr · · Score: 1

      Maybe Lotus, Wordperfect and Borland?

      No. Visicalc, from VisiCorp was the first spreadsheet - not Lotus.

      Spreadsheet history

      Note that Excel had the first GUI-driven spreadsheet.

      Wordprocessors were even older - and Microsoft Word has the distinction of being arguably the first ever massmarket WYSIWYG wordprocessor.

      Borland? Not sure what you're getting at with them, but I'm pretty sure that Harvard Graphics was the precursor to Powerpoint - not anything Borland came up with.

      --
      Coming soon - pyrogyra
    8. Re:cant deny msoft does good things also by gmuslera · · Score: 1

      Sorry, not checked what companies started those technologies, only put ones that had good/top products on that category before Microsoft dreamed entering in those markets. Lotus was strong in spreadsheets, I could had put wordperfect or wordstar, and Borland had good programming languages/quattro pro/paradox.

    9. Re:cant deny msoft does good things also by Anonymous Coward · · Score: 0

      Please give me some technology that Opensource pioneered?

      Dont get me wrong, I use only open source, but because someone didn't invent somthing dosn't mean they can't implement it well.

    10. Re:cant deny msoft does good things also by HankB · · Score: 1

      No. Absolutely not. I had Internet access with OS/2 out of the box when Microsoft was telling us that the Internet was no big thing and we should all subscribe to MSN (which was not an Internet provider back then.)
      Microsoft turned around pretty fast when it became obvious that they could not ignore the Internet, but they were followers, not leaders.

    11. Re:cant deny msoft does good things also by Anonymous Coward · · Score: 0

      Almost all of the functionality of windows was developed as addons and plugins to the OS as it was being used. MS bought (or drove into bankruptcy) many of these tools, such as the desktop toolbar, which was a plugin for windows 3.x.

      Left to it's own devices, I doubt that MS would have progressed as far as it did. The independant developer/hobbyist community assisted MS in it's operability and desktop market share. Of course, now that the developer/hobbyist community is working in Linux, MS sees this as a bad thing.

    12. Re:cant deny msoft does good things also by jsebrech · · Score: 1

      Unix was open source at the beginning. However, I'm not sure whether unix pioneered anything. Multitasking existed before multics even (which was unix's predecessor). TCP/IP might be a first, but originally the network interface itself was a separate machine, called an imp, which did not run unix.

      As far as I know no modern OS pioneered anything. They're all copy cats.

      I think most of the criticism wrt microsoft not innovating comes from the fact that microsoft constantly is wielding claims that they do in fact innovate all the time. They're the ones who need to put up or shut up.

      The only example of a microsoft first I can come up with is cleartype, which I hadn't seen anywhere until microsoft started talking about it (though subpixel addressing wasn't new, cleartype's use of lcd screens to do it was). I like cleartype. It lets me read ebooks on my pc without having my eyes hurt after an hour.

    13. Re:cant deny msoft does good things also by jsebrech · · Score: 1

      TCP/IP might be a first

      D'oh. I posted this and suddenly realised tcp/ip dates back to the 60's, not to the 80's. My bad, sorry.

      So, no, I can't think of anything unix did first. And I need to relax my brain for a while.

    14. Re:cant deny msoft does good things also by shadowmatter · · Score: 1

      What has microsoft actually created that anyone is intested in?

      Clippy?

      - sm

    15. Re:cant deny msoft does good things also by Rick+the+Red · · Score: 1

      Handwriting recognition. Maybe they didn't invent it, but they've made it practical. I've owned a Handspring Visor (Palm OS) and a Pocket PC, and the Pocket PC's handwriting recognition is way better. The Palm OS requires you to learn their way of writing (Graffiti), while the Pocket PC lets you just write. You can print, or use script, or both. You can even use Graffiti. It's not 100% accurate, but neither is the Palm.

      --
      If all this should have a reason, we would be the last to know.
  17. Well... by Anonymous Coward · · Score: 0, Interesting

    Ideally a closed-source OS is more secure. Any vulnerabilities have to be discovered after compilation, making it more of a guessing game. With open source all you have to do is read the code. But that's just the ideal. You just have to remember that our "closed source" model is hardly closed source any more, that it is (from what I have heard) crappy code to begin with, and it is poorly patched, often in an untimely manner. Then you consider the "real" open source model we live with, where most all security problems are reported/found/patched within a day or two - if not hours. The author of the above article seems to realize the ideal situation, which is fine - he makes a point. But the "security" of closed source code is really just security through obscurity. Read "The Art of Deception" by Kevin Mitnick for some great historical examples of why that model always has, and always will, fail...

    1. Re:Well... by CantGetAUserName · · Score: 1

      Talk to the boys at eEye - they seem to be getting along OK without the source, just attacking a black box.

      --
      Semper en excreta sumus solum profundum
  18. For those who don't know... by cperciva · · Score: 3, Informative

    For those who don't know, Dan Greer was fired from @Stake Inc for his criticism of Microsoft

    Dan Greer was not fired because he criticized Microsoft. He was fired because he published his opinions about the Microsoft monoculture without making it clear that those were his personal opinions and not those of @Stake.

    1. 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.

    2. Re:For those who don't know... by Anonymous Coward · · Score: 0

      Dan Greer was not fired because he criticized Microsoft. He was fired because he published his opinions about the Microsoft monoculture without making it clear that those were his personal opinions and not those of @Stake.

      Yes, that IS the official position. That is not what I and many others got from reading what he published.

    3. Re:For those who don't know... by Anonymous Coward · · Score: 0

      Little details and most major details about things tend to escape the slashdot community. It's a little world built on FUD.

    4. Re:For those who don't know... by Anonymous Coward · · Score: 0

      He should have been fired! If I had some employee that was publicly trashing my largest customer I would fire his ass in a heartbeat.

    5. Re:For those who don't know... by Anonymous Coward · · Score: 0

      That's why no one works for you ;p

    6. Re:For those who don't know... by poot_rootbeer · · Score: 1

      He went pretty far to disclaim any @stake connection to the paper.

      But did he go far enough?

      I'm guessing that he didn't run the paper past @Stake's legal department before publishing.

  19. 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.

    1. Re:Hah! by AndroidCat · · Score: 3, Insightful

      When (if?) Linux takes over the desktop, do you think all the Magic Box users aren't going to converge on one distro? What happens when all the stores stock a Big Blue Penguin distro (example), new software works out of the box for it, all the support shops expect it, all the Linux for Total Fscking Morons books assume it, and all the arguments about UI libraries are moot? Some people will continue to download distros and compile, but will that be a larger number than it is now?

      --
      One line blog. I hear that they're called Twitters now.
    2. Re:Hah! by fwarren · · Score: 1
      When Linux takes over the destop, people will be running an operating system where they are not loged in as root, and the OS was designed to operate in a networked environment with ease of use grafted in on top. Instead of a single user non networked OS with ease of use and lock-in as the main design goal with networking and security grafted in on top.

      There are 3 times as many instances of Apache out there as Microsoft IISS, yet IISS is hacked more.

      Why? Because there are more instances of IISS?

      No.

      IISS is inherently less secure because it is intergrated into and built on top of a singler user non networked, non secure operating system.

      All OS security holes belong to IISS, all scripting holes belong to IISS, all intergrated applications holes such as Office, Outlook, Explorer, and Active X belong to ISS. Why? Because a security hole in almost any easy to use Microsoft Intergrated product creates directly or indectly a hole in IISS that can be exploited.

      While a hole in sendmail does not automaticaly equate a way to hack Apache

      --
      vi + /etc over regedit any day of the week.
  20. Migration from Microsoft by millahtime · · Score: 3, Insightful

    As is usual the US is slow at change. We are stuck in our was and that is especially true for the government. Were there are many places in the world that realize the problems with M$ and are migrating to alternatives it's big news here. We (US) are being slow to wake up and realize the truth. But, that is how the US works.

  21. 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/
  22. What he should of said. by FictionPimp · · Score: 1
    "True diversity, Charney said, would require thousands of different operating systems, which would make integrating computer systems and networks virtually impossible."

    What he should of said: True diversity, would require thousands of different operating systems, which we would do our best by making our own "Standards" to make integrating the computer systems and networks virtually impossible.

    1. Re:What he should of said. by Anonymous Coward · · Score: 0
      What he should of said:
      What you should have said was:
      What he should have said:
      Sorry to mention it, but some spelling/grammar errors are jarring, to say the least; you'll find people more comfortable reading your messages if you word them the right way.
  23. These reporters are a little bit confused... by Anonymous Coward · · Score: 2, Interesting

    Somebody explain to me how this makes any sense?

    "Daniel DuVarney and R. Sekar of the State University of New York-Stony Brook are exploring "benign mutations" that would diversify software, preserving the functional portions of code but shaking up the nonfunctional portions that are often targeted by viruses."

    First of all, since when are only nonfunctional portions of software targetted? A buffer overrun can occur in any portion of code. Second, exactly how would you identify nonfunctional versus functional code, and what mutations could you possibly make to it? Make a bad pointer point to even worse memory? I just don't get it. Looks like another $750K wasted on stupid research.

    1. Re:These reporters are a little bit confused... by steve_l · · Score: 4, Insightful

      You could imagine transforms that move code around in memory, so that while the buffer overflow is still there, it is hard to exploit -primarily because all the other interesting addresses are missing.

      Specifically, overflow attacks like to jump the program to the buffer they have written, or a copy thereof. And in that buffer the code needs to reuse existing imports (library calls) so that they can do bad things. If everything moved around during load, exploitation would be harder. Then again, so would processing a core dump :(

      personally, I think there is a better solution, stop using 'buffer overflow' languages like C, C++. Anything else: perl, python, java, C# is more secure. Why are all our systems built on such a foundation of instability?

    2. Re:These reporters are a little bit confused... by mwood · · Score: 4, Insightful

      For that matter, nonfunctional code should have been optimized away.

      What's nonfunctional code doing in there in the first place? I've lost count of the number of times someone has posted on LKML, "I'm removing frobnicate_foo() because I just rewrote the last place that calls it and it's not needed anymore," or, "I just realized that nothing calls x() anymore, so here's a patch to remove it."

    3. Re:These reporters are a little bit confused... by udippel · · Score: 1
      stop using 'buffer overflow' languages like C, C++. Anything else: perl, python, java, C# is more secure.

      I simply disregard the last language, right ? ;)

      Your turn to draw rough concepts on how Byte-code and scripts can be used to write an operating system, device drivers, etc. How would you propose the runtime-environments to be written ?

      With respect to the first, something similar exists.

      May I question the 'insightfulness' of the moderators ? To me this is what moderation is about: distinguish the good from the good-looking. A naive contribution is welcome and refreshing, but not by default Insightful

    4. Re:These reporters are a little bit confused... by Kphrak · · Score: 1

      personally, I think there is a better solution, stop using 'buffer overflow' languages like C, C++. Anything else: perl, python, java, C# is more secure. Why are all our systems built on such a foundation of instability?

      Look at all the ones you mentioned and you've got the answer. P/P/J/C# are interpreted (or run on a VM, which is the same diff from a speed point of view). C/C++ is natively compiled code, i.e. "translated" to assembly for whatever machine it gets compiled on, which is as fast as you can get short of hand-optimizing assembly code.

      You're not going to be able to write fast code in Java. You can write fairly quick code in Perl, but C will still usually run about 20% faster at a minimum in my experience. My pet peeve is the people who write Java GUI interfaces instead of writing a regular XWindow/Qt/GLib application. Often it's used to cut porting costs, but programs written this way are slower than hell and still break on a regular basis -- they just don't buffer-overrun.

      --

      There's no sig like this sig anywhere near this sig, so this must be the sig.
    5. Re:These reporters are a little bit confused... by ImpTech · · Score: 1

      Because all those languages are slow. C is fast. A better solution would be more like OpenBSD, with ProPolice and W^X built-in.

    6. Re:These reporters are a little bit confused... by Tom · · Score: 1

      You could imagine transforms that move code around in memory,

      OpenBSD has a randomized malloc() for that very purpose. To quote Theo: "Each time you run a program, different behaviour..."

      personally, I think there is a better solution, stop using 'buffer overflow' languages like C, C++. Anything else: perl, python, java, C# is more secure.

      Bzzt, wrong. You can fuck up any language. You can't invent a foolproof system. You can't make the system more secure than the people building it.

      --
      Assorted stuff I do sometimes: Lemuria.org
    7. Re:These reporters are a little bit confused... by steve_l · · Score: 1

      1. See
      Cyclone for a version of C without buffer overflows.

      2. C# is not interpreted; it is always compiled down. But it is against the license terms to discuss performance -it may still crawl but we cannot talk about it.

      3. Java GUIs do crawl, but that is what IBM's SWT is for -Swing is the real issue.

    8. Re:These reporters are a little bit confused... by steve_l · · Score: 1

      C# could be more secure. I have issues with it, but it is better than raw Win32. Though so are most things :)

      There is work under way at AT&T research to do a safe version of C. Its called cyclone, and I have pointed to it in other replies to my post. This could be the basis for those bits of code that absolutely must run in native mode.

      The other issue is this: which is more important: performance or security? Its that same tradeoff of 'works vs fast'. If you have a choice, do you choose the working one, or the fast one?

      The problem with security is that nobody (Well, outside redmond) ships knowingly insecure code, but it gets found and exploited anyway. As you cannot 'know' that your code is secure, you need help from the system. If code that ran near any untrusted data source -sockets, HTTP server, whatever- put more emphasis on security rather than tip-top speed, then the system would be more secure.

      Case in point: the SQL blaster used the SQL server discovery point. There is no need for some net service that lists SQL Servers running on a machine to be high performance native code. If you are going to run it, a bit of perl or python will suffice.

    9. Re:These reporters are a little bit confused... by curtoid · · Score: 1

      C# could be more secure

      Instead of attacking the application, hackers just attack the runtime environment - what's that written in? "Secure" languages are useful only for user apps - that is all. Never for OS or Network layer. This layer simply has to be bug free. Period. There is no "language" solution. It's a development methodology problem.

      As far as the secure or fast question, that's up to the user application requirements.

    10. Re:These reporters are a little bit confused... by Cramer · · Score: 1

      This is part of the biological analogy that doesn't work in the computer world... see in the real world, viruses physically invade a cell and implant their DNA into specific locations within the host DNA. Evolution has led to a bunch of "junk" DNA free for the viruses to attack; as it isn't an active part of the organism, there's no harm. HOWEVER, in the computer realm, viruses don't "invade" they use flaws in the active executible code to get in. At that point, programs are point-blank replaced -- not patched like a biological virus. Junk code would only waste space and slow down program execution.

      As M$ aptly points out, comparing computer viruses to biological ones is a very weak argument... unlike a corn or potato crop, a computer can be unplugged and rebooted; the virus can easily be removed and corrected. (not that M$ actually does the latter.)

    11. Re:These reporters are a little bit confused... by frank_adrian314159 · · Score: 1
      You can't make the system more secure than the people building it.

      Oh yeah! And you can't make a chess program that plays better than the people build... Oh you can?

      In reality, you can build protocols that work in the presence of malicious participants. They are called Byzantime architectures. Their use is why you can actually trust some systems. For instance, OS/400 is very good at separating concerns and becomes a very secure OS in the process.

      --
      That is all.
    12. Re:These reporters are a little bit confused... by Tom · · Score: 1

      And you can't make a chess program that plays better than the people build... Oh you can?

      Your analogy is flawed. Programming is still done by humans, so we are not talking about a programming machine comparing to a chess machine. We're talking about programming languages - a critical difference.

      In reality, you can build protocols that work in the presence of malicious participants.

      True, and we definitely need more of these. They are, however, subject to the same problem: They do elimnate classes of problems, but only those that they were designed to eliminate.

      Some programming languages will avoid certain types of problems, due to their design. Unfortunately, being creative and unpredictable, the same programmers responsible for buffer overflows in C will be guaranteed to find similiar, and equally disastrous ways of fucking up their code in C++, Java, C# and any other language you may come up with.

      --
      Assorted stuff I do sometimes: Lemuria.org
    13. Re:These reporters are a little bit confused... by rixstep · · Score: 1

      Why are all our systems built on such a foundation of instability?

      Gee, I don't know - why don't you try getting a degree in programming, and then you can tell us?

      Seriously: if C is at fault, then assembler must be too. But you can't mean C, because you can't know what you're talking about. It's zero-terminated strings, perhaps. Forbidding pointers might just as well send you back to school in Switzerland (but I doubt you will get the reference).

      It's not the language at fault - go that far, and the next thing, you'll be forbidding von Neumann instruction oriented machines.

      No, it's the programmers. Who evidently can't program a damn.

      The same C and C++ are used in Unix. Where it all started. BWK still says to this day that C is his favourite language. Unix is considered very stable and secure. Now why is that, if it uses the same language as Microsoft?

      And KDE is built up on C++. Found any holes in that lately?

      And please, please, please do not tell people or even suggest that a programming language 'developed' by Microsoft would be an improvement in any kind of context - if you find that urge persisting, see your family physician.

    14. Re:These reporters are a little bit confused... by steve_l · · Score: 1

      you must mean *another* degree in CS, to go with my first class honours degree from Edinburgh University, the one where my final year project was 'formal specification of microprocessors' :)

      1. Search for "AT&T Cyclone" to see a proposed descendant of C that takes away the opportunity to screw up so badly.

      2. While the core unix/linus OS is pretty secure, there are all those add on apps that have to be looked at. wu-ftpd for example. Do things like that really, really, need to be written in pointer-unsafe languages? Apache HTTPD is mandatory for a loaded site with lots of static content, but anything with lightweight access can serve up content using alternate implementations. I think my home music server has perl and java http servers, and very good they are too.

      4. Point about C# taken. Actually it is more secure than Java in some ways -it remembers where code came from and grants it the rights of the origin, not the current location. But where it goes wrong is

      (a) They dont mandate signed everywhere. If only signed .net code runs, then it gets easier to centrally revoke the rights of a worm to run.

      (b) They make it so easy to import C/C++ functions from DLLs that much of the framework is just a thin wrapper around the C libraries. A bit of decompiling and you can find out what libraries are used from network entry points, and then it is time to look for security holes.

      (c) They have created a world where some .exe files are safe to run remotely, as they are .net exes, but the rest arent. This is an area ripe for social engineering -"Run this, it is a .net executable and safe to execute".

      On the subject of Von Neumann machines, well, Harvard Architectures are pretty much immune to data/code confusion, given they read them from separate places. Modern CPUs (all 'cept x86) call themselves Harvard Arch, and do have separate $I and $D caches, but you can get away with dynamic code generation on RISC engines if you flush the caches after every write.

  24. Hate to admit it... by Zordas · · Score: 4, Interesting
    but this is true..

    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

    It's hard enough to get Novel - Mac's - PC's - Windows Servers - And SGI computers all playing nicely in a true heterogeneous environment. I couldn't imagine the nightmare if I had another 2-3 other OS's to integrate.

    1. Re:Hate to admit it... by envelope · · Score: 2, Informative

      I don't think the point is to try to integrate multiple different OS's in a single organization. The point is that each organization can standardize on a different OS, so that an attack aimed at a particular OS only affects those organizations which are using that OS, which is ideally a minority of all organizations. The internet is already an integrated network of many different OS types. The only thing needed for interoperation is TCP/IP and XML.

      --

      appended to the end of comments you post, 120 chars
    2. Re:Hate to admit it... by Angstroem · · Score: 4, Insightful
      It's hard enough to get Novel - Mac's - PC's - Windows Servers - And SGI computers all playing nicely in a true heterogeneous environment. I couldn't imagine the nightmare if I had another 2-3 other OS's to integrate.
      Now you make me curios. What is your definition of playing nicely together?

      As long as basic services are needed, I don't see any problem at all. Use NFS, use SAMBA, use CUPS -- use your protocol of choice where you get clients for all platforms. So far no problem.

      We're running Macs, Windows, Linux, BSD, different incarnations of Solaris, Irix, HP-UX, yet even some embedded stuff like vxWorks. No problem to share drives or print to shared printers. No problem to send and receive emails, surf the web.

      And all without nightmares.

    3. Re:Hate to admit it... by bluGill · · Score: 1

      Each time you add something to that mix though, the total effort does not go up proportionally. The first two you mix are harder than the next one. Once you get an SGI systen settup in your network it is much easier to get a Sun system.

      Actually looking at the mix you claimed there, the only systems that wouldn't be nearly trivial are IBM systems: the OS/390 mainframe (Running linux on that system would be trivial), and whatever the AS/400 runs. Perhaps some unknown like ATheOS (did I even spell that close?) would be difficult, but for the most part SGI, Sun, and Linux systems are similar enough to each other that knowing what made one work makes the other work.

      Yes there is always effort in adding new things to the mix, but once you have started the effort goes down. You get one more advantage by having a lot of different systems in the mix: your admins have to know how things work, so you have a much easier time detecting the bad ones, making your total quality go up.

    4. Re:Hate to admit it... by tverbeek · · Score: 1
      It's not that hard to do. I have Red Hat, Mandrake, Coyote Linux, OS X, OS 7.5, Windows 98, BeOS, and a TiVo all playing fairly nicely in my home office (some of these are used more than others, of course), and my day-job environment is very much like what you describe. It takes more planning and cleverness to manage than an all-Microsoft shop, but the ability to do that is why I'm worth a salary in the 5-figure range. {grin}

      Stuff like single-sign-on is notoriously more difficult to implement in a diverse network, but it can be done (though I've always viewed that as a kind of "security monoculture" and I've never really trusted it anyway; I want some roadblocks between systems.).

      --
      http://alternatives.rzero.com/
    5. Re:Hate to admit it... by liquidsin · · Score: 1

      Not if you have people who know how to use all of those systems, but that's the crux of the problem. It's relatively easy for a Windows guru to get a Windows machine online and fairly well secured. Same goes for anyone else proficient with their OS of choice (OS X, Linux, BSD, Irix, etc...). Problem is, somewhere in the neighbourhood of 90% of desktops are running Windows, with (my estimate here) maybe 5% actually knowing what the hell they're doing. In an ideal diverse system, we'd have near equal numbers of Windows machines, Macs, Linux boxen, Irix, Novell, and maybe even some SCO Unix just for kicks, but the people using them would know what they were doing. What we have now is pretty much the exact opposite - dominance by one OS with mostly clueless users. In an idea situation, *you* wouldn't need to worry about 2 or 3 more OS's to integrate, only taking care of your chosen OS. Unfortunately, that'll never happen.

      --
      do not read this line twice.
    6. Re:Hate to admit it... by Zordas · · Score: 2, Interesting

      The integration part gets eaiser with each passing year. (recently killed Samba because MS has a free NSF client now). The REALLY hard part is to hire a desktop suport tech willing to make $15 an hour that knows all of these systems. Think back just a few years ago when you tried to get Mac's and Novel working smoothly. Remember the seeding issues? While I agree with your accessment, my company just will not pay $30-$35 an hour to hire experienced tech's. Heck, in fact i loose a couple every year becaue they can make that amount somewhere else. And I can't blame them.

    7. Re:Hate to admit it... by Anonymous Coward · · Score: 0

      really? what do you call the internet as an example then? All those platforms you listed (and many more) can author and publish material for consumption by all others.

      Standard protocols and interfaces.

      Simple izntit :-)

    8. Re:Hate to admit it... by Anonymous Coward · · Score: 0

      Kreeg je het ook maar he?

      Sukkel.

  25. Biodiversity analogy goes pretty far... by Anonymous Coward · · Score: 0

    ... since the various diverse organisms on the planet seem to have made good use of the standards in place (air, water, gravity, etc.).

    1. Re:Biodiversity analogy goes pretty far... by Anonymous Coward · · Score: 0

      Evolution and adaptation seem to take care of advancing the standards, and advanced standards lead to innovation within the organisms and their surrounding ecosystems.

      If we say that humans are the biodiversity model's analog of Microsoft, where do you think that will lead us? ;-)

  26. The problem is not monoculture... by Anonymous Coward · · Score: 3, Interesting

    The problem is crappy software.

    Would the IT world be a more stable, reliable & secure place if 95% of the world's comptuer ran OpenBSD?

    The problem is crappy software, not closed source commercial software.

    It is the general crappiness of commercial software (and the lethargic rates of bug fixes) that have led to the popularity of open source.

    1. Re:The problem is not monoculture... by Anonymous Coward · · Score: 0, Troll

      How is this interesting? There is a lot of crappy software out there...and not all for MS products.

      Do you know how long it took me to find a good CD burning program from linux? The sad thing is, it still doesn't compare to Nero.

      One of the few reasons I keep Windows around.

      Also, I'd like you to write an OS that works perfectly. I'm not defending MS here, but seriously... I dare you to.

      Linux is great...but there are also a shit-ton of people constantly working on it to make it better / more secure...and don't get me started on how easy it is to hack if you aren't up to date on all the latest patches, kernal updates, knowing what to turn on and when, blah blah blah.

      Everyone needs to stop whining about shit like this.

    2. Re:The problem is not monoculture... by shortcirquit · · Score: 0

      The problem is NOT crappy software.

      Do you have an Amiga 500 at home?
      Is it struck by a virus lately?
      It IS possible to write viruses for an Amiga. There's just no machine left to spread the virus.

      The problem IS the monoculture. Every day, new exploits are discovered in both windows as well as linux. The UberOS doesn't exist.

      Roald

      --

      this->show();
    3. Re:The problem is not monoculture... by shortcirquit · · Score: 0

      I agree with you 100%. You aren't a troll :)

      --

      this->show();
    4. Re:The problem is not monoculture... by ceeam · · Score: 1

      You mean you've never had a crash of more-or-less complex X-win app on OpenBSD? As my ex-ex-boss used to say: "if the app you work with crash you don't care whether app crashed or OS crashed" (well it's true for most regular users anyway).

    5. Re:The problem is not monoculture... by fwarren · · Score: 2, Insightful
      In this context crappy software means crappy from a security standpoint.

      No one is hacking windows with NERO (a great product). No one is hacking Linux with xroast, or cdbakeoven or cdrecord.

      No one is hacking a Linux or Windows box with Java. However, Windows boxes are being hacked with ActiveX.

      Why, because by the above definition of crappy software, Nero, Java, cdbakeoven, xroast and cdrecord are not crappy software. Whereas ActiveX ,Outlook, IISS, Exchange Server, and Internet Explorer are crappy (read insecure) software.

      --
      vi + /etc over regedit any day of the week.
    6. Re:The problem is not monoculture... by Anonymous Coward · · Score: 0

      You mean you've never had a crash of more-or-less complex X-win app on OpenBSD? As my ex-ex-boss used to say: "if the app you work with crash you don't care whether app crashed or OS crashed" (well it's true for most regular users anyway).

      I've had applications crash, but the OS? If the application crashes, just close the window & run it again. No need go through a slow reboot. For a single-user single-application computer, I suppose it doesn't matter if the OS or application crashes, the effect is similar. But many (most?) computers have something running in the background all the time, and multiple users.

      OpenBSD (and many other operating systems) are robust. The designers know that bugs can happen. So design an OS that minimizes the effect of bugs. Run programs with the minimum prividges possible. Run system programs as non-root users. Run applications in chroot. Use systrace to restrict what apps can do. This is not rocket science. It's poor design choices.

      At my last job, we used Trusted IRIX from Silcon Graphics. The OS never crashed in the 5 years I worked there. Why? Better design. Even a disk failure (on a non-raid system) didn't crash the OS. Generated lots of failures in the syslog though. Show me that in windows.

    7. Re:The problem is not monoculture... by neoThoth · · Score: 1

      Actually following that logic the problem is sloppy coders. If these same sloppy coders started writing Linux software wouldn't it be just as inherently insecure?

  27. 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/
    2. Re:The real problem is... by Yaa+101 · · Score: 1

      I agree with your remarks and want to add to this that exactly the same happened in email.
      When software houses like MS started to make email clients that can read HTML we got spam.
      When the same parties decide that attachments could also startup those same VBA macro's we got major worm attacks.

      Now MS want's a paid email system...

      I am sick of companies poisening our system to sell us snakeoil later.

    3. Re:The real problem is... by AndroidCat · · Score: 3, Insightful
      The sad part is that the underlying security in the NT family isn't that bad--if it's allowed to do it's job. It must really suck to keep working on ways to tighten security at MS, and then have marketing whine about "ease of use" and override design decisions.

      When writing for the then upcoming NT5, we were supposed to assume that there would be very limited access by non-OS software to anything n the \windows\ directories. Judging by the ease that some VB scripts running in the IE browser use ActiveX to overwrite stuff there, I bet that restriction got lost before shipping. (Yeah yeah, "IE is now part of the OS". Bah!)

      --
      One line blog. I hear that they're called Twitters now.
    4. Re:The real problem is... by mwood · · Score: 1

      Indeed, if MS would just delete anything they ship that has the word "Active" in its name, the 'net would be a lot safer. Active documents take the only (theoretically) intelligent component (the user) out of the loop and enable much of the unwanted behavior we're seeing.

      Does anyone seriously believe that CHRISTMA EXEC could have spread so quickly or so widely as Blaster?

    5. Re:The real problem is... by AndroidCat · · Score: 1

      Ha! The new article about email card malware is exactly the example I was thinking of. (It's been around for at least a year.) Read it and weep!

      --
      One line blog. I hear that they're called Twitters now.
    6. Re:The real problem is... by FuzzyBad-Mofo · · Score: 4, Insightful

      And Microsoft's goal (gaol) of backwards compatibility ensures that these misfeatures will stay in the infrastructure indefinitely. I realized this yesterday when cleaning spyware off a friend's Windoze box.

      Windows has so many legacy interfaces for loading programs at boot like win.ini, autoexec.bat, ect. that no longer have a pratical purpose, are easily exploitable, are are in a word, "cruft". Their OS is full of this cruft, and it will continue to become more so, as long as Microsoft continues their indiscrimate adding of features without regard to security.

    7. Re:The real problem is... by Grin_ReaperB) · · Score: 1

      I used to use Windows, and, when I stopped using WordPerfect, I switched to Lotus Word Pro. When I got tired of compatability and stability problems with Word Pro, I switched to OpenOffice. I have never used Word or any other Office product if I could possibly avoid it.

    8. Re:The real problem is... by Anonymous Coward · · Score: 0

      And the monoculture is in MARKETING DECISIONS.

      If MS had focussed on security, the problems wouldn't be as bad as they are now. But they didn't because they didn't have to.

      Security is hard and expensive. All your best people, because only your best people can do it right, will be tied up doing something that won't sell. If, say, in '99 MS had changed their ways and started doing a total rewrite for security, I suggest they would have lost market share in the short term. Resources would be diverted from things that sell. And why would they do it unless the market demanded it.

      There is a backlash happening. Having one true way is the wet dream of the industry. Finally there is a comprehensive and almost complete software stack from one vendor that works reasonably well together. This is what the IT has always wanted. Cheaper, easier, less complicated. To suggest that having reached nirvana, finding it doesn't work, is to deny 40 years of conventional wisdom.

      It doesn't work. Get used to it.

      And get on your knees and thank the ragtag bunch that have created an alternative, competition. They are saving the world.

      Derek

    9. Re:The real problem is... by MasonMcD · · Score: 1

      It must really suck to keep working on ways to tighten security at MS, and then have marketing whine about "ease of use" and override design decisions.

      Or it can be really good, a la OS X; you get to keep both. It's probably pretty fun designing good looking vault, keychain and padlock icons.

      http://www.apple.com/macosx/features/security/

    10. Re:The real problem is... by Henk+Poley · · Score: 2, Insightful

      I always wondered why Microsoft didn't decide to abstract the older windows versions into some VMware alike virtual machine environment. So old windows 'cruft' can only affect old windows programs.

    11. Re:The real problem is... by rixstep · · Score: 1

      'I find Windows of absolutely no technical interest. They took systems designed for isolated desktop systems and put them on the net without thinking about evildoers, as our president would say.'
      - Bill Joy

    12. Re:The real problem is... by rixstep · · Score: 1

      Their OS is full of this cruft

      Yup. When they were getting ready to release Chicago, the legacy 16-bit system stayed 'as is', because a lot of the people who had worked on it were no longer around, and no one wanted to touch it with a barge pole - no one knew how it ran.

      Now when they're picking up the pieces after Cutler, it's much the same thing.

      They're not so clueful, these guys, anyway...

      Windows is a hot-wired system. Well-organised it ain't. But it will have taken the source code leak to make it possible for everyone to get a clue just how bad things are under the bonnet.

  28. The monoculture threat is real by Anonymous Coward · · Score: 4, Informative

    The benefit of linux, bsd, and other non-microsoft OS's come from the variety of services run. Microsoft's OS's have to run many services and modules that other OS's can leave to the discretion of the operator. For instance, I can run an old version of linux with no services and its safe. I can run any number and variety of servers. Microsoft seems to have to do it one way and one way only with all these modules that have to be running.

  29. Monoculture not just a Microsoft phenomenon by cperciva · · Score: 3, Interesting

    As easy as it is to point to Microsoft as an example of monoculture, Open Source software is equally at fault here. Take "deflate" encoding as an example: How many different implementations are there? What fraction of deflate-using applications use an implementation other than zlib?

    If anything, the ease of code reuse inherent in Open Source software makes monoculture easier to achieve.

    1. Re:Monoculture not just a Microsoft phenomenon by Dalcius · · Score: 1

      "If anything, the ease of code reuse inherent in Open Source software makes monoculture easier to achieve."

      But the biological and evolutionary nature of fork, patch, merge and the fact that some developers just don't want to reuse someone else's inferrior code makes some of this a moot point. :)

      I think taking the fact that with MS, 100% of the software is the same, whereas in OSS, there are standard components but enough difference in forks and alternate solutions that we won't see near as much of a problem.

      Cheers

      --
      ~Dalcius
      Rome wasn't burnt in a day.
    2. Re:Monoculture not just a Microsoft phenomenon by Anonymous Coward · · Score: 0

      It's even worse than you think. Zlib is within Windows. Remember that exploit a year ago. I bet nobody at Microsoft patched it since Zlib is not obviously within windows (only know now because of the source leak). How long before the next worm?

    3. Re:Monoculture not just a Microsoft phenomenon by Permission+Denied · · Score: 2, Informative
      Very good example.

      I know of only one application that uses deflate but does not use zlib: putty (Windows ssh client). Excellent code, uses own zlib implementation partly to avoid monoculture, partly for other (very good) reasons.

      Another culprit is OpenSSL. I'd REALLY like to see a nonrestrictive-licensed (BSD or public domain, not GPL) API-compatible OpenSSL alternative. In fact, I'm considering doing it myself, but I'm not fooling myself about how much work this is.

      Other (smaller) examples: MD5. All code I've seen uses the same public domain MD5 implementation. The code is short enough that security shouldn't be an issue, but it's still a bit strange that everyone uses the same code when MD5 is a publicized Internet standard.

      One really dangerous example is ASN.1. This is so horribly complex (commitee-designed) that nobody would want to implement an ASN.1 encoder/decoder when a public domain implementation exists, so everybody uses the same code. This is the code that caused those SNMP vulnerabilities a while ago: good example of code monoculture since it affected *nix, Windows and even embedded stuff like Cisco IOS.

    4. Re:Monoculture not just a Microsoft phenomenon by Anonymous Coward · · Score: 0

      What a pile of horseshit.

  30. I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 4, Interesting

    ...that Greer's against monoculture but doesn't explore the effects of what would be needed to overcome that monoculture.

    As outlined in the article (assuming anyone reads it), critics of Greer point out that simply adding a new OS into the mix (dare I say Linux?) wouldn't substantially help. You'd have a duoculture instead of a monoculture. How much more difficult would it be for hackers to create a devastating hack? It even extends beyond OS's. Apache has the majority market share for all web servers worldwide. What affect would a devastating Apache exploit have on such a near-monoculture? Nobody wants to say anything about that, though, because Apache represents the side of good and Microsoft is evil.

    To truly achieve the technological equivalent of biodiversity, we'd need hundreds or thousands of OS's and differing applications. The complexity of trying to get all that crap to work together would be impossible, especially since convergence of any two app's/OS's would be actively discourages to prevent cross-pollination-type attacks.

    It's all well and good to bash Microsoft's monoculture. I'm sure there are many here who'll do nothing but that. However, defining the problem is only the first step; you must present a practical, workable solution. Just saying "Linux will fix it all" simply replaces one monoculture with another. But I bet most people here haven't thought that far ahead.

    --
    In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    1. Re:I suppose it's wrong to mention... by gathas · · Score: 1

      When you consider that email and scripted web pages seem to be the most common source of virus entry, we probably don't need thousands of OS, but proabably a handful and a bunch or application choices. Basically what we have now but with a more even level of competition.

      As a first step, I would suggest that everyone using MS operating systems stop using Outlook and IE.

      As far as integration goes, I think HTML and HTTP, TCP/IP show how easy this can be if we can some up with standards for data formats and transmission protocols.

    2. Re:I suppose it's wrong to mention... by tverbeek · · Score: 1
      OK, you get a B+ for successfully paraphrasing the Microsoft flack's comments.

      But did you critically evaluate whether his argument that we'd need ridiculous numbers of OSes is sound? Ireland didn't need thousands of breeds of potatoes for its population to all survive the potato blight; a handful of still-viable varieties would have been enough to feed them.

      Likewise, in an alternate universe where the desktop computer landscape today was a roughly even mix of Windows, Mac OS, Linux, BSD, OS/2, BeOS, and Amiga, the "network effect" that spreads malware like wildfire in our universe would be drastically reduced. Instead of a 95% chance of any two computers sharing an OS, there'd be a 15% chance, which would reduce the rate of spread profoundly.

      You're right that Linux won't "fix it all". But a duoculture is more robust than a monoculture, and a true multiculture - even if it consisted of equal numbers of just the top four of the desktop OSes I mentioned - would be even more so.

      --
      http://alternatives.rzero.com/
    3. Re:I suppose it's wrong to mention... by Tom · · Score: 2, Insightful

      Apache is much less a monoculture than windos.

      While the core product is the same, the fact that it runs on dozens of OSs alone makes for a lot of difference. For many low-level attacks, offsets will be different, or compiler flaws exist on one system, but not another.

      This is partly true for the windos world as well. Some of the attacks we've seen recently require slightly different code for XP and NT, for example.

      --
      Assorted stuff I do sometimes: Lemuria.org
    4. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 2, Interesting

      OK, you get a B+ for successfully paraphrasing the Microsoft flack's comments.

      If I didn't know better, I'd say that's a derogatory comment. Not a good way to start off your response if you want to be taken objectively.

      But did you critically evaluate whether his argument that we'd need ridiculous numbers of OSes is sound? Ireland didn't need thousands of breeds of potatoes for its population to all survive the potato blight; a handful of still-viable varieties would have been enough to feed them.

      All analogies break down at some point (yet another paraphrasing job, I'm afraid). You say a handful of still-viable varieties would be enough. What if a virus targetted those? To achieve total practical immunity, each organism (or application/OS) would have to be unique. Obviously that's impractical, so what you're actually arguing is at what level is the risk acceptable?

      Likewise, in an alternate universe where the desktop computer landscape today was a roughly even mix of Windows, Mac OS, Linux, BSD, OS/2, BeOS, and Amiga, the "network effect" that spreads malware like wildfire in our universe would be drastically reduced.

      Productivity would almost certainly be similarly reduced due to lack of high-level interoperability between these disparate platforms. Oh, sure, you'd have some base level of commonality amongst all of them (a potential attack vector, by the way), but what you'd end up with is lowest-common-denominator functionality. That is not a blueprint for progress. New functionality would then only come as a result of consensus between competing vendors, traditionally a long, drawn out process. Further, customers just don't like to wait for that stuff. Outlook is a prime example. It introduced a number of non-standard ways for dealing with email (many of which have resulted in security holes, BTW), but consumers loved it enough to eschew the standards-based alternatives. This has been the case in software for decades (remember when Netscape flouted the HTML standards committee on frames?) and is not likely to change.

      You're right that Linux won't "fix it all". But a duoculture is more robust than a monoculture, and a true multiculture - even if it consisted of equal numbers of just the top four of the desktop OSes I mentioned - would be even more so.

      Again, you completely ignore the possible effects any such duo- or multiculture might introduce into the current setup. Right now, people can exchange data between monocultures pretty seamlessly, flawlessly, and effortlessly. By going to a duoculture you may double the work a hacker may do, but you've also doubled the number of points of failure for software interoperability, you've doubled the technical support requirements of both helpdesks and software developers, and you've potentially (worst case) halved the productivity of people trying to exchange data between differing platforms. These are not insignificant concerns.

      You also can't argue that these disparate platforms would ever work well together. By definition of avoidance of monoculture, convergence of the platforms would almost have to be actively discouraged; history has shown us that convergence is a natural phenomena with any group of disparate programs that are expected to work together. Any such convergence would again lead us to a quasi-monoculture scenario where an attack vector exists where application/OS overlap and interoperability exist.

      In short, you can't have it both ways. Users like programs and systems that work together easily, yet those same systems are at higher risk to attack due to that same interoperability. Removing that attack vector would also remove many productivity-enhancing tools and methodologies we've gained due to greater software integration. I don't know about you, but it's been my experience that if users have to choose between security and functionality, they choose functionality almost exclusively. After, Windows and Office offer lo

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    5. Re:I suppose it's wrong to mention... by mattyrobinson69 · · Score: 1

      but you forget to mention that apache is much more secure than IIS. think back a few years. IIS (3?) had a flaw that would let you run any command (eg format) if you just typed it in at the end of the url - ah the good old days. ok, back to today, linux and *bsd's are secure from the ground up. windows is secure from the top down. which is more secure?

    6. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      Yes, it runs across more platforms, but the core code across all of them is strikingly similar. Most Apache exploits to date have been completely cross-platform exploits, meaning that it really is more of a monoculture than you might think. No slam against Apache, by the way, but it's the truth.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    7. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 2, Insightful

      but you forget to mention that apache is much more secure than IIS.

      This is an assertion that cannot be backed up. I've had NT 4.0 webserver that have run years without compromise, and I've seen poorly-run Apache systems that were hacked within 30 minutes of going live. You can say that Apache is much more secure than IIS by default, but an experienced administrator can secure any box, even an IIS one.

      It all comes down to knowing what you're doing and which platform you're more familiar with. I'd rather have an IIS box run by a guru-level administrator than a Linux/Apache box run by a newbie anyday.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    8. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      As a first step, I would suggest that everyone using MS operating systems stop using Outlook and IE.

      This alone would practically stop 95% of all Internet-based attacks aimed at Windows machines. Which again goes to show that it's not so much the OS that's at risk as it is the applications.

      As far as integration goes, I think HTML and HTTP, TCP/IP show how easy this can be if we can some up with standards for data formats and transmission protocols.

      I disagree. These protocols do very simple things and none of them are secure. Look at the current problems we're having with SMTP mail. It is an inherently insecure protocol that offers no integrated method to determine the authenticity of the sender, leaving the way open for massive reply-to-spoofing spam companies like we have today. TCP/IP doesn't handle security, either, and neither does HTTP (HTTPS excepted, of course). HTML is still far more limited than even a garden-variety word processor when it comes to displaying complexly-formatted documents. You're giving examples of simple components like nuts and bolts. I'm talking about the whole machine.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    9. Re:I suppose it's wrong to mention... by pavera · · Score: 1

      The only problem with your analogy is that apache (Like most OSS) has at least 2 versions and normally many more, which are currently in widespread usage. Also the fact that different vendors patch at different times, and have varying configs. If an exploit is found in apach 2.0.48, great but maybe I'm still running 2.0.47 and the bug was just introduced, maybe I'm running version 1 still, this diversity of versions creates alot of diversity in the unix world (not to mention each vendor has their own version slightly altered of the software, and different libraries are installed on almost every system as well) therefore, you can't as a virus writer rely on some windows dll, and make calls against it, because there is no gaurantee the library you need will be there in the linux world and you will have to write a much larger virus to gaurantee you have the functionality you need on the system once you infect it.

    10. Re:I suppose it's wrong to mention... by mattyrobinson69 · · Score: 1

      it can

      think back a few years. IIS (3?) had a flaw that would let you run any command

    11. Re:I suppose it's wrong to mention... by gathas · · Score: 1

      I agree with your comments about security with the standards I mentioned. The point I was trying to get across (not clearly), was that platform neutral standards are a GOOD THING. While the current internet standards have their flaws, I don't think we can deny that they are the biggest reason for the economic/cultural success of the internet and not any specific OS or application. Meaning the web browser is important, not IE or Mozilla, etc.

    12. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      And Apache has never had any such flaw? I beg to differ. Apache has suffered several root-access flaws during its development. All of them are now patched, but they did exist. You can say the same thing about IIS 3, IIS 4, and so on.

      Your ignorance of the facts kind of paints you as an anti-MS zealot. Perhaps you should try reading up on that which you're so adept at criticizing.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    13. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      Platform neutral is always a good thing, but it has a tendency to move slower (sometimes much slower) than any one vendor/developer could. What happens then? Well, if companies A through Y are all clinging to the standard, but company Z comes out with a new "killer" feature, companies A through Y could be in serious jeopardy of being upstaged by company Z. And it's not like it doesn't happen, because Microsoft is the penultimate example of it. Look at how the Internet is now arranged around the needs of IE as opposed to the strict HTML spec.

      The result? The standards process is frequently upstaged by faster, more nimble competitors. Design by consensus is always slow and almost always less functional than what a single company might come up with. And in a capitalistic society such as ours, whoever gives the customers what they want the fastest gets the dough.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    14. Re:I suppose it's wrong to mention... by Nevyn · · Score: 1
      Yes, it runs across more platforms, but the core code across all of them is strikingly similar.

      Actually not even that is true, apache 1.3.x and 2.0.x are very different (and currently you can still buy aomething with one or the other from all major Linux vendors).

      Most Apache exploits to date have been completely cross-platform exploits, meaning that it really is more of a monoculture than you might think.

      Err, I don't think so. I have seen ones that had a table of different "known" offsets for FreeBSD and Linux ... but I haven't seen any that worked on ppc, Sun and alpha as well as ia32 ... and then you have some people using their own compile maybe with StackGuard/exec-shield/mudflap features turned on. Sure you can still play the percentages, but it's far from the same thing IMO.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    15. Re:I suppose it's wrong to mention... by RdsArts · · Score: 1

      Actually, Apache isn't a monoculture because it doesn't have all of the install base.

      Every figure I see talking about Apache puts it at 2/3 the market, with IIS taking up the other 1/3. Of course, that doesn't count the fun variations that all those apps have. Add on that many are running other lesser-known servers, and that the 2/3rds figure is really probably closer to ~2/4ths, and it becomes even less of a "monoculture."

      You can't really put Apache and Windows in the same "monoculture" box because you'd be hard pressed to argue that Apache is at ~95% of all servers.

    16. Re:I suppose it's wrong to mention... by tverbeek · · Score: 1
      If I didn't know better, I'd say that's a derogatory comment. Not a good way to start off your response if you want to be taken objectively.

      Neither is parroting a PR-crafted argument from the company that stands to lose most from an avoidance of monoculture.

      Or whining that I made a derogatory comment about it.

      Productivity would almost certainly be similarly reduced due to lack of high-level interoperability between these disparate platforms.

      Kind of like driving productivity has suffered from the varied places auto manufacturers put the "high beams" control? I think you dramatically overestimate the difficulty (and frequency) of people switching from one system's GUI to another's. Besides, the design of the user interface is not in itself a vector of vulnerability. User interfaces can converge (and as a matter of fact, they have) without also developing the same low-level code exploits that can so easily devastate a monoculture.

      The data-interchange issue is also a red herring. Common file formats can be (and have been) developed to allow easy exchange of data. You don't need to run the same application code on each machine to manipulate that data. Granted, certain companies have used data storage formats for just that sort of market expansion. That doesn't mean it A) has to be that way, or B) should be.

      I don't know about you, but it's been my experience that if users have to choose between security and functionality, they choose functionality almost exclusively.

      Yes, that's what's gotten us into this mess. Perhaps is time to devote less attention to making excuses for how we got here, and more attention on how to fix it. Such as educating people about the problems you seem to want to sweep under the rug, so that maybe in the future they'll consider security as well.

      --
      http://alternatives.rzero.com/
    17. Re:I suppose it's wrong to mention... by tverbeek · · Score: 1
      Which again goes to show that it's not so much the OS that's at risk as it is the applications.

      Most of the problems with IE have come since it became so tightly integrated into the OS. Outlook is pretty well hooked in there as well. But you're right: browser and mail client monoculture are a big part of the problem as well.

      --
      http://alternatives.rzero.com/
    18. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      Well, Outlook can be integrated, but if you don't buy Office it can't be.

      As for IE, at least MS did something smart by disabling IE in the default install of Win2k3. The result? Win2k3 has had far fewer bugs and exploits than any other MS OS at this time in its development life cycle. Go check the bug rate for NT 4.0 and Win2k and you'll see it. Microsoft is improving. Maybe not as fast as we'd all like, but they're certainly moving closer to where we'd like them to be. Now if only they'd revise their pricing...downwards this time.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    19. Re:I suppose it's wrong to mention... by Anonymous Coward · · Score: 0

      An important thing forgotten in the grandparent is that idea of, what if the virus attacks all 4 at once. Well attacking all 4 is much harder and less likely, and incidentally passes on the little detail that viruses in real life arn't stuck to a single species either. Or in other words, you don't know what your talking about.

      Reality simply is that your lowering the chance of all systems failing at once by diversifying. Less chance two different things fail then one, and so forth. Even for a virus writer it's harder to find two good security flaws on two different systems. This can be further reinforced by simply building defense in depth, like real life does. Having many layers of defense, if a fails, well we still have b, and then c and then d. And then you just vary between systems which kind of defenses they have. I think the NSA addition to linux is a good start for gaining this effect.

      Quickshot

    20. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      OK, let's continue to misunderstand my comment in the most Apache-favorable way, shall we? I never said a damned thing about 1.3 vs. 2.0. Duh! It's rather obvious that these two are strikingly different versions of the same program. But that's not what I was saying and I think you know that. If you don't you're denser than I thought.

      Now, once again, with feeling: the Apache 1.3 core code on any platform is strikingly similar to the Apache 1.3 core code on any other platform. The same thing goes for 2.0. Apples go with apples, oranges with oranges. There, now do you see where you were completely and totally wrong? Good, I thought so.

      This ends our lesson. Thank you for playing.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    21. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      The only problem with your analogy is that apache (Like most OSS) has at least 2 versions and normally many more, which are currently in widespread usage.

      Just like Windows has maintained dual code bases with the Win9x series and the WinNT/2K/XP/2K3 series. That doesn't change anything. And even the NT-based kernels are significant variations on one another (at least as significant as the kernel or various Apache versions).

      If an exploit is found in apach 2.0.48, great but maybe I'm still running 2.0.47 and the bug was just introduced, maybe I'm running version 1 still, this diversity of versions creates alot of diversity in the unix world

      And many Windows users don't bother patching their systems to the fullest extent, creating the exact same scenario. Some might have this patch but not that hotfix, making them vulnerable to this but not to that. Some might be running Outlook and thus be vulnerable to a worm, whereas some may be running Netscape mail and not be vulnerable. The analogy remains good despite your attempts to unseat it.

      therefore, you can't as a virus writer rely on some windows dll, and make calls against it, because there is no gaurantee the library you need will be there in the linux world

      So you just do what any other virus writer does and you try all the normal defaults you find in every Redhat, Debian, SuSE, Slackware, and Mandrake install. All of these systems install core utilities and binaries in predictable, known ways. If an exploit is discovered against any of these defaults then all installations of that product are potentially vulnerable. And since all of these have the Linux kernel at their heart, a kernel bug means all of them are susceptible. Again, you fail to see how a Linux/Unix monoculture is just as bad as any Windows monoculture, and a duoculture buys you very little for what you have to give up.

      and you will have to write a much larger virus to gaurantee you have the functionality you need on the system once you infect it.

      Have you ever even heard of punctuation, pal? Periods? Commas? The ever-elusive semicolon? Your post is like reading one long run-on sentence. No, wait, it is one long run-on sentence.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    22. Re:I suppose it's wrong to mention... by prisoner-of-enigma · · Score: 1

      Neither is parroting a PR-crafted argument from the company that stands to lose most from an avoidance of monoculture.

      Or whining that I made a derogatory comment about it.


      Ooooooohhhh...testy, testy. Did I disturb that carefully balanced chip that was resting on your shoulder?

      By the way, it's not parroting when you're coming up with intelligent comments on the relevant issue. But it does seem you most definitely don't like it when someone exposes and uncomfortable truth to you. Maturity issues, I presume?

      Kind of like driving productivity has suffered from the varied places auto manufacturers put the "high beams" control? I think you dramatically overestimate the difficulty (and frequency) of people switching from one system's GUI to another's.

      You know, it's thinking like this that's got the Munich Windows-to-Linux migration project in trouble right now. You should read up on it, but you won't. It's a case study on how to underestimate the difficulty that plain old run of the mill users have when switching "insignificant" things like the GUI. It may be easy for you to switch, and it may be easy for me to switch, but as much as I dislike sharing any category with you, you and I are not the common majority. So you think I "dramatically overestimate" the difficulty, eh? Just try moving a few thousand users from even something as similar as Win2K to WinXP. You've obviously never even thought about such a thing, otherwise you'd know better than to suggest it's not difficult. The Munich LiMux team now knows better. So should you, but you won't.

      The data-interchange issue is also a red herring. Common file formats can be (and have been) developed to allow easy exchange of data.

      So nice of you to sweep the most common complaint so easily under the rug. Thank you for making the world so simple! We should all just decide to use some lowest-common-denominator common file format. And, of course, you have the ability to make all application developers conform to this immeidately, don't you? And when a new feature comes out in one application, this file format will automatically allow that feature to be utilized in other, competing applications, right? What a software miracle worker you are! I salute you!

      doesn't mean it A) has to be that way, or B) should be.

      Ah, but you ommitted "C) but it is that way despite my rose-colored-glasses view of the world.

      Perhaps is time to devote less attention to making excuses for how we got here, and more attention on how to fix it.

      Fine. Offer me a practical solution that everyone can agree upon and mutually decided to endorse and I'll jump on board immediately. But you can no more force that to happen than you can stop the Earth's rotation. You're living in a wonderful pipe dream where everyone acts altruistically, nobody's greedy, and even arch competitors work together for the common user good. It ain't gonna happen, comrade.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
  31. Should of by Anonymous Coward · · Score: 0

    Great command of the English language!!!

    1. Re:Should of by Anonymous Coward · · Score: 0

      Great job of being a prick!

  32. 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
    1. Re:We suggest you reboot... by Anonymous Coward · · Score: 0

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

      Sure, he didn't say anything about plugging the computer back in did he?

  33. 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.

    1. Re:The trouble with diversity by Anonymous Coward · · Score: 0

      Want diversity?

      Want to increase online security?

      Then change.

      Start by Installing a stable, easy to use and secure Linux distro.

      SuSE 9.0 is an easy to migrate to OS for any XP user. ...and no, not everything is the same as XP. It's not XP. You will have to do some learning, but the learning curve is minimal.

      Or you could just continue being the average lazy, ignorent Windows user and keep contributing to the problem.

      Hackers are about to make it even easier for you to be flattened by a virii attack now that Microsoft source has been leaked to the entire world.

      A safe and secure SuSE 9.0 user.

    2. Re:The trouble with diversity by rqqrtnb · · Score: 4, Insightful

      Start by Installing a stable, easy to use and secure Linux distro. So.. In order to be diverse, everyone must use Linux. Aparently your dictionary has a different definition of diverse than mine. Hackers are about to make it even easier for you to be flattened by a virii attack now that Microsoft source has been leaked to the entire world. Exactly how is "Windows Source available on the internet" more dangerous than "Linux source available on the internet" ? The problem isn't that Microsoft software has security issues. All the OS's have 'em to some degree. The problem is exactly "monoculture". One bullet kills all. I'm more of a mind that companies need three operating systems. ... Call them Alpha, Bravo and Charlie to avoid the existing OS arguments. Alpha runs on the corporate web servers, ftp servers and in general anything hooked to the outside world. Bravo runs on the intranet servers that provide file storage, user authentication, etc etc. Charlie runs on the employee desktops. Thus any virus that targets the public layer (Alpha) won't effect internal operations. Any virus that targets the workstations (Charlie) won't spread to the intranet servers (where important data should be stored, and regularly backed up) and any virus that targets the intranet servers (Bravo) needs to get past the other two (Alpha and Charlie) -- or introduced directly -- to be a threat.

    3. Re:The trouble with diversity by pandrijeczko · · Score: 1
      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.

      I'm no Windows programming guru but even I know that certain elements of Windows have existed right from Windows 9x through to XP - sure, MSDOS disappeared but much of the GUI and Win32 bits remains the same.

      Then add Outlook or Outlook Express with the same core mail engine and I reckon you can capture 95% of the Windows user base with "similar" setups.

      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.

      Most people are too damn lazy to want to learn anything (as I said in my earlier post). Isn't it self evident that they need to know more or just take their virus-ridden PCs off of the Internet... end of story.

      We take drunk drivers off the road because they cannot act responsibly for other users, what's the difference?

      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.

      I most certainly would not. Microsoft have always sold their products in exactly the same way and everyone here would agree that viruses spread because people simply do not know what they are doing with their PCs - if they took the time to learn a bit more, they wouldn't be so stupid as to open every email attachment they receive...

      --
      Gentoo Linux - another day, another USE flag.
    4. Re:The trouble with diversity by andreMA · · Score: 2, Insightful
      Exactly how is "Windows Source available on the internet" more dangerous than "Linux source available on the internet" ?
      Because Linux has been open all along and subjected to a cummulative 10+ years of the equivalent of peer review. Windows source hasn't, and has only been reviewed/inspected by a relative handful of people with PHBs urging them to finish what they're doing to move on to the next project.
    5. Re:The trouble with diversity by Anonymous Coward · · Score: 0
      The problem is exactly "monoculture". One bullet kills all.


      horseshit, you gotta be able to penetrate defenses to start with, the problem with ms is exacerbated because there are so many ms machines out there, but the fundamental flaw is ms technology and security or lack thereof.

      how come so many posters at /. seem willing to do volunteer work for ms' well-paid spin doctors?
    6. Re:The trouble with diversity by raga · · Score: 1
      Exactly how is "Windows Source available on the internet" more dangerous than "Linux source available on the internet" ?

      Here's the first "exactly how".

      cheers- raga
  34. Another older monoculture by News+for+nerds · · Score: 0, Troll

    it was called 'UNIX'

    1. Re:Another older monoculture by pandrijeczko · · Score: 4, Insightful
      Hmmm, let me see...

      Solaris, AIX, HP-UX, BSD, FreeBSD, OpenBSD, NetBSD, SCO Unixware, Tru64, Linux etc. running on PCs, SPARCS, DEC PDPs and other vendor-specific server hardware...

      Still looking for that "UNIX monoculture" in there...

      --
      Gentoo Linux - another day, another USE flag.
    2. Re:Another older monoculture by Sprite+Remix · · Score: 0, Flamebait
      Dumbass, it WAS called 'Unix'.

      Funny, parent post was a troll trolling a troll, and of course somebody had to backlash. Oops! there goes my karma!

    3. Re:Another older monoculture by mrscorpio · · Score: 2, Interesting

      Not true, because all the versions of Windows were made by one company, and none of those versions of were made concurrently to compete against another version of Windows...sure, one could argue that anything new is still competing with Windows 98 on the desktop, but that's not the point.

      I do agree that we need different, non-Unix OS's to be available, but your comparison isn't valid.

      Chris

    4. Re:Another older monoculture by pandrijeczko · · Score: 3, Insightful
      If you're going to say that then we have win95, win98, win2k, winnt, winxp.

      Yes, and there are thousands of utilities that run on all those versions of Windows as a few binaries and libraries that are put on the PC at installation time.

      Try finding a single compiled binary or library that runs on all UNIXes across all the hardware that UNIX runs on. (Surely someone with 20 years UNIX experience would know this?)

      I'm tired of all this let's kill windows bullshit.

      Fine, in which case you've responded to the wrong posting - I implied "let's kill those Windows users who are too lazy to learn how their PCs work", a big difference.

      I've been a unix and now linux person for almost 20 years.

      ...and presumably your shell-scripts are also filled with profanities also...

      I'm tired of the elitist shit that goes on in our community.

      So you have a problem with people learning to better themselves, do you? Then you're no different to those lazy users that cause these problems in the first place.

      --
      Gentoo Linux - another day, another USE flag.
  35. 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.
    1. Re:Solution: Multi-OS Boxes by Neurotoxic666 · · Score: 1

      The biggest downside is bloat and cost

      Indeed! A large portion of Windows users won't even pay for Windows anyway and think a computer should be dirt cheap so they go out and buy the "basic kit" at Joe's 'Puters.

      A multi-OS-wifi-majority-rules-functional-networkabl e-compatible-user-friendly computer really is nothing more than an utopia. This wouldn't work today and probably never will. The public (myself included) thinks a 1,000$ PC is just fine and does everything OK. The device you are dreaming of has military uses, and seldom would pay a hundred grand just to download MP3s.

      No flames intended, I'm just being realistic here. Besides, if people pay too much for their PCs, they're more likely to stick with it for a long time - and that's a marketing no-no. Geeks might think it's cool to look for ETs on a beowolf cluster, but most people just don't need that. It's the very same reason Chevrolet Cavaliers sell more than BMW M3's.

      --
      You are more than the sum of what you consume. Desire is not an occupation.
  36. 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. --
    1. Re:i hate this ... by E_elven · · Score: 1

      Grannies are structuring their sock drawers in XML. What if there was a single specification for OS's to use for integrating?

      In any case, nowhere does it say that integration between OS's is supposed to be easy. That's not what OS's are about. An OS is responsible for one machine or one group of machines, and it's not even said that two different machines running the same OS need to be able to integrate (or, more appropriately in the context, co-operate.) This is a problem that can be (and possibly should be) solved in userland.

      --
      Marxist evolution is just N generations away!
    2. Re:i hate this ... by torpor · · Score: 3, Insightful

      An OS is responsible for one machine or one group of machines

      No, sorry, but an OS is responsible for the interaction between a human and a machine, and nothing else.

      If a humans' interaction with the machine requires that that machine be 'integral' with other machines, then this is the job of the Operating System ... this is why the TCP/IP stack is an OS stack, and not a userland stack, for example, or why the file i/o routines are OS-provided, not userland ...

      The reason it is so difficult to integrate Microsoft operating systems with other OS's (and not the other way around) is because Microsoft don't produce an 'operating system', they produce an 'operating system + suite ...', and more often than not they confuse the line between their suite and their OS in a way which makes it very unpalatable for other OS vendors to follow... even though, in fact, some of them do actually confront this obfuscation and address it (case in point: the Samba team).

      If Microsoft really cared about integration, it wouldn't be an issue. They would use open specs, and open protocols for everything (not just the 2% of their system services demanded by the market...) But the problem is, they -know that integration is a key point for an operating system- and thats why they blur the lines between what is an 'integration model' and what is an 'application model'.

      It is next to impossible to sync a users' home dirs on a Windows box and a Unix box, on Windows. Its totally possible to do it the other way around, sync'ing 'from unix' ... the reason for this, is that integration has been designed out of Microsofts operating system model.

      "Integration", to Microsoft, means "Embraced, Extended".

      --
      ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    3. Re:i hate this ... by Sique · · Score: 1

      No, sorry, but an OS is responsible for the interaction between a human and a machine, and nothing else.

      In my operating systems lesson I learned it differently:
      An operating system administers the limited ressources (CPU time, IRQ slots, memory, I/O...) and protects different tasks running on the same hardware against each other.

      Interaction with the user is often done by other means. A server typically has no users, which interact with it, it has clients requesting services.

      --
      .sig: Sique *sigh*
  37. Some things the DoD and others do... by ChrisRijk · · Score: 4, Informative

    What's certainly true is that there's a lot more to having good security than getting rid of the monoculture problem. Probably the most important thing is to care about security from the start...

    Anyway, something the DoD and others have done for some time is to have triple barriers for certain things like firewalls. So instead of having the same firewall product and system all over the place, for each firewall, you have a series of 3 systems: one is a "hardware" firewall (an appliance basically), followed by two different firewall products running on two different architectures. This way a single flaw on one firewall or system will not comprimise overall security.

    They also turn the IT infrastructure into compartments, each walled out with firewall groups. So you have one compartment for front-end servers, one for desktop users, one for your data, etc.

    Yeah it adds to complexity, but this is what the paranoid types do to give themselves peace of mind.

  38. At least get the name right: by daveaitel · · Score: 4, Informative

    It's Dan Geer.

    -dave

  39. ahh, the irony... by di0s · · Score: 4, Insightful

    If I remember my computer history, wasn't Microsoft the alternative to the IBM monoculture? Now that IBM has embraced FOSS, they're the alternative to the Microsoft monoculture...

  40. WARNING! by Anonymous Coward · · Score: 0

    Those who claim their OS (read Linux, OS X, OpenBSD, or whatever) is completely secure are being deceived. Currently, there is no such thing as a totally secure OS. That's just the way it is, and no argument is going to change that fact.

    1. Re:WARNING! by rqqrtnb · · Score: 4, Informative
      But there are MORE SECURE operating systems than Microsoft's various Windows versions.

      The integration of the browser's ability to directly run code in Windows is the big hole that Microsoft has failed to fix. Integration of user software, such as Outlook or Office, directly to the operating system makes Windows the virtual equivalent of a petri dish for the internet and giving every 11 year old hacker the ability to cripple corporate networks globally.

    2. Re:WARNING! by pandrijeczko · · Score: 1
      Anyone who has decided to use Linux, OS X, OpenBSD, etc is hopefully sensible enough to know that security is a process not a goal.

      Anyone doing stupid enough to do so on an Internet forum would be just asking for trouble so I don't know who it is you think actually believes this - I certainly know of no-one.

      --
      Gentoo Linux - another day, another USE flag.
    3. Re:WARNING! by rixstep · · Score: 1

      But there are MORE SECURE operating systems than Microsoft's various Windows versions.

      OK, I seriously doubt this is possible - I mean how can you improve on perfection - but if it should, against all odds, be true - why are you holding us in suspense?

  41. Not monoculture, just laziness... by pandrijeczko · · Score: 4, Interesting
    Is it just me or do all these pro- and anti-Microsoft "prophets" seem to be missing the point entirely?

    The Internet is created on a suite of open protocols that were originally designed for academics & research people to use. Go back 20-odd years and there were no issues of security because only a select few had access to computer networks. Consequently, there was no security built into TCP/IP because there was no need for them.

    Now we have a situation whereby if you are a sensible & knowledgeable computer type, whether you use open or closed source software, you can make a pretty good job of securing computers for the Internet - sure, you probably have a reliance on getting the latest patches, putting in a firewall or two but you can do it. No computer is ever fully secure but you can make it enough of a challenge so that the 99.9% of script kiddies give up trying to crack it and the other 0.1% of knoweledgeable crackers probably don't want to waste time with your little box anyway.

    Then onto email viruses... Knowledgeable computer users don't suffer from email viruses because they either use email clients that can't execute attachments or they set their machines up so that they know when and when not to run attachments - probably by simply looking at whether or not the sender of the email is to be trusted.

    So, in summary, I see this as two core issues, nothing more:

    1. Hype and marketing - Microsoft and other software vendors need to step away from the "sales speak" and simply not be allowed to tell Joe Public that PCs are "easy to use" or "secure". It's no different to reminding people to watch their speed and check their tyre treads on a new car, after all... Where are all these "advertising standards" groups that are supposed to ensure adverts convey truth, not lies?

    2. User laziness - Joe Public needs to get off his backside and learn how to use the Internet properly and how to secure his PC - again, no different to spending time and money in learning to drive. Far too many people, taken in by the glossy adverts and hype, just sit back and expect software vendors to take away all their responsibility away from them because they themselves simply cannot be bothered.

    What really annoys me about this whole issue is that software (and hardware) companies are only going to react to security issues in their products in a way that makes them more money. If the vendor already has his boxed software on the store shelves, he really has no incentive to employ people to work on further security for his products unless his reputation is so bad that he is forced to improve his software at the risk of losing sales - and you only have to look at Microsoft's currently poor reputation and their actual focus on security to see how far down that reputation must go before any action is taken...

    However, on the other hand, DRM can be sold as a security-improving product on the back of peoples' fears of Internet viruses while allowing the Microsoft and others to make money licensing DRM.

    I wish people like Dan Greer would focus more on the ultimate impact of letting Microsoft "take the blame" only to have Microsoft respond with a technology that will make them more money and cut off our freedoms in the process.

    --
    Gentoo Linux - another day, another USE flag.
    1. Re:Not monoculture, just laziness... by lcde · · Score: 2, Interesting

      Knowledgeable computer users don't suffer from email viruses ...

      Since we are relating things to biology, you could say this is survival of the fittest. People who are willing to change their bad habbits on the internet will 'survive'.

      --
      :%s/teh/the/g
    2. Re:Not monoculture, just laziness... by Anonymous Coward · · Score: 3, Insightful

      Friend, it ain't just laziness. Some of us have been urging and working on fundamental security advancements for decades now. But there's a huge *regulatory* problem, preventing fundamental data authentication and encryption in the US, and it's been crippling developers for years. Yes, it's unconstitutional, but the last time it got slapped down it got moved from Customs to Commerce, where it is now a looming brick over the head of every security developer.

      That brick helps prevent *funding* or release of new products that would provide basic security for VPN use, built-in Ethernet encryption to protect us from packet sniffing, SSH instead of unencrypted telnet for programming routers safely, etc.

    3. Re:Not monoculture, just laziness... by pandrijeczko · · Score: 1
      I agree that encryption is a part of the problem but basic stuff like not running the (clear text) services you don't need, using inetd type restrictions and a reasonably configured firewall / NAT router goes a long way towards good security.

      No disrespect to the knowledgeable Windows people on Slashdot (or anywhere else) but the fact of the matter is that the Windows community is rife with stupid, lazy users who are the biggest cause of the whole problem.

      --
      Gentoo Linux - another day, another USE flag.
    4. Re:Not monoculture, just laziness... by UpnAtom · · Score: 1

      I'll be interested in knowing how you propose to fix user laziness.

      I think you're right about DRM though. Microsoft's financial future depends on it. This is why they're promising so much about security, yet doing nothing about it. I doubt they deliberately leaked the source code, but I bet they didn't worry overly when they started relaxing their restrictions on who could see it.

      We need a counter campaign - any ideas?

    5. Re:Not monoculture, just laziness... by rixstep · · Score: 2, Insightful

      Good stuff, but remember:

      1. Both Unix and Linux came out of unstressed environments.

      2. The PC market has led to hysterical commercialism.

      Today we see a planned obsolescence that even the US automotive industry would be ashamed of. As Mark Minasi found when interviewing marketing suits for his book 'The Software Conspiracy', the suits know about security and bugs, but they deliberately prioritise them down.

      They need to get to market instead.

      Unix had its exploits in the beginning. It was dead easy to install a trojan at the login screen. Heck, I devised a hack that worked on all SVR4 machines to take over root. It's just that Unix and Linux have both had a chance to mature without all this hysterical going-on plaguing the market Microsoft is in.

      Plus, and this is a no-brainer: there are a lot more talented people working at Bell Labs and with Linus.

  42. WFH? by IWantMoreSpamPlease · · Score: 0, Offtopic

    >>...for his warnings about the widespread use of Microsoft products and the serious security flaws that are being discovered.

    This is news? I mean seriously, we knew Windows was insecure from the day the first NT server was hacked.

    This can't possibly be news to anyone.

    --
    So rise up, all ye lost ones, as one, we'll claw the clouds.
  43. the end by rastamutz · · Score: 0

    this is the end of M$ until the *nix't beginning. (C) sid vicious

  44. 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
  45. Big News... by Peden · · Score: 2, Funny

    Since when was big news defined by Yahoo bringing it on their front page?

  46. One word for ya: "Mac OS X" by Anonymous Coward · · Score: 0

    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.


    There is a best-of-both-worlds system out there, actually. Open where openness counts, and the fuzzy my-vendor-smooths-out-the-rough-edges and software maintenance fluff that come with a vendor taking responsibility for, well, taking care of their own product.
  47. 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.
  48. Diversity is great... by andih8u · · Score: 4, Insightful

    Diversity can help keep viruses and such from spreading, but it can also be a hindrance. If linux had some standardization where all of the distros all used the same directory structure, package management, etc, it would be a lot easier for companies to write software for it. Now the best they can do is write the software and hope someone else will port it over, or spend time porting it to .RPM, .DEB, etc etc. With windows you don't ever run across cascading dependency nightmares, and every software company knows how to write their software for it. Yes, you should be able to compile linux packages from source without any problems, but when you're talking about trying to get home users to accept linux more, making them compile packages from source definately isn't the way to do it.

    --


    slashdot, news for crazed liberal socialist zealots
    1. Re:Diversity is great... by pandrijeczko · · Score: 2, Insightful
      I think the issue with Linux is that the developer community should not listen to the people calling out for "ease of use" anyway, at least from the point of view of trying to get Windows users to migrate over.

      People need to understand that you cannot decide to use Linux purely because of a fashion statement or an anti-Microsoft feeling. Sure, a lot of people have come into Linux in that way but they've also taken the time to learn about Linux in the process to the point where it becomes "easy to use" to them.

      The issue of companies developing for Linux is different entirely. If we accept that the Open Source movement is still growing, then do we need to worry about commercial software being ported over to Linux? I do everything I need to in Linux these days and I always compile from source anyway (via Gentoo Linux). It would be nice to have a few more games brought over from Windows but other than that, I accept that there will be more and more Open Source software available to me as time goes on.

      I think a little perspective is needed here as I don't recall any of the important players & programmers in the Open Source movement ever making a statement about wanting to bring users in from the Windows community. They're just writing good software that's free to use to all & sometimes needs some effort to get working.

      It's wrong treating the whole thing as a "Linux vs Windows" war because it's just about having an alternative, free way of doing things.

      --
      Gentoo Linux - another day, another USE flag.
    2. Re:Diversity is great... by pavera · · Score: 1

      I disagree,
      there is already a good deal of standardization as far as directory structure is concerned, and most comercial apps I've installed on Linux (they do exist you know) have their own binary installers, they don't rely on rpm or deb or anything else, so I don't think its necessary to standardize on one type of package management. having a good directory layout is key though and that what LSB is all about.

    3. Re:Diversity is great... by pavera · · Score: 1

      More importantly however (sorry for replying to myself) is the fact that installing a program in linux is not like windows its much more like in mac OS, you don't have to write to the registry, you don't have to depend on a bunch of system DLLs, can just zip up a bunch of stuff in a disk image, and then have the user drop the unzipped stuff onto their hard drive and it will just run. this is how mac has always worked, and it is the *easiest* way to install things ever. For normal programs (games, office programs, IM clients, media players) this paradigm works fine on mac os, and it works fine in linux too. for larger more complex server type programs its reasonable to expect someone to compile from source.

  49. 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

    1. Re:M$ tight integration could cause more harm ... by Anonymous Coward · · Score: 0

      If you delete the executable and turn off System restore, than IM is gone. I did it.

    2. Re:M$ tight integration could cause more harm ... by Anonymous Coward · · Score: 0
      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.

      The general software engineering principle you speak of is about low coupling and high cohesion. Or, in other words, keep the stuff that's similar together and don't intertwine unrelated pieces.

      You would be amazed (or not!) at the amount of code that I've inherited from shoddy developers that is highly coupled and has very low cohesion. Once you've code a rats nest of code (and probably no tests), it takes forever to straighten things out.

    3. Re:M$ tight integration could cause more harm ... by rixstep · · Score: 1

      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.

      Apple use a micro-kernel, of course, and Prism started as micro-kernel. While Steve Jobs got Avie Tevanian, MS got Rick Rashid.

      But Cutler abandoned the micro-kernel idea after a while, especially when he was 'gradually' made to understand that he wasn't making a cute console-mode LAN server to be locked good and proper in a vault, but a wiz-bang server with a GUI (Cutler hates GUIs) and with WIZARDS so terminally clueless people could configure his OS.

      Faced with the unavoidable slow-down which all this traditional 'Microsoft technology' meant, he started moving things back in. win32k.sys turned out to be one of the hugest files in the system. That's the Win32 subsystem. Prior to NT4, it ran outside the kernel - where it should. Because the idiots making Windows Explorer were idiots, Cutler had to move it back in, or lose the 10/1 speed ratio he had held.

      The beginning of the end. BSODs due to bad drivers became common under NT4. They'd been seldom seen on prior versions.

      And then Cutler had had enough, and left town.

      And that's when things really started to go bad...

  50. That settles it! by Anonymous Coward · · Score: 0

    I'm switching to VxWorks ... because if it's good enough for NASA on the Mars rovers, it's good enough for me!

  51. Just an FYI... by Anonymous Coward · · Score: 0

    And before my morning Dew, no less!

    "Morning dew" is a slang term, similar to the term "morning wood," but regarding the female gender.

    [see romp.com for more info]

  52. Re:Apple's worse by frankie · · Score: 4, Insightful
    forcing you into a monoculture of quirky, overpriced hardware

    Yeah, and we all know how many awful hardware vulnerabilities there have been in recent decades... :p

    dropped floppies and non-USB interfaces much later, only after they were not that useful anymore

    Except that you're ignoring the chicken-v-egg problem. USB did not become ubiquitous until after Apple forced the issue. No one else had the balls to say "screw dumb serial ports, USB is better". GUI, 3.5", CD-ROM, PnP, etc... Apple intentionally drives technology forward, even when many people are kicking and screaming to stay behind.

    Meanwhile, none of this has anything to do with security and monocultures.
  53. 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.
  54. Tired Joke... by Anonymous Coward · · Score: 0

    ...but here goes: Maybe whoever looks at the source code will fix it and give it back.

  55. Another interesting spin ... by frankie · · Score: 4, Insightful

    My favorite quote on the topic came from Wired. Marcus Ranum thinks Geer's message would have been mostly ignored by the public at large, except for @stake's "brilliant surgical marketing strike on its left foot by firing Dan".

    1. Re:Another interesting spin ... by Anonymous Coward · · Score: 0

      That was supposed to be Score: 5, Funny, you ignorant clods!

  56. Re:Sad news ... Stephen King dead at 56 by Anonymous Coward · · Score: 0

    I've been waiting for goatse's obituary for a while now. I'd like to know the true cause of his death. Like: did he have a mishap while getting anal sex from CmdrTaco? Or: Did a filthy Linux zealot go to far in touching his junk liberally? Too many unanswered questions. Tsk, tsk.

  57. sorry--wrong format by rqqrtnb · · Score: 1

    Start by Installing a stable, easy to use and secure Linux distro.

    So.. In order to be diverse, everyone must use Linux. Aparently your dictionary has a different definition of diverse than mine.

    Hackers are about to make it even easier for you to be flattened by a virii attack now that Microsoft source has been leaked to the entire world.

    Exactly how is "Windows Source available on the internet" more dangerous than "Linux source available on the internet" ?

    The problem isn't that Microsoft software has security issues. All the OS's have 'em to some degree. The problem is exactly "monoculture". One bullet kills all. I'm more of a mind that companies need three operating systems. ... Call them Alpha, Bravo and Charlie to avoid the existing OS arguments.

    Alpha runs on the corporate web servers, ftp servers and in general anything hooked to the outside world.

    Bravo runs on the intranet servers that provide file storage, user authentication, etc etc.

    Charlie runs on the employee desktops.

    Thus any virus that targets the public layer (Alpha) won't effect internal operations. Any virus that targets the workstations (Charlie) won't spread to the intranet servers (where important data should be stored, and regularly backed up) and any virus that targets the intranet servers (Bravo) needs to get past the other two (Alpha and Charlie) -- or introduced directly -- to be a threat.

  58. A response to the idea of a "monoculture" ... by Anonymous Coward · · Score: 0

    summed up in a nifty catchphrase:

    "Security through operating system diversity."

    How best to implement this,I leave as an exercise for the reader.

  59. Re:Apple's worse by Anonymous Coward · · Score: 0

    Except that you're ignoring the chicken-v-egg problem. USB did not become ubiquitous until after Apple forced the issue

    This is not true, as USB was growing before Apple was involved, and continued growing after. However, it shows the problem: why force the issue at all? Things worked out a lot better in the PC world, where you had both USB and pre-USB ports, and didn't have to buy dumb dongles and convertors.

  60. wrong name by Anonymous Coward · · Score: 0

    Uh, guys, that's "Dan Geer", not "Dan Greer". (Only one 'r'.)

    Please show some respect by getting his name right.

  61. The Wall has been Breached by Ridgelift · · Score: 4, Interesting

    "But Geer says the company should disentangle its tightly integrated products, such as Microsoft Word and Outlook."

    The best way they can disentangle their products is to force Microsoft to publish their protocols, so others can build competitive products that can integrate cleanly.

    Perhaps their software should be declared an "essential service", much like teachers and hospital workers here in Canada. When teachers/medical workers strike for too long, the government steps in and says "get back to work, you're essential to our functioning as a culture".

    The bottom line is Bill Gates and his minions are liars and can't be trusted. They comply to every defeat dealt to them with their middle finger raised, and then go right back to abusing their position in the marketplace. The only rules Billy plays by are his own, and the only reasonable way to deal with him is to be unreasonable in demanding he comply.

  62. DevX article author is a tool by tizzyD · · Score: 4, Insightful
    I mean really, come on. Only a fool would not know that open source has the capacity for foul play. But with the eyes of the crackers come the eyes of the police, or in this case, the moderators. So, with a simple code review, you can spot an issue. With OS, you have a chance.

    OTOH, with any closed source system, you have no code review. You have no chance to spot a security hole, purposeful or not. With CS, you simply have no chance.

    Let's review: with OS, you have the opportunity for exposure, but also the opportunity to catch it. With CS, you have no opportunity to know anything. Sounds like the old free markets argument to me. The only person who would really support the CS position is an uniformed tool.

    --
    ...tizzyd
  63. hahahahaha by Anonymous Coward · · Score: 0

    OK, someone do a NO CARRIER joke now.

  64. They still were useful by Anonymous Coward · · Score: 0

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

    In the case of USB, Apple stopped putting non-USB ports on machines at a time when few devices had USB. At this time, the USB technology was less useful than non-USB technology.

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

    No, as it is a free market much less manipulated by the decision of a single company, PC's dropped these things when they really WEREN'T useful anymore.

    Apple can act as the gentle motivational herder....(floppy > email, legacy ports > USB).

    E-mail never replaced the floppy. The "no floppy iMac" was a major blunder at the time, since ti make up for it you had to buy a much more espensive CD-R, or an external floppy.

    Floppy drives only began to vanish on the PC when there was no actual need: CD-R drives and thumb/ram drives became cheap enough.

    So I would hardly call this scenario a 'blunder' on Apple's behalf!

    If you won't call it a blunder, call it a design flaw.

    I'm sure it was of great benefit to both Apple and their users to make a swift concerted step forward.

    It was not a benefit to have to buy a dongled floppy drive when PC users, or to have to get converters.

  65. Word of the Day: frisson by ronmon · · Score: 3, Interesting

    "The hoopla around him losing his job gave the story some extra frisson," said Internet security expert Bruce Schneier, a co-author of Geer's.

    frisson
    n : an almost pleasurable sensation of fright; "a frisson of
    surprise shot through him" syn: shiver, chill, quiver,
    shudder, thrill, tingle

    Overall, this is one of the best written articles I've read in quite some time. The author lets the intelligence of his sources shine clearly. And it's always nice to learn a new word.

  66. Re:Apple's worse by goatan · · Score: 0
    Apple intentionally drives technology forward

    Yep right off the edge of a cliff

    --
    Saying Apple is better than MS is like saying Botulism is better than rabies.

  67. Re:Apple's worse by borjam · · Score: 1

    Hardware standards in the PC world are written in a different ivory tower: Intel.

    Microsoft, of course, has a lot to say about PC hardware standards. Look at the AMD Opteron-Intel 64 bit CPU driver support with the 64bit Windows edition...

  68. I love microsoft by BoomerSooner · · Score: 4, Funny

    They keep all the focus on hacking their POS operating system and help my mac and linux servers avoid the amount of attacks that would happen if they didn't exist.

    MS is a competitive advantaget to those that compete with vendors providing MS based services. BTW my company does have MS servers, Linux servers and we are testing some new OS X server implementations to see if we can eliminate some of our admin tasks with their slick UI & tools.

  69. 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 -
    1. Re:is not monoculture, is evolution. by Cytlid · · Score: 3, Insightful

      Those are all simple, standards-basesd protocols, not an entire OS which would constitute a "monoculture". I can program an smtp client in perl... do you think I could as easlier write an OS?

      --
      FLR
    2. Re:is not monoculture, is evolution. by NotInTheBox · · Score: 2, Insightful

      What you are talking about is protocol, analog to RNA and DNA in biology. Monoculture on protocol is not bad of dangerous and will make life much less difficult.

      However: all protocols need to be implemented and every and all implementations will have bugs. To have a monoculture of implementation will cause there to be a monoculture of one of more bugs which are things outside of the protocol, which should not happen but sometimes it does... if one fails, they all fail.

      IPv4 is so trivial that I could write (have writen) my own, but what is the point?... My MTA (SMTP protocol) is postfix, my web server (http, webdav) is Apache1, but there are others out there and not many people have the same as me...

      --
      What I cannot create, I do not understand
  70. Tinfoil Hats and ReactOS by Anonymous Coward · · Score: 1, Interesting

    Maybe Microsoft is trying to do to ReactOS what SCO is trying to do to Linux?

    1. Re:Tinfoil Hats and ReactOS by Felinoid · · Score: 1

      It would not be unlike Microsoft to do such a thing.

      Before Microsoft pulls a stunt someone else pulls it first and Microsoft sits back and watches how things come out so they can pull the same stunt and have an excuse for it.

      So if Microsoft is trying to SCO ReactOS then the tinfoil hat thing to do is watch the ReactOS code submissions carefully.

      --
      I don't actually exist.
  71. Re:Apple's worse by Lumpy · · Score: 3, Interesting

    No one else had the balls to say "screw dumb serial ports, USB is better".

    because only complete morons say that.

    Serial ports have their place and will be here for a really long time. I dare you to config a cisco router or switch with your USB port. or dare you to configure any of the middle to high end home automation equipment out there with your USB port.

    USB is excellent for low-performance high bitrate data transfers.. firewire beat's it to hell for performance needs (ever wonder why you can't get high end DV cameras with USB?) and RS232/RS485 serial is better than anything that USB or firewire can do for low speed high reliability.

    apple did NOT force the adoption of USB... the explosion of cheap usb products by the release of cheap usb interface chipsets.

    --
    Do not look at laser with remaining good eye.
  72. Simulation by Tom · · Score: 4, Insightful

    I know it's a stupid thing to /. yourself, but here we go:

    My paper on worm propagation from last year (just updated with some more data) shows very clearly what a monoculture does.

    I assumed 40 mio. vulnerable systems in it and showed how a malicious worm can wipe them out in minutes.
    Some of the advisories that eeyes still has on the unpublished list estimate 300 mio. vulnerable systems.

    We've been talking about flash and warhol worms for years now. With each passing day I'm more surprised that it hasn't happened, again.

    --
    Assorted stuff I do sometimes: Lemuria.org
    1. Re:Simulation by Anonymous Coward · · Score: 0

      .. to /. yourself ..

      Selfslash
      Prevailed your honour has.

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

      Cool link you have here, Tom.

  73. USB not "generally superior" by Anonymous Coward · · Score: 1, Insightful

    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).

    USB is not "Generally superior" for many things. Printers, for example. Stuff prints out the same on your typical inkjet whether or not it is plugged in through a Centronix port or USB.

  74. Re:Apple's worse by Anonymous Coward · · Score: 1, Insightful

    > USB did not become ubiquitous until after Apple forced the issue.

    Given the number of users, it's much more likely that USB only became ubiquitous because Win98 finally provided decent support for it.

  75. OS dose effect the tech savy of it's users by Felinoid · · Score: 1

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

    Hardly true.
    Anyone remember the old antiMac FUD
    "When you hide how the os works the user never learns"
    This is FUD not so much for being untrue but becouse MacOs dosen't hide how it works.
    It's not anymore applicable to MacOs than the "Total Operating Cost" FUD is to Linux.

    But Windows dose. Notice how Windows trys to do everything for the user?
    MacOs however shows the user how everything works.
    Linux is for the most part a cluster of tools. There is nothing between the user and the Os. Not even a road map.
    The typical user has to rely on his/her computer to learn and understand how it works and when it dose not coperate the typical user dosen't presue the matter ignorent of the details.
    After all most people use computers to get things done not to learn how they work. This minnor detail must mystify Microofts staff as to why people who do favor Linux do. But it's actually quite simple. Linux users want to know how things work so they can make best use of the equipment.

    On that note MacOs users while not intrested in learnning do learn and end up making best use of the Mac.

    MacOs guides the user.
    Windows encurrages ignorence.
    Linux forbids it.

    --
    I don't actually exist.
  76. UG! by LordKazan · · Score: 1

    I was moderating this thread until I saw this comment - simply modding you down for being an airhead wouldn't get the point across.

    LANGUAGES DO NOT CAUSE ERRORS -- BAD PROGRAMMERS CAUSE ERRORS

    You call the best programming languages out there (C/C++) "buffer overflow" languages - implying that they are broken - because they give you POWER they give you the full control that allows you to write the most effective programs. I want to see you perform pointer arithmetic in perl, python, java or C# -- I can show you some simple pointer arithmetic that reduces execution time drastically.

    Java = distilled OOP to the point of masochism (ie non-OO tasks in OO), drastic performance loss due to being interpreted, all the GUI toolkits are confusing at best

    C# = Platform Locked result of a foul craft cross between VISUAL BASIC and C++, One of my friends had to write in this horrid language for a class project because the other three members of her group were MS-Whores -- she became a rabid MS-hater after that, she never minded them before.

    Perl - Good for a great many things, GUI applications aren't typically good in this language - and absolutely not games, time critical, mission critical, etc

    Python - I haven't seen a use for it yet.... but i hear of it being used.

    --
    If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    1. Re:UG! by steve_l · · Score: 1

      What good is execution time tuning if the time saved waiting for something to execute is lost dealing with security problems?

      I dont want to fault C & C++ explicitly, but buffer overflows and memory leaks are key problems of them, problems we dont need any more. Are any of the next generation languages a good alternative. Maybe not yet. But there is no need for every single line of code to be written in C/C++ for performance these days, and many places where other languages are more secure and easier to write with.

    2. Re:UG! by LordKazan · · Score: 1

      You missed the point of my post - buffer overflows and memory leaks are due to BAD PROGRAMMERS - lazy, or just plain incompetant programming.

      --
      If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
    3. Re:UG! by steve_l · · Score: 1

      maybe so, but it is so hard to be competent when the failure modes of C/C++ are memory leaks and buffer overflows. Also, stdlib almost builds overflows in to so many of the calls. Take, for example, strcpy(). Default action on receiving a source larger than the destination: buffer overflow. Only strncpy() checks for trouble, but even when people are 'clever' and use that, they usually forget to force a \000 into the last char and so when big data comes in, things still go wrong.

      Memory leaks? Incompetence? Probably, but it is very hard to manage object lifetimes in a multithread environment. You end up implementing a reference count layer (as COM and Mozilla's COM equivalent do), and then have reference count bugs instead.

      Now it may just be that with adequate competence and time these problems dont arise, but today they do. All over the place. And I dont think mandating superior competence for developers is going to work -and nor do I think it is necessary. Instead languages that dont leak memory or overflow buffers eliminate common problems.

      As someone elso points, out, incompetence treats failsafes as as damage to be routed around, and real incompetents will only go on to bigger disasters in a more productive language. But that does not mean we have to stick to languages and runtimes that dont do a thing to eliminate the fundamental problems. Its like saying we should ban ABS on cars as bad drivers will still run into things.

    4. Re:UG! by LordKazan · · Score: 1

      which compile's strcpy()? good thing to know

      I don't use STDLIB normally though - i use C++ classes --- this is still not a weakness of the language - but of someone's implementation of the standard library


      New languages the give you less ability over good programmers is never the solution - and im cases like mine it's not even an option. I need to be able to tinker with to low level stuff, etc. I have to OPTIMIZE my code - C#, Java, etc. preclude code optimization. implying that not having pointers is a "failsafe" is like saying a pen without ink writes.

      --
      If you cannot keep politics out of your moderation remove yourself from the Mod Lottery.. NOW!
  77. Apple had nothing to do with USB adoption by Anonymous Coward · · Score: 0

    Apple really had nothing to do with USB adoption. The big printer companies and mouse makers could barely be bothered to make special USB versions with Mac drivers. Apple's niche market was not enough tail to wag the dog here.

    Growing interest in USB in the PC world (including OS improvements where it handled it better) helped force the issue.

  78. You know what they say about "taint" by gosand · · Score: 1
    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.

    Anyone who assoiciates with Microsoft is a "taint by association" - as in this kind of taint.

    --

    My beliefs do not require that you agree with them.

  79. Re:I hope he's wrong ... wondering.. by SlashDread · · Score: 1

    Do the people running these systems have a UltraVeryHigh lawsuit insurance?

    Or do the recipies smallprint standard incorporate "Warning, recipy might be utter bullshit" clauses?

    "/Dread"

  80. 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.

  81. WRONG! stop the lies (was Re:Interesting spin ...) by spoonyfork · · Score: 4, Informative

    Yeah, without Microsoft products, Al Gore couldn't have invented the internet.

    I see my mission now.. to reply to every post with this lame ass joke with information about how it is NOT TRUE. You've heard of snopes.com, the Urban Legends Reference Pages? Please read this article before posting this lie. The proper joke would be, "Al Gore says he took the initiative in creating the Internet!". While certainly a poor choice of words for Mr. Gore even in context of the interview, he did not claim to invent the Internet.

    That goes for you too, moderators. This cliche is certainly not +5 Funny and you know it.

    --
    Speak truth to power.
  82. Don't be Surprised by Anonymous Coward · · Score: 0

    If a submission with this "leaked" code is made to Linux. It will most likely be coming from a minion of MS itself. Be careful with what is accepted into the next kernel. It wouldn't be the first time MS employeed such dastardly tactics.

  83. Which Culture? by smccto · · Score: 4, Interesting

    Monoculture or Diversity?

    The AP ran a story this weekend, captured by Yahoo, talking about Dan Geer and his thoeries of how the Microsoft Monoculture endangers computer security. I have concerns.

    Although I know this won't fend off the zealots who just need to speak their mind, else their puny little heads explode off of their shoulders, atrophied from lack of lifting their hands any higher than a keyboard, I offer this caveat: What I'm about to present is merely philosophical rambling, curious wonder, nothing more than an innocent what if. It is, in no way, intended to offer an argument, solution, opposition, or anything else that would offend (other than those puny headed, shoulderless freaks).

    Just the facts, Mam

    I found it intriguing that, as the AP article mentioned:

    "Steven Cooper, the Homeland Security Department's chief information officer... acknowledged [monoculture] was a concern and said the department would likely expand its use of Linux and Unix as a precaution."

    Why hasn't Mr. Cooper, the media, and suposed security experts who promote U/Linux as a safe alternative, acknowledge that U/Linux also have their share of security advisories? Take a look at Secunia and their product listing. Doesn't anyone care that Solaris 9 had more advisories (42) in 2003 than Windows 2000 Server (36)? Doesn't it scare anyone that, while Windows XP Home edition had 32 advisories, Red Hat 9 had more than twice as many with 72? Debian 3 had 186!

    Doesn't Open Source claim to have a better development model by throwing more eyeballs at the source code, thereby eliminating - or minimizing - security flaws earlier?

    Missing the forest for the trees

    Take a look at this, also from the AP article:

    "Mike Reiter of Carnegie-Mellon University and Stephanie Forrest, a University of New Mexico biologist who has been gleaning lessons for computer security from living organisms for years, recently received a $750,000 National Science Foundation (news - web sites) grant to study methods to automatically diversify software code.

    Daniel DuVarney and R. Sekar of the State University of New York-Stony Brook are exploring "benign mutations" that would diversify software, preserving the functional portions of code but shaking up the nonfunctional portions that are often targeted by viruses."

    Are these people frickin bonkers? We're barely capable of securing the simplest SMTP and FTP services. Software is already beyond our comprehension. What makes us so arrogant as to assume we can write software that makes other software more secure - without breaking it, without opening unforseen security breaches? We are decades away from being that intelligent.

    Of course, on the plus side of this approach, as software gets more complicated, it will be too obfuscated for the Puny Heads to understand and, therefore, will be a great deterrent for attacks! (Yeah, sarcasm)

    Miopic Intelligence

    Dan Geer likes to compare the information world to that of biology, equating computer viruses with biological viruses. I have one problem with this way of thinking. Biological viruses simply exist, have always existed and will always exist. They don't have an agenda. They don't have malicious intent. They aren't scheduled or targeted. They are nature. It's the way the system works. The global ecosystem is s

    1. Re:Which Culture? by Anonymous Coward · · Score: 1, Informative
      Why hasn't Mr. Cooper, the media, and suposed security experts who promote U/Linux as a safe alternative, acknowledge that U/Linux also have their share of security advisories? Take a look at Secunia and their product listing. Doesn't anyone care that Solaris 9 had more advisories (42) in 2003 than Windows 2000 Server (36)?
      Doesn't it scare anyone that, while Windows XP Home edition had 32 advisories, Red Hat 9 had more than twice as many with 72? Debian 3 had 186! Doesn't Open Source claim to have a better development model by throwing more eyeballs at the source code, thereby eliminating - or minimizing - security flaws earlier?
      Yes, that's the claim, and - just to be clear - you haven't proved it true or false here.

      If number of vulnerabilities were comparable it might be fair.

      If Windows 2000 came with several pop, imap, http, and ssh servers and many office suites and email clients and browsers then it might be a fair comparison. Redhat ships (er, shipped) with every bit of software you might need -- compare the entire range of Microsoft software to Redhat's and that might be a fairer comparison.

    2. Re:Which Culture? by Anonymous Coward · · Score: 0

      Why is this modded interesting? It's fundamentally flawed. Next to the bad use of security vulnerabilities it also totally misses the point of how biological systems operate. It doesn't matter that humans can make choices and are intelligent, the outcome will still be the same. We are unable to react quickly enough to viruses, nor are all humans clever enough or care enough to even properly secure systems, as such you should make systems and general setup of large networks to reflect a solution to this problem.

      There biology has some very good examples of how to deal with viruses in open systems, (ie multi layer defenses, which can differ from plant to plant. It only takes one succesful defense layer to stop a virus afterall) as such it would make sense to try and see if section of it can be copied, instead of talking right off like it's doomed to failure and impossible. I'm in favor of objectively giving peope the chance to try and implement such things, and if it works to put into general use.

      Quickshot

    3. Re:Which Culture? by zygote · · Score: 1

      You mention the higher number of security "holes" in various *nix vs MSFT software. If you have a server array with a mix MSFT, Unix, Linux, Mac OS X and such, you're not going to be competely taken down by cracker running an exploit against one OS. And if you have fail-over structured properly, you shouldn't see any disruption to service if a machine is successfully compromised. That is the case against a monoculture. Diversity, not absolute security.

      Tangentially, I agree that biology is a poor metaphor for this, but the idea that "The culture that we should focus on is that of the people responsible for software...[:]...Microsoft" doesn't fit either. The culture to focus on is one that encourages corporations to spend the least possible money on computing resources. Corporation's preference for cheap commodity hardware is what MSFT exploited (that and the Mac/Xeroc PARC GUI) to gain their 95% market share. Why would anyone give a shake when these companies and others complain that their ill-informed bargain hunting has created a system that nearly fatally flawed?

      The "culture" that wed themselves to cheap boxes, enjoyed mightily the savings until the started falling off. Expecting MSFT to fix it and then believing them when they say they can overcome the inherent problems with a closed, monolithic system is not a situation where "we all win."

      Sincerely,
      A puny zealot who must speak his mind lest his head explode...oh, whatever.

      --
      the future is here, it is just not evenly distributed - w. gibson
    4. Re:Which Culture? by KJSwartz · · Score: 1

      In defense of Dan Geer's analysis: Biological Systems have been in the making for 500 million years, and predicated upon 4.5 billion years of mechanical evolution. Computers are qute a recent phenom and it is sheer hubris to disregard the complexity of the biological - mechanical - digital interfaces.

      My interpretation of Dan Geer's article was the 95% reliance on the Microsoft monoculture had created a fragile ecosystem. Every aspect of R&D, Support, Distribution and Product EDUCATION is now controlled by a single entity. As an analogy, if you were stranded on a deserted island and relied solely upon Coconuts for sustenance, you better have a process for managing an bountiful supply.

      That is not to say that Microsoft's dominance of the industry has the same impact as swallowing bountiful coconuts.

  84. Re:WRONG! stop the lies (was Re:Interesting spin . by Anonymous Coward · · Score: 1, Informative

    While this guy might be a little overzealous, this should be modded more 'informative' and less 'troll'...

  85. Re:Apple's worse by Anonymous Coward · · Score: 0

    Not that many care to "hack" hardware.

    The etherkiller (bit of wire with plug on one end, especially a 240 V mains plug, that connects wires to the pins of an ethernet plug) is a fine choice for destroying a network and possibly starting a fire when the wiring overheats.

    You can always flash someone's BIOS for them, most likely rendering the system inoperable. I think the CiH virus did that?

    There was that one Linux bug that killed some CD drives or something with some bad instruction it sent.

    There are probably several other ways to damage components (especially if you muck about with the BIOS settings)

    Someone else could think of more?

    Maybe these don't have "security" implications per se, but I'd hate to have the next Windows worm do some of these things; it'd be a PITA for all the poor techs who have to support them.

  86. TROLL Re:I hope he's wrong ... by init-five · · Score: 0, Troll

    mod down - it's a troll

    --
    Hallowed are the Ori
  87. Microsoft Mono culture? by weierstrass · · Score: 1

    Shouldn't that be .NET culture?

    --
    my password really is 'stinkypants'
  88. No security?!? by El · · Score: 2, Insightful

    no security built into TCP/IP because there was no need for them. TCP/IP was not developed for academics, it's development was paid for by the Department of Defense, thus security was a consideration in the design of TCP/IP from day one. That is why TCP/IP was designed to dynamically reconfigure routing to work around failures, as opposed to SNA, in which the network was statically configured.

    --

    "Freedom means freedom for everybody" -- Dick Cheney

  89. "Big News" Fueled by a Slashdotting? by breadbot · · Score: 3, Interesting
    This story is quickly becomming big news (Yahoo is currently carrying it on their front page).
    I wonder how many stories get elevated to "big news" by being Slashdotted:
    1. Publish Story
    2. Link to it from Slashdot
    3. Yahoo's automatic pull-the-most-popular-up algorithm puts it on the front page
    4. Everybody else notices it too

    Now, that didn't happen in this case, as the story was already on the front page before Slashdot linked it. But it could happen, no?

    1. Re:"Big News" Fueled by a Slashdotting? by rixstep · · Score: 2, Funny

      Now, that didn't happen in this case, as the story was already on the front page before Slashdot linked it. But it could happen, no?

      No. By contract with the OSDN, /. is exempt from the Heisenberg Uncertainty Principle.

  90. Monoculture by Anonymous Coward · · Score: 1, Funny

    If monoculture is such a bad thing, why are people so supportive of "write once run anywhere" Java?

  91. May be legal, but also stupid by Mr.+Underbridge · · Score: 4, Informative
    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.

    To the letter of the law, that's true. However, there's also something called plagiarism which DOES NOT have to be a "cut-n-paste," but can be a situation in which I looked at your work and implemented my version in much the same way. That is a potentially illegal breach of copyright in software just as it is in school with papers.

    As such, the best way to protect oneself from copyright violations is complete ignorance of anything one might potentially infringe. As you say, an implementation is not copyrightable, so if you have never seen someone eles's implementation, you're clean. Basically, proving you've seen someone else's code can be damaging if you get sued for violation. You don't want that. And there's no reason to make the first critical part of their case for them.

    Of course, this is what makes copyright different than patent, as you say. Ignorance does not protect one from patent violations (although it can with regard to penalties, which can be trebled given intent, I believe). Ignorance aka "cleanroom implementation" DOES give complete immunity with regard to potential copyright violations.

    1. Re:May be legal, but also stupid by Safety+Cap · · Score: 1
      However, there's also something called plagiarism which DOES NOT have to be a "cut-n-paste," but can be a situation in which I looked at your work and implemented my version in much the same way.
      So the MS TCP/IP stack was developed totally independent of established protocols? It wasn't? Doesn't that make Windows public domain????????// WTF??!!!!!1 LOL!!!!!1111
      --
      Yeah, right.
    2. Re:May be legal, but also stupid by DavidTC · · Score: 1
      You're just completely wrong.

      Plagiarism is not a breach of copyright under any circumstances, and it's not illegal, period.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    3. Re:May be legal, but also stupid by Kilobug · · Score: 2, Insightful

      As such, the best way to protect oneself from copyright violations is complete ignorance of anything one might potentially infringe.

      So, novel writers shouldn't read work done by authors in the same field, movies makers shoudln't watch other movies, musicians shouldn't listen to music, and so on ?

      Reading what other people did in the same area (same kind of novels, movies, music, ...) is a way to increase the overall quality of intellectual work. Human imagination is limited, no one can invent everything from scratch, reading/watching/listening to several (as much as possible !) other works, taking a few ideas, adding your own, mixing all this, ... is the only way to do.

      There is no mystery why most sci-fi writers were sci-fi readers during their teens, why most musicians were music lovers and why most movies makers where movies addict. The same goes for programmers: reading other people's source code to get ideas you can use (adding your own idea in the mixture) in your programs is the only way to make better and better programs. That's why patents are so bad in the computing field: because program writing is, in some aspects, more akin to book writing than to classical engineering.

      Plagiarism is what I could call "search and replace copy and paste", like, you copy and paste and then rename all the variables... this si still copy and paste. A true rewrite of the same global ideas isn't plagiarism.

    4. Re:May be legal, but also stupid by Mr.+Underbridge · · Score: 1
      So, novel writers shouldn't read work done by authors in the same field, movies makers shoudln't watch other movies, musicians shouldn't listen to music, and so on ?

      It's a little bit different, and if you plan on releasing something damn near the same, you shouldn't. But code tends to get reused whereas books don't. I'm never going to write a book and include a chapter from someone else's. But there are times where I might need to do that in a program - I need a routine that does exactly what yours did. It's probably a good idea if I stay away from your code, then, if I'm going to do the same thing.

      A true rewrite of the same global ideas isn't plagiarism.

      Of course it's not. But part of this is avoiding ever getting sued and/or getting the case overwith quickly if you are. There are a lot of things that one would rather have to defend against - going back to my original post, being sued for copyright violations by MS is certainly one of them.

  92. Written Up? by buckhead_buddy · · Score: 1
    Dan Geer ... has just been written up by AP for his warnings about the widespread use of Microsoft products...
    When I read this sentence, I thought that the Associated Press had disciplined Dan Greer. Not that they had authored an article about Dan's diciplinary actions. The implications of censorship in an organization like the AP are huge to me. After frantically reading the article, I just find that the AP is reporting on Dan's discipline by a former employer. Big news, but not quite as big as I originally thought.

    I know that English is a screwed up language to begin with. But additionally, idioms like "push the envelope" and "developing solutions" would have different meanings to office secretaries and film processors than aircraft designers and anyone subjected to the marketing rhetoric of most computer companies.

    I actually thought the article was pretty good when I read it, but I'm just asking people to be a bit more careful when mixing idioms of different domains.

  93. monoculture, schmonoculture... by Anonymous Coward · · Score: 0

    the problem is crappy software and stupid design decisions. Read Malicious E-Cards - An Analysis of Spam in today's Slashdot articles for a quick description of how one e-mail message used no less than 5 security holes in Microsoft e-mail/web browser to take over recipients' computers.

    Microsoft is the hacker's friend; Microsoft is the spammer's friend; Microsoft is NOT the user's friend!

  94. average windows users by mattyrobinson69 · · Score: 2, Insightful

    like my dad. i forced him to stop using ie, he uses opera now. he's a typical windows user (probably wouldn't userstant outlook if i let him use it anyway).

    he's a typical windows user. he does think of security. he doesn't do anything stupid outright. he insists on running a virus scanner, although he doesn't know how or why to update it, so he never does. he runs a firewall but again, does'nt update.

    he's a typical home windows user. typical people are scared of virus's (because of the news coverage) but do not now how to protect themselves, nor know where to find information. He doesn't ever update windows because he doesn't have time / doesn't know how. he runs windows 98 because it 'just works'.

    no matter how fast microsoft patch things, if they dont release a product thats secure upon release, whats the point to home users? thats a good reason why people should use alternatives.

    1. Re:average windows users by Anonymous Coward · · Score: 1, Interesting

      When I set up a windows system for a user, I remove the links to IE and OE, replacing them with Firefox and Thunderbird. I don't tell them to use linux if they don't have the expertise to use it, I simply attempt to make their systems as secure as possible.

      Quite often they ask if I have problems like they've experienced (spyware/malware toasting their computer), and I tell them no, but then I use Linux and it's not prone to these problems. Several have asked for a linux install, so I gave them a dual boot option to test it out.

    2. Re:average windows users by boligmic · · Score: 0

      Who are you to make this decision for them? Do your job peon.

  95. thousands of OSes aren't required by cdhowe · · Score: 1
    Actually, there's research and literature that examines how big an "N" you need in N-version software diversity for survivability, and it isn't thousands; in fact, many operational high-reliability systems actually only use two versions of software (the space shuttle's computers are built this way as are some aircraft systems). So the comment of needing thousands of OSes really isn't true.

    I've been surprised at how much heat and how little light (as in research light) has been applied to this argument. Dan's diversity argument is on pretty solid ground in the research community. As an example, here are a set of papers nicely compiled by the City University of London's Center for Software Reliability on fault tolerance, and there are quite a few citations on the use of diversity in software. If you don't like the University's papers, you can find similar papers published by the ACM and IEEE, These might help readers with deciding which point of view is best supported by research. Diversity isn't a slam dunk (lots of nasty details to get right), but it's certainly well-examined ground for high-reliability systems, and a lot of folks are now looking how you apply these same principles to commercial, off-the-shelf systems.

    A final thought: the Internet itself is one of the best examples of such a diverse system. At one point, no RFC was ever approved without two independently-developed implementations of the standard. It's one of the reasons it has worked so well and evolved so well over the last 30 years or so.

  96. Mutating Software by dafz1 · · Score: 2, Insightful

    "Daniel DuVarney and R. Sekar of the State University of New York-Stony Brook are exploring 'benign mutations' that would diversify software, preserving the functional portions of code but shaking up the nonfunctional portions that are often targeted by viruses."

    If there is non-functional code that can be modified without causing problems, shouldn't that code be removed?

  97. The Monoculture Song by cabazorro · · Score: 0

    The Monoculture Song (taken from The Simpsons)

    Lyle Lanley: Well, sir, there's nothing on earth
    Like a genuine,
    Bona fide,
    Sanitized,
    One OS
    Monoculture! ...
    What'd I say?
    Ned Flanders: Monoculture!
    Lyle Lanley: What's it called?
    Patty+Selma: Monoculture!
    Lyle Lanley: That's right! Monoculture!
    [crowd chants `Monorail' softly and rhythmically]
    Miss Hoover: I hear this os is filled with patches...
    Lyle Lanley: You'll get them all in easy batches.
    Apu: Is there a chance a buffer won't end?
    Lyle Lanley: Not on your life, my Hindu friend.
    Barney: What about us brain-dead slobs?
    Lyle Lanley: You'll all be given MS Certified jobs.
    Abe: Were you sent here by the devil?
    Lyle Lanley: No, good sir, I'm on the level.
    Wiggum: The worm came off my own mailbox.
    Lyle Lanley: Take my advice, reboot the box.
    I swear it's the earth only choice...
    Throw up your hands and raise your voice!
    All: [singing] Monoculture!
    Lyle Lanley: What's it called?
    All: Monoculture!
    Lyle Lanley: Once again...
    All: Monoculture!
    Marge: But many servers are cracked and broken...
    Bart: Sorry, Mom, the mob has spoken!
    All: [singing] Monoculture!
    Monoculture!
    Monoculture!
    [big finish]
    Monoculture!
    Homer: Open Source... D'oh!

    --
    - these are not the droids you are looking for -
  98. Fired from @Stake? by nametaken · · Score: 1

    Wait, @Stake was at least in part comprised of the old L0pht Heavy Industries guys... they made their living making Microsoft look bad!

    I don't buy this guy was fired for making them look bad. :)

  99. Automating Admin Tasks by Anonymous Coward · · Score: 1, Informative

    If you're looking to automate administration tasks, might I suggest you take a look at cfengine?

    Cfengine, or the configuration engine is an autonomous agent and a middle to high level policy language for building expert systems which administrate and configure large computer networks. Cfengine uses the idea of classes and a primitive intelligence to define and automate the configuration and maintenance of system state, for small to huge configurations. Cfengine is designed to be a part of a computer immune system, and can be thought of as a gaming agent. It is ideal for cluster management and has been adopted for use all over the world in small and huge organizations alike.
    1. Re:Automating Admin Tasks by BoomerSooner · · Score: 1

      Thanks for the great link. The problem I see with using these highly configurable systems is this: when my sysadmin leaves for another job are the skills of setup on this product and administration on it more than just administering the machines directly? Plus by using a tool like that to admin are you missing possible opportunities to find better way's of making the systems operate both together and autonomously? I'm not sure.

  100. Re: serial vs USB by Anonymous Coward · · Score: 0
    dare you to config a cisco router or switch with your USB port.

    Ooh, you got me there. That's a very common and vitally important task for a desktop personal computer. As the 90's would say ... "Not"

    dare you to configure any of the middle to high end home automation equipment

    Maybe true today, probably not tomorrow.

    -F.
  101. Before Visual Basic... by rjung2k · · Score: 1

    ...there was this thing called "Hypercard." You might want to look into it, especially since it was the forefather of the WWW.

  102. Serious answer by spitzak · · Score: 1

    Here are some things that appear to be invented by Microsoft and are important. Unfortunately this list is not going to make even Microsoft happy since everything is somewhat old, easily emulated on other systems, etc, but these IMHO are the real innovations:

    1. The "taskbar", in particular the idea that a window appears in it whether or not it is "iconized" All earlier systems I have seen had the idea that a window "turned into" the icon. Thus finding an uniconized but buried window was quite difficult until they came up with this.

    2. The realization that the text in the icon (taskbar) is much more imporatant than the picture. Unfortunately the HCI dweebs probably stopped them from getting rid of the icon entirely, but at least they got it very tiny.

    3. The mouse wheel. Certainly the idea of the mouse being easily switched in/out of "scroll mode", or having another control on it for scrolling, has been around much longer, but they appear to have realized that limiting the idea to one dimension would allow a user-friendly solution with reliable mechanics.

    4. Rasterizing graphics to the individual rgb emitters in lcd displays (what they call Cleartype and apparently only used for fonts right now by them). Yes it seems obvious now, but nobody seems to have thought of it before somebody at Microsoft did.

    5. Windows 95 design that eliminated the "border line" between the window border and the contents. For instance if you drew a window containing only a gray rectangle, it merged seamlessly into the border. All earlier systems drew a divider line there. Though I know I wrote stuff like this in 1986 for the NeXT (which let you create bascally override-redirect windows), Microsoft seems to be the first commercial venture that realized you did not have to graphically seperate the edges.

    There are probably other things. These are important innovations that will affect computer design long after Microsoft is irrelevant.

    1. Re:Serious answer by Anonymous Coward · · Score: 0

      To my knowledge Risk OS 2/3 from acorn computers already had a taskbar around late 80's early 90's. However it didn't include text, pictogram only. So the next one would still fall to microsoft then. On a more interesting note, Risk OS did implement antialiasing on its desktop. ^_- I figure that must have been about the first OS with that.

      Quickshot

    2. Re:Serious answer by CatPieMan · · Score: 1

      I'm not 100% sure, but I think that back in the day, the guy from Grc.com (I think that's the right site, it won't load right now) had a utility that would re-do letters so that they were smooth on LCD panels. I think he called it something along the lines of 'font smoothing', but it has been a while.

      I don't remember (or maybe I never knew) when the feature was added to Windows (but I don't think it was there in Win2k), but, OS X has had this for a couple of years (predates winXP) and this utility from grc was definitly from Win98 era (pre win2K).

      -CPM

      --
      ---You're all I need, When the water runs deep, You're all I need, Now I cry my soul to sleep -- Collective Soul, Needs
  103. The Monoculture of *BSD by Anonymous Coward · · Score: 0, Troll

    Yet another sickening blow has struck what's left of the *BSD community, as a soon-to-be-released report by an independent commission doing a year-long study concludes: *BSD is dead and mummified. Here are some of the commission's findings:

    Fact: the *BSDs have balkanized yet again. There are now no less than twelve separate, competing *BSD projects, each of which has introduced fundamental incompatibilities with the other *BSDs, and frequently with Unix standards. Average number of developers in each project: fewer than five. Average number of users per project: there are no definitive numbers, but reports show that all projects are on the decline.

    Fact: *BSD has no support from the media. Number of Linux magazines available at bookstores: 5 (Linux Journal, Linux World, Linux Developer, Linux Format, Linux User). Number of available *BSD magazines: 0. Current count of Linux-oriented technical books: 1071. Current count of *BSD books: 6.

    Fact: XFree86 is dropping support for *BSD. The remaining core group believes that the *BSDs have strayed too far from Unix standards and have become too difficult to support along with Linux and Solaris x86. "It's too much trouble," said one anonymous developer. "If they want to make their own standards, let them doing the porting for us."

    Fact: Many user-level applications will no longer work under *BSD, and no one is working to change this. The GIMP, a Photoshop-like application, has not worked at all under *BSD since version 1.1 (sorry, too much trouble for such a small base, developers have said). OpenOffice, a Microsoft Office clone, has never worked under *BSD and never will. ("Why would we bother?" said developer Steven Andrews, an OpenOffice team lead.)

    Fact: servers running OpenBSD, which claims to focus on security, are frequently compromised. According to Jim Markham, editor of the online security forum SecurityWatch, the few OpenBSD servers that exist on the internet have become a joke among the hacker community. "They make a game out of it," he says. "(OpenBSD leader) Theo [de Raadt] will scramble to make a new patch to fix one problem, and they've already compromised a bunch of boxes with a different exploit."

    Fact: NetBSD, which claims to focus on portability (whatever that is supposed to mean), is slow, and cannot take advantage of multiple CPUs. "That about drove the last nail in the coffin for BSD use here," said Michael Curry, CTO of Amazon.com. "We took our NetBSD boxes out to the backyard and shot them in the head. We're much happier running Linux."

    Fact: There are almost no FreeBSD developers left, and its use, according to Netcraft, is down to a sadly crippled .005% of internet servers. "It's just not reliable," said Christine McGee, VP of Technology for eBay, Inc. "Nor do we find it a very modern OS. I would recommend Linux to anyone contemplating a server OS, or maybe Windows, before I would recommend a BSD."

    Fact: DragonflyBSD, yet another offshoot of the beleaguered FreeBSD "project", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing." Netcraft reports that DragonflyBSD is run on exactly 0% of internet servers.

    With these incontroverible facts staring (what's left of) the *BSD community in the face, they can only draw one conclusion: *BSD is dead and mummified.

  104. You seem to misunderstand by Mr.+Underbridge · · Score: 1
    So the MS TCP/IP stack was developed totally independent of established protocols? It wasn't? Doesn't that make Windows public domain????????// WTF??!!!!!1 LOL!!!!!1111

    That's a protocol, not an implementation. If you did things just like they did, that would be a violation. However, the TCP/IP protocol itself is not copyrightable.

    So what, you thought plagiarism was OK? LOL back at you.

  105. Re: serial vs USB by Anonymous Coward · · Score: 0

    more than likely tommorow..

    the $30,000.00 systems installed today ARE NOT going to be replaced every 2 years like computer equipment. they are designed for operation for over 20 years. embedded processors and systems designed for reliability and uptime.

    I saw the next-gen HA systems at CES and ALL OF THEM have rs232 and rs485 with ZERO having usb or firewire.

    maybe in about 30 years they wont have rs232 or 485 but by then USB will be listed as the likes of EISA and microchannel.

  106. Better example than you know. by Chris+Burke · · Score: 1

    Everyone seems to think the Irish Potato Famine happened because the Irish just loved potatoes and that's all they ate. This is incorrect (and seems silly if you thought about it). That's all they were allowed to eat, because the British took all the other crops*. The Irish had no choice but to only grow the one crop.

    Similarly, the existing software monoculture is not a result of everyone saying "Gee, I love monocultures, so let's all buy the same OS!" It's a result of people not having (or not feeling they have) a choice.

    Some day, this will be a non-issue. I'll be running Linux and Enlightenment, your corporate desktop may be FreeBSD running KDE, and your brother will have OSX/Aqua, and we won't have any problems sharing documents, files, etc. All we need to do is remove the penalty for making a choice (not having shit work). The key is to get rid of the companies that hate choice and want to make choosing different cost you. Get rid of that problem, and I feel pretty sure that people's naturally differing tastes will result in exactly the kind of healthy "ecosystem" we need.

    * Even after the famine had started, of course. The British have seriously fucked over the Irish for centuries. Braveheart, wonderful movie that it was, only scratched the surface of the abuse.

    --

    The enemies of Democracy are
  107. Microsoft won't play with the other children by Anonymous Coward · · Score: 0
    From the 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.

    My issues start with the word "thousands", I believe passing a dozen with a reasonable distribution of market share would go along way, the rest is gravy.

    As for interoperability, Nearly every OS available today can speak TCP, UDP, ICMP, IP, SMTP, POP, IMAP, HTTP, HTTPS, FTP, etc. I mean, seariously, when was the last time you though to use HyperCard? But, HTML, you use it every day. Which leads me to higher protocols. PDF, RTF, are all nearly ubiquitous. HTML is ubiquitous.

    I have a friend who used to work in the Tote business. Every year, the companies got together to go over their protocol, talk about implementations and updates. There are alot of Tote companies out there.

    So, what Charney is really saying, Microsoft does not want to have to sit down with Corel, Sun, etc. each year and talk about how they can collectively interoperate to make peoples lives not only better, but apparently safer.

    Come to think about it, Charney might be right. Sending 10 people to a 2 day conference once per year may actually be insurmountable for his company.

    My last point. I posit that most of the technological "advancements" made recently worth any bit of a damn were not made by Microsoft and exist outside their monocultural sphere of influence.

    • C
    • The web
    • Perl, Python, Ruby
    • Java
    • The idea of a windowing system
    • The internet
    • email
    • PostScript
    • Word Processing, Spreadsheets - they didn't invent the concepts, and they never made them better than the competition. I mean, has anyone out there ever used Quattro Pro, for example. Not bad for a spreadsheet.
    • I am obviously leaving out alot, this is a quick 1 minute list.
    In fact, I cannot think of one thing that came out of that company that I wouldn't be happy to say goodbye to.

    Sorry, one last thing I just realized. Isn't it always them who spread the FUD about Linux users being comunist? It sounds to me like Charney is anti-capitalist. Well, I say competition benefits the consumer, not monoculture.

  108. Thanks for the information. by Chris+Burke · · Score: 1

    That's what I was looking for, more or less. Thanks.

    You can't bring back a dead system by changing data in a field. You can't even change the data if the system is down.

    That is only true if the system which crashed and the system with the database on it are the same machine. A database client on a different machine crashing would not affect the database server at all. They could have used any non-crashed terminal to access the database and change the data.

    Then there is this statement, from your last linked article:
    "The resulting database overload caused the ship's LAN, including 27 dual 200-MHz Pentium Pro miniature remote terminal units, to crash, they said."

    It apprently took two hours to restore the network after the first time it happened. Even subsequent times: " Each time, we knew what caused the interrupt and were underway again in about 30 minutes." Thirty minutes to change a field in a database? That's suspicious. It sure seems to me like they had to go around rebooting machines before "everything [came] right back up".

    I was hoping you'd find difinitive proof (i.e. a statement of the kind "The application crashed, but the computer the application was running on was not" or some such). Instead, just more vagueness. Oh well.

    --

    The enemies of Democracy are
  109. It's called "sudo" by Merk · · Score: 1

    See, in Linux, I can be logged in all the time as a non-root, non-administrative user. If I need to do some admin type activity, I type "sudo /etc/init.d/someservice restart". Done. For that brief half-second I'm using admin privileges, but that's it. Under Windows there generally isn't a way to do that unless you are fully logged-in as an admin user. Because of this I can conveniently be a non-admin user under Linux, but under Windows it's a huge pain to be a non-admin user

  110. Re:Apple's worse by sakshale · · Score: 1
    I dare you to config a cisco router or switch with your USB port.
    I happen to use a mac powerbook usb port to connect to my Cisco switches all the time.... Of course, I had to get a USB to Serial adapter, but it works...
    --
    For every problem there is a solution that is simple, obvious and wrong.
  111. Network Diversification and the Potato Famine by sugapablo · · Score: 3, Insightful

    In an age where the world is becoming ever increasingly dependent on computers, we must take a step back and formulate a strategy to make sure history does not repeat itself in the most disaterous way. It was not too long ago that Ireland suffered its infamous "potato famine" that devistated its population that was, in its day, dependent on the crop. One of the key reasons why the famine was so intense was the fact that the Irish were repeatedly planting the same type of potato throughout the country. By doing this, and not realizing that nature provided diversification in the form of hundreds of varieties of potatos to make sure that one set of circumstances could never decimate the potato population, the Irish learned a very valuable, if not painful, lesson indeed. In the land of computers, this form of "biodiversity" only makes sense. If 90% of all nodes on the network are of one kind of "potato" (namely Microsoft) than it's very easy for one plague (or virus) to have incredibly devestating results. We have already seen the damage caused by recent Windows viruses. Each of these have been relatively small and harmless annoyances compared to what a committed and intelligent person could create should such a someone be so inclined and motivated. However, if the world's computers were not so heavily tilted towards a single OS, such attacks wouldn't stand nearly as much of a chance in succeeding to harm a large section of the world's network population. In conclusion, not only do operating systems such as Mac and Linux (as well as Solaris, Unix, etc) represent an excellent freedom of choice for consumers, they represent an enlightened strategy to prevent a cataclysmic disaster to our networks that we've come so dependent on.

  112. Why not keeep a separate stack for return... by GrahamCox · · Score: 1

    ...addresses. Wouldn't that fix most of the stack-based overflow breaches?

    1. Re:Why not keeep a separate stack for return... by steve_l · · Score: 1

      Yes, doesnt Forth do something like this?

      AMD Opteron has the ability to mark regions of memory as no-execute, so only the code pages of your app can be executed; the buffers dont work. WinXP SP2 promises to support this, on both computers out there running 64-bit windows on AMD kit.

  113. Re:Apple's worse by gnu-generation-one · · Score: 1

    "No one else had the balls to say "screw dumb serial ports, USB is better"."

    No one else ever had to interface custom hardware to their computer I guess...

  114. Monoculture is only part of the problem by Anonymous Coward · · Score: 0

    The members of a monoculture do share the same weaknesses. However, the survivability of a monoculture of marshmallows is different than a monoculture of bricks.

  115. Get the Wallpaper While It's Hot! by Anonymous Coward · · Score: 0


    http://www.kde-look.org/content/show.php?content =10782&PHPSESSID=2cbe9cea2118f6a4cec89320f8fea 94f

  116. Confusion of cases by ewe2 · · Score: 2

    While the idea of a monoculture has appeal, the common arguments for it assume a lack of diversity, which doesn't help in this case. Because it isn't lack of diversity that's the problem. MS is just too big and easy a target to ignore.

    Apple has a greater installed base than Linux. Yet there are no exploits or viruses against Apple OS's to my knowledge, although OS X must open the door a little wider these days.

    Programs used under Linux have their own security concerns, naturally. But these programs are used by many other OS's which have their own kinds of vulnerability. You can boil most security concerns with the Linux kernel down to one goal: privileged access. Remember, buffer exploits happen everywhere.

    What really makes Microsoft a big target is the scope for attack: privileged access is the easy part. Network attacks are simple, destruction and/or theft of data a matter of social engineering. The latest MS worms are capable of all these attacks, impossible on other OS's. THAT is why it's the premier target. The flow-on effects of the different kinds of attack simply don't exist elsewhere.

    --
    insecurity asks the wrong question irritation gives the wrong answer
  117. Resilience through diversity by FlyingOrca · · Score: 1

    Resilience through diversity, not absolute immunity.

    Absolutely. And not so incidentally, the classic argument in favour of biodiversity!

    --
    Corruptissima re publica plurimae leges.
  118. DirectX by Anonymous Coward · · Score: 0

    DirectX

  119. Progress by Anonymous Coward · · Score: 0

    Without a Microsoft monoculture, he said, most of the recent progress in information technology could not have happened.

    He is so right. How can you argue this point? The facts support this. Without Microsoft stealing other companies technologies, these companies won't have to innovate new things to stay ahead. Those who can't innovate beyond their one hit wonder, they die (e.g. Netscape). Think Microsoft as a natural disaster, those who can't adapt extinct. So, thank you Microsoft, for screwing us for our own good.

  120. Not a virus, but yeah by Anonymous Coward · · Score: 0

    Phytophthora infestans
    "Although the pathogen is often called a fungus, it's more closely related to kelp and other brown algae"
    http://66.102.7.104/search?q=cache:T_anVNs ff_8J:wh yfiles.org/128potato_blight/+potato-blight+Ireland +pathogen&hl=en&lr=lang_en&ie=UTF-8

    gewg_

  121. Monocultures can be beneficial by 0x0d0a · · Score: 2, Interesting

    The rationale behind avoiding monoculture is that not all members have the same weaknesses, so an attack will not destroy the entire population. While this is a valid point for biological populations, there are some issues with it as apply to computer security. We are not dealing with "members" getting "killed" -- we are dealing with "computers" being "compromised".

    The first issue is that many elements of the whole in some computer systems have the same degree of access. Perhaps half of the workstations at a company run Linux and half Windows. If all of them have roughly the same tasks (as opposed to devoting Windows to web browsing and Linux to email reading), then a compromise of *any* of them allows a compromise of all the important data. Many security systems are weakest-link -- if one element can be compromised, the whole system falls. In this case, all having a polyculture does is expose more weaknesses, reducing the security of the system as a whole.

    The second element is somewhat similar -- most computer networks have some degree of trust relationship between members. It may be something explicit, like having IP-based rsh auth (though that's a bit of an old problem) or allowing access to various intranet Web pages to any internal computers. It may be just allowing a compromised computer to sniff a network that other computers pass traffic over. In this case, a compromise of one member of the network provides an attack vector against the other members of the network. Again, a polyculture exposes more weaknesses, weakening the security of the system as a whole.

    Third, there are security management issues. Most medium or large computer networks have someone or some group with some degree of responsibliity for computer security. That group usually has finite resources and budget. Much of their effort can generally be replicated across similar members -- for example, securing a plaintext authentication in Windows means a fix that just has to be replicated across all members in the network. If their time and money must be spread across multiple types of members, they are less able to spend resources on any one group, and each type of member may be less well managed.

    Fourth, most networks do not follow a "Russian doll" approach, where a potential cracker must compromise first one computer, then another computer, then another computer to get in to the network proper from the outside. In such a scenerio, making each of the dolls different does improve security, since a cracker must compromise all, rather than just one, system. It's pretty common to just have a NATted network with all hosts inside at roughly the same level of internal access, however.

    Overall, I *do* think that it's a good idea to move away from "Microsoft only" on computer networks. Competition tends to improve products, and Microsoft has a poor security track record (and doesn't focus on security very well). However, if an CIO has the sole goal of improving security, and has the choice of rolling out Linux or rolling out Kerberos on existing Windows boxes, I'd have to say that rolling out Kerberos is probably going to do more for security.

  122. Windows source by ElliotLee · · Score: 1

    Now that the Windows source code is released, when can we expect the first Windows distro?

  123. Logic by rofthorax · · Score: 1

    Windows is not nearly as complex as organisms.. The theory behind the survival of organisms is unproven, just as evolution is unproven.. This has been a theory put forth to those fighting harmful bacteria/viruses that if you give people are the drugs quickly it will kill off everything, but if not applied well enough the resistent strains will survive and grow, and will be drug resistent.. However this relies on evolution of species, that the drug resistent strain is strong enough to overcome other organisms that would eat up or break apart the virus.. Anyhow, computer viruses are fairly simple, they are interpretted as instructions when given right to execution.. The primary problem with Windows is not that its random/unpredictable enough to thwart attacks, but that its overly complex, and is made so every year, through the purpose of making money, whereas Linux is relatively simple and can be protected from attacks.. Making an operating system more complex is about the same as security through obscurity, its more of a burden than a solution.. The solution for windows is to reduce the crap between the hardware and teh applications.. Microsoft money maker has always been controlling access to resources, not from hackers but from low-paying vendors, the more money you can shell out for a compiler, the closer you get to the resources and the better your applications can be made.. Its like selling seats to a Football game, those wiht the more insider information into Microsoft and those willing to pay for that information, get closer to the hardware.. And when that new version of winodws comes out that obscures the language and interface design (actually a marketing idea more than for virus reduction), the layers increase, people pay more to understand the obscurity, while holes develop in the architecture, due to complexity.. As you increase the complexity of software, you increase the vulnerability, its proven!! Linux is also not immune to this, if open source developments fail to refactor the sources, they will become more complex, and less dependable, more crackable, hackable.. The best thing to do is embrace good abstraction and ways to reduce points of failure. With the linux, this is to increase eyes... WIth Microsoft its to advertise a lot, brainwash customers with positive reassurance (eg. "no nothing is wrong, everything is okay"), while at the same time making those with something to argue look like fools.. Its like something out of a Ayn Rand book, somewhere between communism and capitalism, respect the social order, but do what you want until you can't get away with it, then give to charity or put forth a positive message such that people will instill more trust, then do what you want until you can't get away with it.. So on..

    --
    Just say no to license servers!!
  124. Re:WRONG! stop the lies (was Re:Interesting spin . by ab762 · · Score: 1

    I know he didn't. Really. I promise not to do it again.

  125. Re:WRONG! stop the lies (was Re:Interesting spin . by spoonyfork · · Score: 1

    Al Gore did not say he invented the Internet. Mussolini did not make the trains run on time.

    Godwin's Law, I WIN! Wait, does Mussolini count? ;)

    --
    Speak truth to power.