Slashdot Mirror


WinInformant Says Windows More Secure Than Linux

nihilist_1137 excerpts from this WinInformant article, which reads in part: "For at least the first 8 months of 2001, open-source poster child Linux was far less secure than Windows, according to the reputable NTBugTraq, which is hosted by SecurityFocus, the leading provider of security information about the Internet. ... A look at the previous 5 years--for which the data is more complete--also shows that each year, Win2K and Windows NT had far fewer security vulnerabilities than Linux, despite the fact that Windows is deployed on a far wider basis than any version of Linux." I wonder how many sysadmins (Windows or Linux) would agree with this conclusion. Update: 02/04 16:54 GMT by T : Looks like the WinInfo site has gone down since the story was submitted, so you may have to content yourself in the meantime with the Bugtraq numbers. Update: 02/04 19:30 GMT by T :Several readers have pointed out that the conclusions WinInformant makes based on the Bugtraq data are not those of SecurityFocus; the headline has been changed accordingly.

876 comments

  1. response to article... by Lumpy · · Score: 0, Offtopic

    Hell I have karma to burn....

    Nt more secure?

    HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA...

    Ohhh, wow.... Didnt know it was April 1st already...

    --
    Do not look at laser with remaining good eye.
    1. Re:response to article... by Anonymous Coward · · Score: 0

      Flamebait, maybe, but not offtopic in any way.

  2. This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 1, Insightful

    The Slashdot crowd will never stand for this. I expect to see hypocrisy in full swing in about 30 seconds, with the zealots proclaiming bias. Never mind that they've consistently relied on SF for past predictions of MS's ineptitudes.

    1. Re:This, of course, will be ignored and ridiculed by KeyserDK · · Score: 4, Insightful

      So true =).

      Open source haven't proven more secure than closed, as the theory about "given enough eyes all bugs are shallow" says.

      The one thing it gives though, is choice. For instance, i dont run rsync(se recent security exploit) and i'll probably never do. Neither will mdk/rh pr. default (Allthough a lot is certainly run by default). Even though rsync comes with mdk/rh.

      Frej Rasmussen.

      --
      still reading?
    2. Re:This, of course, will be ignored and ridiculed by jandrese · · Score: 0

      Or maybe the Slashdot regulars (not the people who hang out at 0 and -1) will look at the piece calmly and discover other very valid flaws with the study. If they don't it will likely lead to an active discussion on bug fixing and exploits. This will happen mostly in the 3+ moderated posts.

      I shouldn't even have to moderate you, but it seems like sometimes anybody who critisizes Slashdot (however unfounded it may be) gets automatic mod points these days. Sad.

      --

      I read the internet for the articles.
    3. Re:This, of course, will be ignored and ridiculed by drewbradford · · Score: 2, Interesting

      Did this study look at just standard Linux distro? Like standard installs of RH, or did it look at hardened versions designed to be secure? It seems to me that there are certainly extremely secure hardened versions of Linux, while Windows is generally limited to relatively standard installations.

    4. Re:This, of course, will be ignored and ridiculed by sehryan · · Score: 1

      sort of like how anyone who praises linux over microsoft gets mod points. gets pretty annoying, doesn't it?

      --
      The world moves for love. It kneels before it in awe.
    5. Re:This, of course, will be ignored and ridiculed by jazman_777 · · Score: 2, Insightful
      Open source haven't proven more secure than closed, as the theory about "given enough eyes all bugs are shallow" says.


      It's a great-sounding theory. It _could_ be true in reality, if everyone were perusing source code, but who really does? Now, some folks _have_ looked at the code for OpenBSD, so it's what I run at home.

      OTOH, open source is amenable to extremely quick fixes for exploits. Once a weakness is known, the eyeballs look at the code, and it gets fixed quickly. I hope. In other words, I don't really know, but it sounds like it's true, so why not promulgate another fine-sounding theory, heh heh.

      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
    6. Re:This, of course, will be ignored and ridiculed by morcego · · Score: 4, Insightful

      Not only that.
      This kind of study don't see what is Linux, and what is agregated software. They say Linux and Windows, but I'm sure they don't include IIS.
      In any case, impact and severity must also be taken into account. Most Windows bugs are remotely exploitable, and give full control of the machine. Most linux bugs are only localy exploitable, or only leak information.
      It's very easy to say that car acidents happen more often then plain crashes. Anyone cares to count the casualities ? Well, I'm not sure this is a good example, once car acidents casuality numbers are, AFAIK, higher, but I think you get what I mean.

      --
      morcego
    7. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 2, Interesting

      ... and it should be ridiculed. The article compares Windows +bundled services with Linux +all possible services. Add in the security holes by all Windows ISVs, and the number will be astronomical. You can't compare Linux +8 MTAs and 5 HTTP servers with 12 embedded scripting languages with NT+IIS+ASP. Add holes for Cold Fusion and all the other "Server" role exploits under Windows and you'd have a far more valid comparison.

    8. Re:This, of course, will be ignored and ridiculed by ryanr · · Score: 5, Informative

      Sigh...

      I can't read the original article, It's been Slashdotted to death. But I think I can make a pretty good guess as to what happened.

      First off, we host Bugtraq, not NTBugtraq, which is Russ Cooper's list. (Any chance we can get that fixed in the story intro? Anyone know if the same mistake is in the original article?)

      Secondly, I'm constantly amazed at how people mis-read our stats page. The Linux aggregate stats are the total of all unique bugs across all the various distributions we track. It's supposed to answer the question "How many Linux-related bugs were there that year." It's based on things like which distro ships a particular package, and when that package is found to have a hole, it also gets attached to the distro. This is so you can look up your distro, and see what bugs you might need to patch.

      Take a look at the top of the page, our script hasn't been running since August, when we switched from Roxen to Apache. So, we're missing the whole last quarter of 2001 stats.

      Regardless of anything else, using these number to declare that one thing is more secure than another is a mistake. Based on our numbers, why didn't they declare that everyone should run MacOS for security? Or that if you want to be more secure, run Debian instead of Win2K?

    9. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0


      I fully believe those numbers. What they fail to mention however, is were those vulnerabilities known in advance and how long did it take for a patch to appear. I am sure M$ issues a patch within hours of finding a bug...or wait no, they conceal it and obfuscate it....that's right it's the OSS crowd that does the OTHER thing (release a patch QUICKLY).

      Code Red worked on nearly the same vulnerability as Christmas Tree Exec virus (read ANCIENT history) I am far from impressed.

    10. Re:This, of course, will be ignored and ridiculed by Malc · · Score: 2, Interesting

      If you're going to look at hardened Linux installs, why not look at a hardened Windows install too? You know: one that has been locked properly to meet its C2 certification, e.g. via the resource kit tool c2config.exe or from this page. As it stands, the most common distros of Linux do not install with good security, and that is why things like Bastille Linux exists.

    11. Re:This, of course, will be ignored and ridiculed by gladbach · · Score: 0, Offtopic

      mod parent up plz

      --
      "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms,
    12. Re:This, of course, will be ignored and ridiculed by Mr+Teddy+Bear · · Score: 0, Redundant

      It's very easy to say that car acidents happen more often then plain crashes. Anyone cares to count the casualities ? Well, I'm not sure this is a good example, once car acidents casuality numbers are, AFAIK, higher, but I think you get what I mean.

      I agree totally, but a better way to look at that same analogy is to think of the amount of people who fly and get killed compared to the amount of people who drive and get killed. Obviously with the 100's of millions of drivers (in the US alone) the percentage of people killed is far greater in plane crashes.

      Bad thing is though, this seems to have the opposite effect on MS vs Linux. MS is deployed on way too many systems (my way of saying they control the market) And they still have the most security breeches per capita. One could argue that the hackers aren't the ones with Windows, and hackers hate Windows and love Linux which is why they never hack Linux systems... And while this is true to an extent this doesn't explain everything. The truest power of Linux over Windows is that Linux patches its stuff very quickly. Also GOOD Linux admins will actually get the patches and put them on. (After evaluating them to make sure they are effected by the security breech and making sure they won't effect anything else in production etc etc etc) I know the service packs for NT were very badly conceived. (Anyone remember SP6... then a week later SP6a?)

      To bring these ramblings to a close... Things tend to be quite different in a real world situation than they are in a controled lab. And enough money can control a lab to make sure it brings out the results wanted.

      Damnit, I want modded up on this. :-P

    13. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      I think it is important to note that 99% of "linux vulnerabilities" are not linux vulnerabilities, but actually non-essential, third party programs. These programs have nothing to do with linux, but do run on the OS. DNS, sendmail, rsync etc are not a part of the OS but have vulnerabilites. We should say that any os that these utilities/services run on has the vulnerability.

      If we include these as *linux vulnerabilities* we should do the same for NT. Include AIM, kazaa (fasttrack), icq and every other insecure program that NT will run in the list as an *nt vulnerability*.

      I do not think that insecure programs running on an OS, written by a third party, should contribute to the vulnerabilites list for a given OS.

      EG. Aim running on NT has a vulnerability. Does this vulnerability make NT less secure? Only if you run the program. The OS is not inherently more insecure because AIM is insecure. If you don't use AIM NT doesn't have the AIM vulnerability....

      Read your statistics wisely.

      l8,
      neilio
      "There are lies, there are damn lies, then there are statistics".

      Mark Twain

    14. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      Did this study look at just standard Linux distro? Like standard installs of RH, or did it look at hardened versions designed to be secure? It seems to me that there are certainly extremely secure hardened versions of Linux, while Windows is generally limited to relatively standard installations.

      Microsoft just said they were sponsoring an 'independent' security assesment.

      I am sure that MS boxes were viewed as being set up by MCSEs with other certs and Linux boxes were probably set up by windows users.

    15. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      Of course the patch that would prevent infection by Code Red was available months before Code Red was written, so perhaps you should find a different example.

    16. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      The study has flaws? Of course it does. Most studies do if you look hard enough. The point is, most on /. will immediately believe anything anti-MS that is said and will not bother checking any facts or doing any thinking beyond that. But on a pro-MS post, they'll go all out of their way to scream bias, poor reporting, flawed studies, or just resort to namecalling. THAT'S sad.

      I disagree with the author lumping all distro bugs into a single figure, but the point was not to say "My OS is better than your OS", it was to present numbers. They never tried to say anything more than that, but whoever posted the header to this article damn sure wants it interpreted as such. THAT'S sad as well.

      And don't forget this: many, many Fortune 500 companies are using Win2k/NT in mission-critical areas, and they aren't failing left and right. They don't fail because competent admins keep them from failing, the same way competent Unix folk do. The problem with Windows is that it's so easy to use nearly anyone can claim to be an administrator. Security faults follow, and then everybody blames MS.

    17. Re:This, of course, will be ignored and ridiculed by jgerman · · Score: 3, Insightful

      I'm not sure I agree. How can you contrast a "security through obscurity" system like Windows to an open one like Linux. It's natural that more bugs are found and reported in Linux, but that says nothing about the number of existing bugs. In addition, having the bug known isn't always the sole indicator either, how long does the bug exists once it is known about . I'd like to see some sort of measurement based on "bug-hours" that measures not only the number of bugs but the summation of the time the bugs were exploitable.

      --
      I'm the big fish in the big pond bitch.
    18. Re:This, of course, will be ignored and ridiculed by Enahs · · Score: 3, Interesting
      Secondly, I'm constantly amazed at how people mis-read our stats page. The Linux aggregate stats are the total of all unique bugs across all the various distributions we track. It's supposed to answer the question "How many Linux-related bugs were there that year."



      I'm still a little unclear on what you mean by "unique bugs." So if there's a glibc vulnerability in all distributions, it gets counted only once in the aggregate?



      If so, I'll consider the numbers a little less suspect.



      Thanks in advance.

      --
      Stating on Slashdot that I like cheese since 1997.
    19. Re:This, of course, will be ignored and ridiculed by bribecka · · Score: 2

      I think it is important to note that 99% of "linux vulnerabilities" are not linux vulnerabilities, but actually non-essential, third party programs. These programs have nothing to do with linux, but do run on the OS. DNS, sendmail, rsync etc are not a part of the OS but have vulnerabilites. We should say that any os that these utilities/services run on has the vulnerability.

      However, if a program is included in a distribution, it *should* be included in those numbers. Comparing a "third party" program like DNS to AIM or ICQ is highly irresponsible, as neither of those come on your friendly WinOS CD.

      --

      Where are we going and why am I in this handbasket?

    20. Re:This, of course, will be ignored and ridiculed by trg83 · · Score: 1

      Just because Linux distributions come with extra software for free--usually identified by being placed clearly in a "packages" or similar folder on the CD(s) does not mean that those packages ARE Linux. Also, despite all the bullshit, Linux is not GNU either. Linux is a kernel...

    21. Re:This, of course, will be ignored and ridiculed by berzerke · · Score: 3, Interesting

      while Windows is generally limited to relatively standard installations



      I once got my hands on the oem installation kit and read through the licensing and instructions. Although I didn't understand everything, one thing I did understand is the OEMs, with a few very minor exceptions, must do a default install. They are prohibited, for instance, from removing or disabling IIS. I bet that'll make a big difference in the exploitablity of any bug and hence security.

    22. Re:This, of course, will be ignored and ridiculed by Mr+Z · · Score: 5, Informative
      Or maybe the Slashdot regulars (not the people who hang out at 0 and -1) will look at the piece calmly and discover other very valid flaws with the study.

      You mean, like this? The NTBugTraq site itself says (emphasis mine):

      There is a distinct difference in the way that vulnerabilities are counted for Microsoft Windows and other operating systems. For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers.

      So, while there may be a stack of Outlook vulnerabilities, those won't get lumped in with Windows. But sendmail vulnerabilities might get lumped in with RedHat. They go on to say (emphasis theirs):

      The numbers presented below should not be considered a metric by which an accurate comparison of the vulnerability of one operating system versus another can be made.

      Further, the numbers themselves do not support the conjecture that Windows 2000/NT had fewer reported vulnerabilities reported over the 5-year period. Let's compare RedHat (the Linux distro for which the largest number of vulnerabilities was reported) vs. Windows 2000/NT from their data:

      • 1997: RedHat 6, Win2K/NT 10
      • 1998: RedHat 10, Win2K/NT 8
      • 1999: RedHat 47, Win2K/NT 78
      • 2000: RedHat 95, Win2K/NT 97
      • 2001: RedHat 54, Win2K/NT 42
      • Total RedHat 212, Win2K/NT 235

      So even though the numbers are potentially skewed against Linux, the totals still come up less for RedHat than for Win2000/NT.

      What the other article must be doing (I haven't read it yet, since I wasn't able load it) is totalling across all distributions, which is wrong. One FTPD vulnerability would get multiplied by all the vendors that ship that FTPD, which isn't quite fair.

      --Joe
    23. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      I agree totally, but a better way to look at that same analogy is to think of the amount of people who fly and get killed compared to the amount of people who drive and get killed. Obviously with the 100's of millions of drivers (in the US alone) the percentage of people killed is far greater in plane crashes.

      To a certain extent it does depend on how you determine "safety", but by the measure of deaths per passenger mile you are 10-50 times safer (depending on the year) traveling by plane than car.

      While it may seem obvious to you that lots of people die in plane crashes and relativly few die in automobile accidents. You should keep in mind that car accidents are the number one cause of death for people under 35.

    24. Re:This, of course, will be ignored and ridiculed by ScumBiker · · Score: 3, Interesting

      In order to meet C2, the NT box can't be connected to a network, a serial connection, or a modem. Well, you can, but you can't allow anybody access to it, same thing. What the hell good is it? I remember this from when an employer bribed me to go to a NT class by letting me keep the FreeBSD 1.7 box as the webserver/dns. Heh. I'm not sure about Win2k and C2, though.

      --
      --- Think of it as evolution in action ---
    25. Re:This, of course, will be ignored and ridiculed by ryanr · · Score: 3, Informative

      Looks like the Linux aggregate has just been pulled from our site, probably since that has been the source of a lot of confusion in the past. But, to answer your question: Yes, the Linux aggregate is done in such a way as to keep the same bug from being counter once per distro.

      If I recall from earlier today, the aggregate number was around 90. If you take all of the Linux distros on the page, and just add the numbers, you get 178.

    26. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      I think that just about everyone agrees that there are some major issues with the article. It's been said in other comments, but I'm going to try to summarize:

      1) Counting the sum of bugs in all distros as the number of "Linux bugs" is just silly. If you have a bug in pico, every distributor releases their own bug fix, which multiplies the number of Linux bugs by 5x or more. The article should have taken the number of bugs in a single distro.

      2) "Bugs in Windows (the OS only)" and "bugs in a Linux *distribution*" are quite different creatures. A Windows install CD comes with *far* less software than a Linux distro CD, which has typesetting software, high-powered text editors, graphics programs, sound editing programs...if you want to compare a complete Windows *system* to a complete Linux *system*, the comparison involved is quite different. If you install Visual Slickedit, Photoshop, Cakewalk, and all the other equivalents of a normal Linux distro on a Windows system, *then* you're talking a more reasonable comparison. If you count bugs in one, it's only fair to count bugs in the other.

      3) Some Linux bugs are found through review of open source code. Perhaps someone's using strcmp() instead of strncmp(). They may *potentially* be a security issue, but not have ever been exploited, or even be actually exploitable. Since Windows is closed-source, the way almost every single bug is found is through actually breaking things -- and so if a Windows bug is reported, it's generally something that has a real-world effect and that people are running into.

      4) The overwhelming majority of security issues that are reported on Linux are local exploits. You generally don't hear about Windows local exploits, since the operating system is pretty much unusable as a multiple-user remote-access OS. Since you can just disable allowing other users to use your Linux box and allowing them to do so remotely, this is nothing more than bugs in functionality that Windows lacks. Furthermore, Windows local security really doesn't exist. I haven't checked out 2k or XP, but at least in the days of NT 4.0 (billed by MS as secure), it was pretty much acknowledged that Windows had no local security. There were huge numbers of security issues with the registry where permissions to screw with or read stuff that shouldn't be messed with existed. These were never repaired, and were out of box issues. Plus, Windows had its share of simply exploit programs-- local exploits that simply immediately gave Administrator access, there was code to catch Ctl-Alt-Del (at that point, I figured that things were pretty much hopeless)...if you had a Windows box, you didn't really even attempt local security. You just secured things remotely and tighted up local stuff enough to keep newbies from screwing stuff up.

      5) Lots of stuff on Windows runs with access to everything. An exploit in IIS, and it's all over. Exploit an unprivileged, chrooted apache...and you aren't much closer to controlling the system. So even a remote exploit on a Linux system is generally much less severe than a remote exploit on a Windows box (assuming each is being administered by a skilled sysadmin...which hopefully big sites have). The bug counts on the systems don't reflect that.

    27. Re:This, of course, will be ignored and ridiculed by TMKroeger · · Score: 1

      > What the other article must be doing (I haven't
      > read it yet, since I wasn't able load it) is
      > totalling across all distributions, which is
      > wrong. One FTPD vulnerability would get
      > multiplied by all the vendors that ship that
      > FTPD, which isn't quite fair.

      But it is another advantage to having a monopoly... =)

    28. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0


      Based on our numbers, why didn't they declare that everyone should run MacOS for security?

      ahem, that actually a good question. i don't know if I'd choose Mac over Linux, but I certainly would over M$.

      OS X/Darwin is becoming known these days as quite a skintight OS...heck, even OS 9 would be better than an NT/IIS config, imo. correct me if i'm wrong, but a box running OS 9/MacHTTP has very little in the way of security issues.

    29. Re:This, of course, will be ignored and ridiculed by rpbird · · Score: 1

      I don't understand the usefulness of your data. If it can't used to conclude anything about anything, if it's flawed, and you know it's flawed, why put it up in the first place?

    30. Re:This, of course, will be ignored and ridiculed by RMSIsAnIdiot · · Score: 3, Informative
      Ugh. Why am I replying to this. You are obbious a Pro-Linux kiddie. I will now go on to explain why your thinking is flawed.

      I think it is important to note that 99% of "linux vulnerabilities" are not linux vulnerabilities, but actually non-essential, third party programs. These programs have nothing to do with linux, but do run on the OS. DNS, sendmail, rsync etc are not a part of the OS but have vulnerabilites. We should say that any os that these utilities/services run on has the vulnerability.

      So, by that theory, we shouldn't include any IIS vulnerabilities in the NT exploits either. Because, of course, "IIS has nothing to do with NT, but it runs on the OS." After all, it's an optional component.

      Bullshit.

      Why are you not including BIND and sendmail? Hello? Most Linux servers are either web, DNS, or mail servers... NT, Novell, and Sun far outnumber them as file servers. So, if we can't include BIND, nor sendmail, then we can't include IIS or Exchange/Outlook. Cause, after all, they are "nonessential third-party programs." Oh wait, heh, they were written by "M$" (using obligatory dollar sign so the author of the parent post can understand who I'm talking about) so I guess they're not thrid-party. But then again, it's not Linux either, it's GNU/Linux. So I guess we can only count kernel exploits. Hmmm. Maybe that means we can only count NT kernel exploits (go ahead, count them.)

      I dare you to root an NT file/print server that isn't running any other services. You can't (or at least, not on any easier level than you could root a Linux or Sun box... heh Sun and their automountd... heheheheh). Anyway, I hope you understand where I'm coming from. Your thinking is flawed.

      But then again, what should I expect? This is Slashdot. It's kind of like going to the Democratic convention and shouting "Gore sucks! Dubya forever!" I didn't really expect too many pro-Microsoft replies here.

      --

    31. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      So even though the numbers are potentially skewed against Linux, the totals still come up less for RedHat than for Win2000/NT.

      The way I read those number is that they both suck, and there's virtually no TCO difference due to security issues between the two OSes.

    32. Re:This, of course, will be ignored and ridiculed by Zeinfeld · · Score: 3, Informative
      In order to meet C2, the NT box can't be connected to a network, a serial connection, or a modem. Well, you can, but you can't allow anybody access to it, same thing.

      That is a consequence of the C2 standard which was written by the military for the US govt in the days before networking.

      C2 was obsolete before the Web existed. Back in 1993 when I was asked to do a security audit of the Web standards against the Orange book I concluded that the standard was no help at all.

      The other reason that C2 is not very useful is that the main concern in Orange book is partitioning multiple users data on the same machine. These days each user has their own machine, a one person computer that does not meet C2 mandatory access control requirements can be perfectly secure - look at a Palm or Pocket PC or a smartcard.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    33. Re:This, of course, will be ignored and ridiculed by tqbf · · Score: 3
      You mean, like this? The NTBugTraq site itself says (emphasis mine):

      There is a distinct difference in the way that vulnerabilities are counted for Microsoft

      This context was just added to the SecurityFocus page. It rules that they added the disclaimer, but don't pretend like it was there before and WinFormant simply ignored it.

    34. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      True, true. Mod that shit UP bitches!!!
      Hehe.

    35. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      Yes, but this is OEM products. Unless an organization wants their systems to be solely managed by an outside source, you can bet they're going to have people to either

      a. (re)Install Windows NT/2K/XP server to meet their needs
      b. Configure the system straight out of the box to meet their needs.

      I recently purchased a new laptop with Windows 2000 OEMed on it. While IIS was installed, it wasn't enabled by default.

      The moment the exploits become critical is when they disrupt businesses, which in turn disrupt the customers (you and I). Therefore, the people managing the systems at this stage should be of adequate training, just as if they were running Linux boxen. Don't forget this -- as a manager, you're not going to hire somebody off the street to administer mission-critical systems who has no qualifications to do so, for whatever platform.

      And for the parent, there are many, many individuals with the know-how to lock down a Windows machine; even using the built-in firewall. Security Policies have been around since at least Windows 2000, which includes built in packet filtering nearly as robust as ipchains/tables. (Administrative Tools/ Local Security Settings).

      Windows != Insecure. Both Windows and any other type of operating system machine are equally dangerous in the hands of the clueless. Just as I'd expect any of my Unix admins to go out and download, recompile and install new packages for ones that exploits have been found in, I expect at least the same level for my Windows admins.

    36. Re:This, of course, will be ignored and ridiculed by Zeinfeld · · Score: 2
      Secondly, I'm constantly amazed at how people mis-read our stats page. ... Regardless of anything else, using these number to declare that one thing is more secure than another is a mistake. Based on our numbers, why didn't they declare that everyone should run MacOS for security?

      I think the problem is that people were misreading the numbers both ways. The use of the raw Bugtraq numbers against Windows was always a canard, the use of the raw figures in the reverse direction is a canard.

      The article's argument is sufficient to demonstrate that the 'Linux is more secure' argument is false, but insufficient to prove 'Windows is more secure'. As you point out few bugs are found on the MacOs, that is not surprising since these days they hold MacWorld in a telephone booth and in any case just how many security holes did Edison have in his desk lamp?

      The problem is that security really is complex, it certainly is not a linear issue and it is completely determined by your operating environment. An O/S configuration to secure server will almost certainly prevent a user getting useful work done.

      As a security professional who is pretty well known in the field, I can tell you that both the Linux is more secure and Windows more secure religious arguments are wrong.

      Windows cannot currently compete in the real high end security configuration where we strip down the O/S to run only the services that are absolutely essential. However Microsoft make no secret of the fact they are working on a platform of that type. If I could find a way to audit that work I would rather buy a secure kernel in than have to spend seven figure sums doing the strip down in house.

      The multiple eyes argument in favor of Open software only works up to a point. The problem is that you rely on the defenders being more vigilant than the attackers, that is not always the case. Although these days the trend in hacking has been to go for the binaries rather than muck arround with source code.

      The biggest problem with Windows is the predeliction for supporting active code in email messages. But Microsoft is not the only company that does not understand the importance of code/data separation. Sun and Netscape have both been guilty of equally eggregious abominations.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    37. Re:This, of course, will be ignored and ridiculed by ryanr · · Score: 2

      Where did we claim it was useful? Why does data have to have an obvious conclusion in order to be useful?

      The reason we put it up is because we were constantly getting mail from students and others who wanted to do studies on the number of vulnerabilities in one OS vs. another. So, we made the data available. We really can't help it if people accidentally or intentionally draw some sort of strange conclusion from it. We've added some text that will hopefully make someone think twice about drawing the most obviously-wrong conclusions.

    38. Re:This, of course, will be ignored and ridiculed by spitzak · · Score: 2
      Even per trip the casualty rate for cars is higher than for airplanes. Another way to put it is that you are more likely to be killed driving to the airport than flying across the country.

      In the US I think something like 50,000 people are killed a year in car accidents. This is equivalent to a fully-loaded 747 crashing every other day.

    39. Re:This, of course, will be ignored and ridiculed by starseeker · · Score: 2

      "For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count."

      And yet, Microsoft claims that it can't remove IE from Windows without destroying the operating system. The irony, the irony...

      --
      "I object to doing things that computers can do." -- Olin Shivers, lispers.org
    40. Re:This, of course, will be ignored and ridiculed by Mr+Teddy+Bear · · Score: 1

      To a certain extent it does depend on how you determine "safety", but by the measure of deaths per passenger mile you are 10-50 times safer (depending on the year) traveling by plane than car.

      Deaths per passenger mile... still not the stats i was referring to. At the risk of being TOTALLY offtopic.......

      If you take passenger miles..... why do most people fly? Because it is too far to drive. So you add a bunch of miles for one person. Then it is still taking into account every single driver and every single plane and not scaling them so the numbers could start the same. Not accurate stats. Those are the kind of stats to lie to you. So those stats are out the window.

      Basically stats will never tell the true story unless you find a common denominator. This is just like saying a city with 1,000,000 people that has had 10 homocides is more dangerous than a city of 10,000 having 5. I mean.. your chances of survival are not as good living in the smaller town.

      Just my $0.03.

    41. Re:This, of course, will be ignored and ridiculed by dannannan · · Score: 1

      I disgree with your interpretation of the data there. Scores do not add up; each service pack of NT is a different product, as is each build of RedHat. Summing up all the vulnerabilities found in the various RedHat builds over the past 5 years does not take into account that the current version may not have all of those vulnerabilities, given that some of the previously known problems have been fixed or otherwise removed. The only remotely meaningful interpretation of the data is to consider known vulnerabilities between current versions of the individual products, which is what the NTBugTraq site attempted to do, after qualifying it.

      Also, I hope you realize that Outlook and sendmail are totally different types of software; Outlook is not an SMTP server, and has no real use running on a server.

      D

    42. Re:This, of course, will be ignored and ridiculed by dannannan · · Score: 1
      Open source haven't proven more secure than closed, as the theory about "given enough eyes all bugs are shallow" says.

      I agree. One of the reasons this is the case is that the notion that closed source gains security through obscurity is really a myth. "Closed" does not mean that people can't look at the source code. For example, many of Microsoft's large corporate customers, as well as government agencies, and universities, all have access to view Microsoft's source code -- including sources to current versions of Windows, like XP. Some customers have reported bugs to Microsoft after reviewing the code, and then they'll even go and diff the sources between versions to verify that a fix actually solves the problem.

      Really the only thing I can see that the "open" model allows for differently is that more people are free to change the code and redistribute it.

      My conclusion is that open source does not have any added benefit for locating bugs, since closed source is really not obscure in the first place. If anything, the "open" in open source more appropriately refers to its openness to fragmentation.

      D

    43. Re:This, of course, will be ignored and ridiculed by dannannan · · Score: 1

      I should also state the glaringly obvious, which is that everyone has access to the machine code.

      What does a C/C++ compiler really do? It basically just solves bunch of complex allocation and alignment problems required to implement a specification. When you're looking at the machine code, you're seeing the solution to those problems. To reiterate: when you're looking at the machine code, the problem is already solved; you're seeing the raw specification, open for all who have the binaries to see.

      Tools like SoftIce, RegMon, and FileMon, or any good debugger for that matter, can all be used to gain a very clear understanding of exactly what the code does.

      Example: Windows Product Activation accurately reverse engineered by some German guys who didn't have the source code.

      The biggest benefit you get from having the original source code is that it makes it easier to change the specification, since all you have to do is recompile.

      And this brings me back to my original point, which is that the difference between open and closed is fundamentally not a difference in the availability of information.

      D

    44. Re:This, of course, will be ignored and ridiculed by dup_account · · Score: 1

      Wrong answer. The point of the article was to say the Windows is better than linux. No other purpose. If they had a different purpose, they would have done a better job of looking into the numbers to come up with better statistics. They just used the raw numbers that most "proved" their point.

      It's funny about the sys admin thing. PCs were originally used to get around the massive IT infostructure, and get the job done. Now IT has taken control of the PC, locked everything down, and is making it harder to get (non M$ Word/Excel) work done.

      The anyone can be an administrator is a funny point. That is one of M$ major marketing points. M$ is soooo easy to administrer that anyone can do it, wereas Unix is complicated and you need a trained administrator to use it. Well, M$ isn't in the easy to securely admin realm anymore, it takes a trained professional.

    45. Re:This, of course, will be ignored and ridiculed by Anonymous Coward · · Score: 0

      ...this meaning that bugs are fixed MUCH faster in open source..

  3. but which were more severe? by Brandon+T. · · Score: 4, Interesting

    Perhaps windows has had less overall security vulnerabilities, but the ones it has had have completely ruined systems and clogged up the internet (i.e. code red, nimda etc...).

    1. Re:but which were more severe? by Prowl · · Score: 3, Insightful

      exactly,

      linux probably had a multitude of minor, rarely exploited vulnerabilities, whereas win2K/NT had relatively few major holes.

      holes that are still now being exploited.

      id be interested to see the amount of revenue lost due to linux exploitation versus win2K (taking market share into account of course).

      sounds like poor data analysis...

      --
      That man tried to kill mah Daddy
    2. Re:but which were more severe? by cyclist1200 · · Score: 1

      "id be interested to see the amount of revenue lost due to linux exploitation versus win2K (taking market share into account of course)."

      I know many who would be interested to see that. Obviously they didn't look at the cost of damage control and fixing the various security holes.

      Gee, I wonder which OS had less damage on the bottom line?

    3. Re:but which were more severe? by Anonymous Coward · · Score: 0
      Perhaps windows has had less overall security vulnerabilities
      Is one security problem that affects hundreds of thousands of compuuters (CodeRed, Nimda, et al) considered one vulnerability? Is one machine affected by 10 vulnerabilities considered 10?

      What about the other non-Microsoft machines that were affected by the flaws propagated by the Microsoft operating system? What about the Internet as a whole?

      This is a completely silly metric. I have yet to see any non-Win32 vulnerability (besides the famous Internet Worm) crawl, infect, and decimate as many Win32 and non-Win32 machines as the dozens of Microsoft vulnerabilities have.

      (and damnit, I forgot my password, so I can't get the karma for this post!)

    4. Re:but which were more severe? by PurpleFloyd · · Score: 5, Insightful

      If Linux had the marketshare of Windows, you can bet there would be lots and lots of scriptkiddies writing Code-Red style worms. Linux has had some pretty major security flaws in the past. Although they were fixed quickly, that doesn't mean that lazy or incompetent sysadmins will patch it right up. This leads to an opportunity for a Code-Red style worm, and if Linux had high marketshare, you can bet that it would have spread rather quickly as well.

      --

      That's it. I'm no longer part of Team Sanity.
    5. Re:but which were more severe? by Anonymous Coward · · Score: 1, Informative

      *sigh* you guys aren't looking at both sides.
      Most and nearly all DoS attacks come from hacked *nix boxes. Want to talk about clogging up the internet? Theres a much more important example.

    6. Re:but which were more severe? by Afrosheen · · Score: 3, Informative

      Linux has a greater server marketshare (apache, etc.) in some organizations so I believe your point is moot.

    7. Re:but which were more severe? by airyk · · Score: 0

      script kiddies don't write exploit scripts, they just use them

    8. Re:but which were more severe? by Thatman311 · · Score: 1

      They only ruined the net because of the market share that Windows has. If Linux had that market share bugs like that would "ruin" the net also. Think before you post.

      --
      Silly Rabbit...Sig's are for kids.
    9. Re:but which were more severe? by Baseballfreak31 · · Score: 1

      I agree with Brandon on that Windows has had many less security problems, the ones it has had were far worse than those on Linux.Like with windows ME, I have heard of many problems with this program.Many were glitches.

    10. Re:but which were more severe? by Anonymous Coward · · Score: 0

      > If Linux had the marketshare of Windows

      I know a bunch of unix admins, none of them run the same linux configuration/version and obviously not the same system configuration, so tell me what freaking ________LINUX________ are you talking about, huh? huh? HUH? HUH!!!???

      /Sorry, I'm having a bad MORON day.

    11. Re:but which were more severe? by Anonymous Coward · · Score: 1, Insightful
      The only reason Linux appears less secure is that holes were found and patched. That is what open source does - allows security holes to be found and fixed. Closed source means you know you have a hole after youve been assraped and you cant do anything about it. You just wait for the next hole to be found. Maybe eventually the closed source keeper will get around to patching it. Maybe not. It depends on how public the vulnerability becomes. A hole few people know about will never be patched.

      So yes the story is probably very true. Linux appears less secure but in the end who is more secure? You know I dont recall hearing very many blurbs about IIS holes recently... Maybe its because anyone in their right mind isnt using it anymore.

    12. Re:but which were more severe? by whopis · · Score: 1
      Linux has a greater server marketshare (apache, etc.) in some organizations

      A greater server marketshare in some organizations???

      Sure... that's like saying Linux has a greater workstation marketshare on my laptop, but that kind of misses the point of the term 'marketshare'.

    13. Re:but which were more severe? by Afrosheen · · Score: 1

      I said 'some organizations' to avoid the trolls but evidently you took the bait. Head to netcraft or your favorite polling site and see how many boxes are running Apache on linux vs. IIS on NT. Also note that IIS isn't automagically activated in XP like it was in 2000.

    14. Re:but which were more severe? by Anonymous Coward · · Score: 0

      You're missing the point!
      There are more bugs in the 100's of Linux distributions, however, Linux is just the kernel, how many bugs have been found in the kernel??
      I'll bet that if you remove 3rd party apps, such as apache/ftp/etc the number will crash. oh, should these bugs be added to windows if the software runs on windows too?

    15. Re:but which were more severe? by RazzleFrog · · Score: 1

      Apache may have more sites hosted but if you look here you will see that more servers run Windows that all other *nix combined. Apache is very popular with hosting companies.

    16. Re:but which were more severe? by catman · · Score: 1

      *sigh' so what? All it means is that on the average, a Windows box runs fewer sites than a Unix box. Using a Unix you just don't need that
      much hardware!

    17. Re:but which were more severe? by RazzleFrog · · Score: 1

      I love when people read comments and not threads. Read the thread again, ok?

      Your troll observations don't deserve the effort of a reply.

    18. Re:but which were more severe? by erc · · Score: 1

      Those don't count, since IIS exploits aren't counted - technically, IIS and IE aren't part of Windows, and so those bug counts aren't included, so of course Windows bug counts are artificially low.

      But what do you expect from an NT site? Honesty?

      --
      -- Ed Carp, N7EKG erc@pobox.com PGP KeyID: 0x0BD32C9B What I'm up to: http://intuitives.mine.nu
    19. Re:but which were more severe? by Anonymous Coward · · Score: 0

      um, I was under the impression that most ddos attacks these days come from script kiddies with fleets of bots running on compromised windows hosts..

    20. Re:but which were more severe? by Anonymous+DWord · · Score: 2

      How many boxes? You're gonna be sad when you find out. If you said something like "how many sites are hosted with Apache," you'd support your point better.

      --
      "If he thinks he can hide and run from the United States and our allies, he's sorely mistaken." Bush on bin Laden
    21. Re:but which were more severe? by RMSIsAnIdiot · · Score: 1
      Here is some hard data to dispel the idea that "Apache outnumbers IIS 2:1 on the net."

      That is, in vhosts.

      OS group Percentage Composition
      Windows 49.2% Windows 2000, NT4, NT3, Windows 95, Windows 98
      Linux 28.5% Linux
      Solaris 7.6% Solaris 2, Solaris 7, Solaris 8 BSD 6.3% BSDI BSD/OS, FreeBSD, NetBSD, OpenBSD
      Other Unix 2.4% AIX, Compaq Tru64, HP-UX, IRIX, SCO Unix, SunOS 4 and others
      Other non-Unix 2.5% MacOS, NetWare, proprietary IBM OSs
      Unknown 3.6% not identified by Netcraft operating system detector

      Microsoft Windows has a significantly higher share of the web when one counts by computer, rather than by host, as in the conventional Web Server Survey. The survey shows 49% of the computers running the web are Windows based; a little more than all of the Unix-like operating systems combined.

      Actually, I didn't believe it myself when I first read it. But it's true. Believe it!
      --

    22. Re:but which were more severe? by RazzleFrog · · Score: 1

      Was netcraft slashdotted? I could have cut and paste from the site too but I chose to just link to it.

    23. Re:but which were more severe? by TheKey · · Score: 1

      Well, I think that the Windows servers just weren't up half the time to get the viruses.

      --
      My Journal - 1,337 fans and countin
    24. Re:but which were more severe? by Old+Wolf · · Score: 2

      Your figures don't mention which of those systems run Apache, so they don't dispel the myth. Perhaps Apache is installed on all of the *nix, and half of the Windows.

    25. Re:but which were more severe? by sjwt · · Score: 0

      And this dosent go both ways how??

      --
      You have 5 Moderator Points!
      Which Helpless Linux zealot/MS basher do you want to mod down today?
    26. Re:but which were more severe? by Anonymous Coward · · Score: 0
      technically, IIS and IE aren't part of Windows

      Maybe IE is not technically part of Windows, but legally it is. At least, that is what Microsoft told the court.

    27. Re:but which were more severe? by Anonymous Coward · · Score: 0
      Oh look, hypocrisy! Linux zealots such as yourself are constantly masturbating over the fact that Linux comes "ready to rock" and doesn't need an extra dozen applications on separate CDs or from separate vendors to take on the world.

      Now, that very fact has bitten you in the ass and you make this feeble attempt to downplay the same factor that was a favorite selling point, what, fifteen minutes ago?

      Pick a lane, chump.

    28. Re:but which were more severe? by stand · · Score: 1

      Part of the problem here is that you can't really compare security between systems in isolation. Much of the "insecurity" of Windows derives from the fact that there are a whole lot of people out there banging away on Windows machines. If there weren't a lot of IIS and Exchange servers out there, Code Red and Nimda wouldn't have even hit anyone's radar screens.

      My Mac-head friends always like to point out that they never have problems with virii and think that this is because the Macintosh is so well designed to prevent this sort of thing. Aside from this being anecdotal evidence, (I, frankly, don't know enough about Macs to judge their design) it ignores the fact that not many people use Macs (relative to Windows).

      In short, the more people that use an operating system, the less secure it is, at least to some extent.

      --
      Four fifths of all our troubles in this life would disappear if we would just sit down and keep still. -C. Coolidge
    29. Re:but which were more severe? by Anonymous Coward · · Score: 0

      That's a Windows vs Linux comparison, not an IIS vs Apache comparison. You're looking at the wrong numbers here.

    30. Re:but which were more severe? by Anonymous Coward · · Score: 0

      You omitted the last part:

      Although Apache running on various Unix systems runs more sites than Windows, Apache is heavily deployed at hosting companies and ISPs who strive to run as many sites as possible on a single computer to save costs. Windows is most popular with end-user and self hosted sites, where the host to computer ratio is much smaller.

      Note that Apache servers can, as one poster noted, run a lot more sites than windows computers can. That's one good reason why Apache is really used more; note that Google uses Linux.
      Also as another poster noted, those figures are for windows and Linux, not Apache itself. (although on a windows machine Apache is crippled and requires more machines/site)

      Anonymous Oyster

    31. Re:but which were more severe? by PurpleFloyd · · Score: 1

      Sure, Linux has greater marketshare in some organizations. In the organization "PurpleFloyd's House" there are 3 linux boxen and one dualboot Win2K Pro/Linux box. Thus, Linux has a much greater marketshare -- in my house, anyway. However, on the 'net at large, Win2k/NT servers are more common. Perhaps this is because of the "point, drool, you've set up a server!" mentality that seems to infect Microsoft -- you can install IIS on Win2K Pro from the CD! One wonders what the hell a server program is doing on an OS supposedly designed even for workstations. To crackers, however, every home user who has cable/DSL and a completely unpatched IIS install is a potential DDOS zombie. Thus, the large numbers of Windows worms. If home users installed Red Hat (which configures all sorts of servers on its install) on a regular basis, the situation would be reversed: Windows, despite having terrible security problems, would go ignored and Linux would be the prime target.

      --

      That's it. I'm no longer part of Team Sanity.
    32. Re:but which were more severe? by krogoth · · Score: 2

      If IIS had even half the market share of Apache, it would be much more dnagerous.

      --

      They that quote Benjamin Franklin on liberty and safety deserve neither.
    33. Re:but which were more severe? by gooberguy · · Score: 1

      Most and nearly all DoS attacks come from hacked *nix boxes. Want to talk about clogging up the internet? Theres a much more important example.

      I'm afraid you are just plain wrong. Most DoS attacks are from hacked windows 9x/ME boxes, which have been taken over by script kiddies with trojans. In fact, sites sych as yahoo, grc.com, ebay, and amazon.com have been taken down for up to 2 hours by script kiddies using hacked windows 9x boxes.

      D/\ Gooberguy

      --


      Karma: Meh (Mostly from meh.)
    34. Re:but which were more severe? by Anonymous Coward · · Score: 0

      You forgot something.
      You don't have to install those programs. They're just on the CD *in case you want them.*
      Now who's the chump?

    35. Re:but which were more severe? by buckrogers · · Score: 2
      Here are some hard numbers that prove you need 2 to 4 times the the number of windows boxes to support the same number of clients as you do when you use Linux and either Tux 2.0 or Chromium X15 WebServer 1.0.

      Tux is a kernel mode web server, but X15 is a user mode web server and has the same performance.

      --
      -- Never make a general statement.
    36. Re:but which were more severe? by kiowa · · Score: 1

      And I would like to see some figures on the "bug is found -> bug is squatted" timeline for various OSes. It really doesn't help much that one OS is really low on bugs, but the 20 or so that are found usually take up to a month to get fixed.

      --
      =-kiOwA-> EOF
    37. Re:but which were more severe? by Anonymous Coward · · Score: 0

      Hey people, follow the link. This guy is either blind, braindead, payed by microsoft, or all of the above.

    38. Re:but which were more severe? by opkool · · Score: 2

      Have you read Netcraft comments about those figures?

      I recommend you this link.. Check also the "Results", down the same page.

      Those figures show number of servers. But some servers can hold more than one site. Have you heard of virtual domains under Apache?

      Also, Apache can (And it is) run under Windows OS.

      So, in short: Those numbers lead me to think that:

      1.- You can have more websites with fewer machines if you do not use Windows OS

      2.- You need a lot of servers with Windows OS to host a fewer amount of websites.

      3. -Your numbers are only one part of the facts, one part that you choose because it fits your need for FUD.

    39. Re:but which were more severe? by RazzleFrog · · Score: 1

      Are you talking about me? I provided the link. Why would I be "blind, braindead, payed by microsoft"?

      Next time be more careful about which reply button you hit dumbass.

    40. Re:but which were more severe? by RazzleFrog · · Score: 2

      The guy may have quoted out of context but you are an absolute moron.

      First of all, you can host virtual domains unders Windows. Second, the site itself states that webhosts prefer Apache which drives its site numbers up signficantly. It doesn't state why they prefer it but I would guess that cost comes into play there. Finally, there is absolute no support for any of your assumptions except spreading your FUD.

    41. Re:but which were more severe? by RazzleFrog · · Score: 1

      I also forgot to mention that your like is from 2000 wheras the link I provided in the original thread is from 2001.

    42. Re:but which were more severe? by RMSIsAnIdiot · · Score: 0
      That is total bullshit. Give me some hard facts to back it up.

      On the other hand, UnixWorld has one of the most unbiased articles comparing Apache and IIS. Basically there are pros and cons to both servers (one being IIS's built-in support for SSL, compared to a pay addon for Apache). Use what fits your needs. Apache isn't necessarily "better" overall, unless of course, you want to spread FUD.

      --

  4. Severity of vulnerabilities by SiW · · Score: 4, Redundant

    The report doesn't seem to take into account the fact that while the number Windows holes was fewer, they were far more severe. Code Red, anyone?

    Btw, I'm not a Linux cheerleader, I'm a Windows guy most of the time, and I subscribe to the "best tool for the job" philosophy.

    1. Re:Severity of vulnerabilities by truffle+pig · · Score: 1

      If Companies were adopting platforms based solely on security, then according to these numbers we would all be Novell shops. Remember it is easy to hit the broadside of a barn, and the Linux and Windows barns are attractive targets.

    2. Re:Severity of vulnerabilities by Pfhreakaz0id · · Score: 2

      Well, code red was based on a hole that had a patch available for months. BTW, I agree with the other posters that this "study" doesn't seem fair (multiple counting of the same bug because it exists in different distros)

    3. Re:Severity of vulnerabilities by Anonymous Coward · · Score: 0

      Tedious

    4. Re:Severity of vulnerabilities by ackthpt · · Score: 2, Funny

      That's it, I'm abandoning all this and going back to CP/M!

      --

      A feeling of having made the same mistake before: Deja Foobar
    5. Re:Severity of vulnerabilities by leonbev · · Score: 2

      Not to mention that Windows security holes are more frequently exploited, causing more overall damage.

      Hell, If I was a script kiddie or virus writer, I'd probably choose to go after Windows exploits over UNIX exploits, too! There is a larger installed base of Windows servers and client systems than there is for any other single platform, and most Windows sys admins are either too stupid or too lazy to patch their systems.

    6. Re:Severity of vulnerabilities by Tower · · Score: 1

      Interesting that they don't mention OS/400 on there at all... I guess 0 is a good number :)

      Considering that OS/400 and OS/390(and now z/OS) are in place for a great deal of critical data safety and reliability installations, it is odd that they wouldn't be listed at all... or maybe there are now vulnerabilities since nobody can program in PL/8 and RPG :)

      --
      "It's tough to be bilingual when you get hit in the head."
    7. Re:Severity of vulnerabilities by timbck2 · · Score: 1

      It's just a gut feeling, with no real info to back it up, but I'd say in general, Windows holes go unpatched *much* more often than Linux holes (just due to user/sysadmin awareness).

      --
      Absurdity: A statement or belief manifestly inconsistent with one's own opinion. -- Ambrose Bierce
    8. Re:Severity of vulnerabilities by Fjord · · Score: 2, Insightful

      This really isn't a badge that Linux can hide behind. Many people, myself included, would like to see linux replace Windows as the mainstream OS. It's hard to say you should switch to linux because it isn't mainstream. If everyone did switch, then it would be mainstream and thus more targeted.

      That said, however, I also whink that this report is exaggerated because of the whole same bug-different ditro thing, the bugs in packages that aren't common for anyone to use (and your can use a root exploit on a package you don't have), plus the fact that I would assume that open source projects would have more security bug reports than closed source ones because it is easier to find them with the source.

      --
      -no broken link
    9. Re:Severity of vulnerabilities by Cyno · · Score: 1

      Don't laugh, I've heard rumors of Novell infected even some of the largest corporations. I have to wonder how anyone would want to move to Novell years after its demise. Or am I wrong, has Novell gone through major revisions, improvements and supports an entirely new set of protocols, standards and features? But look at the bright side, everyone adopts Novell and drops all their unix and M$ techs for some cheap green Novell guys.

    10. Re:Severity of vulnerabilities by truffle+pig · · Score: 1

      Do you think that the folks running the Networks for the Winter Olympics are running Novell? It would seem like a real slap in the face to Novell for the Utah grown NOS to not have any place in the Salt Lake spotlight.

    11. Re:Severity of vulnerabilities by Anonymous Coward · · Score: 0

      The report doesn't seem to take into account the fact that while the number Windows holes was fewer, they were far more severe. Code Red, anyone?

      True, but when a security hole is found in Linux it usually gets fixed in a couple of days, when a security hole is found in Windows it is usually six months or more before Microsoft admits that there is a problem (and half the time they say that it is not a problem they intend to fix).

  5. Define "more secure" by mblase · · Score: 3, Insightful

    Does Windows have fewer security holes than Linux? Apparently so.

    Are they smaller holes -- that is, exposing less control of the system and less potential for damage? Probably not.

    The question becomes, then: would you rather be shot by a dozen BB pellets or a single shotgun blast?

    1. Re:Define "more secure" by blakestah · · Score: 5, Insightful

      You apparently didn't check out NTBugTraq. They simply added up vulnerabilities from different linux distros to come up with a high aggregate number. This is plain wrong because

      1) If a package has a security issue, usually all distros announce the security bug. Thus, the bug gets counted multiple times.

      2) Windows security bugs are all remote compromises, either email attachments, or remote roots. Over 90% of the linux security problems are local security issues.

      As another poster noted, this is a very poorly researched article.

    2. Re:Define "more secure" by denzo · · Score: 0, Redundant
      would you rather be shot by a dozen BB pellets or a single shotgun blast?
      Since a shotgun (usually) fires out many small pellets (smaller pellets with larger gauge number), perhaps a modification to this analogy should go along the lines of: would you rather be shot at a distance by a .410 shotgun or a 50-caliber rifle?

      I'd pick the shotgun, I'd just like to bring along a piece of plywood to take the sting out. ;)

    3. Re:Define "more secure" by murphyslawyer · · Score: 0, Offtopic

      ummm...A single shotgun shell is a whole bunch of BBs...

      --
      I ain't evil, I'm just good looking.
    4. Re:Define "more secure" by LightlyToasted · · Score: 3, Insightful

      I'm not convinced that "Windows has fewer security holes than Linux" just because there was a higher number of vulnerabilities reported. For the reported number to have any weight, there would need to be some consistency in how vulnerabilities are discovered and reported between Linux and Windows. On the discovery side, more eyes on open source code would tend to yield more discoveries, skewing the reported number. On the reporting side, Microsoft has a deserved bad reputation of denying and covering up security vulnerabilities in their products, which would lead me to speculate that they underreport their vulnerabilites, making a comparison useless. Moreover, the open source community has the opposite reputation - that of publishing vulnerabilities as they arise. Again, the results are skewed. I'm disappointed that a security site would perpetuate this flawed logic.

    5. Re:Define "more secure" by fataugie · · Score: 1
      Well no offense, but do you know what makes up a shotgun shell? That's right....say it with me....dozens of BB pellets.

      That is the standard shell, now if you are talking shotgun slugs, well OK then. But, some good old fashioned duck hunting/phesent hunting shells contain lots and lots of small BB's.

      --

      WTF? Over?

    6. Re:Define "more secure" by Afrosheen · · Score: 2, Funny

      I guess the NT in NTBugtraq stands for "Not True".

    7. Re:Define "more secure" by Score+Whore · · Score: 1

      I don't think you looked at the numbers as closely as you would like people to think. Yes, it's true, the *aggregate* linux number is huge, but some of the individual distros are higher than WinNT/Win2K (which is also an aggregate number, BTW.)

      Additionally how do you know that point 1 is true. If I was collecting such statistics, I wouldn't include the same bug, because it's obvious that it's wrong and the value that I would be providing would be lessened. Unless you've actually gone through and analyzed the entire statistics gathering process used, you don't actually know that they are counting the same bug multiple times, you are just assuming that.

    8. Re:Define "more secure" by sheetsda · · Score: 1, Offtopic

      If my understanding of shotguns is correct (I have fired them on several occasions so I'm not totally clueless), there are multiple types of shells, some are buckshot which are, like you pointed out, BBs; however they are smaller, greater in number, and exit the barrel with much higher velocity than air rifle BBs. There are so many, in fact, you can cut a 3 foot wide target in half with about 10 12-gauge shells at 15 foot range. Another type of shell is solid-load in which there is a single large projectile.

    9. Re:Define "more secure" by Anonymous Coward · · Score: 0

      Exactly. This is made worse by the fact that many people don't seem to be actually clicking through and looking at the numbers themselves.

    10. Re:Define "more secure" by Drey · · Score: 1

      They made this same claim 1 or 2 years ago and did their math the exact same way. It would be almost identical to someone adding up all the holes in Win9x/ME/NT/2K and comparing them to 1 Linux distributions reports.

    11. Re:Define "more secure" by BAKup · · Score: 2, Funny

      Hey, look everybody, it's Funny's cousin, Not Funny!

    12. Re:Define "more secure" by 5foot2 · · Score: 2, Insightful

      BB's are copper. Old style bird shot was lead, current stuff is steel. Then there is buckshot and slugs of course. Then we get into the really cool shit, fletchet rounds (a dozen or so finned steel darts), incendiary rounds (think of a ball of white hot fire coming out of the barrel of a 12gauge. The round is for forestry work, setting backburns to fight fires), duplex rounds (for blowing deadbolts and hinges off doors). There are some really cool rounds for shotguns.

      I really think the incendiary rounds are the best for personal defense. I don't think someone would continue to fuck with you if your shooting back at them with great big balls of white hot fire ;-)

    13. Re:Define "more secure" by schon · · Score: 2, Insightful

      Yes, it's true, the *aggregate* linux number is huge, but some of the individual distros are higher than WinNT/Win2K

      Really? Which ones in particular?

      I looked at the page, and I see REDHAT as the highest number for all of the linux distros.

      This number is LOWER than the NT ones.

      So can you explain this sentence for the rest of us please?

    14. Re:Define "more secure" by Anonymous Coward · · Score: 0
      I really think the incendiary rounds are the best for personal defense. I don't think someone would continue to fuck with you if your shooting back at them with great big balls of white hot fire ;-)

      Just make sure you have plenty of fire insurance!

    15. Re:Define "more secure" by mustermark · · Score: 1
      Here's how the number of vulnerabilities should be tallied:

      1. The number of vulnerabilities per distro should be weighted by that distro's percentage share.
      2. The average number of vulnerabilities for linux as a whole is then the sum of these weighted vulnerabilities.

      N = \sum_i w_i * N_i

      where N is the average number of vulnerabilities and w_i and N_i are the percentage marketshare and number of vulnerabilites for distro i. Sorry about the LaTeX -- I couldn't get the ascii capital sigma to look right after slashcode mangled it.

      You could also in this scheme add a (albeit subjective) weighting for the severity of the vulnerabilities. So why can't SecurityFocus do this?
    16. Re:Define "more secure" by jareds · · Score: 2

      1) If a package has a security issue, usually all distros announce the security bug. Thus, the bug gets counted multiple times.

      You obviously didn't check the numbers to see if your claim made sense. See this post.

    17. Re:Define "more secure" by Anonymous Coward · · Score: 0

      Not true. BB refers the size, similar to BBB, T, size 1-8.... has nothing to do with the material it is made of.
      Steel is one of the non-toxic shots, performance (in terms of killing power) is not as great. Most purposes are better done using lead shot (the old stuff) which is much heavier, unless non-toxic shots are needed.
      Most army and police rounds are shotgun rounds are lead. Most hunters still uses lead for turkey and in slug form or BBs for deer.

    18. Re:Define "more secure" by wizkid · · Score: 1


      I've looked at the Security Focus site. 2 things I
      am going to point out.

      First, this info hasn't been updated since August. Alot has happened since then. RedCode, and a Bunch of Nimda variants.

      Second, They are comparing OS distributions. W2K/NT is an OS distribution. RedHat is an OS/Application distribution. Note that if you load the whole RedHat distribution, your getting about 2-3Gb of applications on top of that OS. This survay is Not taking that into consideration. One other side note. Many of those patches/bugs listed for RedHat are pre-emptive security fixes, or application upgrades. We're not comparing apples to apples here. I've worked with both OS's. I keep both of them updated, and have seen the updates for both of them. I'd like to see the numbers comparing Just Windows/NT to Just the RedHat OS,
      with the Apache server loaded. No other apps.
      Does this seem like a fair Comparison?
      W.Kid

      --
      I take no responsibility for what I say. Even though I'm never wrong :)
    19. Re:Define "more secure" by Score+Whore · · Score: 1

      Perhaps you need to look at those numbers again. Last time I checked, 54 > 42. I would assume that that includes all vulnerabilities reported for 7.0 & 7.1, while the MS numbers include NT & 2K.

      Look at the third or fourth chart. The one that lists vulnerabilities for 2001 by OS. It breaks things down into smaller pieces, such as RedHat 7.1, etc. There are four different Linux distros that are higher than Windows 2000.

      Enough of an explanation?

    20. Re:Define "more secure" by Score+Whore · · Score: 1

      Well, is IIS part of 2K? It's not on any of my 2K boxes? It could be installed, but it's not. So do you think they are including IIS exploits in those NT/2K numbers? How about Exchange? Exchange server? I bet they are. So it's rational to include problems with software that a vendor (ie. RedHat, SuSe, Mandrake, Microsoft) includes as (a potentially optional) part of their out of the box install. The vendors should be held accountable for software they include as part of their distros. RedHat, et. al., make choices about what they include in their OSes. And they are responsible for those choices. Yes, Microsoft has dramatically larger resources so one might expect Microsoft to be a little more capable of producing a higher quality product so maybe we should give the little guys some slack when it comes to comparing... fuck that. Linux distributors have chosen to compete with Microsoft, they should be held to the same level of accountability.

    21. Re:Define "more secure" by Bob+Uhl · · Score: 2
      The question becomes, then: would you rather be shot by a dozen BB pellets or a single shotgun blast?

      What's amusing is that BB is a size of shot. So getting hit with a dozen BBs is the same as catching part of a shotgun blast. And, in fact, a dozen BBs could cause a much nastier wound than, say, a single .40 round. So it's not quite so cut-and-dry.

    22. Re:Define "more secure" by berzerke · · Score: 5, Insightful

      Another note from bugtraq that will really push the numbers in favor of Windows. I quote: "* There is a distinct difference in the way that vulnerabilities are counted for Microsoft Windows and other operating systems. For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers." MAY?!?!? More likely WILL.



      So let's see. IE vulnerabilities aren't counted. There goes the fairness in the numbers right there. Was IIS counted?

    23. Re:Define "more secure" by Anonymous Coward · · Score: 0

      Umm... nice analogy, we in hickville know what is in a shotgun shell, unless you are using slugs...

    24. Re:Define "more secure" by schon · · Score: 1

      Perhaps you need to look at those numbers again. Last time I checked, 54 > 42. I would assume that that includes all vulnerabilities reported for 7.0 & 7.1, while the MS numbers include NT & 2K.

      Perhaps YOU need to look at ALL of the numbers:

      1997 : RedHat 6, Win2K/NT 10
      1998 : RedHat 10, Win2K/NT 8
      1999 : RedHat 47, Win2K/NT 78
      2000 : RedHat 95, Win2K/NT 97
      2001 : RedHat 54, Win2K/NT 42
      Total: RedHat 212, Win2K/NT 235

      In all but two of the years, Win2K/NT has more than RedHat. And in total, Win2K has more.

    25. Re:Define "more secure" by schon · · Score: 1

      Oops, I forgot to add:

      The one that lists vulnerabilities for 2001 by OS. It breaks things down into smaller pieces, such as RedHat 7.1, etc. There are four different Linux distros that are higher than Windows 2000.

      First: You neglect to mention that ALL of them pale in comparison to Windows NT, which is the reigning king, with 71.

      Second, there are NOT "four higher than Windows2000", there are THREE, and they are all the same damn OS (Redhat 6.2)

    26. Re:Define "more secure" by wizkid · · Score: 1


      I've dealt with W2K boxes. The patches for Exchange, SQL etc are handled from a different patch site, and are not part of the OS. They are handled by MicroSoft as Applications, not as part of the OS.

      IIS is distributed as part of the OS. It is a seperate option. The patch tree is distributed with the OS patches. Therefore, that is why I believe that it should be compared to Linux distributions with Apache.

      I agree that Microsoft and Linux are compeating aganst each other. Therefore, MicroSoft should be held accountable to the same level as Linux distributions.

      My employer uses exchange servers to deliver mail. We had 2 3 day outtages in the Aug-Oct timeframe. Every time a new variant came out, the mail servers were shutdown for at least 1-2 hours. The Sendmail servers didn't miss a lick, but instead queued the mail for the exchange servers. This isn't really indicating a problem with exchange, but in the attitude that MicroSoft has had with security issues in general That's why Bill, and the rest of the cronies at the top levels of MicroSoft are starting to make noise about stablizing and locking down there OS's and Applications.

      Ya know, what good is an OS without applications. The applications, OS etc has to be looked at as a whole system, not the OS and applications. What good is an OS without an Application, and Visa Versa. The Linux vendors look at there systems this way, so YES, the patch numbers are higher. This is a Good thing. This indicates to me that they are supporting them. The numbers for W2K/NT in this survey, as far as I can tell, are not including the MicroSoft applications.

      Basicly, what it boils down to is that in this instance, saying one OS is better then the other because of the patch count is Balony.

      With the outages we've had, due to $M products over the last 6 months, and the lack of outages we've had with Linux and Unix apps, I'd have to say that the UNIX apps are more secure, after being locked down. Remember, NO OS TODAY IS SECURE IN IT'S INITIAL INSTALLED STATE. UNIX, NT OS/2 and even CowBoy Neal's LinDosy OS isn't secure out of the box. They all have to be LOCKED DOWN. RedHat 7.2 is getting very close now. I believe some of the other DIstros are getting there too. Lets hope Billy Boy is serious about getting W2K/XP/ETC locked down better also. All the OS distributers should be held accountable. This includes both RedHat and MicroSoft.
      W.Kid

      --
      I take no responsibility for what I say. Even though I'm never wrong :)
    27. Re:Define "more secure" by Score+Whore · · Score: 1

      What the fuck? Do you not read? Or do you always argue your own argument so you can win? Jesus fucking Christ on a crutch. You're looking at the fucking 2000 table. Not the 2001 table which is what the rest of the fucking thread is talking about.

      As far as the rest of the discussion goes, assuming you want to join us over here where we are talking, of the four linux distros with more vulnerabilities reported, there are three different distributors involved. That's three different groups of people making more fuck-ups than Microsoft.

      Next time you might want to actually make sure you know what everbody is discussing before uncorking that giardia laden orifice you call a mouth.

    28. Re:Define "more secure" by Anonymous Coward · · Score: 0

      You shouldn't count IE vulnerabilities. Unlike say xfig, in Redhat, it's not part of the OS.

    29. Re:Define "more secure" by Anonymous Coward · · Score: 0

      Actually, those were the tables from '97 to '01. In *total*, RedHat comes out with less bugs.
      One year's worth of statistics in this case doesn't mean shit.

    30. Re:Define "more secure" by Anonymous Coward · · Score: 0

      People should really learn to read.

      "There is a distinct difference in the way that vulnerabilities are counted for Microsoft Windows and other operating systems. For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers."

      In other words if package abc from xyz linux has a security hole it counts against the xyz linux distro as a whole even though package abc may or may not be installed and may or may not even be linux. On the other side of the coin programs like lookout express and internet exploder are not counted against windoze.

  6. Less because MS doesnt tell by peripatetic_bum · · Score: 5, Insightful

    Look, the obvious point about this should be that the reason Linux has more known vulnerabilities is that linux has always been very open about what is wrong with linux.

    As for MS, I only have to point to the the major bug, that they knew about for weeks, but didn't let anybody know about!

    Now Im not saying that linux is more secure (as much as i would like to) but the data and report based from it, just makes no sense, if you think about how vulnerabilties are and are not reported

    Thanks for reading!

    --

    Sigs are dangerous coy things

    1. Re:Less because MS doesnt tell by TMLink · · Score: 1
      As for MS, I only have to point to the the major bug, that they knew about for weeks, but didn't let anybody know about!

      Which one?

      --
      Every time a guy gets a threesome, somewhere in heaven an angel gets his wings. --Cary Tennis
    2. Re:Less because MS doesnt tell by quantaman · · Score: 1

      I think a more accurate application of your comment should be which one has had more breaks. This is where the security through obscurity that M$ subscribes to would hurt them more. Also when a bug is discovered which OS is usually first in providing a fix for the OS?

      --
      I stole this Sig
    3. Re:Less because MS doesnt tell by peripatetic_bum · · Score: 1

      ah this one
      the universal plug and play

      http://stacks.msnbc.com/news/676671.asp?cp1=1#BO DY

      Thanks

      --

      Sigs are dangerous coy things

    4. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      Hitler's Germany had no crime or dissent, according to their propaganda. Totalitarian governments and businesses can make things appear as they want.

    5. Re:Less because MS doesnt tell by Col.+Panic · · Score: 3, Informative
      Im not saying that linux is more secure

      The thing about linux is that if you don't know how to set it up you can unknowingly install LOTS of services, most of which are unnecessary for a home user and many of which can be compromised. Redhat's "everything" install sounds pretty neat, but you probably don't want to run an FTP server, DNS server, SQL server, etc. if you don't absolutely need it (and know how to configure it). Mandrake (at least the older versions) has better security setup, allowing you to check off a security level during install that does a decent job of hardening the OS. Of course, not knowing that you are installing file shares on a cable modem with no firewall could be even easier to compromise :)

    6. Re:Less because MS doesnt tell by Refrag · · Score: 2

      There are varying levels of publicity (is that a word?) of bug notes in the Microsoft Knowledgebase. I know this because I used to be part of Microsoft Support. I believe there are developer-level, escalation-level, employee-level, partner-level, contractor-level, and fully public bug notes. I may be wrong, it's been a few years since I was there (thank goodness).

      --
      I have a website. It's about Macs.
    7. Re:Less because MS doesnt tell by SilentChris · · Score: 3, Interesting
      "linux has always been very open about what is wrong with linux."

      Open, maybe. Willing to change, rarely. Just look at the recent code rift between pre-release forks and the slowly growing consensus that Linux isn't up to the task. Something as simple as a paging system has to be debated endlessly (in the meantime, having different systems with different potential vulnerabilities). We may not be able to look at the MS code, but we can be pretty sure what doesn't work on one machine shouldn't work on another.

    8. Re:Less because MS doesnt tell by broter · · Score: 2, Insightful

      You're right about the pedestrian installs being way too feature filled; however, I'd like to point out the obvious caviot that Windows* does this as well. Very often the options added in Windows* are poorly documented, if at all, so you get into much the same situation as a newbie Linux user w/o an experienced Linux friend to ask. What do you deinstall? What do you keep?

      Personally, I'd like to see a more OpenBSD like install for all the consumer products. Although the user would have to work a little harder to get what they want, they would (presumably) learn a bit more about the system. If that fails, then they would at least have to admit liability for braindead configurations (er... most of em).

      --
      "One man can change the world with a bullet in the right place."
      - Mick Travis, "If..."
    9. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 1, Informative

      "Very often the options added in Windows* are poorly documented"

      Right - at least with the RedHat installer, you can see that "Everything" includes bind, sendmail and so on.

      Windows 2000 had a neat issue where if you installed IIS, it automatically configured Internet Printing over HTTP. Which of course had security problems. So you asked for a webserver and got a printserver. It's that kind of braindamage that gives MS the reputation they've got.

      (Another obvious example is the Index Server filter exploit used by Code Red. Nobody uses it, so wtf is it registered by default?)

    10. Re:Less because MS doesnt tell by peripatetic_bum · · Score: 2, Interesting

      Hmmmm,

      I guess I can take you up on two points

      1. Paging debates: Yes, I agree it seems that there has been a lot of talk about it, but it has been out in the open AND the potential vulnerabilities are well known AND if you need security you cant Beat the stable debian kernel 2.2, which I geuss is another way of saying that you Know Very Well that you can have can have problems as you are told up front

      2, We are talking about Pre-Release forks here (which i geuss is part of point 1) and we are talking about MS releaseing Release canidates, but know about Huge Security Holes like the plug and play

      No?

      Thanks

      --

      Sigs are dangerous coy things

    11. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      WHY WAS THIS MODDED REDUNTANT!? He was one of the first ones to write this, idiots: cant you tell time

    12. Re:Less because MS doesnt tell by SilentChris · · Score: 3, Funny

      "you cant Beat the stable debian kernel 2.2",p>One could also argue that you couldn't beat the original DOS in internet security because it couldn't (easily) connect to the internet. Anyone who argues that an older version is the way to go is fooling themselves.

    13. Re:Less because MS doesnt tell by peripatetic_bum · · Score: 1

      Anyone who argues that an older version is the way to go is fooling themselves.

      Well Im certainly arguing this, as Most Production computers Used for Real Work are no where near the cutting edge.

      I think that part of you is trying to have their cake and eat it too.

      If you want newer advanced features, you have to understand that they are indeed Newer features, less mature and all

      anyway, I look forwad to your reply

      --

      Sigs are dangerous coy things

    14. Re:Less because MS doesnt tell by dimator · · Score: 2

      As for MS, I only have to point to the the major bug, that they knew about for weeks, but didn't let anybody know about!

      And if YOU know about a bug and you tell the world, then you're helping the terrorists!! You're so un-American!!

      --
      python -c "x='python -c %sx=%s; print x%%(chr(34),repr(x),chr(34))%s'; print x%(chr(34),repr(x),chr(34))"
    15. Re:Less because MS doesnt tell by peripatetic_bum · · Score: 1

      Actually, if you read in the news, the FBI did in fact contact MS and ask them about the Hole, because there were concerns that there were a lot of vulnerable computers that MS didnt inform, and the FBI had a very strong talk with MS, any wonder why they declared this month to be Fix-Bug Month?

      Thanks!

      --

      Sigs are dangerous coy things

    16. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      Is that anything like the WU-FTPd exploit that Red Hat patched a week early (because the various distro companies agreed not to disclose the information until a previously agreed upon time)? After all, that one had only taken 8 months for them to decide not only that it was exploitable, but that it should be patched and the user base informed.

    17. Re:Less because MS doesnt tell by jelle · · Score: 2

      First of all: Improving the vm has nothing to do with security. Second: the 'pre-release forks' you mention should be considered 'internal releases' for people like you, don't touch them. Proprietary software goes through the same thing, it's just not releases until they have something more final. It's the whole 'release early, release often' philisophy behind open source development.

      "Something as simple as a paging system"

      By that statement, I must conclude that you don't realize how much impact the vm subsystem has on the system performance and reliability.

      And really, why should Torvals, Cox, and the others bother about a buffer overflow bug in wu-ftpd? It's not their software, they do kernel space, not user space.

      There are many different programs for the same task under linux, there are at least 5 smtp servers, probably the same amount of ftp servers, at least four http (web) servers, etc. Geesh no wonder, that if you sum up all the bugs, you'll see more for Linux. The insider here is that nobody actually runs all of them in parallel, so if you're using proftpd, then vulnerabilities in wu-ftpd are not applicable to you, etc.

      This is what I think is true: Linux is up to the task, and will demonstrate so.

      Umm, by the way:

      "and the slowly growing consensus that Linux isn't up to the task..."

      Which consensus, which task? You're making a classic "everybody knows that" statement: its without merit. Really, it's the same as saying "It's simple to prove, I'll leave the exercise up to the reader", also doesn't prove anything.

      "We may not be able to look at the MS code, but we can be pretty sure what doesn't work on one machine shouldn't work on another."

      In my experience, with the MS code, you never know until you've tried it.

      --
      --- Hindsight is 20/20, but walking backwards is not the answer.
    18. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      "and the slowly growing consensus that Linux isn't up to the task."

      Talk about a smear.

      What growing concensus by whom that Linux isn't up to WHAT task?

      Himmler would be proud.

    19. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      > There are varying levels of publicity (is that
      > a word?)

      IS PUBLICITY A WORD???

      Oh God, I weep for my language.

      Is 'language' a word? Fuck.

    20. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      So, Linux kernel 2.4.x is to Linux kernel 2.2.x as Windows XP is to DOS?
      No.
      Try going back down to just Windows NT (Pretty reasonable, once it is heavily patched and service-packed) and maintaining the same claims of stability and safety.

    21. Re:Less because MS doesnt tell by Anonymous Coward · · Score: 0

      I think the intended word was "publioicity." ;-)

    22. Re:Less because MS doesnt tell by DunbarTheInept · · Score: 2

      The only difference between linux kernel design debates and closed-source ones is that linux debates are carried out in the public. Slow-witted people assume that just because you get to *witness* the linux developers have debates that this means there is more confusion and disagreement between them than between developers in a closed source project. Bull. Whatever disagreement there is in a closed project will not occur where the public can witness it.

      A parallel can be drawn about security problems too.

      --

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

    23. Re:Less because MS doesnt tell by SlugArt · · Score: 1

      lol, you of course assume that anyone typing in English is from America.

  7. Sure ... by NWT · · Score: 1

    Hum, this must be a joke ... i'll go and see right now it that article wasn't written by a M$ employee!
    But ... perhaps there are people who enjoy patching their WinNT Servers every 2 days, who knows ...

    --
    Life sucks.
  8. From a technical standpoint. by llamalicious · · Score: 4, Insightful

    Well, that may be all well and good from a purely technical (or counting reported bugs) standpoint.

    But when you consider Microsoft's installed user base, there's just no comparison to how widespread MS is.
    It's a damn good thing there were less bugs reported for Windows, as with each one, the repercussions are far far greater.

    ~sigh~

    1. Re:From a technical standpoint. by MrResistor · · Score: 3, Insightful
      Well, that may be all well and good from a purely technical (or counting reported bugs) standpoint.

      It isn't, though. Even the counting method used in the article is flawed. As mentioned in several other posts, package bugs are often listed for each distro that uses that package, so a single bug could easily be counted multiple times (and, in fact, this is the case since the article is based on the Linux aggregate, which simply counts the number of bugs reported on all Linux lists and adds them tegether).

      Even at the most basic level, the article is FUD. The fact that this article was published without the editors checking even basic facts (like, for example, the fact that NTBugTraq is not hosted by SecurityFocus) certainly casts WinInformant in a bad light, and I will definately take any information I get through them in the future with a large grain of salt.

      --
      Under capitalism man exploits man. Under communism it's the other way around.
  9. Did anyone get a look at the article? by lemox · · Score: 1

    The damn thing was already /.ed before the first comment was posted...

    --

    "We obviously need a new moderation category: (-1, Woo-fucking-hoo)" --Mr. AC

    1. Re:Did anyone get a look at the article? by Score+Whore · · Score: 1

      There is no article to speak of. It's a one paragraph blurb, most of which was copied directly into the slashdot posting.

  10. Response. by saintlupus · · Score: 1

    Send in the trolls, one and all.

    --saint

  11. Oh, boy. Just another example... by aslagle · · Score: 1

    I think we've just seen another example of the old adage, "You can make statistics say anything you want them to."

    1. Re:Oh, boy. Just another example... by Dak+RIT · · Score: 1

      47% of all people know that :)

    2. Re:Oh, boy. Just another example... by Anonymous Coward · · Score: 0

      So the statistics don't support what you groundlessly believe to be fact. Therefore the statistics are wrong. Get a life.

    3. Re:Oh, boy. Just another example... by aslagle · · Score: 3, Informative

      >> So the statistics don't support what you groundlessly believe to be fact. Therefore the statistics are wrong. Get a life.

      No, that's not what I said.

      Let's look at the methodology behind these statistics - and why it 'skews' the results.
      1. Each 'bug' is treated as the same, whatever the severity.
      2. The individual reports from the distros are combined to form a 'linux' category that doesn't exist in real life.
      3. 'Linux' actually refers to a kernel, not the entirety of the programs included in a distribution.
      4. The 'Windows' category does not include programs by MS that would need to be included to make the comparison valid vis-a-vis the programs included in the Linux distros.
      5. The comparison includes 'reported' bugs. So, we're comparing reports from a host of people who do this for linux, versus a 'closed' company like MS who seems to believe in 'security through obscurity'.

      As a result, even though this may not have been intentionally skewed in Microsoft's favor, it certainly gives the appearance of same.

      This is why the adages about statistics exist. You can collect your numbers and publish them, but if you compare apples to oranges, your numbers are invalid by definition.

      This has nothing to do with whether I use MS or Linux. In fact, I use Opera instead of IE, but if you look inside my house, you won't find an installed distro of Linux anywhere.

      So you thought you saw bias and assumed it was fact. Therefore it was. Get a life yourself.

    4. Re:Oh, boy. Just another example... by Anonymous Coward · · Score: 0

      Yes - 68% of all statistics are just made up.

  12. Simply put, by Andorion · · Score: 3, Insightful

    Simply put, the reason Windows systems seem more vulnerable is because SO MANY MORE people use them, and don't keep them patched. As a rule of thumb, someone running Linux at home knows what the term "security vulnerability" means and keeps his system up to date, where someone running Windows whatever doesn't.

    Of course, that's not the case in the server market. If you want to talk about worms, remember one thing - the ONLY reason Code Red and other such worms exist is because of the popularity if the windows platform, on desktops and servers. Don't kid yourself for a second into thinking that the reason there aren't any widespread worms for *nix systems is because it's more secure.
    br -Berj

    1. Re:Simply put, by Anonymous Coward · · Score: 0

      When presented with a FACT that doesn't jive with your reality wish list, you shouldn't try to explain it away. That's intellectual dishonesty, Andorion.

    2. Re:Simply put, by FortKnox · · Score: 2, Troll

      You are correct, but this opinion will be drown in the sea of "No way! M$ sucks!" replies (and when slashdot posts a troll like "Windows is better", it gets about 400 replies). Its funny how people back security focus when it talks about MS vulnerabilities, but once it mentions Linux, they are "Uniformed" or a variety of other things (just read from any other thread to see what I mean).

      What's the definition of a Zealot??

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    3. Re:Simply put, by Drestin · · Score: 1

      You should take your own advice. Those numbers are facts, maek your opinion on what they mean but by simple count there are more vulnerabilities in linux distribs than on W2K/NT - deal with it. Your post is known as sour grapes.

    4. Re:Simply put, by joshtimmons · · Score: 5, Informative

      Actually, there aren't SO MANY MORE windows servers on the internet than *nix boxes.

      Please see this fine article http://slashdot.org/article.pl?sid=01/07/13/124025 7&mode=thread which tries to compare the number of windows systems vs unix systems on the internet.

      Here are a couple of their conclusions:

      1. GNU/Linux is the #2 web serving operating system on the public Internet (counting by IP address), according to a study surveying March and June 2001
      2. GNU/Linux is the #1 server operating system on the public Internet (counting by domain name), according to a 1999 survey of primarily European and educational sites.
      3. GNU/Linux is the #2 server operating system sold in 1999 and 2000, and is the fastest-growing.

      Even taking the statistics most favorable to Microsoft, they had almost twice as many IPs on the public internet than Linux did in 1999. However, during that same period, there were many more than twice as many expoits, viruses, etc. that attacked windows vs unix.

      Linux has far too many installations on the public internet to be dismissed as too rare to interest hackers.

    5. Re:Simply put, by greenfly · · Score: 2

      But your comment seems to imply that IIS is more widely used than alternatives. It seems that a lot of people get confused between the market share Microsoft has in the desktop market, with the server market.

      Now whether IIS admins don't patch their machines or not is a different matter, but a simple trip to netcraft will show you that Apache is deployed about twice as much. That seems pretty popular to me.

      It seems that things like Code Red existed because of the severity of the security flaw, and the how easy it was to infect and spread. The recent security flaws in Apache, on the other hand, have been very minor.

      So why exactly do you think that IIS is more popular?

    6. Re:Simply put, by Rupert · · Score: 5, Insightful

      l10n and ramen were two recent worms that attacked a bug in some versions of BIND on almost all unices. This would appear to be evidence against your theory that "no-one writes worms for *nix because of lack of market share".

      Find another excuse.

      --

      --
      E_NOSIG
    7. Re:Simply put, by Anonymous Coward · · Score: 0

      Yes, that was my point... Linux has more security problems than Windows according to SecurityFocus, this is a fact. I'm not a Linux bleater...

    8. Re:Simply put, by zulux · · Score: 2

      the ONLY reason Code Red and other such worms exist is because of the popularity if the windows platform

      Apache has twice the market share of Windows IIS - and has half the exploits. Take a look at the Netcraft uptimes at http://uptime.netcraft.com/up/today/top.avg.html . Notice any thing?

      There is A SINGLE WINDOWS SYSTEM in the top 50. Why? Beacuase Windows crashes and beacuse Windows has security problems. The rest are all a form of *nix. Nice and stable and secure.

      --

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

    9. Re:Simply put, by mvdwege · · Score: 4, Insightful

      Its funny how people back security focus when it talks about MS vulnerabilities, but once it mentions Linux, they are "Uniformed" or a variety of other things

      In a word: Bullsh*t.

      Securityfocus presented the numbers without bias, without commentary even. It is the MS shills that try to draw conclusions from these numbers, and one by one they take the aggregate Linux number, because it suits their agenda.

      However, that aggregate number is worthless to draw conlusions from. At most one could use the distro numbers to draw the conlcusion that the average Linux distro ships with more (potential) vulnerabilities than Windows 2000. Of course, since the average Linux distro

      1. ships with more server software than Windows (multiple mail servers for example),
      2. has a habit of reporting all vulnerabilities, from local DoS to remote root,
      of course it will show more vulnerabilities.

      So, the numbers tell us nothing new, except that the MS apologists will grasp at any straw to discredit what little competition they have.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    10. Re:Simply put, by jargoone · · Score: 1

      He didn't say server. He said system. That counts desktop systems.

      Thanks for playing.

    11. Re:Simply put, by Afrosheen · · Score: 2

      Check your links. There was not one single Windows server listed, they were all IRIX, FreeBSD or BSD. Personally, the uptime on my apache box serving 6 real domains is 96 days.

    12. Re:Simply put, by Anonymous Coward · · Score: 0

      Now that is funny. If it's not the official dictionary definition, it should be. And it should include a picture of Stallman to really get the point across.

    13. Re:Simply put, by SilentChris · · Score: 2

      Under the basis that most workstation now *act* as servers (whether intentionally as Unix machines or unintentionally as Windows machine with sharing turned on), one should assume that the number of Windows machines on the net, in general, is the most important statistic.

    14. Re:Simply put, by jamwt · · Score: 1

      You are correct, but this opinion will be drown in the sea of "No way! M$ sucks!" replies

      Is anyone else getting tired of easy karma-whoring by continuing to hammer slashdot on the bias issue?

      Yes, the vast majority of slashdot users are linux advocates. But in case you haven't noticed, your wild-eyed call for fairness has been said.

      I believe you will find those linux advocates among us have taken a certain sensitivity recently to blind evangelism and unreasonable Microsoft bashing.

      Most of the responses here seem to be very even-handed and considerate. They pertain specifically to what has been presented in this particular story, and not the entire body of the documented history of MS-Linux flamewars.

      And it's all due to gentle, kind pleas for impartiality from concerned individuals like yourself. Thank you!

      In the future, I will be using my moderation points to mark such postings as "troll" and "offtopic"; they are both!

    15. Re:Simply put, by FortKnox · · Score: 1

      Is anyone else getting tired of easy karma-whoring by continuing to hammer slashdot on the bias issue?

      Heh. Easy Karma Whoring you say??
      Easy Karma Burning is more like it.
      I'm not bringing up biases; I'm bringing up elitism and zealotry.

      Elitism: I'm sick of people saying "Linux is great" then when people talk about making it mainstream, immediately they say "No!". They love linux being small, and love that they are in the 'select few' communities that can understand it.

      Zealotous: Linux is Good, Windows is bad. Yet, the last time they use windows was Windows 95 before OSR2. Then they comment on articles like these about security issues they've only read from a biased news source (yes, I agree slashdot is biased, but that's not what I attack).

      When I read Taco's posts (not article comments, but posts), he's a true advocate of Linux. There are quite a few advocates still on here. They love linux, don't care what MS is doing (or care, but doesn't bash), understand the idea of "Use the tool that works best for the situation", and aren't angry or violent. Then there are the rest: Elitists, Zealots (both can be for either OS, mind you), Trolls, Crapflooders. I will continue bringing these posts up when I see it happen a lot in one article. And don't worry, I get modded down eventually. Keep in mind, I'm not a "windows lover", I'm just anti-zealot/elitist. I also rant about it in my journal, and see that many people share my opinion. The only karma whoring happening, is your disagreement to my post.

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    16. Re:Simply put, by jamwt · · Score: 1

      Heh. Easy Karma Whoring you say?? Easy Karma Burning is more like it.

      Incorrect. At the moment, your post is rated 3.

      If slashdot readers are truly biased, why are they modding your post up?

      Have you really contributed anything useful or new by whining about the horror of slashdot impartiality? Or have you just contributed to your points?

      Hint: your post is modded up because slashdot readers are careful to avoid insensitivity and partiallity. Not because you've really said anything new or useful.

    17. Re:Simply put, by FortKnox · · Score: 1

      I hit the karma cap WAAAY before I started posting about elitists/zealots. I'm currently at the cap, but I'm sure it has more to do with the articles I've submitted (check hof). I'm sorry you think I haven't added something. Eventually, I hope the community will change the way they post, and I feel I will have added something very big.

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    18. Re:Simply put, by llamalicious · · Score: 1

      That's fine on the server side, as this article is primarily concerned, that said... IIS (a "server" component) is available in the desktop arena of MS. (See Win2K Pro/Win XP Pro)
      If you count PWS (installed with Frontpage/Office) then add Win95, 98x, ME etc. to the mix.

      Furthermore, I know a lot of "developers" who use MS Server products (NTS, 2KS) as their primary desktop OS due to limitations of the WKS/Pro versions. So it's not just an ISP-hosting/business-server problem.

      We are still talking a significant number of open systems.

      And another /.er pointed out however, their method of counting is, primarily, wrong. Counting the same kernel bug or Bind hole for each distro is wrong, if not criminally insane.

      This isn't to say the linux distros don't have holes, they do, and yes, they make nice targets for black hats, but in this case Windows is to Linux as an unlocked car with the removable in-dash cd-changer is to the locked Chevette with the push-button AM only radio.

      I've been informed to watch my step as I get off my soapbox. :)

    19. Re:Simply put, by Anonymous Coward · · Score: 0

      yep. i'm stupid. forgot my closing bold. forgot my preview too.
      -llamalicious DOH! feel free to mod down as (-1: Bad HTML)

    20. Re:Simply put, by Anonymous Coward · · Score: 0

      I work at an ISP in Calfornia where we have hundereds of co-lo's. You have no idea how wrong you are when you say "someone running Linux at home knows what the term security vulnerability means" . I wish I had a dollar for every customer that ran a defualt install of RH6.1 and wondered why they were hacked in a matter of hours. Don't get me wrong, MS blows but from a security standpoint, Linux aint much better. Go for OpenBSD, hands down the best.

  13. Statistics.... by Toby+Truman · · Score: 2, Interesting
    How valid are these statistics?

    Let's keep in mind that Linux users who find bugs or issues are far more likely to report them, document them, publicize them, and share them.

    Microsoft users who finds bugs call Microsoft tech support, who informs them politely that it's a feature, and lets the issue be stored deep in their databases somewhere.

    This is not an issue of who has more issues, but whose issues get reported and publicized more.

    1. Re:Statistics.... by Score+Whore · · Score: 1

      This is bullshit. No offense intended, but what support do you have for your theory? That's like saying that there isn't any descrepancy between the AIDS epedemic in Africa (> 25%) vs. North America (< 1%), it's just reported more in Africa.

      Major/minor security issues are well reported by third parties pretty much across the board. What's more people want to give MS black eyes. They actively search for problems there and when they do they wave their hands above their heads, jump up and down, hoot and holler, and in general try and get as much attention for themselves as they can. It's not a reporting issue. It's just one of those things about life. (ie. OS coders are often doing it out of curiousity and once that itch has been scratched and it's Good Enough(tm), they are "done" regardless of the actual state of their project.)

    2. Re:Statistics.... by Znork · · Score: 2

      The statistics are fairly accurate (altho you do have a point), but they're comparing basic Windows (the product) with Linux (the distributions).

      Add Windows, SQL server, some other RDBMS (many linux dists ship with multiple database servers), exchange, some other mailservers, etc until you replicate the functionality in a Linux dist. Then count again.

      Those SF statistics arent very useful, and SF has already several times basically said that anyone trying to read them the way that WinInformant seems to have been doing has a fairly faint grasp on reality.

    3. Re:Statistics.... by IntlHarvester · · Score: 4, Insightful

      Let's keep in mind that Linux users who find bugs or issues are far more likely to report them, document them, publicize them, and share them.

      Good point, but it would be better if you took it out of the context of the "users" and put it in the context of the developers. It works out more like this:

      Open Source Project X Developer (who may well be on someone's payroll) finds a previously unknown security bug. He patches the bug and informs RedHat and other distro vendors, who then issue a security bulletin. One strike against Linux in the security count.

      Meanwhile Microsoft Product Y Developer finds 100 unknown security security bugs in his big Feburary cleanup period. They are all rolled in to service pack 3. Microsoft issues a bulletin recommending all customers upgrade immediately. Zero strikes against Microsoft.

      So you are counting ALL security bugs on the Linux side verus only publically reported security bugs on the Windows/Solaris/whoever side.

      (Furthermore, it seems nobody considers local root exploits on Windows to be that big of a deal. I remember when RedHat put out multiple advisories for vi, joe, ed, and a bunch of other editors for a temp file vulnerability. [You'd think that "ed" would be rock solid by now...] Would that sort of thing even be considered a bug on the Windows side?)

      --
      Business. Numbers. Money. People. Computer World.
    4. Re:Statistics.... by Anonymous Coward · · Score: 0

      > Would that sort of thing even be considered a > bug on the Windows side?

      Well, on win9x there is no 'root' exploit,
      because everything already runs as root...

  14. ??? by toolo · · Score: 0

    Just because there are vulnerabilities in joeblow3rdparty software means Linux, as a kernel is more insecure? Pretty funny, considering I still have Nimda spiders hitting every box I see.

  15. How severe though? by oregon · · Score: 2, Insightful


    Linux may have had more, but were they as bad?

    The IIS holes in 2K that allowed CodeRed to spread and the uPnP holes in XP which, luckily so far, have been pretty much unexploited were both buffer overrun holes which caused, or had the potential to cause, v.serious work outbreaks.

    Did Linux have anything on this scale?

    --

    ---
    Oregon
    1. Re:How severe though? by Hoonis · · Score: 1
      The IIS holes in 2K that allowed CodeRed to spread and the uPnP holes in XP which, luckily so far, have been pretty much unexploited were both buffer overrun holes which caused, or had the potential to cause, v.serious work outbreaks.

      Did Linux have anything on this scale?

      Yes actually, if you're running an unpatched older distribution that had either the bind, wu-ftpd, ssh, lpr, or a couple other bugs, I bet you'll find some odd net connections and irc bots on your system.. the activity level of probes looking for linux holes (just like the automated IIs worms) is increasing dramatically. Check CERT for the details

  16. There goes the Slashdot Neighborhood by BRO_HAM · · Score: 2, Insightful

    Oh man, I can hear the keyboards typing right now. One thing you don't do to the slashdot community on a monday morning is call their OS less secure than windows.

    On a side note, it's all about how you configure your OS. At this point, you can pretty much do the same thing with each OS from a security standpoint. It's all of the other software that usually does it - web server, DB server, application server, etc. But we all know this right?

    --


    my sig is so witty and fun - it tickles almost everyone who reads it.
  17. You know what they say... by Eagle7 · · Score: 1

    "Lies, Damned Lies, and Statistics."

    --
    _sig_ is away
    1. Re:You know what they say... by Anonymous Coward · · Score: 0

      Funny I thought it was "Lies, Damned Lies, and Metrics"

      Oh well so much for those Software Engineering classes.

  18. Lousy research by JanneM · · Score: 3, Interesting

    His mathematics is pretty bad. To get the security problems for Linux, he adds all security announcements from each of the major distributions - completely ignoring that most of those announcements are for the same bug. The Linux number is thus about a factor 4 too high.

    Also, the Windows announcements are for the OS itself only, while the Linux announcements cover programs that do not count as OS stuff under Windows.

    Badly researched piece.

    /Janne

    --
    Trust the Computer. The Computer is your friend.
    1. Re:Lousy research by orkysoft · · Score: 1

      I recall having read on Slashdot about a statistics report where the researchers made exactly the error you're describing: counting the same hole in two distros twice.

      --

      I suffer from attention surplus disorder.
    2. Re:Lousy research by Florian+Weimer · · Score: 2

      And the argument that you would expect less security holes in GNU/Linux systems because they are not as widely deployed as Microsoft-Windows-based systems is not convincing at all. Security vulnerabilities are there even if hardly anybody uses the piece of software inquestion.

    3. Re:Lousy research by Col.+Panic · · Score: 2

      Also they capitalize on the fact that Redhat major release versions at x.0 are untested in the field. x.1 is somewhat patched and x.2 is near rock-solid. Of course they only mention those first 8 months of 2001 because 7.2 was released in 10/2001.

    4. Re:Lousy research by mpe · · Score: 2

      His mathematics is pretty bad. To get the security problems for Linux, he adds all security announcements from each of the major distributions - completely ignoring that most of those announcements are for the same bug. The Linux number is thus about a factor 4 too high.

      Wonder how impartial an entity called "wininformant" is likly to be in the first place?

      Also, the Windows announcements are for the OS itself only, while the Linux announcements cover programs that do not count as OS stuff under Windows.

      Even with Microsoft's creative definition of what makes up an "operating system".

    5. Re:Lousy research by dup_account · · Score: 1

      I agree. This, to me is one of the two most important points. The other being about the severity of the bugs. I think a really really interesting number would be the cost that each security vulenerability has cost. Using the same standard that companies use when they complain about piracy, I would estimate that M$ vulenerabilities have cost billions vs low millions for linux.

      Another thought, How many of the problems are with default configurations vs properly configured? I believe that some of the Linux distributions had problems with lax default security, but could be tuned up for much better security

    6. Re:Lousy research by Anonymous Coward · · Score: 0
      His mathematics is pretty bad.
      Your english are pretty bad.
    7. Re:Lousy research by Anonymous Coward · · Score: 0

      The other weird part about this is that all the Linux stats (at least the way he refers to them in the article) are aggregated while 98 and NT are listed seperately.

      It just seems like this dork had a bone to pick, saw what he thought he wanted to see on SF, and ran off with it.

      So what?

    8. Re:Lousy research by cyclist1200 · · Score: 2, Insightful

      "Also, the Windows announcements are for the OS itself only, while the Linux announcements cover programs that do not count as OS stuff under Windows."

      The funny things is the journalists get all indignant when you point this out to them and ask them to throw in the security holes for IIS, IE, OE, Office, SQL Server, etc.

    9. Re:Lousy research by Stipe · · Score: 1

      Indeed. Just like trying to measure the quality of a product by counting the number of bugfixes that have been released. Poor quality programs may not have bugs fixed/ tracked, high quality programs do.

    10. Re:Lousy research by cyclist1200 · · Score: 2, Funny

      >>>Even with Microsoft's creative definition of what makes up an "operating system".

      LOL. I can just hear MS PR:
      "All Microsoft software products are inextricably tied to the operating system...except when they are mentioned in a security announcement."

    11. Re:Lousy research by cyclist1200 · · Score: 1

      His mathematics is pretty bad.
      Your english are pretty bad.

      If that's the best you can come up with, your logic is pretty bad.

    12. Re:Lousy research by tongue · · Score: 0, Flamebait

      No, dumbass, your grammar is poor; mathematics is a singular concept, not plural, thus requiring "is" as opposed to "are".

    13. Re:Lousy research by wizkid · · Score: 1


      I wouldn't say it's lousy research. Winformant is a Microsoft FUD site. I'm sure they went out, counted all the bug reports for There one version of windows, and compared it with every distribution of Linux. They've announced several times over the last year that Linux is there #1 enemy. They are a FUD based company, so this is thier way of attacking Linux.

      Note: As many of you know already, winformant has been slashdoted, so I can't see the original article. I've seen other articles from there site in the past. They've all been FUD type articles in the past, so I'm going to brashly ASSume that this one is also.
      W.Kid

      --
      I take no responsibility for what I say. Even though I'm never wrong :)
    14. Re:Lousy research by Anonymous Coward · · Score: 0

      From M-W.com:

      Main Entry: mathematics
      Pronunciation: "math-'ma-tiks, "ma-th&-
      Function: noun plural but usually singular in construction
      Date: 1581
      1 : the science of numbers and their operations
      ...

      Usually singular in construction, but the formal function is plural.

    15. Re:Lousy research by Asic+Eng · · Score: 3, Interesting
      What I don't get is this: this exact same miscalculation was already in an article referred to by slashdot, about a year ago. Neither slashdot nor the writer of the article seem to have learned anything... I'm somewhat surprised that the slashdot editors didn't point out that mistake right away. It also seems strange that Security Focus would still publish these "aggregate" numbers - they seem to only confuse people, and I don't see what sense these numbers would make?

      Anyway, what I found interesting is that Redhat faires so badly - about as bad as Win2k, and about twice as bad as any other Linux distribution. If SuSE has only 21 tracked bugs, and comes with a lot of software (7 CDs now, I think) is Redhat with 54 entries doing something wrong?

    16. Re:Lousy research by Anonymous Coward · · Score: 0

      You should talk. Take a (close) look at your sig. "Its" does not mean "It is."

    17. Re:Lousy research by TheAwfulTruth · · Score: 2, Flamebait

      If you were a regular reader of that site you'd notice that he does a fair amount of MS bashing when they deserve it. And he priases them when they deserve it. He does the same for Apple and Linux too! Unlike Slag-dot here where a middle of the road, honest observation is always treated with a -1 moderation.

      --
      Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
    18. Re:Lousy research by firebat162 · · Score: 1

      windows announcements are for the OS itself only? what about IIS? about IE? do those count as 'OS only'? Aren't those where most of the vulnerabilities come from?

      they're talking about the whole system.

    19. Re:Lousy research by RedGuard · · Score: 1

      I thought releasing beta ("untested in the field")
      software was a Microsoft practice. Why is an
      excuse for Linux vendors?

    20. Re:Lousy research by Col.+Panic · · Score: 1

      Actually, Redhat has started releasing beta versions, I believe. I would never deploy a Redhat x.0 release in production, for the reason above. However, I also would never deploy a Microsoft operating system the first year it is released, so ...

    21. Re:Lousy research by spectecjr · · Score: 1

      The funny things is the journalists get all indignant when you point this out to them and ask them to throw in the security holes for IIS, IE, OE, Office, SQL Server, etc.

      I've seen more Linux users get indignant when you count a sendmail bug as a Linux bug than the other way round.

      "Linux is just the kernel!" they shout.

      Really? Well, I guess Windows is just the kernel too.

      Simon

      --
      Coming soon - pyrogyra
    22. Re:Lousy research by KevCo · · Score: 1

      I get his newsletter and I agree that he does tend to slam MS quite a bit and he will occasionally praise Apple and Linux (more often Apple, not so much Linux). But he will very often take jabs like this at Linux with biased, skewed, or otherwise incomplete facts. I get the feeling that alot of it is just pushing back at the slashdot-type MS bashing that is so prominant these days.

      Nevertheless, I wouldn't put too much weight in this little article. His newsletter is great for those of us working in an MS world, it helps keep me informed in the latest MS news the way that slashdot keeps me up to date in everything else (well except Novell...slashdot needs more NetWare articles =P ) but I wouldn't give any more credence to his opinions that I would the typical slashdot flamewar.

    23. Re:Lousy research by Charles+Dexter+Ward · · Score: 1

      The issue with red-hat is that almost always they find the bugs first, or is done by a red-hat user. So red-hat has more security warnings.

    24. Re:Lousy research by Anonymous Coward · · Score: 0

      Ay-men. Thank you.

    25. Re:Lousy research by Anonymous Coward · · Score: 0

      and poorly written english...

      Its wierd, I can notice something as arcane as using the phrase "badly reasearched" but I can't learn a foreign language for the life of me.

      strange.

    26. Re:Lousy research by Anonymous Coward · · Score: 0

      "I believe that some of the Linux distributions had problems with lax default security, but could be tuned up for much better security "

      Oh, you _believe_ ?
      Is that right ?
      Nobody gives a flying fuck what is that you believe ...
      Stupid Linux troll.

      Thank you for you time.

  19. All stock OS'es? by soupforare · · Score: 1

    Do they mean out-of-box?

    (the site's been slashdotted already)
    If so, than that's stupid, no Sysadmin worth his salt would leave a machine without proper updates/securing.
    An workstation/server is only as secure as you want it to be, that's it.

    --
    --- Do you believe in the day?
    1. Re:All stock OS'es? by shaunbaker · · Score: 1

      the same could be said for any user with a win2k box. you must remember that the intellegence of the user base is the primary reason for linuxs higher apparent security. virus writters dont want to target thier "elite" os but are just happy screwing with families who run their windows machines and are unaware of patches and the need to apply them. on the matter of msft not releasing the exploits until they are fixed (like UPnP) would you have prefered they release the bug and ask for exploits or hurry to fix it before it is exploited. although i do understand that an annoucement without the bug fix would be much more fun for the usual slashdot bashing

  20. it's not the OS stupid by SpacePunk · · Score: 1

    It's the administrators. If you have someone administrating either OS that's incompetant then you will have security holes. A competant administrator will close up either OS tight.

    -

  21. Redhat!= Linux by gmack · · Score: 1

    This should be a wakeup call to RedHat to fix their distro. They are making everyone else look bad.

    It's time to get rid of apps with bad security records. This means you Bero!

    1. Re:Redhat!= Linux by ^me^ · · Score: 0

      But RedHat's insecurities exist in most other distributions. RedHat also fixes these bugs fairly fast.

      Sure, RedHat has had screwups, but it's more the default-install weenies that come over from the M$ world that are the insecurity problem than the OS itself. Don't blame either RedHat or M$ for their users.

      Mandrake is slowly gaining newbies more than RedHat. That said, Mandrake is going to be more insecure in your view as less and less bother with updates. Sounds fishy to me.

      --
      No one ever says, 'I can't read that ASCII E-mail you sent me.'
  22. Vulnerabilities vs Exploits by MasterOfErm · · Score: 1

    Perhaps a better statistic to look at if you're interested in which is more secure is the actual number of boxes which were exploited... and I'd guess that last year the windows machines win that category by a landslide.

    Of course, it all comes down to the admin in the end, so any talk of which OS is more secure doesn't really mean much. A clueless admin on a very secure OS can still open the gates wide to anyone that tries.

    1. Re:Vulnerabilities vs Exploits by Archanagor · · Score: 2, Insightful

      Well, no offense, but: "Duh!" Of coruse alot more Windows-based machines were exploted. You've got 2 very good reasons for this:

      1) Wide distribution. Yep. Contrary to your belief, Windows is distributed more widely than Linux. So, of course more boxes will be hit.

      2) Idiot users. I mean, lets face it, There's a reason why most windows users aren't on Linux. They're morons! Anyone and I mean anyone that runs an attachment from someone they hardly know that's written in worse english than a retarded 7 year old would write deserves what they get. Unfortunantly, they're the reason the network was clogged with NIMDA. Code Red was more a result of wide spread use of IIS.

      Gawd, I'm sick and tired of the linux bigotry around here. Linux is great and all, but I sure wouldn't want to join a group of the most closed minded bigots in the world, just to have the privelege of using a free OS that's actually pretty decent. I think I'll stick with Windows. Monopoly and all. You people are doing Linux a great disservice. Don't get me wrong, I like Linux, but it doesn't serve my needs as a desktop OS. Maybe instead of basing MS someone could make it more useful for the masses?

    2. Re:Vulnerabilities vs Exploits by heptapod · · Score: 1

      It's simpler to bash MS users for being stupid, it helps keep their minds closed from using something that may actually teach them something and introduce them to alternatives.

    3. Re:Vulnerabilities vs Exploits by Archanagor · · Score: 1
      I think you overestimate the vast majority of the people on this planet. Just drive through dallas for a few minutes, and you'll understand :)

      Anyway, all bashing aside. Would you run a screensaver that was attached to a message that read:

      How are you ?
      When I saw this screen saver, I immediately thought about you
      I am in a harry, I promise you will love it!

      Upon seeing this from a well-known person in the company, and knowing they were fluent in the english language, I decided that I'm not taking chances with the cute little screensaver. Five minutes later... My e-mail is crapflooded and the network is grinding to a halt. Why? Because there are people out there gullable enough to fall for it.

      Is it a security hole in Microsoft's software that lets users dig themselves into a nice deep pit, or, is it just simply a user that should know better, but apparently doesn't?

      Blame the source, not the messenger.
  23. Number of bugs is the wrong metric! by Victor+Danilchenko · · Score: 3, Insightful

    What matters is not how many bugs there have been, but the total window of vulnerability per bug -- the time elapsed from bug's discovery to bug'a closing. One really bad bug that remained open for a year is much worse than 10 bugs each remaining open for a week, you see.

    --

    --
    Victor Danilchenko

    1. Re:Number of bugs is the wrong metric! by Anonymous Coward · · Score: 0

      The "$" is the correct metric, or manhours, or whatever. If Application XYZ is not an industry wide application, the "$" factor is very low. Now, if it's UPnP...

  24. Eye of the beholder by Lothar · · Score: 1

    It's all in the eye of the beholder. Especially if you have a borg eye. hehehe.
    They can't be serious!

    Lies, lies, and damn statistics! You can always manipulate numbers. I suspect they have a different idea of vulnerability and seriousness than the rest of us.

    But we know by ourselves that linux is better and we strive every day to make that happen. Keep that in focus and don't let this bother you at all.

  25. There might be some reasons by Tompie · · Score: 1

    In my opinion, the reason for this is that Linux is more used in a non/less-commercial way than WinNT/2k.
    WinNT/2k admins have money to buy that OS, so I suppose they also have more money/time to spend on security (and use it in a more professional way).
    Some linux boxes on the other hand are "hacked" together, and thus not always secure. Maybe the popular fact that "linux is more secure than windows" makes them believe they are not vulnerable.

    1. Re:There might be some reasons by Lumpy · · Score: 2

      n my opinion, the reason for this is that Linux is more used in a non/less-commercial way than WinNT/2k.
      WinNT/2k admins have money to buy that OS, so I suppose they also have more money/time to spend on security (and use it in a more professional
      way).
      Some linux boxes on the other hand are "hacked" together, and thus not always secure. Maybe the popular fact that "linux is more secure than
      windows" makes them believe they are not vulnerable.


      are you nuts? anything "hacked together" in a business is asking for trouble and will get you fired. the difference between the NT machines and the linux machines in business are pretty much identical... I wouldn't call running redhat 7.2 on a Compaq ML530 "hacked" together. I would call running a fileserver on a old desktop that the company was going to throw away hacked together, but then it will also fail because the hardware cant handle the load you are about to put on it... I.E. acting as a server. as a desktop it's perfect.

      Sorry, but companies dont run around screaming about what they use, or place banners on the front of the building.. they use it and use it quietly.
      and Linux is in more commercial use than you think or any "survey" can report. I have had these surveys call me, I tell them "that is secret information, no comment." to everything they ask. It's none of their damned business as to what is giving my company a major edge over everyone else.

      --
      Do not look at laser with remaining good eye.
    2. Re:There might be some reasons by Tompie · · Score: 1

      The only thing i can say to that is that i know a lot more "ordinary" people who run a Linux server (apache server or whatever) than people run a Windows server at home. (and "ordinary" people don't look for security fixes every day)

  26. Unfair comparison, uninformed journalist. by opkool · · Score: 3, Redundant

    After reading the whole thing, I came to the conclusion that this is an unfair comparison:

    -They only count bugs for one Microsoft OS product. I mean, there's Win95, Win95osr2, Win98, Win98SE, Win2000, WinME, WinCE, WinNT4.0...

    -They count one bug for each distribution. I mean, if a bug is detected on rsync, it shows as one different bug for every distribution, that is, one but for Mandrake 7.0, one for Debian, one for Mandrake 7.1 ...

    So, this makes me wonder if the journalist is plainly uninformed or if has no idea of what he is talking about (a laid-off journmalist from the gardening section re-hired for a tech-writter position).

    The conspiracy theories, black helicopters and Microsoft-payed journalists, from my point of view, do not apply here.

    Well, who said the world was fair?

    1. Re:Unfair comparison, uninformed journalist. by Anonymous Coward · · Score: 0

      Yeah, but this occurs just about every year from the windows journalists. It gets old and this is not even worth giving hits to the site for it. The funny thing is that with M$'s emphasis on security, it is possibile for M$ to catch up. But by then, nobody will believe these journalists becuase they are all busy crying wolf.

    2. Re:Unfair comparison, uninformed journalist. by Anonymous Coward · · Score: 0

      It's worse than that. If you look at the RedHat BugTraks entries, you'll notice that MySQL bugs are counted as OS bugs. If you look at the Windows BugTraks you'll notice that MS SQL server is not counted as an OS bug.

      If you add up all the Windows 2000, SQL Server, Exchange, IIS, and IE bugs and compare them to all the Linux Kernel+X11, Postgres, sendmail, Apache, and Mozilla bugs you'll see Windows is by far less secure.

    3. Re:Unfair comparison, uninformed journalist. by Drestin · · Score: 1

      I seriously doubt you read "the whole thing" because then you wouldn't have made such an uninformed post.

      The W2K/NT counts are for exactly that: W2K and NT4. There is a seperate category for W9x/3.x and that's seperate.

      All the distribs have their own counts but the aggregate does NOT include duplicates of the same vulnerablity (simple math would have proved that to you had you bothered).

      Your FUD and obvious bias obviously is the rule of the day here but couldn't you at least get simple math right?

    4. Re:Unfair comparison, uninformed journalist. by Anonymous Coward · · Score: 0

      hey, rsync runs also under Microsoft, so
      Microsoft->bugs += 8
      :-)
      Win95: 1
      Win95osr2: 2
      Win98: 3
      Win98SE: 4
      Win2000: 5
      WinME: 6
      WinCE:7
      WinNT4.0: 8

    5. Re:Unfair comparison, uninformed journalist. by opkool · · Score: 5, Informative

      What I read was the original article before it went down by /.

      So worry for the thing on Win9x/3.x + WinNT/2000.

      So they are talking of Server OSes. So Win9x/3.x do not account as such.

      What you say is that, of course, they do not include duplicates of the same vulnerability. But then there's no such program as rsync-2.07-3.i386.rpm on Debian 2.2 . Can you see it?

      Also, why it is strangely coincidental de number of bugs for Red Hat Linux 6.2 for Alpha and Sparc? See:

      For 2001, we see:
      RedHat Linux 6.2 sparc - 18
      RedHat Linux 6.2 alpha - 18
      Debian Linux 2.2 sparc - 18
      Debian Linux 2.2 arm - 18
      Debian Linux 2.2 alpha - 18
      Debian Linux 2.2 68k - 18

      Coincidental? See it yourselves at SecurityFocus WebSite

      Maybe is a cross-architechture bug? Will this mean that, in fact, it is the same bug?

      Then the numbers for Mandrake, Red Hat and Debian are waaay too similar (2001) to be just a coincidence (Mandrake 7.1, Red Hat 7.0 and Debian 2.2 can be thought as "equal distributions" by means of timeline, packets versions and such):

      RedHat Linux 7.0 - 28
      MandrakeSoft Linux Mandrake 7.1 - 27
      Debian Linux 2.2 - 26

      Then, on 2001, we can assume that Red Hat 6.2, Mandrake 6.0 and 6.1 have the same package versions :

      RedHat Linux 6.2 i386 - 20
      MandrakeSoft Linux Mandrake 6.1 - 20
      MandrakeSoft Linux Mandrake 6.0 - 20

      And those numbers are also very very close to the ones for Red Hat Linux 6.2 on different architectures.

      Maybe, just maybe... they are the same bugs?

      Then, on previous years, the trend is the same.

      With all the respects, I am no FUDing here. I post my comments to some piece of news that was flawled.

      And I tried to explain why it was flawed. And I was vry carefull to not to blame conspiracy theories.

      Then, again, I'm human. And I make mistakes. Like the Win0x/3.x and Win2000/NT of my previous post.

      But this does not invalidate at all my message.

    6. Re:Unfair comparison, uninformed journalist. by jareds · · Score: 2

      What you say is that, of course, they do not include duplicates of the same vulnerability. But then there's no such program as rsync-2.07-3.i386.rpm on Debian 2.2 . Can you see it?

      Look, if you look at the big table, "Number of OS Vulnerabilities by Year," in the SecurityFocus stats, you will find (except for 1998, where they seem to have made a mistake) that the Linux aggregate number they list is less than the sum of the numbers listed for each Linux distribution. This is why your claim that they are counting duplicate bugs is dubious.

      Of course, you are probably correct that if there is an rsync bug they will count it in each distribution, but you can see that they do not simply add the numbers of all the distributions together to get the aggregate, so this is not a problem.

    7. Re:Unfair comparison, uninformed journalist. by Anonymous Coward · · Score: 0

      I can't believe this uninformed post is modded so high!

      I'll explain it at the kindergarten level. Bob has 10 toys, Alice has 8. Combined, Bob and Alice have 13 toys. How is this possible? Bob and Alice share 5 toys!

      The aggregates only count unique bugs, dude. Chill out.

  27. Something strange... by Xerithane · · Score: 2

    wininformant.com fails to resolve.

    SecurityFocus.com has absolutely nothing on their site about this article.

    I would find it at very best to be poor journalism to label an operating system more secure just based on the fact that it has less published vulnerabilities. First off, it's easier to locate vulnerabilities in *NIX software. Windows it isn't, mostly because it's closed up and the Windows common user is not motivated with finding a security exploit.

    If you look at the types, and severity (which I'm hoping the article does) of it and summise a judgement based off that I think it's pretty obvious which operating system is more secure.

    Either this is a /. troll, and they didn't bother to realize the DNS for wininformant.com doesn't exist, or wininformant.com is dead at the moment, or wininformant.com is a group of Microsoft FUD monkeys, or I'm running the wrong desktop OS.

    --
    Dacels Jewelers can't be trusted.
    1. Re:Something strange... by mpe · · Score: 2

      SecurityFocus.com has absolutely nothing on their site about this article.

      Somehow this dosn't suprise me

      I would find it at very best to be poor journalism to label an operating system more secure just based on the fact that it has less published vulnerabilities.

      This isn't actually journalism it's a type of political properganda.
      Involving selectivly quoting an impartial third party...

    2. Re:Something strange... by cperciva · · Score: 2

      wininformant.com fails to resolve.

      I think we've managed to slashdot their nameserver. wininformant.com points at ns1/ns2.duke.com, and my traceroutes get stuck in a loop between s8-0-0.7513.den.iccx.net and Edge-Serial-1-1-Lov-CO.rmi.net.

    3. Re:Something strange... by jamie · · Score: 2
      "I think we've managed to slashdot their nameserver. wininformant.com points at ns1/ns2.duke.com, and my traceroutes get stuck in a loop between s8-0-0.7513.den.iccx.net and Edge-Serial-1-1-Lov-CO.rmi.net."

      It's not a slashdotting; the site went down shortly before Slashdot ran the story. I'd checked the link a few minutes before it went live, but we only confirmed it being down right as the story went up, so we couldn't take it back down again.

      Hopefully they'll have it fixed soon.

      If anyone cares, duke.com does provide their DNS and duke.com is currently unreachable. Duke.com also appears to provide a wide variety of Windows-related products such as magazines and email lists (according to Google's cache).

      Iccx.net is their upstream provider and iccx appears to have a router misconfigured or something. And not that it matters, but...

      $ HEAD 'http://www.iccx.net/'
      200 OK
      Cache-Control: private
      Connection: Keep-Alive
      Date: Mon, 04 Feb 2002 17:05:58 GMT
      Server: Microsoft-IIS/4.0
      ...

      Unfortunately, I can't find the original story anywhere in Google's cache. Sorry.

    4. Re:Something strange... by cperciva · · Score: 2

      It's not a slashdotting; the site went down shortly before Slashdot ran the story.

      Maybe they got scared and preemptively shut down their servers as soon as they saw a request come in from slashdot's IP range?

  28. flawed logic by esme · · Score: 2, Insightful
    When you break the numbers down by Linux distribution, Win2K had fewer vulnerabilities than RedHat Linux 7.0 or MandrakeSoft Mandrake Linux 7.2

    And this is exactly the kind of flawed logic that always creeps into these kinds of discussions: there is no "Linux" to compare with "Windows", there are only a bunch of distros. Totalling up all the holes in all the distros makes no sense at all.

    And when you compare Windows to a given Linux distro (much closer to a good comparison), Linux wins every time.

    -Esme

    1. Re:flawed logic by zzyzx · · Score: 0

      Read what you pasted. It says that Win2K had FEWER vulnerabilites than Red Hat7.0

  29. in a related story... by resonator · · Score: 1, Funny

    Scientists have discovered that internal combustion is cleaner and more efficient than anit-matter.

    1. Re:in a related story... by LinSux · · Score: 0

      What do you have against GWB? I'm a fan of yours, but if you keep up the liberal slander, I might have to ditch you.

      You hurt my feelings!

      Long live GWB and MS!!!

      --
      Slashdot. News for Zealots, Stuff that matters (if you're a linux zealot!)
  30. The more accurate question by Gothmog · · Score: 5, Interesting

    Pure quantity of security holes really is not the most question. To me there are two factors:

    1. How severe is the hole if exploited.

    Are we talking a DOS, a root compromise, the ability to take over a domain controller. The effect of a compromise needs to be taken into account.

    2. How easy to exploit is the whole.

    Is it a theoretical exploit, or are there tools floating around? Can it be easily mitigated by a good firewall, or can viewing an email cause the problem.

    These questions seem to me more important than pure quantity and should be taken into account when building a threat assesment of a system.

    1. Re:The more accurate question by SilentChris · · Score: 5, Insightful
      "These questions seem to me more important than pure quantity and should be taken into account when building a threat assesment of a system."

      Oh please. This is the same Slashdot that touted 30K bugs for Windows 2000 (like every other major tech publisher) regardless of the fact that the bugs were not known and many were probably "We spelled "maximize" wrong here".

    2. Re:The more accurate question by Anonymous Coward · · Score: 0

      You replied to a post from an individual, you didn't reply to "Slashdot" as a whole. Slashdot isn't a uniform lobby group, and he probably agrees with you that the W2K 30k bug count is meaningless. What's with accusing people of hypocrisy for something "Slashdot" said?

    3. Re:The more accurate question by sheldon · · Score: 2

      Actually I think the claim from Slashdot was 65,000 bugs. :)

      Ahh, yes here it is...
      http://slashdot.org/article.pl?sid=00/02/11/1840 22 5&mode=thread

      Slashdot would have claimed that Windows 2000 had 4 million bugs, but they used an unsigned short in their program and lost count.

    4. Re:The more accurate question by Oliver+Defacszio · · Score: 2, Interesting
      Because, in the Win2000 30k bugs article, there were immediately 100,000 zealots slobbering to jump in and agree with the "Slashdot opinion".

      It happens all the time around here so, yes, accusing Slashdot of hypocrisy is most often also correct on an individual user basis.

      --

      -
      Inventor of the term 'pardon my French'.
  31. To use bit of old wisdom.... by MxTxL · · Score: 1, Troll
    It's quality not quantity.

    Perhaps linux has a greater number of security flaws but Window's security flaws, while less in number, are much more serious, drastic and more devastating in terms of network infrastructure.

    Using a number to rate things like this is absurd.

  32. Yes and No--Security is time by dnoyeb · · Score: 1, Insightful

    Today security is measured in how long it takes you to break into a box, and not if you can break into the box. So on the one shoe, you can say windows is much more bombarded and patched than Linux because so many "testers" are willing to "test" the security of windows. But on the other hand, since security is measured in how long it takes to crack something, even though windows may end up with fewer holes, the fact is there are more "hole seekers" which effectively reduces the security.

  33. Learn to mirror the damn pages, Slashdot. by Xzzy · · Score: 0, Offtopic

    Two freakin' comments in this thread when I view it, and wininformant is already refusing connections. Shame too, cuz I got plenty to say on the subject but it's kinda hard to make informed statements when you can't even read the link.

    Suppose I could just base my post off the story submission like most other readers do, but nah, that'd be irresponsible. ;)

    /rant off

  34. Not being a Windows apologist by prisoner-of-enigma · · Score: 5, Funny

    But it is possible to have a very secure Windows environent. No, it does not involve turning the box off ;^)

    Take this example: you have a highly competent NT/2K administrator (they do exist) and a pitiful *nix administrator. Which one is going to produce a more secure box? Any objective person would have to say the NT/2K guy would, because he knows his platform well enough to shore up vulnerabilities. Nimda, I Love You, and many other worms did not hit affect my company because we took security very seriously beforehand. Malicious attachments (.EXE, .SCR, etc) were banned long before I Love You came along.

    Now, having played devil's advocate for a moment, let me say that if you have a tightly controlled *nix box with a competent admin and a focus on security, you can create a damn near impregnable system. The weaknesses then lie with the applications, not the OS, and that's something ALL vendors need to work on (you listening, Larry "Unbreakable" Ellison?)

    --
    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:Not being a Windows apologist by archen · · Score: 2, Insightful

      "Take this example: you have a highly competent NT/2K administrator (they do exist) and a pitiful *nix administrator."

      Every time someone brings this up I keep thinking it's sort of redundant. I guess, being a rather pitiful administrator in both respects; I find it easier to at least start locking down a unix box (FreeBSD in my case). With Unix you can tighten a box up instantly just by looking through hosts.allow (and hosts.deny in Linux's case) - it certainly doesn't take a genius to figure out what's going on. By contrast windows has a lot more to do with disabling services which (in my opinion) you're never sure what they do or if you need them. And sooner or later you'll end up fishing in the registry...

      To me Unix systems are easier to secure because security is a part of the system, and not an afterthought / "oh so we're getting bad press so we'll start an inititive" sort of deal.

    2. Re:Not being a Windows apologist by prisoner-of-enigma · · Score: 5, Interesting

      Microsoft certainly does little to help those of us trying to secure their systems. The knowledgebase is confusing when it comes to system hardening, and MS loves to ship their products with absolutely every feature and doo-dad turned on. It makes setting up a Win2k webserver such a pain in the ass, but over time we've compiled a checklist that makes things much easier. Much like Linux, we made the checklist with the input and experience of many others.

      Contrast this with a typical RedHat install. Sure, you can elect to not install a ton of stuff, but the dependencies can and will drive you nuts if you need widget-1.12-i386.rpm, which conflicts with Perl, glibc, and about ten thousand other things you don't want to fool with. Then couple that with the overwhelmingly nonexistent or conflicting/out-of-date documentation that is (isn't?) available for some Linux modules, and you're reduced to playing Sherlock Holmes again. And what do you do when the HOWTO doesn't answer your question? Posting in a newsgroup results in about 50% of the responses being "read the HOWTO you fucking l00ser", 40% being wrong/misinformed/don't-know-either responses, and only 10% being useful and helpful.

      What both Windows and Linux need is a "Secure" install option that by default has nearly everything turned OFF, and then a simple way to add/enable functionality as needed. Templates for webservers, DNS, FTP, mail servers, and such would be great, and they should keep pace with patches and updates for the OS and related applications. Why no one has bother to do this is beyond me, but I think this laziness has resulted in 90% of the exploits seen in ALL OS's on the web.

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    3. Re:Not being a Windows apologist by tarogue · · Score: 1

      Actually, Red Hat 7.2 (and maybe 7.1, but I don't remember,) already does this this. If you install as a Workstation, most server daemons aren't even installed.

      --
      Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
    4. Re:Not being a Windows apologist by prisoner-of-enigma · · Score: 2

      True, it won't install many server daemons, but it will install a ton of desktopware (XWindows being a primary offender) that is not needed for a server and poses a HUGE security risk in and of itself. Desktopware isn't usually tested to the same level as server stuff, and only a fool would trust it.

      No, they need a "Secure Install" option that further asks if you're making a webserver, DNS, FTP, etc. and will set the machine up appropriately with the most stringent security settings. I'd much rather have a list of security to TURN ON in order to enable some function than a list of things to TURN OFF to make my system more secure. In the former case, it may take me a bit to get the functionality I want, but I probably won't compromise the security. The latter means I can get the functionality immediately but the security is never even mentioned.

      --
      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:Not being a Windows apologist by coene · · Score: 0

      "With Unix you can tighten a box up instantly just by looking through hosts.allow (and hosts.deny in Linux's case) - it certainly doesn't take a genius to figure out what's going on."

      For the record, windows servers arent used, let alone even allowed in our datacenter, but your example of proper security (hosts.allow) isnt even the tip of the iceberg when it comes to securing a *nix system. I do a lot of work with Linux and *BSD and its never that easy. Even if your running a simple web server, having a properly tuned httpd.conf is a requirement, let alone all other applications, system security (user scheme, file locations and permissions, execution rights, partitioning schemes, etc). If you think a hosts.allow file is all you need to secure your system, think again. And this IS transferrable to a Windows system. A good Windows sysadmin will disallow filetypes and remove all of the M$ provided vdirs in IIS, and do everything thats needed to meet the fundamental basics of a secure platform.

      What it comes down to is for whatever platform your running, have a systems administrator that knows what they are doing. Nothing comes secure out of the box (though OpenBSD is damn close!!)

    6. Re:Not being a Windows apologist by InfoSec · · Score: 1

      Mandrake has this option. If you install with either the 'high' or 'paranoid' security levels, the installed services are installed with very tight restrictions. In fact, at high and paranoid, sshd will not allow remote root; apache does not allow CGIs; local root login is denied(paranoid only); etc... Not too shabby.

      --

      Wherever you go, there I am...
    7. Re:Not being a Windows apologist by prisoner-of-enigma · · Score: 2

      Mandrake is one of the distros I have yet to try. Based upon your comments, I think I will.

      Thanks!

      --
      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:Not being a Windows apologist by llin · · Score: 1

      The mindset you describe is exactly that of OpenBSD. Say what you will about Theo as a person, but for out of the box security, OpenBSD is hard to beat.

      My current preference for Linux is to install a Debian minimum install and apt-getting or compiling exactly what I want. There's a bit more work involved (setting up PAM, logins, wheel, netfilter), but I prefer the certain things about Linux better (apt-get, ReiserFS and /proc among other things) .

    9. Re:Not being a Windows apologist by Buckaduck · · Score: 1
      But it is possible to have a very secure Windows environent ... Nimda, I Love You, and many other worms did not hit affect my company because we took security very seriously beforehand. Malicious attachments (.EXE, .SCR, etc) were banned long before I Love You came along.


      Wait a minute. You strip malicious email attachments before they reach the client PCs, and your Windows boxes don't get infected from them, and you give Microsoft's OS credit for this?


      Sure, you can avoid a virus on Windows if you never download one. But what if your users manage to download one anyway? Through a ZIP file perhaps, or on a floppy disk, or through one of IE's vulnerabilities? Uh oh...

    10. Re:Not being a Windows apologist by Tom7 · · Score: 2

      Right on.

      I think it will be hard to do, but I think it's important. Furthermore, when you elect to turn on a network service, it should download the newest version from Redhat or whatever, and install that instead. If you don't have network access, what are you doing installing wu_ftpd?

      Also, it blows my mind that redhat doesn't ship their default internet services compiled with stackguard. The performance loss is negligible (the people who need hard core performance will be recompiling and tuning themselves, anyway), and it would make buffer overflows unexploitable automatically. WTF, redhat?

    11. Re:Not being a Windows apologist by Uebergeek · · Score: 1

      Actually, you are incorrect about stackguard. Go read the nice technical deconstruction in phrack concerning overcoming the stackguard compiler's attempt at using canary words to prevent buffer overflows...

    12. Re:Not being a Windows apologist by Tom7 · · Score: 1

      Yes, canaries are not perfect, but I believe the stub code that XORs the return address with a random word pretty much makes exploiting buffer overflows impossible. Am I wrong?

    13. Re:Not being a Windows apologist by Anonymous Coward · · Score: 0

      >Malicious attachments (.EXE, .SCR, etc) were banned long before I Love You came along.

      I received two malicious email attachments last week. Both were W32 viruses from complete strangers. I have never received a malicious attachment - or any attachment at all for that matter - that would run on my Linux box.

      One way of looking at this is that my Windows box has been attacked over the last five years far, far more often than my Linux box. In that light alone, Linux is more secure, regardless of any proactive administrative securing.

      I don't think it's possible to come up with an objective answer as to whether the locks on my 2001 Linux with iptables and pine are better than the locks on my 2001 Windows with atguard and eudora, but I can state with conviction that it was a helluva lot easier to track down the necessary patches for the Linux box than for the Windows box.

  35. Actually, to be fair... by cperciva · · Score: 4, Informative

    I can't remember hearing about many *new* security holes in win2K recently.

    I can't get to the article right now, so I'm not sure exactly what their argument is, but while I can remember hearing about quite a few major security holes in the unixes (I think everyone was bitten at least once by ptrace race conditions) I can't think of any similar issues in win2k.

    XP, on the other hand... but we're not talking about XP here.

    1. Re:Actually, to be fair... by jandrese · · Score: 2

      That's because by the time you hear about them they are old security holes.

      MS isn't quite as vigilent about releasing announcements of security vulnerabilities to BugTrack as the general Linux community.

      --

      I read the internet for the articles.
    2. Re:Actually, to be fair... by Drestin · · Score: 5, Interesting

      Actually, IIS hasn't had a hole since last August and IIS 5.1 hasn't had one, period. XP has only had the UPnP hole (new technology, consider it a version 1.00 bug).

      There are FAR fewer holes in W2K than people would like to admit. IE may have some problems but not the base OS. Even IIS has been tighted up a great deal.

      People need to understand something, we know MS almost never get's it right the first time (see version 1.00 bug) and may not the second but eventually they do. OK, they sucked at security to begin but with all those resources and the pressure from the top and from outside - did you really think they'd sit still or get worse? Nope - ask Netscape what happens when you become their focus of attention. Tux comes out and smokes IIS 5 and everyone laughs... according to the results of my beta tests with IIS6, we'll see who's laughing when it's publically benched.

      Your lesson is: MS learns. It's almost never right the first time but... it learns.

    3. Re:Actually, to be fair... by thona · · Score: 1

      Thats a very good point of view - actually thats the lesson that has to be learned.

      Linux gurus are pretty tough ignoring this.

      You just dont get into the attention of MS - once they start moving, you are dead.

    4. Re:Actually, to be fair... by thsths · · Score: 2, Interesting

      There are FAR fewer holes in W2K than people would like to admit. IE may have some problems but not the base OS.

      Ok, if you tell me how to install W2K without IE, I would even accept this argument.

      Even IIS has been tighted up a great deal.

      You mean it is a lot less insecure now than it used to be? :-)

      BTW, are "user gains access he shouldn't have" really considered on an W2K system? The majority of "linux" bugs seem to be of this type (symlink attack allowing to read some log file or something). Since W2K is still basically a single user system, I would imagine these are not taken to seriously.

    5. Re:Actually, to be fair... by gorilla · · Score: 2

      But according to Microsoft, IE is the base OS. It's certainly not possible to run 2000 or XP without it.

    6. Re:Actually, to be fair... by Artana+Niveus+Corvum · · Score: 1

      if you tell me how to install W2K without IE, I would accept this argument.

      How about the following (not for initial install, but anytime after). Make sure you have "show all files" turned on. Find the file C:\Winnt\inf\sysoc.inf. Open it in notepad. Remove all instances of "hide" in the file. Save the file. Now open up the Add/Remove Programs dialogue from the control panel and then go to the Add/Remove Windows Components section. See how much extra stuff you can actually install/uninstall there? (including IE). Frankly, Windows is crap without IE IMHO... but it's not much better with it so give it a go if you like... (note: C:\winnt above should be replaced with the directory where you installed win2k)

      --
      -----------------------------------------
      Remove the Greed which plagues mankind.
    7. Re:Actually, to be fair... by Lumpy · · Score: 3, Interesting

      There are FAR fewer holes in W2K than people would like to admit. IE may have some problems but not the base OS. Even IIS has been tighted up a great deal.

      EXACTLY!!!!!! Sorry you cant count any BIND holes on linux. Or any sendmail, ssh,telnet,ftp,etc...

      so after removing all holes that are for software that runs on the OS, linux has what 1 maybe 2?

      This is why I pitch a royal bitch about most certification and security analyses... they are testing things that are not a part of the CORE OS. and therefore are meking everything a mess.

      Let't take NT4.0 and a slackware linux with packages A and N installed. no software other than what the base os allows. (no ftp, not BIND, no sendmail, no servers of any kind.)

      then let's look at the holes... the number of problems on both sides will dwindle to almost nothing. with NT losing because of the silly run all services as the system account bungle.

      if you were to apply a daemon mindset to Nt, and able to run most of the services as a almost-no-access user, over 1/2 the trouble would evaporate.

      --
      Do not look at laser with remaining good eye.
    8. Re:Actually, to be fair... by Danse · · Score: 2

      Ok, if you tell me how to install W2K without IE, I would even accept this argument.


      Even if it is possible to remove it somehow, Microsoft considers it to be an integral part of the "base OS." They even testified to that effect under oath during the anti-trust trial.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
    9. Re:Actually, to be fair... by smittyoneeach · · Score: 1

      I can't remember hearing about many *new* security holes in win2K recently.

      I posit that they'll emerge when Mr. Softy needs to start forcing people into an XP migration, in order to meet earnings targets.

      The cynicism will continue until Mr. Softy evokes some other response to his business practices.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    10. Re:Actually, to be fair... by mkc_673 · · Score: 1

      >I can't remember hearing about many *new* security holes in win2K recently.

      That's why they came out with XP!
      ;)

    11. Re:Actually, to be fair... by Anonymous Coward · · Score: 1, Informative

      Hmm - the only "hide" entry in that file on my W2K box is "imagevue". Doesn't sound like that will uninstall IE for me.

      Besides, as pointed out by the federal courts, IE is "comingled" into the base install. Even if the program icon or iexplorer.exe is removed, an "IE" vulnurability is most likely in the base libraries and will affect other software.

    12. Re: Actually, to be fair... by dne · · Score: 1
      XP has only had the UPnP hole (new technology, consider it a version 1.00 bug).

      So howcome Windows 98, 98SE and ME were affected too (1980's technology)?

    13. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      In actuality, what we're talking about are KNOWN holes. I'm quite sure there are countless security holes in Win2k that are yet to be found. They will be...it will just take time. It's known as security through obscurity.

      However, with an open source OS, holes can be found and patched before an actual exploit is available. Peer review keeps everything in check, and helps prevent new security holes.

    14. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      Counting holes is invalid. Why? Microsoft's gag order on the publication of security holes, that's why. And now we see yet another reason why Microsoft doesn't want the public knowing what's wrong with the software they're paying thousands of dollars for.

    15. Re: Actually, to be fair... by Anonymous Coward · · Score: 0

      uh... 1980's technology? what decade of "technology" do you place UNIX in general then?

      "nyah nyah, your OS is older than my OS... er... i mean.. what were we arguing about again?"

    16. Re:Actually, to be fair... by LiNT_ · · Score: 2
    17. Re:Actually, to be fair... by Shimmer · · Score: 1

      What on earth makes you think that W2K is a single-user system? It isn't. Neither was NT, for that matter. NTFS provides real ACLs to prevent "user gains access he shouldn't have" problems (and I'm not aware of any major vulnerabilities in this area).

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    18. Re:Actually, to be fair... by elmegil · · Score: 2
      This is why I pitch a royal bitch about most certification and security analyses... they are testing things that are not a part of the CORE OS. and therefore are meking everything a mess.

      I think you're on the wrong track here. The point of a security certification is to assure that the SYSTEM (not just the OS, not just one app) is secure or not. EVERYTHING that is going to be run in production needs to be tested together, otherwise the test is worthless. On the other token, if some scam artist is testing things that you know AREN'T going to be run in production, you should flag them as the charlatan they are.

      --
      7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
    19. Re:Actually, to be fair... by jonabbey · · Score: 2

      I get the impression that W2k is a single-user system because the great majority of software for use on W2k is written with single-user assumptions in mind, and because the operating system provides precious little support for multiple concurrent users. I had to fix a permissions problem on a W2k box, and it was just about the most frustrating experience in my life. The software I was installing couldn't cope with being installed without administrator privileges, so I had to try to install the software, see that there was a problem, *log out*, log in again as administrator, fix the first directory permissions problem, *log out*, log in again as the user, try the install again, see that there was another permissions problem, *log out*, log in again as administrator, fix the second directory permissions problem, *log out*, log in again as the user...

      Repeat that 3 more times and you'll know why I was cursing. I *never* curse at work, and certainly not around people I'm supporting.

      Just remember, it's far easier to use Windows than it is to do something wacky like opening a shell window, typing 'su', and proceed to fix a problem relating to multi-user permissions.

      To be fair, WinXP is supposed to be somewhat better about concurrent use with their quick user switcher.

    20. Re:Actually, to be fair... by Shimmer · · Score: 1

      I would agree that most Windows software is still built with single-user assumptions in mind. I don't see how you can blame this on the OS, though. Some people are just slow to change.

      Until I installed XP a few months ago, I ran my home W2K box using a non-admin account. It was painful in some cases, but I almost always found a way to make it work. It's much easier now with XP, but it works under W2K as well.

      Are you familiar with the "Run As" feature in both W2K and XP? When starting an app, hold down the Ctrl key, right-click on the icon, and choose to run as Administrator (or whatever account you want). No need to login under multiple accounts (even though, yes, this is now possible under XP).

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    21. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      you have to pick a point and use that across the board. cince everything that has nasty holes in it in the Unix world can also nowdays be ran under NT, shouldn't NT also inherit the holes too? what about the other 60,000 apps out there?

      The problem is that they use one standard for NT and another for Linux/Unix... and that skew's the results on every test. sendmail != linux nither does apache or bind. I dont equate backorfice, VNC, pc anywhere, or the other plethora of network tools with NT. but maybe we all shoud nowdays. like you say the system is only as stable as it's weakest part.

    22. Re:Actually, to be fair... by jonabbey · · Score: 2

      Are you familiar with the "Run As" feature in both W2K and XP? When starting an app, hold down the Ctrl key, right-click on the icon, and choose to run as Administrator (or whatever account you want). No need to login under multiple accounts (even though, yes, this is now possible under XP).

      Hm, I am now. I imagine running Windows Explorer as an administrator would solve the particular problem I had fairly well, although I am still faster and more proficient on a UNIX-style command line.

      Thanks for the tip.

    23. Re:Actually, to be fair... by NineNine · · Score: 2

      Security through obscurity? You're right, but I'd argue it's the other way around. Script kiddies are pounding away on W2K boxes, not Linux boxes. If anything, Linux is enjoying security through both obscurity and many various trees/distros. W2K is out there and in front. It's certainly not obscure.

    24. Re:Actually, to be fair... by tenordave · · Score: 1

      - Snip - Tux comes out and smokes IIS 5 and everyone laughs... according to the results of my beta tests with IIS6, we'll see who's laughing when it's publically benched. - Snip - Wait, so you mean the newer the software, the faster it is likely to go?

      --
      http://students.washington.edu/djwatson
    25. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      Unfortuntely, Run As doesn't work with the file explorer, and that complicates fixing permission issues a bit.

      Either use a 3rd party GUI file manager ("2x Explorer" is good.), or Run As cmd.exe and use calcs.exe.

      NT4 has a "SU" feature in the resouce kit that's similar to Run As.

    26. Re: Actually, to be fair... by Drestin · · Score: 1

      Because UPnP on those OSes is an add-on/patch. It was not in the original OS. UPnP is a new technology.

    27. Re:Actually, to be fair... by Drestin · · Score: 1

      You missed the point one way but it still works. Yes, the newer software will go faster, in this case. The point I was making is that IIS5 was good and fast. Tux is much much faster and whipped MS's butt in benchmarks. So... MS Learned a lesson - it has now created IIS6 from the ground up (nearly complete rewrite) to be faster and more efficient in a style similar to how Tux acomplished it. MS learns...

    28. Re:Actually, to be fair... by ColaMan · · Score: 2

      Actually, IIS hasn't had a hole since last August and IIS 5.1 hasn't had one, period. XP has only had the UPnP hole (new technology, consider it a version 1.00 bug).

      There are FAR fewer holes in W2K than people would like to admit. IE may have some problems but not the base OS. Even IIS has been tighted up a great deal.


      That is , holes that you can see.

      Let's get the source out and have a look hey? Oh, sorry , can't do that. And as pointed out before, A code audit in Microsoft just results in a "patch / update / service pack x" , but a code audit in the real world results in postings to BugTraq.

      --

      You are in a twisty maze of processor lines, all alike.
      There is a lot of hype here.
    29. Re:Actually, to be fair... by Shimmer · · Score: 1

      Unfortunately, you can't run Windows Explorer this way. But, you can run Internet Explorer this way and simply browse to your hard drive. You'll find that it behaves a bit strangely (e.g. no auto-refresh), but otherwise it works fine.

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    30. Re:Actually, to be fair... by Shimmer · · Score: 1

      See my comment here. All you have to do is right-click on iexplore.exe (or a shortcut to it).

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
    31. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      >It's certainly not obscure.

      Ding Ding! School bell! Time for a lesson:

      What actions a Microsoft product takes in a given situation are not known. There is no access to the source code, so there is no easy way to make them known. Thus they are obscured by Microsoft.

      The hope is that hiding the details of the program will hide the coding and design mistakes from exploiters.

      It also doesn't work.

    32. Re:Actually, to be fair... by Anonymous Coward · · Score: 0

      >it has now created IIS6 from the ground up
      >(nearly complete rewrite) to be faster and more
      >efficient in a style similar to how Tux
      >acomplished it. MS learns...

      Do they? Really? I have my doubts.

      MS *ADOPTS*. MS *EMBRACES*. MS does not necessarily LEARN.

      Think about their entire business foundation. How did they get started on the road to PC domination?

      They developed a GUI for PC's, and made the API public. "Here you go, PC developers... ensure your program works on Windows and you need never code for specific hardware again!" (nice theory).

      Regardless, many PC developers do just that... they write many innovative and clever programs for this new kinda-sorta-portable API. Portable across any two PC's in any case.

      Some of those programs begin to sell quite well... what happens? MS buys them. If they can't buy them cheaply, they steal the ideas and create their own product. Then they change details of the OS so that THEIR product has an edge over the competitor! They sit back and wait for OTHER DEVELOPERS to hand them new ideas on a plate, then they chew up said developer and spit him out.

      Logitech mice, Office suites, Web browsers, Remote desktops (Citrix?)... anyone like to add more examples?

    33. Re:Actually, to be fair... by Malcontent · · Score: 2

      I guess that's what passes for innovation at MS these days. Chasing the taillights of open source developers. Too bad red hat did not get a patent on embedding a web server in the kernel.

      --

      War is necrophilia.

    34. Re:Actually, to be fair... by jonabbey · · Score: 2

      Well, that doesn't do me much good when what I need to do is change directory permissions. What's the officially recommended way for an Administrator to do permissions fixing in the filesystem without having to logout and log in again as Administrator?

    35. Re:Actually, to be fair... by dannannan · · Score: 1

      Did you ask Microsoft for a source code lisense? They do grant them, you know. Lots of customers have access to the latest source code from MS and actively review it, diffing the versions before and after various fixes to keep MS in line.

      D

    36. Re:Actually, to be fair... by Shimmer · · Score: 1

      Like I said, just use Internet Explorer instead of Windows Explorer. The shell is integrated into IE so it works the same way.

      Steps:

      1. Find or create a shortcut to IExplore.exe (there's one on the Start>>Internet menu).
      2. Run the shortcut as Administrator.
      3. Type "C:\" in the address bar.
      4. Voila, your hard drive is spread before you with admin privliges.

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
  36. Two worthwhile questions... by sterno · · Score: 2

    If Linux did indeed have more bugs, there are two questions worth asking:

    1) which versions of Linux? If you were concerned about security you probably wouldn't be running the most bleeding edge version

    2) how siginificant were the security holes? Are they remote root compromises or something less severe. Linux might have several more minor vulnerabilities and look numerically worse if windows has one gaping vulnerability

    Having said that though, I'm willing to believe this is possible :)

    --
    This sig has been temporarily disconnected or is no longer in service
  37. WIDNOWS is secure, APPS aren't... by fzammett · · Score: 1, Troll

    Let's make this perfectly clear, shall we?

    Look at all the security issues that have come to light for Windows over the past year or two. I'd bet my newly purchased house that over 90% of them are APPLICATIONS that are insecure, NOT the OS.

    How many security problems are a result of Outlook alone? 70%? Wouldn't surprise me a bit.

    How many are direct results of VBA? 80% or more? Yeah, I'd think so (and I happen to love VBA but there's no arguing the danger that is opened up when you allow that level of integration and automation in software).

    I don't think there were a massive number of problems that arise from protocol-level problems, security subsystem abuses or kernel hacks. Sure, there is always the occassional buffer overflow and things of that nature, but I'd bet the number is about equal with what you get on any other OS out there.

    It's the apps folks, not the OS. Compare the Linux kernel with the NT kernel and I bet they are both secure as hell. It's what's on top of them that's a problem sometimes.

    --
    If a pion (n-) collides with a proton in the woods & noone is there to hear it, does lamdba decay into the source pa
    1. Re:WIDNOWS is secure, APPS aren't... by opkool · · Score: 2

      What it seems to me, is that they compare the bougs announced by the maker in their shipped products.

      So, from maker "Windows", for the "Windows 2000" product, they would ammount the bugs found in every single application shipped with the "Windows 2000" CD.

      Then, from maker "Red Hat", for the "Red Hat Linux 7.0" product, they would ammount the bugs found in every single application shipped with the "Red Hat Linux 7.0" CDs.

      So, what they show are ammount of bugs announced from a released product form one vendor.

      Anyway, they comparison is flawed because they add for "Linux" all the bugs found on every single distribution.

      And this is bogus. A bug found on "bind", for example, would be accounted as 1 bug for Mandrake Linux 7.1 + 1 bug for Mandrake Linux 7.2 + 1 bug for Red Hat Linux 7.0 + 1 bug for Red Hat Linux 7.1 + 1 bug for Debian Linux 2.2 + ...

      You see, it is the same bug. But ther "grouping" is erroneous.

      So far for fairness.

    2. Re:WIDNOWS is secure, APPS aren't... by slaughts · · Score: 1

      But that's part of the problem with Windows. They blur the line between what is an application and what is the OS...

    3. Re:WIDNOWS is secure, APPS aren't... by Anonymous Coward · · Score: 0

      when you close of the netbios-ssn in windows, (not an app) let me know

    4. Re:WIDNOWS is secure, APPS aren't... by pete-classic · · Score: 2

      You are dead wrong.

      I suppose if you interpret "OS" as "kernel" you're right, but that isn't very sensible.

      Windows (beyond DOS or the NT kernel) is crippled by "legacy support." Recall that the typical install of NT 4 used FAT as the filesystem. A filesystem with NO NOTION OF FILE OWNERSHIP. This IMO is an OS issue. Another example is that, as I understand it, services that drop privileges can just take those privilages back. This turns a potential DOS into a "Administrator" exploit.

      MS puts just as much effort into ease of use for developers as they do for end users. Easy and secure tend to be in conflict.

      Bottom line is that software has bugs, and applications can't be trusted. What the OS can control is localizing the damage. IMO the UNIX model does a far better job of this than NT/Win2k.

      Another example that is from the Win9x world, but perfectly illustrates what I am saying is that there was an exploit for IE that cause the browser to overwrite the boot sector with the browsers "Favorites." It is completely the OSes fault that it gives a web browser write access to the boot sector.

      -Peter

    5. Re:WIDNOWS is secure, APPS aren't... by Anonymous Coward · · Score: 0

      It takes maybe 30 seconds to unbind it. On a default install of Win2k that is the only thing running and it's trivial to unbind.

    6. Re:WIDNOWS is secure, APPS aren't... by fzammett · · Score: 1

      Excellent response, I find it almost impossible to argue against anything you said!

      I would love to read the article referred to here, of course it's completely unavailable at the moment.

      I think it is fair to differentiate between Win2K and above and anything before that. I think it's fair to say that Windows' security before Win2K is, shall we say, suspect?

      However, from Win2K and above, I think it is a much improved story, and while I agree the OS still allows some things that maybe it shouldn't, I think it's a much better comparison to make to other OS's.

      I should have been more specific in my comments I suppose since when I think of Windows I don't even think of anything prior to Win2K anymore because I would NEVER use any of them anymore.

      --
      If a pion (n-) collides with a proton in the woods & noone is there to hear it, does lamdba decay into the source pa
    7. Re:WIDNOWS is secure, APPS aren't... by Anonymous Coward · · Score: 0

      "Windows is crippled by "legacy support." "

      That's true - there's some real shitty default permissions and way too many 3rd party apps that demand Admin access.

      " Recall that the typical install of NT 4 used FAT as the filesystem. "

      None of my NT4 boxes ever did, but it's true that putting \winnt on FAT was some strange MCSE mantra.

      "It is completely the OSes fault that it gives a web browser write access to the boot sector."

      If I run a webbrowser as root on a Unix system, there's nothing preventing it from overwriting anything, including my bootsector. Are you saying that Unix is defective?

      Bitching that Windows doesn't have a "sandbox" system is kind of silly because no commonly available OS has this feature. (and no, FBSD Jail doesn't cut it). Included in that is every complaint that Administrative users should be prevented from running the VBS equiv of rm -rf.

      Moving to a capabilities sandbox system is a huge deal, will break tons of programs. However Microsoft is going in that direction with .NET, and they'll probably get there before Unix does.

    8. Re:WIDNOWS is secure, APPS aren't... by pete-classic · · Score: 2

      If I run a webbrowser as root on a Unix system, there's nothing preventing it from overwriting anything, including my bootsector. Are you saying that Unix is defective?

      No the admin who does that is.

      Bitching that Windows doesn't have a "sandbox" system is kind of silly because no commonly available OS has this feature. (and no, FBSD Jail doesn't cut it). Included in that is every complaint that Administrative users should be prevented from running the VBS equiv of rm -rf.

      Moving to a capabilities sandbox system is a huge deal, will break tons of programs. However Microsoft is going in that direction with .NET, and they'll probably get there before Unix does.


      1. I didn't say sandbox. The original example was about priveleged serviced that drop privs being able to take them back. So for instance, if you are running an anon ftp server on NT and on Linux, and they both bind the port then drop the root/admin privleges, and they both have a hole that allows a remote user to execute arbitrary commands as the ftp server the NT box is "rooted" and the Linux box is not. This has nothing to do with a "sandbox."

      2. A lot of what you are talking about is available on *NIX today via ACLs. So it would seem that Windows is already beaten.

      -Peter

    9. Re:WIDNOWS is secure, APPS aren't... by Anonymous Coward · · Score: 0

      ... and if you take scisors to the network/modem cable it's even more secure. Apps AND Os. You are right...now let see you load the Nt Kernel (alone)with any functionality.

  38. Let's start with the defense... by Score+Whore · · Score: 0, Flamebait

    Of course now we're going to get tons of people who say "Linux is just the kernel." Or "It's the distros that are insecure, not Linux." Or "It's apache/lpd/sendmail/wuftpd/bind/etc that's insecure, not Linux." But let's get our ass on straight here. Nobody posting here is just running Linux-the-kernel. We're all running Linux-the-kernel plus apache, plus userland tools, plus bind, plus sendmail, plus proftpd, plus etc. And we all tell people we are running Linux on our servers, and perhaps sometimes we'll say "with apache as our webserver." But ultimately it's "Linux" that is our OS. And all the mainstream apps that we include are part of that "Linux" that we tell people we use. And, yes, it is appropriate that we take our lumps on issues like this. This isn't a dick measuring contest, it's about running a quality IT enviroment and providing a quality service to our customers. Denial won't provide that.

    And for those who really really want to argue that it's not Linux at fault, then make sure that you point the finger squarely where it belongs: at yourself! Right? I mean, Linux-the-kernel doesn't have any remote buffer overflows in it's webserver. It doesn't provide for local root escalation. It's the tools that you, the admin, are responsible for having in place there that are the problem. And since you obviously chose to put them there (via installing them with the standard RedHat installer, or dl-ing, compiling and installing by hand) you are the one who is responsible. So there.

    1. Re:Let's start with the defense... by fader · · Score: 2

      This argument applies in both directions. While the Linux apologists use the "Linux is just the kernel" argument, the Microsoft apologists trot out the tired old "it's only third-party apps and drivers that are buggy" line.

      I agree that it makes sense to look at vulnerabilities in systems that people actually use to get stuff done. (After all, a box running nothing but a kernel with no I/O, no network connection, etc. is impregnible, but useless.) But if we apply that logic to Linux, we should apply it to Windows as well.

      How many bugs do you think would show up if we included not only Windows kernel exploits (of which there are a fairly good number, I'm betting more than those strictly in the Linux kernel) but also those in IIS, Outlook, Exchange Server, etc.?

      As someone who's seen the results of having these beasts running in a production environment, I can tell you which OS I feel more secure running, and it ain't from Redmond.

      --
      - fader
    2. Re:Let's start with the defense... by Score+Whore · · Score: 1

      I am betting that the numbers listed on the NTBugtraq site do include holes in IIS, Outlook, Exchange Server, SQLServer, etc. Just like I expect that they include bugs in Apache, Sendmail, mysql, etc.

      Personally, all the servers at work run Solaris. And we still harden the hell out of it, and have multiple firewalls segregating various boxes from each other and the net at large.

  39. Quality vs Quantity by WIAKywbfatw · · Score: 3, Insightful

    Surely it's not the number of vulnerabilities that either OS displays that's important but rather their severity?

    I mean, an exploit that requires the malicious party to have physical access to a machine and then only gives him access to one specific folder on a system is hardly as big a deal as one that gives a script kiddie sitting in his bedroom complete remote control of your corporate servers, allowing him to copy, overwrite and delete files, folders and hard drives at the click of a button?

    Let's try to compare apples and oranges here. Just because McDonalds has more restaurants than Michelin-stared ones it doesn't make the Big Mac a better meal.

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  40. Wait for the fury. by freakboy303 · · Score: 1, Troll

    The *nix junkies are going to make this thread 1000 posts long but the numbers are there. I can heartily belive that Windows has less security holes it's just that with Linux not having a viable market share no one really bothers to take the time to exploit those vulnerabilities. It's security by obscurity. Let's say two auto makers each make a truck and company A sells 100,000 units of truck A and company B sells 1,000 units of Truck B. Truck A explodes into a fire ball 20 times and Truck B does the same 2 times. The popular conclusion is that Truck A must be unsafe because it exploded so much but the truth of the matter is that Truck B is actually 100 times more dangerous....but it only blew up twice so nobody will believe the facts. Thats my .02 cents

    --
    -- I am baseball in Minnesota.
    1. Re:Wait for the fury. by forgeeks · · Score: 0

      Are you stupid?

      --
      -- Powered By Linux
    2. Re:Wait for the fury. by freakboy303 · · Score: 1

      Does that mean you don't have anything worthwhile to say? Come on, if you are really as smart as I'm sure you tell all your friends you are then you can come up with something better to say than "are you stupid?" Does Windows have problems? Of course it does. Are these problems perpetuated in a large part due to "paper MCSE's" that really have no business running a large network. Abso-fucking-lutely. I work for a company that hasn't been damaged at all by any worms/virii in two years. This company has 40 Win NT and Win2k servers and do you know why we don't have problems....'cause we are not stupid. But you probably have a bigger dick than me and drive a cooler car because you use linux on a regular basis, so...I must be stupid.

      --
      -- I am baseball in Minnesota.
    3. Re:Wait for the fury. by BLU-82 · · Score: 1

      Sounds like a healthy combination of replies. Obviously, the OS is as secure as the user/admin makes it, regardless of how secure it is out-of-box. Since the more common "end-users" probably use Microsoft more than nix, the OS is bound to be shot full of holes by every script kiddie out there, not even mentioning the real people that code stuff like Nimda, OR the fact that you're not cool if you don't dis Microsoft. I'm more of an M$ creep, which makes me well aware of the bitch that security updates are, and how dependent a company can be on SysAdmin to make sure all the holes are plugged. So, I think the fella who mentioned that there may be fewer holes, but the fact that the holes are HUGE, said it best... uh, however he said it.. ede

    4. Re:Wait for the fury. by freakboy303 · · Score: 1

      That's a totally valid arguement. On an exploited level, yes, the MS holes are much bigger than the *nix holes. But everyone seems to want to say that the whole article is bogus becuase, yes, it is "cool" to diss windows. The whole issue hear with the jackass who just asked me if i'm stupid is the fact that this IS a baised community, plain and simple. It would be nice to able to state my opinion without being flamed but what can you expect from a linux user *insert sarcasm here*

      --
      -- I am baseball in Minnesota.
    5. Re:Wait for the fury. by Grax · · Score: 1

      The Apache truck delivered 56.5 % of the units while the IIS truck delivered 30.75% of the units.

      No Apache trucks exploded. Many, many, many IIS trucks exploded. IIS Trucks are more dangerous, I believe.

    6. Re:Wait for the fury. by markmoss · · Score: 2

      Or maybe it's that truck A is tricked out like a sports car and sold mainly to idiots that can't drive and don't have the sense to stay home, while truck B is designed so that you can't get it out of the dealer's lot until you've studied how to drive it. It might or might not be inherently more dangerous, but I'd worry about the one that's operated by idiots more. ;-)

      Seriously, your numerical argument applies somewhat to e-mail viruses, but not to direct attacks on servers. Crackers don't go after the entire population of computers -- they mainly go after those that can be reached directly on the web, since you probably have to first compromise a firewall to reach the rest. Windows sells on lots of desktops and laptops, but it isn't the biggest player in servers. (Or not in machines that are _intentionally_ servers -- I've heard stories about home computer users, who couldn't define "server", clicking a single checkbox and totally exposing their machines on the web.) If Windows is attracting most of the cracking efforts, it's because they think they have a much better chance of succeeding there. If they thought they'd have as easy a time cracking into *nix servers, they'd be doing that, because there are plenty of targets.

    7. Re:Wait for the fury. by Anonymous Coward · · Score: 0

      Are you an idiot?

  41. Facts?! by Kargan · · Score: 1

    "Facts, schmacts, you can use facts to prove anything that's even remotely true." - Homer J.

    --
    Palaces, barricades, threats, meet promises
  42. You mean KNOWN vulnerabilities, right? by chancycat · · Score: 2, Insightful
    One camp (Linux) is pretty open, and honest about those holes.


    The other camp ain't. We do hear about some vulnerabilities out of Microsoft, but more often it's independent disclosure that open's out eyes. So, how many problems are left unaddressed, and unknown by all but the secret holders? Simple: we don't know.

    At least with opensource I can look at the code.

    --
    Evan - needs to hit preview before submitting
    1. Re:You mean KNOWN vulnerabilities, right? by prisoner-of-enigma · · Score: 4, Insightful

      Granted, you can look at the code, but do you? I run both Linux and Windows environments at our dev company, and I must say that the "hardening" list of things you must do to secure Linux and Windows is pretty much near the same length. In some cases, Linus is harder to secure because so many things lack documentation or have not been tested properly (if at all).

      While I have many bones to pick with MS, disclosure of bugs is a tentative one. On one hand, if they find a bug, don't tell anyone, fix it, then tell everyone, all in a short period of time, I'll all for it. If nobody (or very few people) knows about the exploit, the chances of me being hit by it are very small. The closed source prevents hackers from climbing all through the code and pre-emptively looking for bugs to exploit. This can be a Good Thing(tm), but it can also be a Bad Thing(tm) if MS finds an exploit, does nothing about it, and then a wily hacker exploits it.

      The ability to see the Linux source does me and my dev team little or no good. We are software developers and don't have the time to run through hundreds of thousands of lines of code looking for vulnerabilities. We don't have the time to try and understand poor documentation, conflicting requirements, and other pitfalls that can strike open source. I would go out on a limb and say that the vast majority of LInux users don't climb around in the code. Who has the 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
    2. Re:You mean KNOWN vulnerabilities, right? by prisoner-of-enigma · · Score: 2

      In some cases, Linus is harder to secure because so many things lack documentation

      Y'know, I just noticed this typo. I wonder how Torvald's feels about my comment now?

      --
      In the end they will lay their freedom at our feet and say to us, Make us your slaves, but feed us. - Fyodor Dostoyevsky
    3. Re:You mean KNOWN vulnerabilities, right? by Anonymous Coward · · Score: 0

      he probably feels like he's been violated... :-p

    4. Re:You mean KNOWN vulnerabilities, right? by barawn · · Score: 2

      The thing here is, that's not the point. Just the fact that the code is available to you is the entire key - yes, it might not do you any good, and yes, you don't read through the code, but other people do. How many people does Microsoft have working for them? How many of them are working on security? (yes, all of them, now, in theory) And how many of them are security experts? You can't fix a hole you don't know exists. Therefore, finding the hole is the important thing, and this is DIFFICULT. It's like trying to find a bug that MIGHT exist in your program - even if you spend all of your time looking for it, you'll miss tens of other ones. With open source software, there are huge numbers of people working on things - literally, huge. And I'm sure a ton of security experts look at the Linux code - especially when a bug is found - to see if something else might be vulnerable.

      The important thing here is that with Linux, you *know* when a vulnerability is found. Suppose it's a really really subtle one, and it takes MS a long time to fix it. Suppose the same in Linux. In the Linux case, you know about it, because someone else looked through the code, and if you're intelligent (and a sysadmin, for instance) you'll filter Bugtraq for anything that pertains to your system. Then, you get the advisory, and can disable whatever's causing the hole if there's no fix and the data's that sensitive.

      What I'm trying to say is the strength of the open source security model is the fact that the people who are best at it (security experts - not all of them work for Microsoft) can find the bugs. With MS's security model, only MS can find the bugs, and finding bugs is hard. Very hard. I personally think they're crazy with their model. Even if they don't release the source code, explaining the bug can only help. Giving information to people smarter than you to help you with a problem can only help you - and there are a LOT of people who are very smart who don't work at Microsoft.

      And Linux isn't really hard to secure. In fact, I think one of the distros ASKS you what services you want to allow in. If you only allow SSH in, you're not going to be vulnerable to much.

    5. Re:You mean KNOWN vulnerabilities, right? by praedor · · Score: 3

      It is not important that YOU personally do not go through the source. There are enough people who can and do that you are covered. NO ONE gets to go through M$ code except M$ people, and then, only a subset of them likely see the whole beast.


      With windoze you have a bunch of blackhats looking for exploits and going for it because Windoze is 1) pervasive...one vulnerability on one windoze box is virtually assured of being useful against ALL windoze boxes, and 2) a blackhat after linux is competing against a much larger number of whitehats looking at the same code, finding the same bugs - with the whitehats releasing patches as soon as the problem is found. You could wait months to years before M$ "accepts" that a problem exists, realises that it really is their responsibility to fix it (instead of simply blaming the attacker), and releases a patch on two servers from which the whole world gets to compete to download.


      Lucky for you that you do not HAVE to look at the code to search for problems...but you COULD if you wanted.

      --
      In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
    6. Re:You mean KNOWN vulnerabilities, right? by irix · · Score: 2
      and I must say that the "hardening" list of things you must do to secure Linux and Windows is pretty much near the same length

      Riiight. For example, check out the IIS hardening list here. Then tell me what you have to do to secure Apache out of the box. Which list is longer?

      I am sorry, but I work with Windows, Linux and Solaris all of the time. You can do a RedHat 7.x install out of the box that is secure, less one run of up2date to get newer version of some packages. Zero reboots. Now tell me the steps you have to follow to secure your NT install again?

      I don't know what you are running in your development environment, but it seems to me that you are talking out your ass.

      --

      Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
  43. Linux as a whole, or just MY Linux? by mblase · · Score: 3, Insightful

    The SecurityFocus charts seem to say that in the last several years, WinNT/2K has had 2/3 to 3/4 the vulnerabilities of Linux -- all Linuxes combined, that is.

    When you break it down, however, Windows has been about equal to Red Hat and well above all the othe Linuxes and Unixes in the chart.

    As a willing participant in the capitalist scheme, I don't care how secure everyone else's servers are -- just the one securing my stuff. The only thing this chart tells me is that if I want a secure server OS out of the box, I should start with Mandrake or Debian instead of Red Hat or Windows.

  44. Consider what is included in RedHat or Mandrake by cornice · · Score: 1

    Well I can't seem to reach the site but I imagine that that the comparison is again invalid. If this is a comparison of Linux kernel vs bare Win2K install then I suppose the stats speak for themselves. However, if this is Win2K vs RedHat or Mandrake then this is skewed since RedHat and Mandrake contain many times over all of the software one might need for a server and a desktop. This skews the exposure rating unless the comparison is between Redhat or Mandrake and Win2K + MSOffice + everything else imaginable for a desktop and serevr PC. A comparison of Win2K with a hardened, stripped down version of Linux might be more accurate. Otherwise this is simply saying that a complete install of RedHat or Mandreake is less secure than a plain install of Win2K which is a worthless statement.

    1. Re:Consider what is included in RedHat or Mandrake by mark_lybarger · · Score: 2

      it's actually win2k .vs. redhat AND mandrake AND suse AND AND AND. the linux numbers are agregate of all the distros they evaluate.

  45. Interesting they do not mention OpenBSD by Lord+Hugh+Toppingham · · Score: 0
    OpenBSD is widely regarded as the most secure OS there is, due to its open security audit model.

    I wonder where OpenBSD ranked in this survey ? Apparently there has not been a remote root exploit in the out-of-the-box configuration for over four years.

    Despite all the BSD is dying trolls out there, BSD is alive and kicking Linux and NTs asses (in security terms)

  46. paul thurrot works for windows and .net magazine by K7001 · · Score: 0, Flamebait

    "Paul Thurrott
    Paul Thurrott is the news editor for Windows & .NET Magazine. He writes a weekly editorial for Windows & .NET Magazine UPDATE (http://www.win2000mag.net/email) and writes a daily Windows news and information newsletter called WinInfo Daily UPDATE "

    nice timing with the windows security initiative

    --
    perl -MIO::Socket -e 'IO::Socket::INET-new(PeerAddr="some.windoze.box:1
  47. Read between the lines. by theLunchLady · · Score: 1

    NTBugTrack -- `nuff said.

    1. Re:Read between the lines. by Drizzten · · Score: 1

      ...what do you think it should be called? Super Pete's OS/2 BugTrack Emporium? It focuses on Windows, so it's concievable it should be named accordingly.

      --

      "All mankind is at the mercy of a handful of neurotics". - Norman Douglas
    2. Re:Read between the lines. by jaavaaguru · · Score: 1

      Wonder why it focuses on windows ;-)

  48. Hey look at that by Archanagor · · Score: 2, Informative

    I sent a similar article, but was rejected. Peh, guess I need to work on my editorial skills.

    Anyway, before anyone gets on a high horse here. It needs to be said that it's the code. Not the features that allow users to do stupid things. Most of what's out there choking MS-Based networks is becuase of the ease of which users can execute attached scripts and executables. Oh, and a hole in IIS, but that was mentioned in the article.

    Yes, MS is a monopoly. Yes, they're trying to squeeze more cash out of their consumers (Stupid WPA). But, damn, they do produce some of the most solid code out there, as well as some of the most feature-rich, usable applications. Alas, that's just my opinion, and considering that I use mostly MS apps, I might be slightly biassed.

    1. Re:Hey look at that by Archanagor · · Score: 1

      Oh, yeh. And I can't spell either. Biased not Biassed. Heh

  49. Break it down.. by iamsure · · Score: 3, Interesting

    1. Severity - The issues that exist on Windows platforms are demonstratably larger. There is no administrator/root containment of priveldge (generally), and most of the security issues reported are indeed system-level, remote, and widespread.

    2. Activeness - The common issues reported for Windows deployments are almost universally in use and actively being exploited BEFORE the report. Most *ix vulnerabilities are not being actively exploited (and definitely at a lower level of activity), and are generally patched to resolve the issue FAR quicker.

    3. Openness - "Linux" has no control over the release of bug reports. Microsoft on the other hand, does, to a degree. They can actively "persue" the matter and encourage the bug reporter to remain quiet about it until they can respond. In some cases for MONTHS even for well established bug hunters like eEye, on very large vulnerabilities like UPNP.

    In closing, there are lies, damned lies, and statistics. Sure, you can put whatever spin you want on it, and I think I have in this posting.

    ONE thing needs to be clear, there are alot of bugs, and having many eyes isnt preventing them from happening on Linux.

    No matter where you sit, its justification to yet again work diligently to reduce the number of potential bugs by secure programming techniques.

  50. how Orwellian by xah · · Score: 1
    It is Orwellian to blame Linux for the lion's share of security problems, when the Microsoft platform is far less secure, as evidenced by the many Outlook related e-mail viruses. Correct me if I'm wrong, but this study doesn't include viruses, which are security vulnerabilities. Neither does it include exploits against the commonly installed Microsoft Office programs. OTOH, does the study include Linux security bugs from both the core OS and distro packages?

    I apologize grievously if my assumptions are incorrect. The "winformant" article is Slashdotted, and the NT Bugtraq chart was not entirely clear to me.

    --
    I am not a lawyer. Do not take my words as legal advice. If you need legal advice, consult an attorney.
  51. If Windows went open source... by axehind · · Score: 1

    how many exploits do you think people would find in the first month?

    1. Re:If Windows went open source... by SpaceLifeForm · · Score: 1
      how many exploits do you think people would find in the first month?

      More than MSFT will find this February.

      --
      You are being MICROattacked, from various angles, in a SOFT manner.
  52. These numbers aren't really relevant by ralphj · · Score: 1

    What is relevant, is the severity of the securityholes and the time it takes before the producer of the app in question puts patches out and how soon these get installed by the sysadmins. The latter seems to be the biggest problem anyway.

  53. Much harder to compare "Linux" versus Windows by defile · · Score: 3, Troll

    Unlike Windows, there are many independent distributions of Linux that may or may not be vulnerable to a security hole. Also unlike Windows, each distribution has shorter release cycles. Futhermore, many Linux distributions come with lots of bundled software that not all sys admins install.

    This means that security holes discovered against Windows could be far more devastating because of the uniformity of the installed systems. Code Red/Nimda, etc. would've been much harder to pull off against all variants/distributions of Linux. There's much more paydirt in developing good Windows exploits, since they're likely to work against ALL Windows systems, which means the exploits are likely to be very refined and well tested. Compare to Linux exploits which are usually very hard to get working the first time.

    It's also harder to find security holes in Windows since it's closed source (which doesn't make them any less severe). Many security analysts won't even bother since it mostly involves using a debugger to poke at a task for hours, rather than simply grepping source trees for unsafe functions.

    But yeah, it is pretty disgusting that Linux in general has this many security holes.

    1. Re:Much harder to compare "Linux" versus Windows by bkocik · · Score: 1
      I'm gonna catch hell for this, but just for fun, allow me to paraphrase a bit:

      Unlike Windows, there are many independent distributions of Linux that may or may not be [compatible with an application]. Also unlike Windows, each distribution has shorter release cycles. Futhermore, many Linux distributions come with lots of bundled software that not all sys admins install.

      This means that [applications developed for] Windows could be far more [prolific] because of the uniformity of the installed systems. [Office/Photoshop], etc. would've been much harder to pull off against all variants/distributions of Linux. There's much more paydirt in developing good Windows [applications], since they're likely to work [with] ALL Windows systems, which means the [applications] are likely to be very refined and well tested. Compare to Linux [applications] which are usually very hard to get working the first time.

      I'm not trying to make a point, I'm just playing with words. =)

    2. Re:Much harder to compare "Linux" versus Windows by mangu · · Score: 2

      It's also harder to find security holes in Windows since it's closed source

      I see. That's why no one steals cars, right? Without detailed design plans, car thieves can't find the vulnerabilities in car locks.

  54. bias by Lord+Omlette · · Score: 3, Insightful

    Bias isn't necessarily what annoys me. I would like to see more stories which foster discussion as opposed to sensational bullshit. Isn't their an interesting or nerdy or thought provoking or geeky news item that we can discuss? For fuck's sake, we know Microsoft sucks, we know 80% of slashdot's traffic is from IE, we know we don't like .NET, we know Ballmer is a monkey, come on, let's talk about something (ANYTHING) else.

    --
    [o]_O
    1. Re:bias by Anonymous Coward · · Score: 0

      Oh, no, if you want real slashdot fodder try following this link: http://www.kth.se/internt/nyheter/2002/01/pressrel ease020114eng.html

      In short: B.G. is being awarded an honorary doctorate at KTH in Stockholm, Sweden on thursday. Craig Venter and David King will also be awarded.

    2. Re:bias by ichimunki · · Score: 3, Insightful

      I agree. The numbers from SF are purely for entertainment value only and the WinInformant site is Slashdotted (they must be running Windows, haha) so I have no idea what they said.

      If you look at the SF numbers for any given distribution of GNU/Linux, they are smaller than the Windows numbers. Also, the numbers don't take into account things like severity, remote vs. local, whether the package affected is a core component of a functional server, package redundancy (one bug in four different FTP servers on GNU/Linux vs. four bugs in IIS is not delineated), popularity of the package to the platform is not discussed, etc etc.

      And yes, I'm using IE to post this because Netscape seems to have proxy issues here at work, not because I want to.

      --
      I do not have a signature
    3. Re:bias by xtremex · · Score: 1

      From what I see at Securityfocus, it just seems that INDIVIDUAL programs on Linux have exploits (most of them are LOCAL exploits). I don't count a local vi buffer overflow as a security breach. Most of the Windows exploits are actual WIndows OS exploits.
      Or am I wrong?

      --
      If you're not a Liberal in your 20's, then you have no heart.If you're still a Liberal in your 30's you have no brain.
    4. Re:bias by MadAhab · · Score: 1
      Yeah, one also has to wonder what software counts as part of a Linux system... it differs among distributions, for one thing.

      And Balmer is not a monkey, he is a baboon.

      --
      Expanding a vast wasteland since 1996.
    5. Re:bias by doob · · Score: 1

      ...they must be running Windows, haha...

      It's funny you should say that, because according to Netcraft, they are!

      --
      In the spoon, there is no Soviet Russia!
    6. Re:bias by Anonymous Coward · · Score: 0

      Errr....

      You're wrong.

      A few months ago, I cannot recall the name, but the serious exploit that was found in Windows XP, as well as every previous version of Windows -- that was one of the first OS level exploits.

      Most exploits have to do with the programs which run on top of the core Windows OS itself -- this includes IIS, where I'd wager a good chunk of the numbers come from.

    7. Re:bias by Ionized · · Score: 1

      well, yes, you are. wrong that is. "windows" exploits are either outlook exploits or IIS exploits, 99% of the time. i cant remember the last time there was an exploit of the windows OS itself.

    8. Re:bias by ryusen · · Score: 2, Informative

      This is taken from the security focus site:
      "For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers."
      It sounds to me like vulnerbilities on 3rd party apps included with linux distros are counted, but vulnerbilities in things like outlook, ie, and iss are not... i don't see how anyone who considers themselves a news organization can take , as serious data, any site which even says their numbers might be skewed...

      --

      I believe sex is highly over rated... unless it involves me
    9. Re:bias by Doug+Merritt · · Score: 2

      How can you simultaneously ignore and ridicule it? If you're pointedly ridiculing it, you're not ignoring it, now are you?

      Note that this is talking about the ratio of known & reported issues.

      Take a wild guess: which kind of system will have a higher percentage of its bugs that are unknown and/or unreported ; open source or closed source?

      --
      Professional Wild-Eyed Visionary
    10. Re:bias by Anonymous Coward · · Score: 0

      Wasn't Microsoft trying to convince us a little while ago that these "applications" were core to the operating system???

    11. Re:bias by Anonymous Coward · · Score: 0

      "... cant remember the last time there was an exploit of the windows OS itself."

      lay off the weed, your memory might get better. Although it does sound as if you've been smoking for quite a while.

    12. Re:bias by Anonymous Coward · · Score: 0

      ok, name one. for extra credit, try and answer without using google.

    13. Re:bias by dup_account · · Score: 1

      But, what was said above is that the "application" expliots in Win affected the OS wereas a linux application exploit isn't going to affect the OS

    14. Re:bias by Anonymous Coward · · Score: 0

      Maybe you should name the last linux kernel exploit first..

  55. Open source nature of Linux by John+Harrison · · Score: 5, Insightful
    Is it a surprise that there were more vunerabilities DISCOVERED for Linux than for Win 2K? How many people are looking over the source code of Win 2K for bugs? Now how many have access to the couse code for Linux? It seems pretty obvious where you will find more bugs in the short term. Also, do you think that Microsoft "announces" any and all bugs that it finds internally or are these just bugs that were found outside of Microsoft? How easy is it to find these bugs in Windows without the source? How many more would be found if source code was availible?

    In the long term Linux will have progressively fewer bugs/vulnerabilities due to its open source nature. Look at the numbers on the same chart for NetBSD. There were 9 vulnerabilities found in 2001, and 42 found in Win 2K. 54 for RedHat and only 2 for TurboLinux.

    Obviously everyone should switch to Turbo Linux.

    1. Re:Open source nature of Linux by stapedium · · Score: 1

      In the long term Linux will have progressively fewer bugs/vulnerabilities due to its open source nature.

      You are making the assumption that those bugs will just naturally be replaced with higher quality code. It may, but lots of resources and effort need to be put in to fix bugs. This is a requirement no matter what the distribution and licensing terms are.

      Its one thing to make a progam invulnerable to a particular exploit script, its another to prevent the development of a new exploit.

    2. Re:Open source nature of Linux by tshak · · Score: 2

      How many people are looking over the source code of Win 2K for bugs?

      Let's focus on "Quality Man Hours". Really, how many people a) have the expertise to actually read the Linux source, b) have the time and energy to read through it, c) have the competence to identifiy security issues. We now have a _much_ smaller set of people. Of those people how many hours per day/week/month are they spending doing this? At Microsoft, they pay employees to work on multiple areas of Win2K full time.

      We can theorize all we want about whethor Open Source can put more quality man hours towards security issues, but there is no way to quantify and compare it to the resources Microsoft invests in it's products.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    3. Re:Open source nature of Linux by John+Harrison · · Score: 2
      You have an excellent point. Here's some more food for thought:

      How much expertise does it take to understand what the hell is going on in the Win2k code? I have no idea. Maybe it is a bastion of simplicity. How much expertise does it take to understand the Linux source code? Is it harder or easier than Win 2K? Is identifying security issues easier in one than the other?

      Are there companies paying people to read the Linux source and make it more secure? IBM? RedHat? The NSA? HP? VA? Ok, that last one was a joke. But seriously, are these full-time developers going to do a good job of finding security issues? If Linux is easier to read/fix/find the bugs in than Windows are these people going to be more productive than their counterparts at Microsoft?

      While we're at it, which community of application developers is more security-aware, Linux of Windows? Which OS makes it easier to write insecure applications?

    4. Re:Open source nature of Linux by swillden · · Score: 2

      You are making the assumption that those bugs will just naturally be replaced with higher quality code. It may, but lots of resources and effort need to be put in to fix bugs. This is a requirement no matter what the distribution and licensing terms are.

      True, but this is another reason why open source works well. Security patches tend to get posted to mailing lists, discussed and generally batted around by quite a few people before they make it into the code. While a company could do the same, I've never seen it happen. Typically the manager picks the programmer who wrote the offending bit, or who knows the most about it and orders him or her to fix it.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    5. Re:Open source nature of Linux by Kanasta · · Score: 2

      How many people DO look over the source code of Linux just to look for bugs?

      I would suggest most just USE Linux.

      There are prolly more ppl paid to look at w2k code than people working on Linux code at any one time.

      Of course, those looking at w2k code are prolly not searching for bugs either, but adding more 'features' to it.

    6. Re:Open source nature of Linux by tshak · · Score: 2

      These are all very good questions which support my final contention: "It is folly to even try to make any assertion regarding which code base is more likely to be secure based on it's Open or Closed source nature."

      We can have our theories, but there are just way too many unknowns and counting the "potential number of eyeballs" looking at the source code is really trivializing the issue.

      While we're at it, which community of application developers is more security-aware, Linux of Windows? Which OS makes it easier to write insecure applications?

      Remember, the original assertion was regarding the "Open Source Nature" of Linux. The focus of a team is generally independant of it's Open or Closed source nature.

      --

      There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
  56. Keep in mind... by buffy · · Score: 2

    That this is in large part due to the nature of Open vs. Closed source applications. Linux is open, and a lot of the bugs tracked are found because of just that--it's open, and people can look inside and see. Windows is closed, and has statstically significant (understandment) fewer eyes examining it.

    So, measuring how secure an OS (and OS) is, by the number of items in (NT)Bugtraq is a red herring.

  57. sircam, code red, nimda by demon-cw · · Score: 2, Interesting

    i wonder when was the last time someone found a hole in your firewall by exploiting a hole in your apache to get your sendmail sending the contents of your harddrive to everyone and his hamster?

    1. Re:sircam, code red, nimda by SuiteSisterMary · · Score: 2

      When's the last time somebody exploited a hole in your IIS? Oh, wait. They didn't. They expolited add-ons that IIS happened to use. I wonder what sort of vulnerabilities I can do with, say, mod_php or mod_perl?

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    2. Re:sircam, code red, nimda by oregon · · Score: 3, Insightful

      They expolited add-ons that IIS happened to use

      But are installed by default.

      No-one had to take any extra steps to install the indexing DLL to make themselves vulnerable to code red.

      It may not be part of the core webserver, but the indexing DLL is, to all intents and purposes, part of IIS.

      --

      ---
      Oregon
    3. Re:sircam, code red, nimda by SuiteSisterMary · · Score: 3

      And it was until very recently that most linux distributions installed every networking service under the sun, including wu-ftpd, for example, which is notorious for being full of holes. And I'll point out that the 'how to secure IIS' lists and documents on Microsoft's website include steps for securing the IIS addons. The stupidity required to install ANY OS and put it live to a public network, without going through a security exercise yourself, is strictly user error.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
  58. Some explanations??? by Zwack · · Score: 5, Interesting

    Greetings,
    I wonder how they decided what is "more secure", but my guess is that it's based on the number of reported exploits/bugs.
    Does anyone know if they used any weighting on the types of exploits/bugs. I would consider a remotely exploitable bug to be much worse than a locally exploitable bug as you can't control people that aren't on your box as well as the people that are. I would consider a root/administrator access bug to be worse than a denial of service type bug.

    So, given a weighting scheme of :-
    Remote Root = 4
    Remote Denial of Service = 3
    Local Root = 2
    Local Denial of Service = 1
    How would the different OSes stack up?

    My guess is that without even taking number of installations into account you would find that Microsoft was at least as bad as the various Linux/Unix versions. I'm not going to say that they were worse.

    Anyone want to do some analysis on the same information given a weighting scheme and see what the differences are?

    Z.

    --
    -- Under/Overrated is meta-moderation, and therefore is Redundant.
    1. Re:Some explanations??? by btellier · · Score: 2

      Bah. Linux would outscore MS by hundreds, but only because Linux distributions come with THOUSANDS more programs than Windows. Most of the bugs you find for Linux fall into 2 categories:

      1. Local root/elevation holes for packages like SpaceCommander .03 Beta which require SUID privs for graphics libraries.

      2. Daemons which Linux offers you for free, but would cost you hundreds on Windows, and are just as buggy.

      If we're going to compare Windows to Linux in this way we have to set up two boxes that offer the exact same services and local user functionality.

    2. Re:Some explanations??? by Technician · · Score: 2

      Local Root = 2
      I like it! Any version of WIN 3.x, 9.X, CE etc. all fail local root. Ever hit cancel on the Windows login screen? Ever reboot to get past a locked Windows screenscaver? Ever reboot somebodys Linux box to get past a locked screensaver? Ever hit cancel on a login screen on somebody's Linux box? Simple "my mother can get in" issues with Windows are non-issues on Linux. Mom can't just reboot my personal machine to check where I have visisted recently on the internet! It takes lots more skill to look into somebody's nix box.

      --
      The truth shall set you free!
    3. Re:Some explanations??? by DunbarTheInept · · Score: 2

      You need to normalize with regards to remote usability. I would think that remote root exploits are a bit easier on systems that have more remote
      usefulness. (If your machine won't let *anyone* have a remote shell, legit or otherwise, then it's more "secure", but only in a trivial irrelevant way.
      In that regard, I would expect Linux to actually have more remote exploits, but this is because it also has more remote usefulness. Windows is probably more "secure" than linux against remote users, but only in the same sense that a computer that is unplugged is infinitely more secure than one that is turned on.

      --

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

    4. Re:Some explanations??? by TicTacTux · · Score: 1
      The easiest way to get W2000 DHCP server DOSed is to administer it with NT4 dhcpadmn.
      As this requires admin privileges it won't count as a 'security bug'.
      How many mixed NT4/2000 environments have you seen in the past?

      You probably have to repeat that over and over again - the biggest threat to a working system are [in-|over-]competent admins. In the past it turned out that none of both worlds were immune to inadverted misconfiguration.

      Feb 4 08:15:36 hal9000 bind: refused to HUP and re-read the configuration file /etc/named.conf as there's utter bullshit in there

      I am not asking for a system that is more clever than we are, but starting a second instance of a critical server to check the config file shouldn't be too hard. Yes, exim and some other un-redhatized products can do that...

      --
      Use The Source, Luke!
    5. Re:Some explanations??? by EvlG · · Score: 2

      Most Linux machines can be subverted by something as simple as a bootfloppy, or linux single

      local root exploits are not something to underestimate.

    6. Re:Some explanations??? by Technician · · Score: 2

      True, however I was referring to a snoopy mom trying to pull up my document history or web history. In Windows, everybody shares the same history. In Linux, history is not shared. Great, so mom is a little savey and can local boot as root, will she still know what web sites I visisted? It takes a lot more savy than to boot up as anybody, open your favorite browser and view history. It is true a root exploit will allow viewing of logs, but can a non-technical (non-admin type) user find them?

      --
      The truth shall set you free!
  59. How Orwellian? by Anonymous Coward · · Score: 0

    How is this Orwellian? I seem to miss the distinction...

    1. Re:How Orwellian? by Anonymous Coward · · Score: 0

      Don't mind that poofter, he's just talking nonsense. He thinks that invoking the name "Orwell" may get him some mod points, but he is wrong.

  60. SecurityFocus Says Windows More Secure Than Linux by ekrout · · Score: 1, Offtopic

    SecurityFocus Says Windows More Secure Than Linux

    In related news, we've just sent flying swines down to Hell. Initial reports from Satan's lair indicate a cold front moving through.

    --

    If you celebrate Xmas, befriend me (538
  61. Wait a sec... by saberworks · · Score: 5, Interesting

    1. How many of the Linux vulnerabilities are in services that aren't linux? IE: sendmail, apache, ftp servers, and whatnot? Just because something is packaged with linux doesn't make it linux. Do the windows bugs count IE bugs and every other MS software running on the system? What about other packaged software such as AOL and whatever other links they provide?

    2. Sheer number of vulnerabilities mean nothing - are they counting the severity of the vulnerabilities?

    3. Are they counting the time it took before A) someone discovered the vulnerability and B) a patch was issued?

    4. If there are comparable numbers of linux vs. win2k servers out there, which actually had more break-ins? (This question not valid if there is a wide gap in numbers since then the lower of the two probably benefits from that "security through obscurity").

    5. I think having full source code availability leads to people actually FINDING the bugs, whereas Windows could have way more, but we don't know about them unless people are actually TRYING to crack the system (as opposed to finding them working on source or whatever).

    1. Re:Wait a sec... by Anonymous Coward · · Score: 0

      "How many of the Linux vulnerabilities are in services that aren't linux? IE: sendmail, apache, ftp servers, and whatnot? Just because something is packaged with linux doesn't make it linux. Do the windows bugs count IE bugs and every other MS software running on the system? What about other packaged software such as AOL and whatever other links they provide?"

      OpenSource Advocates often point to the combined use of all component programs as a Linux OS. Eg. "Out of the box my system is a mailserver, firewall and webserver with an office like productivity suite." Now because of this bundle the number of bugs and security holes has gone up. Too bad. That's the price one pays for greater functionality.

    2. Re:Wait a sec... by Fizzlewhiff · · Score: 1

      If you look at the BugTrack data at about mid page you'll see these numbers.

      MandrakeSoft Linux Mandrake 7.2 33
      RedHat Linux 7.0 28
      MandrakeSoft Linux Mandrake 7.1 27
      Debian Linux 2.2 26
      Sun Solaris 8.0 24
      Sun Solaris 7.0 24
      Microsoft Windows 2000 24

      By looking at these numbers I can only assume they are counting the bugs on that CD. But do they count bugs if a service pack CD is included? For example, if I buy 2000 today versus a year ago, I get a different serice pack CD in the box.

      With the Windows worms out there the majority of them seem to attack the same vulnerabilities over and over again. This makes sense I guess because unfortunatly when you apply a service pack to Windows, something as simple as replacing your NIC will send you back to your pre-patch levels. This is something which I think Microsoft needs to spend more time educating people about. How many people know they need to reapply service packs when they add new hardware?

      When I think about it, I get more security notice emails from the Red Hat network than I get critical update notifications from Microsoft. But what does this mean to me? Does it mean that one os is better because it has less bugs or does it mean that one company is better because they are doing more to let me know about potential problems?

      But I guess the big story here is BSD is far more secure than Linux or Windows or Solaris.

      --

      'Same speed C but faster'
    3. Re:Wait a sec... by Anonymous Coward · · Score: 0

      "3. Are they counting the time it took before A) someone discovered the vulnerability and B) a patch was issued? "

      I should add c) How available/easy to install the patch was.

      If they were counting these three things then Linux would be toast. When Microsoft finds a serious security hole they patch it damn fast and throw the sucker in an easy to install patch all over their website. MS may have a lot of other problems, but when they seriously fuck up they fix things damn fast and make sure the fix is available.

    4. Re:Wait a sec... by Tony-A · · Score: 2

      How long did it take Microsoft to make a search of Code Red return results? It was stale on /. before Microsoft seems to have heard of it. Several days may be damn fast for you, but not for me.

  62. Does that mean... by letxa2000 · · Score: 1

    ... that now Bill Gates doesn't have to spend a month on fixing their broken security? I'm sure he'll be thrilled that he can go back to bloat...

  63. overload by Anonymous Coward · · Score: 0


    Site are ./ed.

    Anyhow, how we counting bug? WindowsOperatingSystem against Linux_RedHat_FtpD_SQL_WebServer_GodKnowWhat_Dist ?

    A linux dist happens to contain _alot_ more then WindowsServer2000 do.

  64. Re:What?!? by rhanneken · · Score: 3, Insightful
    Do the names "Nimda", "Code Red" and "I Love You" ring a bell?

    The fact that you can cite flaws in Windows security proves that Windows security is imperfect, not that Windows is less secure than Linux.

  65. Types of Vulnerabilities by mattrope · · Score: 1

    I can't seem to access the article, so I'm not sure whether it addresses this, but it seems to me that the type of vulnerabilities discovered would be an important factor in determining how secure each OS is. Obviously remote exploits are more serious than local exploits. Likewise, the amount of privileges gained through each exploit should also play a role (i.e. does the exploit give administrator/root privileges or just guest/nobody power?) I'm not saying that the conclusion of the article is right or wrong, I'm just saying there's more to an OS's security than number of vulnerabilities.

    Of course it's worth noting that the security of an operating system doesn't necessarily reflect the security of the systems using it. System security is an ongoing process that requires human intervention; if a sys admin is lazy and doesn't install patches then his system will be insecure regardless of which OS he uses.

  66. Apples and Oranges by jocks · · Score: 1

    This test is not actually sensible at it compared the W2K Os against the entire distro of RedHat. In order to be fair we should really compare either:

    1. A base linux install, enough to get a window manager, against W2K, OR

    2. All pieces of software available for W2K against a fully installed RedHat distro.

    Basically the results make absolutely no sense and no real meaning can be taken from it.

  67. Look at the Mac stats for a second by Vespillo · · Score: 1

    MacOS has 11 vulns. while MacOS X Server has 1 vuln. Those numbers really suprisized me.

    --
    The problem as I see it is that I have no personality of my own.
  68. Bogus statistics by coyote-san · · Score: 3, Interesting

    If this is the same article mentioned on LWN (can't be sure, since it's slashdotted), this article compared the number of bugs reported against Windows against the number of bugs reported against Red Hat. And Debian. And SuSE. And another distro - forgot which one.

    I'm sure it was an honest mistake that most Linux bugs were counted multiple times.

    But I don't buy into the "bug count" argument anyway. It's a lot like that controversy over the "most decorated US veteran" (Hacksworth?) - a lot of people think that you can have a warehouse full of bronze stars and distinguished service medals and it's all scrap metal next to a single Congressional Medal of Honor (post.).

    What was the last remote root exploit for a widely used Unix service? What about local exploit for a widely used Unix application?

    Now ask the same thing about Microsoft.

    Finally, "NTBugTraq" may be respected but that doesn't mean it never publishes crap -- sometimes for the purpose of shooting it down. I've seen this happen on comp.risks and elsewhere.

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
  69. Measurements of Vulnerability by Lendrick · · Score: 1

    The problem with weighing security vulnerabilities is that, apart from just counting the bugs, it's a completely arbitrary measurement. One might assert that Bug X is worse than Bug Y, but there's no scientific way to back up those assertions.

    Some people might argue that total cost in damages caused by security vulnerabilities is a good measurement (and certainly, Windows has racked up billions of dollars in this category). The truth, however, is that with Windows' wider deployment, it's far more prone to attack in general. Since Windows machines make up some 90% of all desktops, more virus writers target it, and the viruses written for it have more places to spread. Dense, non-diverse populations are inherently more vulnerable to plagues.

    Is Linux really more vulnerable than Windows, in the grand scheme of things? Given the above facts, it's difficult to say. There are valid arguments for both sides.

    That said, it's been shown that Linux users as a community have the resources to get in and fix security holes far quicker than Microsoft is capable of doing with Windows. So, if you feel like complaining about the security report, my advice would be to take that energy and use it to help with testing and patching instead.

    Peace,
    Lendrick

  70. This is crazy by forgeeks · · Score: 1, Insightful

    Okay lets break it down:

    Linux by default includes:
    A mailserver
    an ftp serer
    a telnet server
    a web server
    a database server
    etc....

    Windows by default include:
    A store receipt
    IIS maybe..
    ummm

    okay so what are they basing their study on? The same system setups? Are they comparing postfix with exchange server or sendmail with exchange server? Mysql with MSSQL or MySQl with Oracle? I don't understand this study, nor do I believe it. I think this study is biased and fixed. It is funny that this study is released as M$ releases the W2K rollup package to fix the broken/hackable files.

    --
    -- Powered By Linux
  71. This study has "vulnerabilities." by Uttles · · Score: 2, Troll

    First of all, there's no weighting in the charts. So in other words, an attacker can break into a Win2000 box and control everything about it, or he can telnet into a Linux box but has no access to change anything or even browse the root directory, yet both attacks are chalked up as a "1."

    Also, read this from their "about us" section:
    The company has approximately 50 employees and is privately held, backed by venture funding from SOFTBANK and E*Trade Ventures.

    Funny, I seem to remember a story not too long ago about E*Trade joining .NET, and there's that one about 6 months ago when the E*Trade mutual funds started to tank and they moved towards more MS stock... draw your own conclusions.

    --

    ~ now you know
    1. Re:This study has "vulnerabilities." by xZAQx · · Score: 1

      Actually, E*TRADE is switching their entire operation over to linux. This is the 3rd time I've said this, and no one has listened yet.

      But here's the article anyway.

      I posted this to ./ , but it was (of course) rejected ...

      --

      We dance to all the wrong songs.
      --Refused.
    2. Re:This study has "vulnerabilities." by opkool · · Score: 2

      ... and just now., E*Trade is moving towards Linux.

      The world is amazing.

    3. Re:This study has "vulnerabilities." by chrisw15 · · Score: 1

      Funny, I seem to remember a story not too long ago about E*Trade joining .NET, and there's that one about 6 months ago when the E*Trade mutual funds started to tank and they moved towards more MS stock... draw your own conclusions.

      Funny, I remember seeing last week that E*Trade was moving their servers to Linux...draw your own conclusions without the conspiracy theories...

    4. Re:This study has "vulnerabilities." by Anonymous Coward · · Score: 0

      Follow opkool's Information Week link above. They are not moving their "entire operation" to Linux -- they are moving their "customer-facing Web sites".

      If E*Trade is like any normal financial company, they've probably got one of everything on the backend, including everything from VMS, to IBM mainframes, to 9 UNIXes, to Windows, to Linux. It's quite possible that they are doing both Linux and .NET projects at the same time.

  72. Slackware by Phroggy · · Score: 2

    How does Slackware stack up to other distributions and to Win2k? I know Slackware 8.0 (like most other *nix distros) had a remote root exploit in telnetd, and there are updates for about a dozen other packages; how does this compare to RedHat?

    Saying "Linux has more security holes than Windows" is at least as stupid as saying "I just got Linux 7.2".

    --
    $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
    $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
    1. Re:Slackware by Cro+Magnon · · Score: 1

      I don't know how Slackware compares to RH and others, but I do know that I got r00ted on my Slackware 7.1 box last year! Windows may be worse than Linux, but Linux still sux on security!

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  73. What about the last half of 2001? by larsu · · Score: 3, Insightful

    Anyone remember Code Red? Nimda? I sure do. I still get 300+ scans a day from infected Windows boxen.

    Also, most linux vendor security announcements posted to Bugtraq are for add-on software not enabled by default. They are also announced by each vendor individually, and the author of the package. Most Windows announcements are about vulnerabilities in the OS (IE) or widely deployed packages (IIS, Outlook) from the author of the exploit (after secure@microsoft.com has ignored them).

    The entire article needs to be modded -1 flamebait.

  74. heehee by blueroo · · Score: 1

    I read this article a few days ago. I thought it was funny. Basically, Slashdot didn't read the article before posting again. The synopsis of this boils down to "Slashdot says Winmag says SecurityFocus says NT is more secure than Linux.", except SecurityFocus never said that. Doh. Winmag instead just wrote an article counting the total number of exploits for Linux and NT, and gave the OS with the lowest number the best "secure" rating. Of course, since these stats came from the NTBugtraq list, it must be SecurityFocus sanctioned *cough*.

    Your poster knew this. Way to go poster. You've successfully trolled the frontpage of Slashdot.

    1. Re:heehee by forgeeks · · Score: 0

      Another genius...think about it...If they say that Linux has more holes than Windows, do they need to say Windows is more secure? No... It speaks for itself...

      --Where is that moron block when ya need one!

      --
      -- Powered By Linux
  75. He just linked to it a 3rd party's stats by Drestin · · Score: 1

    Who he works for doesn't make it possible for him to fudge those numbers.

    You are truely desperate to deny these figures aren't yoU?

    1. Re:He just linked to it a 3rd party's stats by mvdwege · · Score: 2

      Well Mr. Black, if you had spent a few minuts on COLA, you'd have seen these numbers debunked multiple times, yet every time one of the MS apologist regulars tries to bring them up again!

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    2. Re:He just linked to it a 3rd party's stats by Lemmy+Caution · · Score: 1
      Ah, advocacy groups. It's good to know that flat-earth devotees have a place to go in these difficult times.

      I once used advocacy group threads as an example of resistance to Habermasian and Gricean claims about discursive cooperation in a paper I wrote for college. It's incredible how resistant to real rationality and reasonableness people can be once they get religion.

    3. Re:He just linked to it a 3rd party's stats by mvdwege · · Score: 2

      Hehe.

      It's not that I take advocacy groups very serious, but given the tone of that poster, I assume he used to be a regular at the particular advocacy group I frequent.

      Otherwise, I just like debate (and flamewars), so why not spend some time on a .advocacy group?

      And on a serious note, this particular article has been fodder for discussion for about two weeks now. Slashdot is a little slow on this one.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    4. Re:He just linked to it a 3rd party's stats by Drestin · · Score: 1

      Actually Mart - I used to spend a lot of time in COMNA where the COLA nuts (hehe) cross posted a lot.

      I do not consider these numbers debunked; not then and not now. They are valid numbers. What conclusions you draw from them is open to debate and that debate has never been settled to anyone's satisfaction in either group (no suprise there).

  76. Really? by ouija147 · · Score: 1

    That seems like an unusal slip up for SecurityFocus. I have been trying to get to the article since this was first posted. There were no comments and it was already /.ed. Sure would like to read the article to verify this.

    1. Re:Really? by mvdwege · · Score: 2

      It isn't. These particular numbers were presented on SecurityFocus without commentary. I'd guess the aggregate number was only added for completeness' sake.

      It is all the pro-windows pundits that try to bend these numbers to their agenda.

      Mart
      --
      "I know I will be modded down for this": where's the option '-1, Asking for it'?
    2. Re:Really? by Znork · · Score: 2

      Nah, they've published these statistics for several years, and every year someone like this article comes along and says 'hey, look, if I cant read and have no idea what these statistics are, I can believe that Windows is more secure than linux'. The statistics are always there, it's just that you dont have anyone making anything of them until you find a really inexperienced new journalist who hasnt seen them before, tried to understand them, or seen the last newbie guy getting them explained to him in a friendly fashion. I think its some sort of initiation rite of passage in security journalism.

  77. I've known this all along. by NoMoreNicksLeft · · Score: 1

    Even forgiving all those linux worms that flooded the entire internet for much of last year, it was the mysql/php buffer overflows left and right that allowed any script kiddy to gain root access with a web browser.

    Oh wait, I think I have this backwards, never mind.

  78. Make that KNOWN vulnerabilities by Restil · · Score: 2

    Remember people, while we can be pretty damn secure (no pun intended) in the fact that we've gotten most of the security holes out of linux, there could still be many unknown holes in various windows operating systems that simply have yet to be discovered. With the source open, you're going to find more holes, assuming all things were done equally.

    Also, are we looking only at the linux kernel itself (compared to the windows kernel) or all the programs that are typically packaged with it? Gnu and Linux usually stand together, but counting vulnerabilities in every program that could ever be run suid root may be reaching a bit far.

    -Restil

    --
    Play with my webcams and lights here
  79. What is 'linux' anyhow by cvanhorn · · Score: 1

    I am curious as to what that consider linux and what they dont. If they are counting the number of security vunerabilities of all the available linux utilities and kernel or just the 'core' parts. I know I personally would have a different definition of what programs make the the core linux and which ones are optional. GPM recently contained a vulnerability, but I dont consider it important or required at all.

  80. that's great, but by hyperstation · · Score: 1

    in the hands of a clueless sysadmin, anything is insecure

  81. It is an interesting question - and a proposal by victim · · Score: 3, Insightful
    Which OS has more security problems is an interesting question, but I would not use ntbugtrack's data to answer it for the following reasons...
    • Having one of the OSes embedded in their name immediately makes my wonder about bias.
    • They have an aggregate data column for `all linux distributions' where they overcount the same bugs. Despite breaking windows OSes into two columns, they don't aggregate these together.
    • They do not attempt to quantify either theoretical severity of a problem or actual real world impact of the problem. The linux community tends to have more bug reports for theoretical problems that are fixed before they are exploited.
    • The statistics from ntbugtrack have been stale since August. This is an abandoned site. I suspect anyone doing a serious analysis would start with current data.
    • It is possible that MS bugs are under reported. All Debian security bugs are fully reported by policy. Microsoft has a policy (recently at least) of supressing minor bug reports and quietly fixing them.
    • Your typical linux distribution is OS, plus OS utilities, plus all of the applications. Application level bugs will show up in the linux distributions, but not in the windows columns. Consider the recent rsync bug. That should be a bug for all of the major linux distributions, but will not appear in the windows column even though rsync can be installed and run on windows. (This is an example, I have not verified that the bug affects windows. I believe it does from the description. Don't flame me over this one.)

    So, how about we do a serious analysis? I'll put up a system that lets people rate the various bugs by severity along a couple of continuums. (Like theoretical impact and actual impact.) Then people can use this data to draw more accurate conclusions. If at least 10 people respond to this post, and two thirds of them think it is a good idea, I'll put one up and link it here.
    1. Re:It is an interesting question - and a proposal by Spreetin · · Score: 1

      Sure, sounds like a good idea. I would be glad if you put such a page up and then persueded the slashdot crew to put it on the front page :-) Seriously speaking, it would be cool if you did that.

      --
      8 * 7 = 42
  82. These stats are a bit odd... by lorian69 · · Score: 1

    Alright, someone help me understand the statistics here. In the first listing (Number of OS vulnerabilities by Year) I looked at the year 2001 column. Obviously, the aggregate linux column was very high... how many of those bugs were duplicates?

    Aside from that, the only distribution in that first listing with more vulnerabilities than Win2k/NT was Redhat. Of course, there were no version listings provided for that chart.

    When broken down to versions, suddenly there are more vulnerabilities than the previous generic listing. Is this a different type of vulnerability? The first is listed as "OS," the second as "package." Regardless, not only do they not list the most recent versions available, but there are 10 LESS vulnerable linux packages than Windows 2000, and 4 that are MORE vulnerable. How does that figure into the end conclusion? Does that make linux more or less vulnerable than Windows 2000?

    In any case, as mentioned by several others, the statistics don't include the severity of any of the vulnerabilities at all, rendering the statistics pretty much worthless.

    (Think I said "vulnerable" enough?)

  83. The security of any OS lies... by TobyWong · · Score: 5, Insightful

    The security of any OS lies in the skill of its admin. An idiot with a 2k box is no more secure than an idiot with a linux box and vice versa.

    --
    - Toby
    1. Re:The security of any OS lies... by B00ji+B0y · · Score: 2

      I aggree. Everyone knows that Linux -without the necessary adjustments - is like leaving a Ferrari with the door unlocked and the keys in the ignition. It's up to the administrator. I found it interesting that the stats on the site showed that the Red Hat and Madrake distros both had increases in security holes over the last two years. Why do you think that is? Seems backward. Could one say that adding more capabilities and packaged programs to the OS make it less secure?

    2. Re:The security of any OS lies... by TobyWong · · Score: 3, Insightful

      10-14 new linux exploits which dont apply to 95% of linux users. I'm on the debian security mailing list and almost every notice they send out is regarding a package I dont use (on a package heavy box even).

      Look at it this way, when you say "linux exploits" you are not only talking about kernel issues and quality packages but every half-baked bit of code to come out of a college dormatory. If you include all the windows shovelware in with those exploit numbers I venture to say that you would see a very different picture.

      --
      - Toby
    3. Re:The security of any OS lies... by Dalaram · · Score: 0

      True, and this is also why Linux will commonly have less problems. Any idiot on the street has heard of Windows and can easily set up a windows system. However, the more skilled admins can and do set up Linux OS's. Therefore, windows absorbs most of the moron factor. It doesnt necessarily mean that Linux is more secure, but in fact that the poll is skewed because the average user without any tech-geek connections does not know how to protect his system.

      --
      all my .sig are suck
    4. Re:The security of any OS lies... by stinky+wizzleteats · · Score: 1

      That's not really true.

      While the skill of the operator is certainly the primary consideration in how securely technology is actually implemented, you are standing on completely different ground when you implement open source software as compared to Windows.

      In the case of windows, bugs may exist, and you have no way to ever know about them except at the behest of Microsoft. Therefore, your ability as an admin to respond to bugs is limited by whether M$'s marketing department wants you to know about them.

      With something like Linux, you've got the source code right there in front of you. You have complete control of the system.

    5. Re:The security of any OS lies... by Anonymous Coward · · Score: 0

      "An idiot with a 2k box"

      Almost by definition my son.

      Almost by definition.

  84. bugs should be weighed, not counted by hopeless+case · · Score: 1

    the subject says it all.

  85. Wow, talk about your slashdot fodder... by dasmegabyte · · Score: 5, Insightful

    Again, Winformant, in a desperate attempt to seem like they aren't a bunch of toadies, has struck an "independent" blow against linux's "security myth," by proving that more holes were found in linux than in Windows.

    Well, duh. Linux is full of holes. But that's not winformant's problem. You see, each of those holes was cleared up in a matter of days and a patch was freely available. There were no egos and press releases claiming there are no holes. There were no programmers waiting around while Marketing decided the best colour for the patch's installation wizard. There was no downtime as millions of machines had to get the file from a single MS server because the patch's license didn't allow redistribution. There were no hours of wringing hands as sysadmins watched hackers pick off their boxes one by one because there's no workaround while the patch was built. There was no possibility for diving into the code and fixing it yourself; and if there was there'd be no way to release the patched dll. Oh, and if a linux machine was compromised, there was little chance of it polluting the entire network...because the bug affected less than 1% of the install base of that particular OS, and not 100%.

    Not to mention the reason that so many Linux patches were "found" rather than "discovered" is that bored sysadmins can sit around with sheets of source code, hoping to find a hole and make a name for themselves on BugTraq. With windows...well, you'd better be good with BlackIC and ASM, because it's the only way you're finding the hole.

    --
    Hey freaks: now you're ju
    1. Re:Wow, talk about your slashdot fodder... by SilentChris · · Score: 2
      "Not to mention the reason that so many Linux patches were "found" rather than "discovered" is that bored sysadmins can sit around with sheets of source code, hoping to find a hole and make a name for themselves on BugTraq. With windows...well, you'd better be good with BlackIC and ASM, because it's the only way you're finding the hole."

      So you're saying that its easier to find holes in Open Source software? Wouldn't this make it easier for a cracker to read the source code and build an exploit off it?

      There is some advantage to security through obscurity. Say, for starters, some hacker X tries to exploit OS's Y and Z. Y is Open Source. He looks at the code, finds a bad buffer, builds his exploit. Z is closed. He has to root around with BlackIC (or any of the other hacking tools), play around with the assembly, maybe even wreck a few OS's in the process?

      Which one do you think is faster?

      Further, once the vulnerability is released, what makes people think it'll be "easier" to discover on the Open side? I'm in the same situation as if my OS was closed. For example, I've just discovered a vulnerability that causes my screen to show "Hey Dude". Someone must have broken in. But where's the problem? The screen buffer? The IP stack? A misguided pointer? While thousands of people are spending hours to pour over the Open code finding a needle in a haystack, Microsoft's (admittally) no better developers, who are a much smaller group and can work with a much more homogeneous code base, don't have to work nearly as hard because they pretty much know the code inside out.

    2. Re:Wow, talk about your slashdot fodder... by dasmegabyte · · Score: 2

      Yeah, of course it's easier to discover a 'sploit in open source. The question is whether it's worthwhile to look or not. If a hole is 'sploited, then spotted and fixed within hours, what good is it?

      As a hacker, it's in your best interest to stay undercover for as long as possible...and "obscure security" is the best cloud cover I can think of. "Oh, there's no hackers in there, it's too much work to find the hole" is not the excuse I'd like to give my employer when I've got a colony of scriptkids running eggies on my print server.

      Remember, hackers are probing your network anyway. They're already looking for holes and testing the waters. They're the guys hunting for change in the payphones at the bus station and testing the lock on the door marked "employees only." They aren't going to be affected by the "obscurity" of closed source networking.

      With microsoft, security isn't simply a matter of finding a bug in the software (which isn't as easy as you seem to think; MS has relatively high developer turnover and runs a LOT of legacy code nobody really "knows", remember Linus's line about the AT&T fix?). It's a matter of finding a bug, proving it's a bug, getting MS to admit it's a bug and eventually release a patch. With open source, you can bypass every one of these steps.

      --
      Hey freaks: now you're ju
    3. Re:Wow, talk about your slashdot fodder... by barawn · · Score: 2

      What you're assuming is that everyone's ability to read code is equal. I disagree with the first poster that a bored sysadmin could actually find a security hole. Finding bugs is hard - really hard. Especially bizarre ones.

      So, given that everyone has access to the code, if crackers can find a hole faster than everyone else. I think, honestly, the people who will find it are the people who are best at it - people who have worked in computer security a long time. They're not likely to be crackers, to be honest. So, for the most part, I think you're best off with an open-source model.

      Plus, with the Microsoft system, it's not that you don't have access to the code - you just don't have access to the code's internals. You know what the functions are. It's pretty trivial to write a program to iterate through several thousand system calls looking for something to break. These are the kind of holes that are easy to find in closed-source models (they're also the kind that ARE found in closed source models.) Linux, however, probably is more vulnerable to wackier bugs like race conditions and so forth.

      As for how to find it: you know, I wouldn't be surprised if the way a lot of already-exploited bugs were fixed was by someone actually obtaining the script-kiddie package. There, you HAVE to have the source code to understand how something's being screwed up. That said, I'm sure Microsoft can do the same, but, again, it's a lot easier with a helluva lot more people.

    4. Re:Wow, talk about your slashdot fodder... by FastT · · Score: 2
      Microsoft's (admittally) [sic] no better developers
      Have you or anyone else here ever tried to get a job coding at Microsoft? Microsoft's interview process is extremely rigorous; it is NOT easy to get a position there. Most other software companies, including (or especially) the big-name ones, have a fairly high percentage of clunkers working for them. Not Microsoft.

      Contrast this to the skill base of the coders working on Linux. What are the requirements necessary to start hacking away on Linux? You won't find someone mistaking '=' for '==' at Microsoft.

      Nearly every one of Microsoft's coders are A-list. They don't have to hire anything less. Even if there are many more, most of Linux's coders are B-list at best--students, part-timers, hackers, sysadmins, webmasters, tech support guys. Sure, these guys have the heart, but that doesn't mean they have the chops.

      It's easy to be seduced by the common assumption that there is a large group of dedicated, top-shelf engineers out there working day-in, day-out on all areas of Linux, but that's only half-fantasy at best. Sure, there are some greats out there, but the more likely reality is a) they're few in number compared to the legions of paid employees at Microsoft (all of which we know are directly contributing, full-time), and b) many of them work on the stuff they *want* to do, rather than the stuff that *has* to be done. In some cases this translates to fitting the right people to the right job. Regardless, the result is the same: it leaves areas of Linux neglected by the best engineers.

      --

      The only certainty is entropy.
    5. Re:Wow, talk about your slashdot fodder... by SilentChris · · Score: 2
      I agree with you. I think everything released on the OS side after 2000 and everything released on the Office side after 2000 have been stable, reliable products. XP is my OS of choice right now for reliability and compatibility reasons.

      I know Microsoft's trials are rigorous. The problem, though, lies in the consensus that there are a lot of bugs in Microsoft software (like most software) and that these bugs, presumably, wouldn't be so easily missed by super-developers. I'm not saying Microsoft's coders are bad - I'm just saying they are probably equal with every other company's out there. It's just that their products get a baptism by fire because so many people use them.

  86. Re:What?!? by Drestin · · Score: 0, Troll

    Does "Ramen" ring a bell?

    (/.'s 20 seconds min to reply is the lamest thing I've ever seen... I'm typing this to slow down my submit clicking because I can actually read and type faster than a 1st grader... stupid...)

  87. There is No Science Here. by tqbf · · Score: 5, Informative
    I like SecurityFocus. The people in charge of SecurityFocus are with-it and honest. I am completely confident that this work was done in good faith.

    However, the conclusion being drawn here is invalid. The SecurityFocus vulnerability survey is interesting, but it is not itself a reasonable methodology to generate security metrics between operating systems.

    I could pick nits at this ad hoc study for hours, but the biggest problems are also the most obvious:

    First: the study associates third-party software with the operating system, and aggregates all the distributions together into a meaningless "Linux" category. This study is literally just pattern matching against advisories.

    Second: there is no notion of "severity" or "impact" in the study. This is a shame, because SecurityFocus has actually put some real effort into deriving a taxonomy of vulnerabilities from their (enormous) vulnerability database. There is no way to determine whether the N Linux vulnerabilities were equivalent to the K NT vulnerabilities.

    Third: the study compares a kit of open-source software, which has received extensive peer review, to a closed-source product. It should surprise nobody that Linux has more documented problems than Windows: it's actually possible to go find vulnerabilities on Linux. Finding Windows vulnerabilities requires black-box reverse engineering.

    Finally, both Linux and Windows do a reasonable job of locking down server configurations out of the box. What IT people need to know is vulnerability breakdown by operating system and by deployed configuration. This study does nothing to inform us of whether a Linux web server is at more risk than a Windows web server, or whether it's safer to expose a Linux print server or a Windows print server. Organizations that deploy homogenous Apache+NFS+ssh server farms don't care about XFree vulnerabilities or Samba problems.

    I don't think SecurityFocus is actually trying to make claims about the relative security of Linux and Windows. I think they've been a bit careless with this report though; it's a reasonable thing to try to generate from their database, but more thought should have gone into presentation.

    SecurityFocus has the on-staff expertise to publish some real conclusions about the distribution of vulnerabilities between Linux and Windows. Before this database report is misconstrued by the trade press, it would be enormously helpful if they could publish a statement about the conclusions that can be legitimately drawn from it. It'd be good press for them, too.

    1. Re:There is No Science Here. by Glonk · · Score: 1
      First: the study associates third-party software with the operating system, and aggregates all the distributions together into a meaningless "Linux" category. This study is literally just pattern matching against advisories.

      If you're including IIS with Windows 2000 bugs, it's only fair to include the third party Linux applications common.

      Second: there is no notion of "severity" or "impact" in the study. This is a shame, because SecurityFocus has actually put some real effort into deriving a taxonomy of vulnerabilities from their (enormous) vulnerability database. There is no way to determine whether the N Linux vulnerabilities were equivalent to the K NT vulnerabilities.

      The last time that list was released, Unix was still #1.
      http://www.sans.org/topten.htm
    2. Re:There is No Science Here. by Shimmer · · Score: 1

      the study compares a kit of open-source software, which has received extensive peer review, to a closed-source product

      A "kit"? Like a model rocket or a lego set? Some of the people who make this kit feel that it is ready for enterprise use. You can't have it both ways.

      -- Brian

      --
      The most rabid believers in American Exceptionalism are the exact same people whose policies are destroying it.
  88. Sigh... history repeats itself... by X · · Score: 2

    This same thing happened last year... Some guy wrote a piece claiming similar things, and making the same mistake: adding up all the bug entries against all the distributions, so that many bugs were counted several times over (and somehow not adding up Windows 9x bugs with Windows NT bugs..... ). When will people learn.

    --
    sigs are a waste of space
  89. One big missing factor by 0xA · · Score: 2
    Linux fixes are easier to deploy! Deploying and checking on MS bug fixes is a pain in the ass. Apply, reboot, apply, reboot.

    They are making some headway with this, the qchain tool, hfnetchk a couple others but it still takes longer to check, deploy and test these damn tings that it does with any other *nix I've worked with.

    RANT
    I think the first thing MS needs to do is get a decent remote shell for Windows servers. There are some okay 3rd party products out there and Terminal Sevices does help too, but I don't need the full GUI just a shell that isn't hadicapped like their silly telnet server.
    /RANT

  90. And what does this tell us? by Guppy06 · · Score: 2

    It tells us that when Microsoft doesn't try to over-burden their operating systems with silly gizmos and features it's actually pretty damned good. Windows 2000 was only an evolutionary change from NT 4 (many of the changes were supposed to originally come with NT 4), had the history of the NT code base behind it, and it got the job done without too much glitz and glamor.

    It wasn't until Microsoft thought up NT 5.1 (aka XP) with all sorts of inane bells and whistles to try to convince us that we need to upgrade that the bottom fell through on their security again.

    While this does vindicate my continued use of Windows 2000 in the XP era, I really don't feel this vindicates Microsoft too much. When it comes to operating system releases, Windows 2000 was a bit of a fluke. A fluke because nine times out of ten Microsoft tries to overload a new OS with silly features (think 98 compared to 95), and this time they "messed up."

    While Windows 2000 is secure, the underlying philosophy in Microsoft that made them decide to release XP is not.

  91. Windows IS secure by m4g02 · · Score: 1

    Windows is really secure, before the welcome screen is the most secure Os i have seen, but after booting ie, iss, outlook, well... better not to boot them... so is very secure as long as dont boot anything. *grin* very secure piece of crap that dont do a shit.

    --
    Sigs are for morons... Wait a minute...
  92. Very Difficult to measure by wizarddc · · Score: 1

    If you think about it, WINDOWS hasn't had any major bugs or security holes lately. It's been Outlook and IIS who's been the victims of the Big Media holes and trojans. It might be a valid claim to say Windows (2K, XP), as an OS, is more secure than Linux, but not as an enviroment.

    --
    Th
    1. Re:Very Difficult to measure by Anonymous Coward · · Score: 0

      XP's universal plug and play hole.

      About as major as you can imagine.

  93. I agree by joeblowme · · Score: 1

    I think the figures are probably accurate on the number of bugs. But Linux exploits aren't necessarily exploits. If someone debugs the code and finds something that is written funky that can be taken advantage of, That is not an exploit because he knows right then and there how to fix it. It should be rated on how long known exploits are out before the exploit can be patched or taken care of. That is the real measure of security. When Microsoft wants to wait 3 weeks to release patches, release patches that cause more problems, or denies that the bugs exist that is more of an issue than anything else. At least with Linux when it's found it's taken care of.

    --

    If your not cheating your not trying. If your not trying your not winning and if your not winning why play?
  94. A *nix OS? Unsecure? Not Like Windows by Spencerian · · Score: 2, Insightful

    What someone said--a primary security hole (something you drive side-by-side trucks through) are Windows applications. Visual Basic and, by extension, Outlook, are big culprits.

    But many of the things that make Windows unsecure do extend at the OS level. Here on my Macintosh, my firewall is set to lock out IPs that try a NETBIOS check, as well as various port scans. It's also aware of the Code Red variants.

    My Mac OS (9 or X) ignore them. As with Linux, my OS doesn't know or care for NETBIOS.

    And OS X, as a better example for all the huff, is a *nix family OS--and still in its infancy compared to the older Linux distros and UNIX itself. A UNIX class OS is only unsecure in the magnitude of Windows when we open up all the elements of the OS that are normally closed by default--permissions, certain root access, and so on. Therefore, you have to be a Raving Buffoon(tm) to set Linux or any *nix for a fall.

    Window's faults are inherent to perpetuate its market share as well as stupid coding. And now MS wants to "fix" it? Give us a break.
    /.

    --
    Vos teneo officium eram periculosus ut vos recipero is.
  95. Lies,Damn liars and stats by Anonymous Coward · · Score: 0

    Anybody take a whole five seconds to look at the chart? Linux and it's bugs are counted by counting Red Hat,SuSE,Mandrake ETC ETC. So if a bug is found in the Linux kernel then that bug is counted Xtimes [once for every distribution] Hell they might count it once per release!.

    1. Re:Lies,Damn liars and stats by Anonymous Coward · · Score: 0

      Hell they might count it once per release

      Security holes aren't fixed before a new version is released???

      Wow! Linux is worse than I realised.

  96. Why is this automatically false? by Tom7 · · Score: 4, Insightful

    Again, I find it disturbing how easily everyone shrugs this off as propaganda or something.

    Listen, everyone: Times are changing. Linux has gotten big and complicated, and is no longer automatically secure. Long gone are the Slackware days where you'd download a minimal kernel/utilities package and then compile only the apps you need, by yourself, and understand everything. Complex software has security problems, and the linux community has done little but use the "lots of eyeballs" method to counter that. Microsoft software is also quite complex, and they have fewer eyeballs (I hope, though I am not sure), but they have publicly recognized the problem and are at least pretending to try to fix it. Microsoft also has a bunch of research into technologies for producing machine-checked code so that they don't even need lots of eyeballs. (I really wish that linux had this too; see a related rant http://slashdot.org/comments.pl?sid=26315&cid=2851 880 ).

    My linux box has been rooted twice. I keep up to date on patches, I read bugtraq. My windows box, also connected to the internet all the time (and getting a lot more use), has never been compromised through 95, 98, 2000, and XP.(I have been Winnuked, that's the worst thing that's happened.)

    I guess my point is: this is not something to laugh at. Some day soon, people will not think of Microsoft operating systems as crashy (already happening to an extent) and insecure (...), and then linux will have a much tougher sell to the average guy who doesn't care about Free Software. Instead of laughing smugly about an article like this, maybe we should be worrying?

    1. Re:Why is this automatically false? by Phoenix+Rising · · Score: 3, Interesting
      Microsoft also has a bunch of research into technologies for producing machine-checked code so that they don't even need lots of eyeballs. (I really wish that linux had this too;


      Linux DOES have this - there are various and sundry programs which will scan your code for you - even kernel code. And if you don't want to rely on the programmer, there are libraries available for Linux which prevent a number of these holes - automatically.


      My linux box has been rooted twice. I keep up to date on patches, I read bugtraq. My windows box, also connected to the internet all the time (and getting a lot more use), has never been compromised through 95, 98, 2000, and XP


      Of all the boxes I've had to monitor, only a disused Windows box has ever been compromised. I am constantly bombarded with virii and worm attacks from compromised Windows boxes; most of the Linux boxes "attacking" my network are owned by the hackers.


      I'd stand by my Linux install just as soon as I'd stand by any Windows box I've had a hand in hardening.

      --
      Let us live so that when we come to die, even the undertaker will be sorry -- Mark Twain
    2. Re:Why is this automatically false? by Grax · · Score: 1

      You failed to mention how you were rooted?

    3. Re:Why is this automatically false? by vicious_sloth · · Score: 1

      What everyone on slashdot is saying is that the comparasion is unfair, and therefore making it misleading, this is just another example of how to make statistics lie for you. No one is denying the problems with linux.

      --
      Sun is Warm, Grass is Green
    4. Re:Why is this automatically false? by jdavidb · · Score: 4, Informative

      Long gone are the Slackware days where you'd download a minimal kernel/utilities package and then compile only the apps you need, by yourself, and understand everything.



      Wrong. I entered those days quite recently, with Linux From Scratch. LFS isn't exactly a "security solution," but it's hard to break into a machine when there's nothing running on any port except ssh.

    5. Re:Why is this automatically false? by Skuld-Chan · · Score: 1

      none of my linux boxes have ever been compromised - they are just old sparcstations running debian. However I log literally hundreds of attempts per day - mostly from what I'm guesssing are zombied windows machines (at least thats what it looks like)

    6. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      Those days aren't gone. Download Slackware, install a minimal package set, and get to compilin'.

    7. Re:Why is this automatically false? by Mr.+Jackson · · Score: 1

      I too am amused by the tendency of all the posters to dismiss this article so completely. As a regular slashdot reader, I've learned to take as given that Windows is inherently insecure. To learn that one can add up a count of anything bad, unfairly or no, and get a higher number for Linux than Windows, well, hell, it's news, at least.

    8. Re:Why is this automatically false? by electroniceric · · Score: 1

      Well put. And if Linux does get any more substantial market penetration, there's ton of damage a rooted Linux box can do. Especially if it's playing firewall/gateway/router, etc.

      Rather than wasting valuable keystrokes complaining *yet again* that someone's biased against us, we ought to start working on simplifying patching. It's still too dang hard.

    9. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      Time to start running Debian my friend.

    10. Re:Why is this automatically false? by bmw · · Score: 1


      Listen, everyone: Times are changing. Linux has gotten big and complicated, and is no longer automatically secure. Long gone are the Slackware days where you'd download a minimal kernel/utilities package and then compile only the apps you need, by yourself, and understand everything. Complex software has security problems, and the linux community has done little but use the "lots of eyeballs" method to counter that. Microsoft software is also quite complex, and they have fewer eyeballs (I hope, though I am not sure), but they have publicly recognized the problem and are at least pretending to try to fix it. Microsoft also has a bunch of research into technologies for producing machine-checked code so that they don't even need lots of eyeballs.


      You are absolutely right, complex software is, by nature, less secure. The thing you seem to forget is that Microsoft operating systems are still far more complex than anything else I know of. The quantity of code is amazing. The fact that such complex and massive software even works at all is truly a feat of human engineering (the same is true for things like Mozilla). IIRC, Windows 2000 was estimated to have something like 40-60 million lines of code.

      "The size of Windows 2000 is absolutely amazing, and it will have even more security bugs than Windows NT 4.0 and Windows 98 combined." -- Bruce Schneier

      Due to the size and complexity of current MS software, there is absolutely no way they are going to secure what they already have. Regardless of how much effort they say they are putting into it. You cannot hack true security into software after it has been nearly completed. It MUST be designed into the software from the very beginning. How many people think that MS is going to completely rewrite Windows?

    11. Re:Why is this automatically false? by WNight · · Score: 2

      Of course Windows doesn't get "rooted", it doesn't do anything. I doubt more than 1% of windows boxes are running IIS/etc.

      My old 95 gaming box was nukable, but as you say, nothing else. But it couldn't do anything. Look further back to my MS-DOS box and it was totally secure, I mean NSA level secure. Of course, it wasn't network connected to anything, and didn't offer any network services, but ...

      I'll admit that Linux (and BSD, etc, etc) have problems. Even OpenBSD has a few bugs, I'm sure.

      The issue I take with this article is that it's being directly compared to Windows and found lacking - in security. I'd laugh, except for the incredible absurdity overload.

      Take Linux (from a security concious distro) and Windows, install both, with the same services and GUI. (This means a full install of KDE or Gnome)

      Count the holes in those, and get back to me.

      Then count the number of local root exploits, as in, let a user log in and run arbitrary binaries - see which machine is the most resistant to "rooting" or crashing. (Excepting boot-floppys, that's too easy.)

    12. Re:Why is this automatically false? by Tony-A · · Score: 2

      Actually, I think the comparison is fair. This is a count of vulnerabilities fixed or patched. Consider the depth of the fixes. Do they address the root causes or just twart a particular exploit? How often to the fixes backfire? How easy will it be to find the next exploit? Are you really that much safer with a currently patched system?

    13. Re:Why is this automatically false? by truffle+pig · · Score: 1

      I'll agree with the Statement that due to it's closed nature they are likely as to yet undiscovered vulnerabilities waiting in Windows 2000. That said there are likely vulnerabilites waiting to be discovered in the Myriad of Linux distos and components out there. With this in mind what makes Windows far more dangerous is a real lack of understanding and experience that many NT admins suffer from. We all know someone who read the test preps and Brain dumps and got their MCSE without any real understanding of the nuts and bolts of NT. Therefore with no clue of what they are/were trying to secure. With good Engineers and Admins I am just as comfortable with the security of a Windows box as I am with a *NIX box. The whole thing plays right into the whole guns don't kill people...people kill people argument. Operating Systems don't kill Admins...Admins kill Admins or something like that.

    14. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      I am running debian.
      BIND got me anyway, 2 days after I installed the newest version.

    15. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      Well, yes, that's how you and I run linux perhaps, but that is not what "linux" is today.

    16. Re:Why is this automatically false? by Tom7 · · Score: 1


      OK, sure...

      I got rooted by the BIND exploit before it was patched. (.edu spaces tend to get scanned for vulnerabilities early since they usually have great bandwidth) This particularly pissed me off because I had *just* upgraded to the newest bind at the time. Fortunately, their root kit made my machine not boot, so they didn't really do any damage.

      The first time was with wu_ftpd, a long time ago. I have since gotten sick of patching that beast, and I re-wrote it in SML to be buffer-overflow free (see other rant).

      My point was not that Windows has no security holes if you run lots of network services, merely that even a reasonably vigilant person can still get their linux box rooted. It is far from invincible; it just tends to be simpler (at least, it used to be) and have more capable users.

    17. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      You call that being vigilent? lol. what a bunch of crap. You installed 2 of the most insecure programs for Unix and you wonder why you got hacked. rofl.

    18. Re:Why is this automatically false? by Tom7 · · Score: 1

      An AC flames,

      > You call that being vigilent? lol. what a bunch of
      > crap. You installed 2 of the most insecure
      > programs for Unix and you wonder why you got
      > hacked. rofl.

      Actually, asshead, they came with my distribution of linux. I am talking about linux the operating system, not like "the kernel plus sshd" (which, as I recall, has also had remote exploits recently).

      Vigilance refers to my expediency in staying up-to-date on patches. My overall point is that linux and its associated applications are not particularly secure.

    19. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      How can a Linux box do more damage than a Windows box when cracked? I really don't understand this argument at all, but it has resulted in my department not allowing Linux on personal workstations connected to the net. Is it that Linux systems have so much functionality for havoc without additional software installs? Does it actually make a difference to a cracker?

    20. Re:Why is this automatically false? by Anonymous Coward · · Score: 0

      So they came with your distro, WTF didn't you turn them off?

    21. Re:Why is this automatically false? by fredrik70 · · Score: 1

      well win2K was pretty much a rewrite rather than building on the NT kernel

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    22. Re:Why is this automatically false? by Grax · · Score: 1

      I would say that Linux has more tools to work with to secure a system. Whether a specific project is secure or not seems to depend on the programmers for that specific project. Both BIND and wu_ftpd have a history. Unfornately you're probably one of the ones that was using them when they got that history.

      I run BIND chroot and on a non-root account. That should offer some extra protection. and I don't run any ftp server. I'm unhappy with the protocol so I use http instead of anonymous ftp and ssh/scp instead of password protected ftp.

      Also, while you were rewriting wu_ftpd, IIS was suffering from a multitude of flaws, yet you had no opportunity to rewrite that to fix them.

    23. Re:Why is this automatically false? by Tom7 · · Score: 1


      An AC flames,

      > So they came with your distro, WTF didn't you turn them off?

      Because I need them.

      Eventually I got sick of security issues and rewrote FTPD, (BIND is soon...) but the fact remains that those are the standard network services for linux, and they are insecure. Unless you think linux is just the kernel, I think it's fair to say that linux has its fair share of security problems unless you replace some of its packages with others.

    24. Re:Why is this automatically false? by Tom7 · · Score: 1


      I agree with you that it is easier to secure a linux system, but mainly because it is just simpler. On one side people are still working on things like linuxconf to make it easier for unknowledgeable folks to admin a linux box -- and (I think) this will lead to security problems, just as GUIs and wizards did in windows. But windows already has years of experience...

      > Also, while you were rewriting wu_ftpd, IIS was
      > suffering from a multitude of flaws, yet you had
      > no opportunity to rewrite that to fix them.

      Sure I did. I presume you're implying that because it's closed-source? I didn't need the source to rewrite the ftp daemon (from scratch); the source is shitty, huge, and in a different language. I just used the RFC, and it would have been just as easy to rewrite a web server.

    25. Re:Why is this automatically false? by Grax · · Score: 1

      The term rewrite made me think that you rewrote wu_ftpd rather than wrote your own ftp server.

      Writing a web server is pretty easy. Writing a web server that supports activeX components, indexing, etc in a secure fashion is a lot harder.

      As far as Linux being simpler, why in the world would I want a web server capable of 3d graphics, neato sound effects, etc. My Linux servers have uptimes of 7 1/2 months. They would have been up the entire year since their install if not for a power problem at our ISP. Simpler is good. Experienced people should have figured that out by now.

  97. shades of April First grin by Anonymous Coward · · Score: 0

    illustrates the art of marketing nicely, a more well written piece of managerial verbage as was ever wrought ... ten for ten

    2tek
    if windows was a ship, i'd be bailing

  98. Winformant.com runs on NT! by larsu · · Score: 1

    Netcraft says that www.wininformant.com, the site which holds this report, which got promptly slashdotted, runs IIS4 on NT4.
    I'll refrain from making jokes about Win boxes not being up long enough to be exploited, or something like that.

  99. He's right, but for the wrong reasons by ChaosMt · · Score: 2

    Linux is a target. When the black hats are sweeping the network, they see a bunch of windows boxes that are easy to break into; whoopty-shit, who cares. No challenge, no glory, and no use. On the other hand, when they find a linux box, it's a gold mine. Linux is the friendly unix which give it's owners a false sense of security. Linux, being easy, tends to install so much, which gives greater opportunities to install security flaws. Linux is also far more useful to a black hat. He's probably also using linux; he can just run his root kit with out thinking and then all of his tools are installed and ran without a recompile or any fuss. It's easier for black hats to own a linux box and use it's network tools than it is for a black hat to do the same with a windoze box. Most linux boxes have a compiler installed (which is right and good thing), the opposite is in windoze land.

    Conclusion: Linux is still better and more powerful than windoze any day, which makes is a more attrative target. Since the barrier to entry with linux has been deeply lowered, may nieve good people are installing a powerful OS for fun, just to find out that with power, comes resposibility.

  100. Burn, baby burn by .sig · · Score: 2

    Well, I've never used a computer in my life, so I obviously have no bias whatsoever in this. I don't know the details of why Windows is said to be more secure than linux (slashdotted already, of course) but it seems pretty obvious.

    I'm not one to bash Linux, though I prefer a real *nix any day. However, I'm not one to bash Windows either, it's actually a pretty good OS. (Something that I can see a lot more now that I work with a copmpany designing systems dozens of time more bloated and complicated than even XP) The real reason Windows seems so much more insecure is because so many people use it, and it's become such a standard that it makes an easy target for custom made cracking tools. It's just as easy, if not easier, for someone who knows what he's doing to break into a linux system and completely take over. In fact, it's always seemed to me like someone could do more damage with a cracked linux box than with a Windows one.

    But of course windows doesn't stand a chance here, it's hard to argue with an "I'm right because I said so" attitude that a lot of the more vocal people seem to have. I honestly thought my monitor was going to burst into flames when I started reading the above comments...

    --
    -Space for rent
    1. Re:Burn, baby burn by Anonymous Coward · · Score: 0

      Well, I've never used a computer in my life

      How did this post get here?

    2. Re:Burn, baby burn by .sig · · Score: 1

      Sorry, the ironic tags must have gotten parsed out. It was supposed to be funny, as only someone who has never used a computer would truley be unbiased as to what the best OS is.

      --
      -Space for rent
  101. MS new focus on security... by wheel · · Score: 1
    ... starts with a PR blitz about how it's already secure!


    Typical.

  102. Makes sense by kick_in_the_eye · · Score: 1

    The more a system is up, the more you can break into it. The BSOD (copyright MS) is the security that Linux needs. Its the one secure feature that even the best crackers cannot get past. Show me a room full of BSOD NT Servers, and you'll also see a room of secure data and apps. Linux does win with file security though. If you direct all data to /dev/null, I dare anybody to break in and read that data. We call that Write many, read none.

  103. Stats by marvin+tph · · Score: 1

    According to the page OSX-server had only 1 vulnerability in 5 years. I doubt this is very accurate (if it is feel free to chime in with recommendations that we all switch OS's immediately). I think we need to keep in mind that This whole thing is wildly inaccurate. Rounding errors, double counting, unreported bugs, firewalls. If you're using these numbers to do anything important, you're insane.

  104. Apples to Open Source Oranges by Anonymous Coward · · Score: 0

    Setting aside the accuracy of the results, this is a comparison of a system where the code can be examined by anyone and a system that doesn't allow the public to view the code. Even if the systems had an identical number of bugs (which I am not claiming) the open system would have more bugs reported simply based on the fact that the errors can't hide behind compiled binaries.

  105. Very secure... by ehiris · · Score: 1

    Scalable and stable too :)

    OOOOOPS the site is gone lol

  106. Hmmm.... by Seabass55 · · Score: 1

    Maybe since they are reporting that Windows is more secure.
    SecurityFocusdotcom is now switching over from Linuxto XP.

  107. Case of bad statistics by alta · · Score: 3, Insightful

    Ok, here's what I noticed. The SUM of all Linux's put together had a higher bugcount than windows 2000.

    Now, how many people do you know that install redhat, then add to it all the security bugs in caldera, Connectiva, Mandrake, Slackeware, Suse, and Turbo Linux?? None, that would be extremely difficult. This is akin to saying the Ford Taurus has fewer bugs than all of the Nissans put together, therefore it is a better product.

    Also, we are assuming that all bugs are created equal. Guess what, not so. Windows bugs have superpowers, faster than a speeding packet, stronger than a firewall, able to leap entire networks in a single bound! Linux security bugs take down processes, sometimes servers. Windows bugs take down Networks, or internets!!!

    But I'm sure they'll never get called on it, because their readership is windows users. They are preaching to the choir, and they will ignore us and our quest for accuracy.

    --
    Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.
  108. how to manipulate statistics by kkith · · Score: 1

    LOL, this so called "scientific" data has been presented in such a way that a Windows marketer would love. First note that Linux has an AGGREGATE column while Windows does not. A better use of the graphs would be to remove the aggregate column. I mean really, does a Linux distribution exists that incorporates ALL other distributions? I don't think so. If the Linux aggregate column cannot be removed, then a more fair representation would be to also aggregate the Windows vulnerabilities, then check to see how the numbers compare. I also wonder how the numbers have changed with the introduction of XP. A side note: Besides...what good is an OS that had less vulnerabilities crop up last year when that system is unstable! (IE Windoze)

  109. MICROSOFTS new focus on SECURITY - Security Focus by argoff · · Score: 2

    Well, now we know what they were really talking about when Microsoft said they were going to place a new focus on security - "SecurityFocus", or focus on Linux security and not Microft security.

    Of corse it's been known for a long time that Linux has more security flaws *REPORTED* simply because it 's open source, and people do alot of intense study of it's security. But this does not mean that Linux is less secure, it means that we find and fix security flaws faster than Microsoft can find them.

  110. Inexperienced Programmers? by johnthorensen · · Score: 3, Insightful

    I was thinking to myself yesterday about how the nature of open-source lends itself to a lack of "talent auditing". Meaning, there **MAY** be a greater chance of bugs being introduced into an open-source project because the programmers are often not hired professionals.

    I would like to see a comparison in bugcounts (say, per line of source code) between open-source projects supported by professionals (i.e. people trying to make money off of it, i.e. mySQL) and projects supported by weekend programmers.

    I just had an ironic thought. Since most open-source business plans revolve around providing support, would that make those companies want to introduce MORE bugs? :-P

  111. Data shows Windows pretty bad by jcasey · · Score: 2, Insightful

    Take another look at the data refrenced by the article! It actually shows the Windows 2000 was one of the worst as far as security goes. The linux aggregate score does not resemble any of the individual linux distros mentioned. What I would like to know is, How did the author ever draw the conclusion that Windows 2k was more secure ? And what was the point of comparing the score of an os with an aggregate score ? That makes no sense either!

    --
    X
  112. Ah the joys of FUD by bruns · · Score: 1

    These idiots probably counted up security reports by adding each report from each distribution together rather then per package/kernel/etc.

    The same report from Debian, Redhat, Slackware, and Mandrake doesn't frickin mean that there are 4 holes! It means that there is 1 hole. When will they get this through their head?

    You have to look at each report, match each hole, count it as 1, and move onto the next. I'll bet that in the end, 9x/NT will have about 2x as much security holes, if not more.

    --
    Brielle
    1. Re:Ah the joys of FUD by bruns · · Score: 1

      MMm, looks like I am right (from the vnunet.com article):

      Breaking the figures down by distribution, Mandrake Linux 7.2 notched up 33 vulnerabilities, Red Hat 7.0 suffered 28, Mandrake 7.1 had 27 and Debian 2.2 had 26.

      How much you want to bet the bulk of them are the exact same bug?

      --
      Brielle
  113. Not True by j7953 · · Score: 5, Insightful
    [...] To get the security problems for Linux, he adds all security announcements from each of the major distributions - completely ignoring that most of those announcements are for the same bug. [...]

    I can't connect to WinInformant, but if you look at the numbers available at SecurityFocus, you'll see that they did not simply add up the numbers. Linux is listet with 96 aggregated vulnerabilities for 2001, while e.g. Red Hat has 54, Debian got 28, and Mandrake got 36. There are more Linux distributions listed, but these numbers allone show that your claim is wrong (unless WinInformant has different numbers).

    You'll also see that Red Hat had 54 vulnerabilities while Windows 2000 had only 42.

    However, I'd still agree that the WinInformant article is badly researched (but please note that, as stated above, I've not read it, I only know the part that Slashdot quoted). The article claims that Windows is more secure "according to the reputable NTBugTraq," however, SecurityFocus does not make any claim concerning the security of either Windows or Linux, they just make the numbers available as a statistic. In other words, WinInformant doesn't have any source for their claims, they just found some more or less interesting numbers and made up a story.

    --
    Sig (appended to the end of comments I post, 54 chars)
    1. Re:Not True by Znork · · Score: 2

      SF has, for those with memory, already been through this before, and pointed out that anyone reading the numbers the way WinInformant appears to have done has a problem comprehending these statistics.

    2. Re:Not True by Anonymous Coward · · Score: 0

      So if I understand correctly, they're comparing the aggregate Linux figure vs. the Windows figure. That's still pretty bogus. Suppose, for the sake of argument, that these figures included one vulnerability in sendmail, one vulnerability in Exim, and one vulnerability in Postfix. Because RH uses sendmail, Debian uses Exim, and Mandrake uses Postfix (all by default), this would count as three vulnerabilities, despite the fact that just one of those servers would be installed on any given system. A better measure would be the average number of vulnerabilities per distribution. In the case of the three you've mentioned, that works out to 39.3, which is less than the 42 for Windows.

      Of course, this is all just a band-aid on what sounds like reporting with much more serious problems, but still....

    3. Re:Not True by fidget42 · · Score: 1

      You'll also see that Red Hat had 54 vulnerabilities while Windows 2000 had only 42.

      I wonder if they lumped all RedHat distros together (6.0, 6.1, 7.0, 7.1, ad infinitum). Or all versions of each Linux distro for that matter? Just a thought

      --
      The dogcow says "Moof!"
    4. Re:Not True by blazerw11 · · Score: 2

      You'll also see that Red Hat had 54 vulnerabilities while Windows 2000 had only 42.

      It was Windows 2000 and NT and all of RedHat's supported distributions. No Windows XP.

      In 2001, RedHat was support 6.0 to 7.2 (6.0,6.1,6.2,7.0,7.1,7.2) That's 6 releases! They have been reporting security issues in all of these. For instance, The enscript (RHSA-2002-012) here can be found under security updates for all those distributions. This is an issue from this year, tho (2002-1-17).

      Worst case for MS is a double count on the NT/2k grouping.

      BugTraq updated their site to say basically that their grouping methodology is poor and skews the numbers.

      --
      A great many people think they are thinking when they are merely rearranging their prejudices. -- William James
    5. Re:Not True by mjh · · Score: 2
      However, I'd still agree that the WinInformant article is badly researched
      I've read a lot of "information" articles at WinInformant. Enough to know that their use of the prefixes "Win" and "dis" are roughly equivalent when applied to any form of the word "information".
      --
      Key to financial independence: Spend less than you earn. Save and invest the difference. Do it for a long time.
  114. Anyone should know this... by Anonymous Coward · · Score: 0

    A system is only as secure as its weakest link...and that includes sysadmins. If this a security issue, windows and linux can both be as secure or insecure, depending on how it's set up. And there is NO system so secure you can't get into it. The numbers mean didley in a case like this...

  115. DUH - Individual Distros all beat Windows NT by Anonymous Coward · · Score: 0

    What exactly does the linux aggregate represent. Who would be idiot enough to install all of the major distributions on the same machine. Or even on multiple machines. Why don't they have a windows agregate that includes all of the different windows variants (not too mention where is XP). More secure than what? Apples to orange here (not oranges they compare one distribution to multiple distributions). Get a clue on your reporting.

  116. This might take down my poor little server! by penguin_nipple · · Score: 2
    How vague of the story!

    Are they referring to the core OS? Regarding kernel vulnerabilities? Regarding Apache vs. IIS? I noticed one of the tables on the SecurityFocus site, show "Top Vulnerable Packages 2001" - what exactly does that mean? , installed packages and running daemons? or the kernel each OS is packaging?

    Look at those tables. How can you refer to Windows NT 4.0 versus Internet Explorer versus IIS versus RedHat Linux 5.2!!!

    Those are really huge apples and massive oranges... This is marketing fluff, vague and doesn't do anyone any good! Doesn't matter if you are referring to Windows, Linux, Solaris, QNX, or whatever. These are raw stats, without enough detail to make an informed decision regarding their meaning.

    Look deeper into statistics, et al. before flaming one way of the other!

    OK , so let's narrow it down Microsoft IIS servers are more secure than Linux/*NIX/Apache servers? How about the immesnse propogation of crap that unpatched IIS servers are propogating on the 'net?

    I am running a little hobby server at home, running FreeBSD and I have been getting a HUGE number of NIMDA requests, so , is NIMDA resolved? ummm I think not...

    Here's the proof, it's a quick and dirty generation of the requests my apache is getting from the clueless IIS dorks on Rogers@Home (an informal traceroute has shown most of the requests coming from within the @Home network).

    I like SF , I read SF, but those tables and statistics are completely ridiculous and I'm not even slamming MSFT one way or the other....

  117. This Sounds Like The "USRobotics Effect" by istartedi · · Score: 2, Troll

    When I was in tech support, everybody thought USRobotics modems sucked. We spent a lot of time dealing with USRobotics problems, much more than any other modem. Then we realized that USRobotics modems were in 70-80% of the PCs on the market. That meant that if USR modems caused 60% of our problems, they were actually better than the average modem!

    I can't get to the article, but if they are talking about desktops, then anything less than 90% of the security problems coming from Windows actually means that Windows is better than average. For servers that number would have to be what, 30%?

    There are other statistics involved here too. For example, Linux people always point out that Linux bugs get fixed faster than Windows bugs. True, but if the Windows patch gets released after 2 weeks, you still are still running clean more than 90% of the time--it just doesn't make that big a statistical difference.

    Then of course there is the difference between "bugs found" and "bugs exploited". I imagine fewer "hackers" exploit Linux bugs because of sheer hate for "M$". If they ever let an AOLinux loose on the market, it might become a hate-target, and then all of the sudden Linux looks a lot less secure.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    1. Re:This Sounds Like The "USRobotics Effect" by Anonymous Coward · · Score: 0
      Of course, U.S. Robotics modems really do suck, now that they've been bought out and sullied their good name.

      ~~~

    2. Re:This Sounds Like The "USRobotics Effect" by Anonymous Coward · · Score: 0

      Ah, remember the days when we could salivate over the possibility of someday, just maybe, getting one of those sweet 16.4Kbps USR Couriers for your BBS? Or how about the totally awesome proprietary 9600Bps HSTs!!! Luxury!! I was lame and had to buy a cheap $250 v.32bis 14.4k modem to upgrade from 2400bps.. :-(

    3. Re:This Sounds Like The "USRobotics Effect" by laudre · · Score: 1

      When I was in tech support, everybody thought USRobotics modems sucked. We spent a lot of time dealing with USRobotics problems, much more than any other modem. Then we realized that USRobotics modems were in 70-80% of the PCs on the market. That meant that if USR modems caused 60% of our problems, they were actually better than the average modem! This is a straw man argument. When you're in tech support, you're dealing with things on a purely quantitative basis, and often dealing with the same problem many, many times. When I worked tech support for an ISP, there was a known problem with X2 USR modems, and a known workaround. A good 50% of our phone calls, for a span of time, had to do with that exact problem; we'd rattle off the instructions for the fix over the phone, and then take the next call, which would be either that problem or, most likely, one of two or three other common problems. As I recall, 95% of our calls were dealing with known issues; while our call volume was high, our actual workload was pretty small, since it was pretty much repetition. The numbers we're seeing here, though, are tracking separate bugs, not repetitions of the same bugs (except, as noted, where those bugs are repeated across Linux distros). And, as I recall from reading the article off of OSNews yesterday, it's both servers and desktops. If anything, the article, as has been noted before, is heavily weighted towards showing that Linux is less secure by misrepresenting the numbers.

    4. Re:This Sounds Like The "USRobotics Effect" by geekoid · · Score: 2

      When I was in tech support, everybody thought USRobotics modems sucked. We spent a lot of time dealing with USRobotics problems, much more than any other modem. Then we realized that USRobotics modems were in 70-80% of the PCs on the market. That meant that if USR modems caused 60% of our problems, they were actually better than the average modem!
      This makes it painfullyclear that you need to make some effort to study statistics, and how to aplly numbers, because that is a meanless statement, statistically.
      At no point where USRobotics in 70-80% of the PCs, ever. When I worked there they wished that was true. In its most glorious days, it was about 40%.
      60% of your problems? is that all p[roblems or just modem problems? for the sake of arduement I'll say that you meant modem problems.
      again, meaningless. Is that total phove calls? or total unique problems. i.e. not 10 people all calling with the same problem.
      so, if you had 100 people, 80 of them have modem A installed, and 20 of them have Modem B installed.
      And all of them have the same (in)competencty level. Now in this situation if 60% of your calls dealing with modem hardware problems where USR you tenitavly have a point.
      But since you where dealing with more then 2 modems, you have no way of knowing the breakdown for each type. sure 60% of them might be modem A, but the reamaining could ALL have a different modem(unlikely), and thus each one better then Modem A.
      What is a 60% problem rate compared to the industry as a whole? that is what you need to compare to begin to get meaningfull information from your numbers.

      Gaining this kind of information can be tricky, which is why you don't go to a site, just gather numbers, then expect the results to even be slightly correct.

      Then of course there is the difference between "bugs found" and "bugs exploited". I imagine fewer "hackers" exploit Linux bugs because of sheer hate for "M$". If they ever let an AOLinux loose on the market, it might become a hate-target, and then all of the sudden Linux looks a lot less secure.

      You clearly don't understand the mentality of people who like to break into other systems(note I do no use the term hacker). You break into windows people say "eh, been there done that" you break into a box woith a secure reputation, now your cock of the walk, so to say.
      yes there is a big difference between the "bugs found" and "bugs exploited". People find bugs in Linux, and report them. How do you find a bug in Windows, befor its been exploited? you don't.

      you still are still running clean more than 90% of the timeyou can't know that. If its an exploite to your system, and its not patched, you have no way of knowing whether or not you've been rooted.

      I would love Windows to become a model of security, most of my family uses it and I don't want to see them get hurt by some dufus with a script, but its not.
      Both history and real experience point, time and time again to Windows being unsecure.
      Its getting better, but its a long way from Linux, and even a longer way from BSD.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    5. Re:This Sounds Like The "USRobotics Effect" by fferreres · · Score: 0

      Learn some math. One thing is reported problems or tech support calls, that would rise in the same amount than the installed base.

      Another thing is problems found in the modem or OS. They could scale as a larger installed base makes for a more profitable exploit, but they are independant from installed base.

      --
      unfinished: (adj.)
  118. Easier than that... the accounting is WRONG... by Anonymous Coward · · Score: 0

    The accounting is wrong... they are counting Mandrake, Red hat, etc... they aren't sorting out common exploits to distributions... e.g., if the snuff_server X.YZ had an exploit bug and that version of snuff_server was present in 6 different distros they are counted as 12 different exploits... it's not correct... if they want to summarize all distros as LINUX, they should account only individual exploits. By the way... I think that flame bait was posted about one year ago... was an article written by some MS-friendly journalist...

  119. site gone down by csbruce · · Score: 2

    Looks like the WinInfo site has gone down since the story was submitted, so you may have to content yourself in the meantime with the Bugtraq numbers.

    Musta been hacked.

  120. My response to this posting: by Figz · · Score: 1

    hahahahahahahaha....

    demonic, uncontrollable laughter continues indefinitely....

    --
    [figz@figz figz]$ kill -9 `ps -ef | awk '$1=="figz" { print $2 }'`
  121. Quit freaking out, it is obviously flawed by Squash · · Score: 2, Informative

    The moron at wininformant added all exploits for all linux distributions together. Image the obvious scenerio, where bind8.x.x has a root compromise. This would only count as a single exploit, however the article counts it once for eash distribution that acknowledged it.
    If you look at the charts yourself, you see that Win2k had 42 exploits in 2001. In comparison, SuSe had 21. Redhat had 54. OpenBSD had 14. The figures also are not focused on a particular release. I would expect that the numbers would be substantially lower if it only look into account the current releases. Suprise, SuSE still publishes security announcements for 6.x in addition to 7.x, and those are counted.

    THe author of the atricle need to look up Aggregate and try writing an article again.

    --
    Squash
  122. Simply put youre dead wrong by Srin+Tuar · · Score: 5, Insightful


    Of course, that's not the case in the server market. If you want to talk about worms, remember one thing - the ONLY reason Code Red and other such worms exist is because of the popularity if the windows platform, on desktops and servers. Don't kid yourself for a second into thinking that the reason there aren't any widespread worms for *nix systems is because it's more secure.


    Dont kid yourself. The various free o/s's are simply a harder target. They are more diverse, both across O/S's and distributions, and even within a distribution there are different configurations. On top of all that any individual box can be a totally custom system built from the source pool.


    There are countless email readers, multiple web browsers, all types of competing server daemons. When you take the windows monoculture you simply dont find such diversity. The competing software are simply wiped out.


    Its a well known and intuitive fact that monocultures are far more vulnerable to disease and parasites than a healthy diverse population.

    1. Re:Simply put youre dead wrong by Hoonis · · Score: 1
      This isn't really the point. The reason all those Microsoft worms are so prevalent is simple, default out-of-the-box configurations sitting on DSL connections or Cable modems are perfect launchpads for DDOS attacks.

      Why isn't this happening on linux boxes? IT IS! *ANY* operating system that is hooked up 24/7 to an internet connection is a target, INCLUDING linux. The fact that it CAN be secured doesn't mean it WILL be.. the number of people who don't patch their OS when ssh, bind, wu-ftpd, ptrace expoits, etc are discovered is probably around 99%.

      DDOS attacks originating from cracked linux boxes are going on already, there really are just fewer of these in use in the DSL/Cable Modem scenario compared to Microsoft machines running IIs.

      If you think *you* are safe, go check out CERT for exploits on any outside-facing services you are running. The older SSH protocol has a widely publicized flaw that results in many machines being rooted. You can only keep yourself safe through constant maintenance & vigilance.

    2. Re:Simply put youre dead wrong by Anonymous Coward · · Score: 0

      " the number of people who don't patch their OS when ssh, bind, wu-ftpd, ptrace expoits, etc are discovered is probably around 99%."

      Really? And where did you find this number? NTBugtraq?

      If you're going to post something like this, post facts, not numbers pulled from your ass. Try to consider the relevance of your argument as well. Does a linux server NOT RUNNING ssh need an ssh update? Not every linux box on the planet with a 24/7 connection is running ssh. Wu isn't as prevalent as it used to be either, most new admins are going with proftpd.

    3. Re:Simply put youre dead wrong by SilentChris · · Score: 2
      So you're saying that its easier to find holes in Open Source software? Wouldn't this make it easier for a cracker to read the source code and build an exploit off it?

      There is some advantage to security through obscurity. Say, for starters, some hacker X tries to exploit OS's Y and Z. Y is Open Source. He looks at the code, finds a bad buffer, builds his exploit. Z is closed. He has to root around with BlackIC (or any of the other hacking tools), play around with the assembly, maybe even wreck a few OS's in the process?

      Which one do you think is faster?

      Further, once the vulnerability is released, what makes people think it'll be "easier" to discover on the Open side? I'm in the same situation as if my OS was closed. For example, I've just discovered a vulnerability that causes my screen to show "Hey Dude". Someone must have broken in. But where's the problem? The screen buffer? The IP stack? A misguided pointer? While thousands of people are spending hours to pour over the Open code finding a needle in a haystack, Microsoft's (admittally) no better developers, who are a much smaller group and can work with a much more homogeneous code base, don't have to work nearly as hard because they pretty much know the code inside out.

    4. Re:Simply put youre dead wrong by JimmytheGeek · · Score: 1

      "Microsoft's (admittally) no better developers, who are a much smaller group and can work with a much more homogeneous code base, don't have to work nearly as hard because they pretty much know the code inside out."

      Actually, there are thousands of developers with a hand in nt/2k/xp, and nobody knows 40+million lines of code inside and out. Many changes to the MSFC dll are done by different PRODUCT DIVISIONS (eg SMS from the backoffice folks, IE, office, etc.)

      I found most of the developers I encountered to be competent stepford wives/husbands - kind of plastic, missing something fundamental to humanity- but they could code. There were a few that matched the super-iq hype MS surrounds itself with. Anyway, broadly speaking you are probably right: the coding ability is probably comparable. The coding MOTIVATION is very different between open source developers, who do it for love, and MS coders, many of which I suspect are incapable of love. The quality bar was explicitly - "good enough for market adoption"
      That has to contribute to dehuminization, and account for the manifest difference in quality between flagship Open Source projects and MS products.

    5. Re:Simply put youre dead wrong by SilentChris · · Score: 2
      "many of which I suspect are incapable of love"

      I doubt very much in that. Many techheads I know (outside of the few in the late 90s who were taking administration courses to "make a quick buck") are totally indebted to technology and play with it just as much at home as at work. That includes coding. That included Microsoft developers who go home and (guess what) work on code for everything, and in all likelihood other OS's.

    6. Re:Simply put youre dead wrong by ThaReetLad · · Score: 1

      If you're into shooting fish in a barrel, you'll aim at the big fish. Slightly different point, I'm a totally green linux user. I installed it once an got totally lost. The default installation must have been frighteningly insecure, as bad, if not worse than a default Win2k one. But at least M$ included a method to guide and encourage novice users to keep their system more or less up to date via Windows Update. If I had stuck with Linux i'd have been a menace to the internet.

      --
      You can't win Darth. If you mod me down, I shall become more powerful than you could possibly imagine
    7. Re:Simply put youre dead wrong by cyclist1200 · · Score: 1

      Sounds like your linux experience took place quite awhile ago.

  123. This is not news! by Adrian+Voinea · · Score: 2

    Is this news? We all know that Windows is reliable, secure and easy to use. My MCSE friend told me that, so it must be true!

    On a more serious note, there might have been more reported Linux vulnerabilities, but the Windows vulnerabilities were much more serious. Also, you can't compare the number of vulnerabilities discovered in the code of open-source software with the number of vulnerabilities discovered in closed-source, not-allowed-to-be-reverse-engineered software.
    aka... It's much harder to find a Windows vulnerability than it is to find a Linux one.

  124. This just in ... by Serpent+Mage · · Score: 3, Funny

    Connectiva has been declared the safest operating system ever with combined vulnerabilities over the last 5 years equalling 0. Everyone in corporate america and those banks too should immediately through out all other operating systems and switch over to Connectiva.

    Warning: Connectiva does not support vulnerabilities and all calls will be redirected to the nearest OS distributor.

  125. Re:What?!? by Anonymous Coward · · Score: 0

    The 20 second limit I'm sure is to avoid the "Me too!" type posts that say such trivial things as "I agree!". I hardly think it's some indicator that your brilliant typing skills are so 133t that you are outside of the normal bounds.

    In 20 seconds a fairly good typist (60wpm) can type about 20 words. The 20 second limit is sorta saying "If what you have to say is less than 20 words then maybe you shouldn't say it?".

  126. reading and comprehension is a good thing by plik · · Score: 1

    I dont understand.

    They compare each Linux distribution individually AND combine them all together? The statistic that WinInformant must be using is comparing Linux (aggragate) aka all Linux distro's combined. And when you combine all of the Linux distro's together _all_ of them have had more security exploits then Microsoft Windows? Well, uh, duh! You don't have Debian NT, Redhat NT, SuSE NT, et all. You have Microsoft NT. Whoever wrote the summary for that survey is a complete moron. But maybe thats what the article moderators want? Submissions by morons? To not carefully analyze what gets posted so that people can get really pissed, so I'll be here posting this message? The title should _not_ say Security Focus says windows more secure then Linux. Maybe WinInformant did, but I haven't been able to look at the original article yet. Morons. All of them.

    Regards,
    Tom

  127. Re:Why page widening is evil by Anonymous Coward · · Score: 0

    I like the page widening troll. I think hes funny so suck it!

  128. Usage Pattern by Ixikchitl · · Score: 1

    The charts at BugTraq seem to follow the market share and usage rather than actual bug information. In other words they are handling only reported bugs.

  129. Another important factor... by Comrade+Brightski · · Score: 1

    One thing I think people often forget to consider is the familiarity the sysadmin has with administering his particular distro. With the exception of a few, even the some of the most hardcore Linux zealots cut their teeth on Windows before switching to Linux. Thus, no matter how secure an OS is, it's only as good as the person running it-- and the majority of the population is better at running Windows. I think that the open source nature and sheer simplicity (in design, anyways) of Linux lends itself to being a much more capable performer, given an experienced user. It just happens to take a lot more time and effort to patch, recompile, reinstall, and reboot than it does to download and execute the latest patch from Microsoft. And of course, being geeks, we have the burden of upholding one of Larry Wall's three sacred virtues... laziness. ;)

    --
    "Software is like sex. It's better when it's free." -Linus Torvalds
    1. Re:Another important factor... by juhaz · · Score: 1

      Well, that might have been it ten years ago, but on any modern distro, you fire up your up2date, apt-get, or equivalent, get and install those patches almost automatically, and then you either boot or don't boot, depending on if it's kernel bug or in user land.

      Just happens to take a lot less time and effort than to download the latest patch from microsoft, and boot n times.

  130. And I quote: by JoeGee · · Score: 2, Informative
    "These vulnerability statistics have not been calculated since August due to a site migration issue. We are working on the issue and as soon as it is fixed, this message will disappear. Thank you for your understanding."

    Since August we have had these recent problems. The universal plug n play bug was even on /.'s front page. Partial numbers for a year don't tell the whole story.

    I subscribe to both bugtraq and ntbugtraq, and I must say the general quality and quantity of ntbugtraq submissions has decreased considerably in the past year. Most bug-related Windows traffic seems to be appearing over on bugtraq. While I certainly admire Russ Cooper's knowledge, I am not certain that his list is any longer a completely accurate source for information regarding Windows-related security issues, and I question any numbers based on ntbugtraq submissions.

    Some security issues must be significant enough for Microsoft to release a 17 MB "security rollup package" for Windows 2000 on January 30th, 2002.
    --

    Get off my virtual lawn, you damned virtual kids!
  131. Re:What?!? by Aqua+OS+X · · Score: 1, Insightful

    Let's just put it this way. More people use windows, more people want to exploit windows... and at the very least, from a social perspective, windows is bound to be less secure.

    This last year the window community has really taken quite the widespread beating with viri (as usual). The linux community has not. Less people use linux, less people know what to do with linux, less people hate linux, less people wish to exploit it, and therefore less people are going to screw with it.

    No operating system is perfect and or totally secure, however the more you scrutinize something the more apparent its flaws become. The Windows operating system has a hell of a lot more people looking at it under the micro scope...and that's an understatement. This, along with geek loathing and common software variables, is the reason why windows is less secure. The widespread common viri are just the result of all of this BS, and in my mind they totally prove that Windows is less secure. This is the same argument that us Mac diehards have been spitting out for years.

    --
    "Things are more moderner than before- bigger, and yet smaller- it's computers-- San Dimas High School football RULES!"
  132. another take... by Anonymous Coward · · Score: 0

    another take can be found on this story, here: vnunet and here .

  133. Dos from hacked boxes. by Anonymous Coward · · Score: 0

    Pretty much all DoS attacks come from hacked linux boxes. 95% mabye? Oh... and the other 5% doesn't come from Windows-based machines either. Script kiddies hijack (l33t word of the week for 'hack') linux boses and use them for their own agendas. From using age-old security flaws to exploits which are not even publicly known yet, they take over boxes (most often undetected by their admins) and use them to attack. I know code-red was very wide spread (no pun intented), but in my opinion the problems DoS attacks can cause are be faw worse than such windows-based viruses.

  134. Worse still by Srin+Tuar · · Score: 5, Insightful

    Windows security holes typically have exploits in the field, whereas linux vulnerabilities are commonly realeased from code review- hence having no preexisting exploits (that are known and demonstrated). Some are in fact purely theoretical, and may have to use to a malicious user.


    So even if you keep on top of your windows updates religiously, keep in mind that they are generally reactive. So there is always that window of vulnerability...

    1. Re:Worse still by Anonymous Coward · · Score: 0

      "So even if you keep on top of your windows updates religiously, keep in mind that they are generally reactive."

      You're wrong. Most of these Windows vulnerabilities had fixes before the exploits were written.

    2. Re:Worse still by Anonymous Coward · · Score: 0

      Most of these Windows vulnerabilities had fixes before the exploits were written.

      Including Code Red, and the majority (if not all) of the exploits used by Nimda. The problem is simply that there are too many people running Windows boxes that don't secure their systems or keep them up to date. Nimda was a prime example, since it exploited old IE and OE/Outlook holes to attack older versions of IIS, essentially using the most likely exploitable portion of the populace (average desktop users) to find and exploit the much smaller portion of the populace (stupid admins).

  135. Wininformat by Anonymous Coward · · Score: 0

    This is a troll right?

  136. number of testers and ther openness by rednuhter · · Score: 0

    Number of Linux/etc tests/developers = x^n (a lot)
    Number of MS testers = *CLASSIFIED* (but less than x^n by a laarrge magnitude).

    Likelyhood to spread diserturned information.
    Linux = 90% (or alot of them)
    MS *CLASSIFIED* (they never spread the information, until forced to)

    --
    ERR 411[Max number of witty sigs reached]
  137. Agregating bugs across distributions? by utahjazz · · Score: 1

    I'll keep this study in mind next time I think about running Linux Aggregate Server on my machine.

  138. Re:What?!? by Anonymous Coward · · Score: 0

    Morning sir....

    I'd like to report that although I still have 38 karma, my +1 bonus no longer works.

    I used to be able to post at "0" (-1 with a +1 bonus), but that no longer seems to be the case.

    What great things you have to look forward to once you choose to stop crapflooding! -1 posting forever?

    -- Anomymous Coward.

  139. Worst Distribution has Less than W2k by blazerw11 · · Score: 3, Interesting

    Linux (aggr.) has more, but each individual distribution does not. Simply put, if you add up every security issue with every OEM release of Windows (Compaq, Dell, HP, etc.), Windows would aggregate to a much, much higher number. The worst Linux distribution, RedHat, had 95 compared to W2k/NT's 97 (in 2000). And while Redhat was worse in 2001, the Windows numbers don't include XP. (Before you bitch at me about the "single" RedHat vs. the "aggregate" W2k/NT, RedHat had multiple versions out these years.

    What is the Linux (aggr.) anyway? The individual distribution numbers don't add up to that aggregate total. Does bugtraq not even know the Linux distros?

    --
    A great many people think they are thinking when they are merely rearranging their prejudices. -- William James
  140. Another slant by f00zbll · · Score: 1
    Here is another slant on the whole security issue the writer did not take into consideration.

    The mindset of the user.

    Considering windows has a larger install base and a large portion of those users are average people, security to large portion of window users constitutes less of an issue. It's not that windows users don't think security is not important, but rather they don't care to know the guts of an OS. Large portion of windows users don't understand the hacker culture or realize hackers do it for the fun. By virtue of the user-base, hackers will see windows has a more attractive playing field. Therefore any security hole in windows has a higher risk potential than the *nix counter part. People who use and administer *nix systems tend to have a better understanding of security and the hacker culture. I have no proof of this, but I would guess unix users have a higher percentage of security freaks, than windows. Unix users tend to be technologists, therefore vulnerabilities are caught sooner than later and patches are applied more frequently.

    The article should have taken these and other issues into consideration when calculating the relative risk of security holes. Lazy writers are a dime a dozen. Perhaps more people in the unix community should write articles and provide objective analysis of OS security issues.

  141. shameless karma whoring by gowen · · Score: 1
    vnunetVNUnet cover the same story:
    Although the statistics so far only go up to August 2001, aggregated distributions of the Linux operating system suffered 96 vulnerabilities while Windows NT/2000 suffered only 42.

    Breaking the figures down by distribution, Mandrake Linux 7.2 notched up 33 vulnerabilities, Red Hat 7.0 suffered 28, Mandrake 7.1 had 27 and Debian 2.2 had 26.


    So I suppose that now means that 42 33.
    --
    Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
  142. hmm... by Xaxeon · · Score: 1

    Linux is a relative term... There are many flavors of linux out there. Slackeware, which I use, happens to be much more secure (according to SecurityFocus, that is) than any Windows system. But it is all relative to the size of the holes and the serverity of them, as well as the speed at which they are patched. Also, the fact that the stats haven't been updated since August might have some baring on the totals(Re: the message at the top of the page). As far as OSes go, to each, his or her own.

  143. Both Windows and Linux have security problems. by Anonymous Coward · · Score: 0

    That is why *I* use FreeBSD.

    1. Re:Both Windows and Linux have security problems. by opn_human1 · · Score: 1

      well, that's why *I* use osX and BeOS!! (I'm really suprised this wasn't one of the adds plastered across apple's site durring their macworld campaign "More than the rumor sights could imagine, and more secure too!") these security ratings are so flawed in the first place I don't think I could ever take them seriously. When it finally comes down to it; it's up to you to make sure your box is safe

      -adios

  144. Some Specifics by Nos. · · Score: 2
    Okay, I decided to have a look at Red Hat's stuff for 7.2.

    Since its release, there have been 29 security fixes. So, lets have a look at them:

    • 1 fix for syncookie vulnerability (not enabled by default
    • 1 fix for apache-devel where you could trick apache into displaying a directory index
    • 1 fix for OpenSSH, must be enabled by admin to be vulnerable
    • 1 fix for xchat which would allow other IRC users to execute IRC commands as you - not exactly a root exploit
    • 1 fix for uucp - RedHat 7.2 is not vulnerable, down to 28
    • 1 fix for at - RedHat 7.2 is not vulnerable, down to 27
    Given that 2 have to be enabled to be vulnerable, we're down to 25.

    All in all, almost all vulnerabilities were from different packagea. Only 1 kernal problem. So, you would need to be running ~25 specific packages to be vulnerable. So, any reports using the 29 patches on RedHat's site (see above link) without actually reading the descriptions is going to be way off base. Now the same thing may be true for W2K machines, but I haven't looked to see.

    Most were not remotely exploitable, and some weren't even local-root exploitable. Some all you could do was view files!

    In any case, at the bottom of the SecurityFocus's page should be slashdot's poll disclaimer:

    If you're using these numbers to do anything important, you're insane

  145. Not again. by Znork · · Score: 2

    This is pure bullshit, and its even old bullshit. SecurityFocus have themselves claimed so. It's been around before.

    This always comes up due to several problems with the statistics:

    First, they're comparing Linux distributions with everything from several database servers through webservers, through rsh, ssh, telnet, ftp, compilers, etc to plain Windows. Include IIS, SQL server, shareware telnet servers windows, ftp servers, Outlook, etc and do it again. It is not quite the same thing, nor will your average linux machine have those services running anymore than your average Windows machine. Still, the vulnerabilities are counted if they ship with the CDs.

    Second, the 'aggregate' statistics are completely misleading. Those statistics add up every vulnerability in every program that any Linux distribution vendor has seen fit to put on a cd. That is even more farfetched.

    Sigh.

  146. Re:Look everybody! I can hate MicroSHIT too!!! by Anonymous Coward · · Score: 0

    Microshaft might have more money to throw at the problem, but OSS has more people to throw at it!!

  147. Re:What?!? by Anonymous Coward · · Score: 0

    And if you do crapflood, you post at -1 forever as well.

    Seems like I have nothing to lose, my friend.

    -TM5K

  148. Oh, come on! by Anonymous Coward · · Score: 0

    The same damn story was posted a year or two ago, with the same misuse of stats and the same knee-jerk reaction from posters here who didn't read the blinkin' story!

  149. Mark Twain once said... by Anonymous Coward · · Score: 0

    There are lies, damn lies, and statistics.

  150. not applicable by Pharmboy · · Score: 1
    Keep in mind that you can't compare "bug for bug" in Linux and Windows. Most people use them for different purposes, and linux users are much less likely to use "default" installs. Linux is used more often for servers than clients, for example.

    Another for instance: I have a couple boxes that are only used for web servers, with everything else cut off (no telnet, no ftpd, etc.) and one box that is dns only (no other services, except identd, etc.)

    You don't see as much of this in the windows world, where you pay for each license, and dedication is expensive. I use older machines (ppro 200, etc) for lesser, smaller tasks, and I know I am not the only one.

    So, while the fact may be true that there are more POTENTIAL security holes in Linux, it does not equal lower security. You can't just compare them like "apples to apples" this way.

    --
    Tequila: It's not just for breakfast anymore!
  151. Ill tell you why by Jeff+Knox · · Score: 2, Insightful

    Ill tell you what the flawed logic is. You can completely ignore that stats, and you can completely ignore direct comparisons. It all lays in the software. Most of the Linux vulnerabilities were for software that most people dont install, non standard stuf. Like, bitchx exploits or exim exploits. Not everyone installs that by default. So this aggregated Linux number is basically exploits from the tens of thousands of pieces of software available for unix systems. This is why its flawed logic. Most of the Windows vulnerabilities are default install problems. They are standard with the OS. Even under the break down by Mandrake, that includes all software you find on the Mandrake cd. Not only software that is by default installed (under all install options even). If you include ever peice of software that runs on the windows platform, that was exploitable last year, I think you would get a number that would blow it out of water. On a side note, thats not even taking into consideration source is available for most of this linux software, so it is easier to find more exploits. This is a good thing, not a bad thing. This just means they havent found all the exploits yet, because they use closed source. Security by obscurity does not mean its more secure :P

    --
    Jeff Knox
  152. Shouldn't this... by eth1 · · Score: 2, Funny

    have been filed under 'Humor'?

  153. Three types of lies in the world by Orsmo · · Score: 1

    There's an old saying that goes something like this:

    There are only three types of lies in the world: Lies, Damned Lies, and Statistics.

    It's important not to summarize the meaning of statistics too sharply, or they will tend to obscure the truth rather than highlight it. Here we have a comparison between NT and Linux based on a simple statistic of number of security vulnerabilities reported for each. Hmm... so what's been compared then?

    If I take an NT 4.0 CD and install it on a PC, then take a CD (or more likely a set of CDs) from a Linux distribution and install that on the same type of machine, how much software is on each? How many security holes are there? Even forgetting that there are dozens of choices as to which Linux distribution I install, you have the problem of determining in each case, where do OSes end and Applications and Services begin?

    NT, when installed has the kernel, some core services and some libraries, a few minimal applications and that's about it. If you want the thing to run various enterprise services, go install the whole Back Office suite. Want a database server? Go add MS SQL Server, or Oracle or whatnot. Need Desktop apps? Add Office in any of its varieties to get the combination of apps you want. What about graphics apps? Any number of other tools, utilities, services, development environments, drivers, libraries, etc... install them.

    Are we measuring security holes introduced by these additional software products installed?

    With a standard Linux distribution (take your pick which one) you'll get all of these things, in dizzying array, straight out of the box. Measure the security holes now.

    My point, of course, is that you're comparing apples to oranges if you don't split the apps from the OS. Or at a minimum make the same types of apps, services and libraries available on both machines regardless of what came on the CD from the OS vendor. If you do that, I'd doubt you'd come to the same conclusion.

    Of course, the site is slashdotted at the moment, so I can't read the actuall comparison, so if the methodology used took all this in to account, then by all means throw my comments out the window. Yet somehow I feel it a safe wager that this wasn't factored into the comparison.

    --
    -- Begin thoughtfuly, end insensitively.
    It has more impact that way.
  154. "with all the software included with Linux" by tophernet · · Score: 1

    An interesting Sub-topic would be in reply to the numerous posts about all the software that is included in a Linux Distro.

    I thought everyone complains that MSFT bundles too many apps with their OS and that's why they are a monopoly.

    People here seem to claim they don't bundle much of anything compared to Linux Distros. So do Slashdotters think MSFT is not a monopoly?

    1. Re:"with all the software included with Linux" by Jeff+Knox · · Score: 1

      No, because the software bundled with linux is freely available. The problem is Microsoft bundles their OWN software, which cost money, thus elminating competition, by making it easier for people just to use whats on the system. These linux distros are not bundling their own software that competes with commercial software, and making money off of it. Most distro companies dont make much of their distro anyway, because its freely downloadable. What you propose is a logical fallacy, because their is on correlation between the two.

      --
      Jeff Knox
  155. Security where it counts by The+Bungi · · Score: 1

    Windows 2000 is a completely secure OS. So is Linux. The problem is all the stuff that runs in them. I've never considered IIS to be a part of Windows, nor do I think Apache is a part of Linux. As long as people who are detached from the core OS security concerns (and indeed the whole QA thing that goes on at the kernel level) continue to write code that answers to marketing more than it does to basic development guidelines we'll continue to see these problems. That goes for all OS's - the problem is Windows is a lot more visible than Linux or Unix for that matter.

    It's not "my OS is more secure than yours"... it's "my web server sucks less". Tacking everything on to the OS is short sighted.

  156. So, do you think M$ would say this... by AB3A · · Score: 1

    ...if Linux weren't GPL'ed?

    I doubt M$ has the guts to use a half-baked statistical white-wash such as this against another party that could sue them --such as HP.

    --
    Nearly fifty percent of all graduates come from the bottom half of the class!
  157. Linux is not "more secure" unless you make it so by Hoonis · · Score: 1
    Being able to secure a machine that has a network connection is not trivial, regardless of the OS. If you are a first-time installer of either windows or a popular linux distribution, you are almost certainly putting up a remotely-rootable machine.

    Making a machine secure is a process of very careful testing, updating, and maintaining a machine. From a stock install of a distribution like RedHat, you have to first shut down services you don't want to run, verify that you have shut them down with a portscanner, install updated kernels, daemons, local tools & programs to avoid *local root* exploits, modify MANY default configuration files to make the system more secure, and subscribe to mailing lists at various security sites to test things out.

    Quite honestly, you probably need to get cracked a few times to really learn this lesson correctly. Setting up a publicly networked Linux server is not a job to be taken lightly, especially if you don't want to donate your system resources to crackers!

  158. Secure? Really? by Anonymous Coward · · Score: 0

    What the article doesn't tell you is that the installation of Windows 2000 that had only 42 security holes runs on a box not connected to the Internet.

    And secured in a Class III bank safe.

    And launched into Mars.

    It's still insecure, though.

    Goddamn Martian hackers.

  159. Aggregate totals by Bagheera · · Score: 2

    The "raw numbers" have always been a point of contention. What is the phrase? "There are lies, damn lies, and statistics." This is almost certainly a case of adding up the numbers and drawing conclusions from them without seeing what they represent.

    The raw number of reported vulnerabilities is not an accurate reflection of security of an OS. Add to that the fact that the many of the "Linux" vulnerabilities are in applications that are common across multiple distros and often (in the case of the numerous bind and sendmail vilnerabilities for example) common to many flavors of UNIX.

    I would be actually interested in seeing an Apples to Apples compareson done here. How many "remote root exploits" (Admin access for Windows boxen) have been reported, v "Local root" v "Elevated privilege."

    Also, should vendor software exploits that simply RUN under Windows be included in the numbers? In the case of "Linux vulnerabilities" that's often exactly what's happening.

    Raw numbers really don't mean jack.

    --
    Never attribute to malice what can as easily be the result of incompetence...
  160. A lot of people just want to take down M$.... by crashx99 · · Score: 1

    I'm sure that XP and NT and 2k are really secure, but everyone and their mom wants to find a bug in the software, trying to make it look bad. I'm sure if everyone worked toward making worms and virii for kmail, it would be considered the worst mail client....EVER. So just look at who the script kiddies are targeting.

    Crashx99

  161. Who installs Linux Aggregate??? by p7 · · Score: 1

    Where does this reporter get off comparing Windows to the Linux Aggregate? Looking at the stats he evidently used, you will have less vulnerabilities using all the Linux distros, except Redhat. The reporter makes it sound like if you install Linux you will have more than twice as many vulnerabilities, when in all actuality you will have many fewer, unless you use Redhat and then you only have twelve more.

  162. NT Bugtraq is not owned by SecurityFocus by UnderAttack · · Score: 1

    NT Bugtraq is not associated with Securityfocus.
    The 'regular' bugtraq list is a securityfocus site. But NTBugtraq is part of TruSecure if I remember right (and moderated by Russ Cooper).

    --
    ---- join dshield.org Distributed Intrusion Detec
  163. Mod this up by damas · · Score: 1

    Well, the guy has a point.
    The last bug I saw listed on the linux list on this site was: kicq DoS attack. LOL.

  164. Article Text by Anonymous Coward · · Score: 0

    From the newsletter on Friday.

    Thanks to David Byrne for this tip: For at least the first 8 months of 2001, open-source poster child Linux was far less secure than Windows, according to the reputable NTBugTraq, which is hosted by SecurityFocus, the leading provider of security information about the Internet. (The company's 2001 statistics are available only through August 2001 for the time being.) According to NTBugTraq, Windows 2000 Server had less than half as many security vulnerabilities as Linux during the reported period. When you break the numbers down by Linux distribution, Win2K had fewer vulnerabilities than RedHat Linux 7.0 or MandrakeSoft Mandrake Linux 7.2, and it tied with UNIX-leader Sun Microsystems Solaris 8.0 and 7.0. A look at the previous 5 years--for which the data is more complete--also shows that each year, Win2K and Windows NT had far fewer security vulnerabilities than Linux, despite the fact that Windows is deployed on a far wider basis than any version of Linux. So once again, folks, you have to ask yourselves: Is Windows really less secure than Linux? Or is this one of those incredible perception issues? For more information and the complete stats, visit the SecurityFocus Web site. I'll check back on this story to see how all of 2001 shapes up.
    http://securityfocus.com/vulns/stats.shtml

  165. NTBugTraq reputable? by jordan · · Score: 1
    Uhm, hold on a minute there, folks.


    Since when did NTBugTraq become reputable by anyone's hand OTHER than the moderator, Russ Cooper? Is anyone actually reading NTBugTraq? How does a history of a moderator editing other people's posts, a moderator who uses the list as his own personal battleground, how did NTBugTraq all of a sudden become so reputable?


    And Russ Cooper himself? Uhm, what background does he have that makes him reputable? TruSecure, a front organization created by him with little background? What research has Russ contributed to the security community? Where is his experience that proves he knows what he's talking about?


    No one can argue with numbers, and I'm not arguing that statistics can be manipulated out of context to prove just about any assertion, but reputable? Give me a break. Russ Cooper is a flaming idiot. Just read his posts about w00w00 to his own list recently, and ask yourself if he doesn't sound like a clown.


    --jordan

  166. Linux (aggr) vs Windows NT.. by josepha48 · · Score: 2
    THi sis interesting data. They aggregate all the linux distributions into one and do the same for BSD, but they do not aggregate all the windows version into one.

    Anyone who has used linux knows that all the different distros are slightly different and that this is not a fair comparison.

    In looking into the data further it would be more plausable to compare the aggregate of Linux vs the aggregate of BSD. Then you could say that the BSD's ahve less security flaws.

    If you compare lets say Redhat to WinNT4.0/2k then you have an almost even amount of bugs per year. Okay so neither has less security issues.

    The real questions then become 1) how serious the bugs? 2) how long a fix took? 3) Were people who installed the OS and then used NOTHING but what came with the OS to secure still affected?

    In the case of Redhat or BSD you can turn off all your services and thus you are not affected by bugs in the ftp daemon. You can do this on NT as well, but by default NT does not come with an ftp daemon. (NT server maybe?)

    In the case of BSD and Linux you can enable the firewall that comes with the distro/OS. Once again NT 4 (maybe 2k does?) does not have one by default install.

    Lastly how many windows machines were takes over last year by the security flaws vs Linux? Now rather than do this on a 1 to 1 comparison a more reasonalbe level of comparison would be a perscent, like % of linux boxes take over by a security flaw out of the total linux server numbers, vs the % of Windows boxes taken over due to security flaws. I.E. if you have 1000 windows boxes adn 100 linux boxes but 10 of the linux boxes were taken over and 50 of the windows boxes were taken over then you have 50/1000 or .05 and 10/100 or .1 which is 5% and 10% respectivly, thus windows would be better but these number I have made up so real numbers are needed. The same could be done with BSD as well as Sun and the other OSes they mention.

    --

    Only 'flamers' flame!

    1. Re:Linux (aggr) vs Windows NT.. by unconfused1 · · Score: 1

      I'm totally with you on this issue.

      The other question is what vulnerability are they talking about in a specific distro? Lets say their are 30 vulnerabilities with UnconfusedLinux (for example), but 12 are from the version of Squid I included, 10 from Tux, and 8 from mod_frontpage. And say that 95% of the users of my distro don't use those features because I do not put them on the default install?

      So, for this situation it counts up to 0 vulnerabilities. Are they counting those kinds of situations? No way.

      This is just like the chatter about Linux being so vulnerable because of the worms that attacked BIND. Wow...what a thought that most people wouldn't even be using BIND on their Linux workstations, or likely not even on many servers.

      Bottom line is that groups like Bugtraq need to be MUCH MUCH MUCH more specific with their statistics.

  167. Actually that was worse.. by schon · · Score: 1

    They made this same claim 1 or 2 years ago and did their math the exact same way

    That was the infamous Mr. Moody.

    I can't read the most recent article (/.ed), but from what I can gather, the old article was much worse..

    This one takes the aggregate, the Moody article took the aggregate and added it to the total of the individual linux numbers to arrive at his number..

    So this article is wrong because it says "if you add all of the holes of all of the Linux distributions, Linux is worse than NT"

    Moody's article is worse because it said "if you add all of the holes in all of the Linux distributions, THEN DOUBLE IT, Linux is worse than NT"

    1. Re:Actually that was worse.. by Drey · · Score: 1

      Ah, thanks, I forgot who did it and I forgot that he managed to find a way to count even worse. Fuzzy math ...

  168. His point is not moot. by tshak · · Score: 1

    Worms thrive on total volume, not specifically servers. The more systems infected, the more powerful it is. It is much more attractive to write a worm that can:

    a) Exist on a platform that has millions of machines running a relatively similar configuration.

    b) Get in as a trojan horse to an uneducated user (how many laymens install Linux?).

    --

    There is no longer anything that can be done with computers that is nontrivial and clearly legal. -- Paul Phillips
    1. Re:His point is not moot. by jamwt · · Score: 2, Insightful

      Worms thrive on total volume, not specifically servers.

      Umm... Can you think of really a more damaging worm lately than Code Red?

      Did it need clients/volume? Or just he 2X% of NT/2K servers out there unpatched?

    2. Re:His point is not moot. by Anonymous Coward · · Score: 0

      Almost all production NT web servers were patched within a day or so of CodeRed's release.

      Most of the Code Red infection damage was on Cable/DSL networks with their wannabe-l335 clients running a most likely warezed MS server product as their desktop OS.

      So, yes, popularity matters.

  169. So comparing win9x to win2k security is fair? by Otis_INF · · Score: 2

    Please, tell me: adding the numbers of vulnerabilities of win9x to win2k is fair to you? Or is it more fair to just compare the win2k vulnerabilities with the linux vulnerabilities? I don't know, but I know who will 'win' according to those numbers.

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:So comparing win9x to win2k security is fair? by Danse · · Score: 2

      What would be fair is to actually do a real study rather than simply add up the number of exploits, neglecting to note how many are remote, and how many are local, among other deficiencies. Then there is the issue of them not including the equivalent MS apps in the totals. The linux distros ship with databases, web servers, etc. Microsoft's equivalent applications were not included in the MS totals. The SecurityFocus article was just some mildly interesting numbers pulled from their database. The WinInformant article was just wildly unscientific, self-serving bullshit that used SecurityFocus as a reference to give it an air of respectability.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
    2. Re:So comparing win9x to win2k security is fair? by Anonymous Coward · · Score: 1, Funny

      Number of Windows 98 Vulnerabilities: One

      Vulnerability 1 -- The Product has no security features.

  170. The real number's are! by Anonymous Coward · · Score: 0

    Mandrake 8.1 => 109 Packages
    Mandrake 8.0 => 161 Packages

    These are the number of updates on the ftp sites, but all are not scurity updates, but some may include several security updates, so thses numbers may be quit close to the real security bugs found in Linux, so wath was the number for Windows?????

  171. Does Open Source favor evil deep magic hackers? by Jeppe+Salvesen · · Score: 3, Insightful

    Let's be fair. Some of the malicious hackers are extremely good. Does source code peer reviews improve security? If the guy reviewing the code is dumber than mr. evil hacker, then he might leave open an exploit for mr. evil hacker to enjoy and abuse.

    With closed source, mr. evil hacker will need to spend more time discovering the inner workings of the software than he will with open source.

    So - will he then produce more exploits running through open source software grepping for common starting points for exploits than he will when dissecting closed source programs?

    Remember - at any moments, the black hat community knows about exploits the rest of us don't know about. No computer has yet been classified as formally secure (to the best of my knowledge). We could all be at risk.

    --

    Stop the brainwash

    1. Re:Does Open Source favor evil deep magic hackers? by John+Harrison · · Score: 2
      Which target is more attractive?

      1. Linux systems. They are viewed as relatively secure so it is a "challenge" for the hacker. There aren't that many of them though.

      2. Windows systems. Might not be as much of a challenge but if you write a nasty virus/exploit you could make the headlines.

      I am sure that there are people attracted to both options.

    2. Re:Does Open Source favor evil deep magic hackers? by Stonehand · · Score: 1

      Whatever runs the big e-commerce sites, I'd think...

      --
      Only the dead have seen the end of war.
    3. Re:Does Open Source favor evil deep magic hackers? by John+Harrison · · Score: 1

      Well no we know what kind of evil hacker you'd be. :) I think that there are plenty of people who would like to see their Outlook virus show up on the national news. There are also plenty of people liek you.

    4. Re:Does Open Source favor evil deep magic hackers? by swillden · · Score: 2

      Remember - at any moments, the black hat community knows about exploits the rest of us don't know about.

      In the case of closed source software this is almost certainly true, because very few people are willing to invest the tremendous effort required to find holes in closed source programs. And even when they are discovered (this happens plenty!), the company that makes the software often shrugs it off or ignores it until an exploit is released.

      In the case of open source, while it is easier for black hats, it is also vastly easier for white hats. Even more importantly, when defects are found, they tend to get fixed very quickly (assuming users update, of course) and they're publicized far and wide which narrows the window of opportunity for a successful exploit.

      I don't know if it's even possible to prove it, but it's certainly arguable that the large, open community of white hats gain more from accessible source than the small, fragmented and uncommunicative black hat world.

      No computer has yet been classified as formally secure (to the best of my knowledge).

      Not true. Depending on your definition of "computer" and your definition of "formally secure", many have. Some special-purpose computing devices have been proven secure under a definition of "secure" that should make pretty much anyone happy. In addition, some devices have extensive physical security protections that have proven resistant to attack by really bright people with millions of dollars and sophisticated labs and machine shops.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  172. "AAAHHH!!! It's the SLASHDOTTERS!!!" by Dave_bsr · · Score: 1

    I think you are right - they run a linux-bashing peice, that is controversial enough to get put up on slashdot...and only after it is up do they realize what they have done. So as soon as their servers get some hints of slashdot, they just shut down and wait for the horde to give up. BTW, I read this article the other day, and came up with the same conclusions as the slashdot crowd seems to have. I'll see if i can't find it in my mozilla's cache at home and put up a mirror of some sort. but that will have to wait, i'm in school now.

    --


    Who is this Anonymous Coward character, how does he post so much, and why is he always such a whore?
  173. Exactly (it deserves to be rediculed and ignored) by FreeUser · · Score: 3, Insightful

    Exactly right.

    These numbers only reflect that GNU/Linux is more open and public in reporting its bugs than Windows, which is not surprising given Bill Gates & Co.'s efforts to suppress information about existing bugs in their operating system (the rightly rediculed notion of achieving security through obscurity).

    There is absolutely no correlation between number of bugs reported and number of bugs existing, be they security related or not. This is doubly true when one party (Microsoft) is actively working to suppress such information about their own products.

    The incompetence of the author writing this story, and of the Security Focus editorial staff for letting it through, is staggering. With this kind of security "expertise" is it any wonder at all that Nimda worms and the like run rampent across the net?

    Indeed, if one wants to draw correlations (always a risky endeavor without corraborating evidence) it would make far more sense to correlate the percentage (vs. installed base) of demonstrably compromized systems running one operating system vs. another. As Code Red, Nimda, etc. have demonstrated, Microsoft's products win this one hands down. Indeed, in this case there is massive corraborating evidence to back up the conclusions of such a correlation ... years of it, all in the public record.

    --
    The Future of Human Evolution: Autonomy
  174. Perhaps you could put that on the stats page? by mikemulvaney · · Score: 3, Insightful
    Secondly, I'm constantly amazed at how people mis-read our stats page. The Linux aggregate stats are the total of all unique bugs across all the various distributions we track

    I thought this was probably true, but I could not confirm it until I manually added up the bugs for a given year. Maybe you could explain the terms a little better on the page itselft?

    Regardless of anything else, using these number to declare that one thing is more secure than another is a mistake.

    That sounds like another piece of advice that should be on the stats page, not buried in a slashdot comment. Its unfortunate that someone misinterprets your statistics and publishes a misleading article every 6 months, but I can't help but wonder why you don't take proactive steps to help people understand the meaning of your web page.

    -Mike

    1. Re:Perhaps you could put that on the stats page? by DevNull+Ogre · · Score: 1

      Regardless of anything else, using these number to declare that one thing is more secure than another is a mistake.

      That sounds like another piece of advice that should be on the stats page, not buried in a slashdot comment. Its unfortunate that someone misinterprets your statistics and publishes a misleading article every 6 months, but I can't help but wonder why you don't take proactive steps to help people understand the meaning of your web page.

      He does put it on the stats page. From the page:

      The numbers presented below should not be considered a metric by which an accurate comparison of the vulnerability of one operating system versus another can be made.
      (Emphasis is in the original.)

      In all fairness, it might have been added in response to your comment. After a hasty glance through the page source, I didn't see any sort of timestamp. But I seem to remember that disclaimer always being on the page (though it had been a while since I last visited--back before the site migration).

    2. Re:Perhaps you could put that on the stats page? by ryanr · · Score: 3, Informative

      We used to have comments on the page that reflected those concernss. Unfortunately, it seems that they got replaced with the message that indicated the stats weren't being updated at present.

      Similar wording has been re-added, and the aggregate number has been pulled (to help keep people from jumping to conclusions.)

  175. Re:Statistics.... count the bugs in fixpacks too by Locutus · · Score: 3, Interesting

    I wonder if these stats would look the same if a count of the bugs in the fix packages were counted and not just the BugTrax ones..... hummmm.

    >
    > This is not an issue of who has more issues, but whose issues get reported and publicized more.
    >

    Well said. The best defense to this FUD I've seen so far. Be sure that there are 100's of Microsoft employees who's only job is to figure out holes in the Linux model such that it makes Windows look better. There was the re-surgence of communism and the GPL cracks the foundation of our economy to name 2 off the top of my head.

    The Microsoft model is to hide the bugs because it makes the product "look" more flawed. Having flown the BSOD flag over Redmond for the last few years shows they NEED to hide the bugs because perception is that the product IS FLAWED. Now the flag is SECURITY and they need to hide the bugs again.... Linux and opensource on the other hand, project reliability and security through openness. So like always, Microsoft uses manipulated statistics to ATTEMPT to show Windows is better. Remember in 1995 when NT sould 100% explosive growth of NT?....

    Your one-liner blows the thousands of dollars spent on that report right out of the water. IMHO.

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  176. Erroneous stats analysis by Anonymous Coward · · Score: 0

    There's not only the NUMBER of security holes that counts. The general stability, the intensity of the security problem caused by the hole (remember CodeRed?), the time of reaction to patch, the general knowledge of NT admins vs. unix/Linux, all of that makes NT a very poor candidate speaking of security history. I'm pretty sure SecurityFocus got a special subsidy since M$ announced new investments in security... for a company that never knew anything about security but snakeoil.

  177. Clearly. by Ironfist_ironmined · · Score: 1

    Clearly windows is better defended against linux specific virii.

    But really, for security, its CP/M! dear god is that brilliant.

    Microsoft are catching up with the world though, they are only 9 years behind apple now, and about 20 years behind UNIX systems. Fantastic.

    Flamebait is served best liquered up.

    The limits of my language are the limits of my world. -- Witgenstein.

    --
    0xC3
    1. Re:Clearly. by Vegeta99 · · Score: 1

      If I had mod points, I'd mod you down as a troll. 9 years behind Apple eh? Take away MS Office and Apple would be dead.

  178. While you're in the forest, watch for the trees. by Nurlman · · Score: 2, Insightful

    The argument that "Linux has a smaller installed base, so its security holes are less important" sounds like a paraphrasing of the old "security through obscurity" canard.

    After all, aren't you really saying that those security flaws are less critical because script kiddies and crackers are less likely to come across a Linux box than a Windows one?

  179. OpenBSd by Anonymous Coward · · Score: 0

    umm OpenBSD unhacked for last 5 years (http://openbsd.org) ... why was that not in the article?

  180. In other news... by Anonymous Coward · · Score: 0

    While the Super Bowl was playing, the Detroit Lions defeated the Carolina Panthers in an exhibition game.

    Linux security vs. Windows security. Sounds like a battle for last place.

  181. Yes True by mattdm · · Score: 2

    I can't connect to WinInformant, but if you look at the numbers available at SecurityFocus, you'll see that they did not simply add up the numbers. Linux is listet with 96 aggregated vulnerabilities for 2001, while e.g. Red Hat has 54, Debian got 28, and Mandrake got 36. There are more Linux distributions listed, but these numbers allone show that your claim is wrong (unless WinInformant has different numbers).

    I thought that too after looking at the SecurityFocus numbers, but then I figured it out. Scroll down the page a bit to the "Top Vulnerable Packages 2001 Packages", and there you'll see the numbers that the article references -- "MandrakeSoft Linux Mandrake 7.2: 33", "RedHat Linux 7.0: 28", etc.

  182. Re:What?!? by Anonymous Coward · · Score: 0

    Me too!

  183. Interesting read... by Anonymous Coward · · Score: 0

    ...but, I'm bored out of my skull sitting here at work. It is interesting to see how few vunerabilities exist for the Mac OS. I recently switched from the x86 platform to Apple after exclusively using x86 based machines for the last 12 years.

    So far, I'm impressed. And very broke. :)

  184. Re:Exactly (it deserves to be rediculed and ignore by ryanr · · Score: 5, Informative

    The incompetence of the author writing this story, and of the Security Focus editorial staff for letting it through, is staggering. With this kind of security "expertise" is it any wonder at all that Nimda worms and the like run rampent across the net?

    We didn't write the article in question, nor are we hosting, nor did we have any opportunity to see it ahead of time. (Or now... still can't see it.) Sadly, we have very little editorial control over other people's websites.

  185. This ignores so much... by uucpbrain · · Score: 4, Interesting

    The problem here is just that there is no "aggregate Microsoft" category. Heck, there's not even a W95/98/ME category! But if you lumped together all W95/98/ME/2K/NT/XP vulnerabilities, then made sure that you dealt with apps evenhandedly, "aggregate Linux" would start looking great all of a sudden.

    Now consider exploitability. Let's take Mandrake for example -- although their figures are already way lower than NT's (or, no doubt, 95/98/ME's), a default install includes 'libsafe', which means that none of the buffer overflows or format bug exploits will work. There go 3/4 of the theoretical vulnerabilities, including the ones which haven't been discovered yet. And a libsafe rpm could be installed on almost any Linux system in a matter of seconds without breaking anything, making the whole raw tally concept very questionable.

    The only way to secure an MS system that broadly and quickly is to cut the Ethernet cable.

    I leave my Linux box on the Internet without worry, and my investment in security has been maybe an hour and $0.00. I can and do take my time on patches because I know that almost none of the bugs have any chance of being exploited on my system. That is a realistic measure of Linux security, and I will delightedly compare it to Windows any day of the week. Securityfocus' figures, taken by themselves, don't mean anything.

  186. The Virus Bowl by Myuu · · Score: 2, Funny

    And the game is 2 to 1

    OS:Linux
    --------------
    Virus:Sendmail, Wu-ftpd

    OS:Windows
    --------------
    Virus:Windows

    They neglect the 600 OE viruses each year...

    --

    forget it.
  187. More interesting statistics... by sheldon · · Score: 4, Informative

    Screw securityfocus, let's look at bulletins released by manufacturers.

    Microsoft security bulletins released in 2002:
    MS02-001

    Redhat security bulletins released in 2002:
    2002-018
    2002-015
    2002-014
    2002-012
    2002-011
    2002-009
    2002-007
    2002-004
    2002-005
    2002-003
    2002-002
    2001-171
    2001-168
    2001-165

    And if you look at 2001 results you'll see a somewhat similar trend, although not near as pronounced. Somethink like 80 versus 60.

    Are these statistics meaningful? Of course not. If you have read Paul's columns you would know he reported this tongue and cheek. It was a slow news day, he noticed this, had to make fun of it.

    What makes this story interesting, and why Paul reported it is because if the numbers had been reversed you would be assured that would be the headline of the day on slashdot, and if anybody questioned it they would be called Microsoftie apologists.

    And look at the responses you see here. They're almost comical. Reminds me of the responses to the Mindcraft benchmark. Fear, Uncertainty and Denial. :)

    1. Re:More interesting statistics... by RedWolves2 · · Score: 1

      I wish I had moderator access right now I would love to mod this up. And this is only one distro. Why aren't these stories on slashdot?

    2. Re:More interesting statistics... by RedWizzard · · Score: 2
      What makes this story interesting, and why Paul reported it is because if the numbers had been reversed you would be assured that would be the headline of the day on slashdot, and if anybody questioned it they would be called Microsoftie apologists.
      Funny, I don't remember seeing ANY stories on Slashdot reporting Windows to be less secure than Linux. I've seen at least a few like this one reporting Windows as more secure than Linux. There are fairly frequent stories on the more serious vulnerabilities/bugs/viruses/worms that show up for Windows but that's to be expected: most story submittors and most readers use Windows.

      I don't know, I guess some of you people still believe Slashdot should be some sort of paragon of fairness. When are you going to realise that it's just a bunch of guys posting what they think is interesting? Fairness and accuracy have never come into it.

      And look at the responses you see here. They're almost comical.
      Pretty low calibre, I agree. 90% are redundant for a start.
    3. Re:More interesting statistics... by irix · · Score: 2
      Are these statistics meaningful? Of course not. If you have read Paul's columns you would know he reported this tongue and cheek.

      I just read it, and it does not sound very tongue-in-cheek to me at all.

      And look at the responses you see here. They're almost comical.

      Well sure, some of them are comical. What else is new when you have 800 people posting to a forum. Do you think if WinInformant had a feedback section that we wouldn't see hundreds of Windows fanboys flaming Linux?

      Most of the highly-rated posts in here aren't comical. They are pointing out that this guy comes off like an ass comparing apples to oranges. And they would be right.

      --

      Do you even know anything about perl? -- AC Replying to Tom Christiansen post.
    4. Re:More interesting statistics... by fferreres · · Score: 0

      Screw securityfocus, let's look at raw numbers from our microtrend viruswall linux edition:

      Windows virus detected: 76452
      Windows virus variants detected: 493
      Other OS virus detected: 0
      Other OS virus variantes detected: 0

      That means that if i didn't have :
      1) the antivirus software
      2) NAT firewalling
      then we'd be completely screwed.

      What good is testing a server OS without server applications while every sysadmin is trying the hell to stay clean from Windows worms and virus?

      --
      unfinished: (adj.)
  188. "LINUX" vs. Windows? by bo0push3r · · Score: 1

    gah.. i mean, from a server standpoint i'd much rather run linux for reliability reasons, but this data is all garbage.

    this must be with a standard install. they're basing the linux numbers on distrobutions when what they should be doing is reviewing IIS vs. various packages and so forth. it is possible to install and properly configure redhat with no known remote exploits.. just as it is possible to more or less secure a windows box.

    the #1 security vunerability that exists for absolutely EVERY platform is a lazy sysadm.

    however, for my love of video games, nothing replaces windows on the desktop for me. :)

  189. Not only that, but... by MattW · · Score: 5, Insightful

    It gets worse than that. Let's consider:

    Most bugs that show up for redhat or any other linux distribution will NOT affect a well-secured machine in the first place. If you plan, for example, a standard web or database server, you're only going to permit ssh and apache or ssh and your brand of sql. How many vulnerabilities in the past year have been on those services? Practically none. Only 1 in ssh, and there was AMPLE warning to get patched before exploits were in the wild. The majority of bugs are for packages not often deployed, or not relevent to a server system where there is no user access.

    Meanwhile, an enormous number of these linux bugs are irrelevent on a firewalled system, never mind the incompetency of sysadmins. A firewall will protect your X font server or your installed-by-default nfsd/statd, but Microsoft has had many high-profile, extremely-widely-abused holes in a server's primary services (IIS, MS-SQL, etc).

    Anyhow, trying to say these statistics show that NT is more secure than Linux is not only irresponsible but absurd.

    1. Re:Not only that, but... by Anonymous Coward · · Score: 0

      Why would a firewall protect your X font server and not your MS-SQL installation? It seems like you are the one who's spinning this now.

      I support your gist however - a bug tally limited to those affecting public WWW/FTP servers is probably much more interesting than every MS-RPC or RedHat LPD exploit. The fact is that both OSes (Unix and Windows) have a bunch of "trusted LAN" services that will probably never be really secure and will always be firewalled.

    2. Re:Not only that, but... by bogado · · Score: 2

      The reason is simply that if you firewall the SQL server on a machine dedicated to serve SQL it will render the machine useless. The orinal post states that MS has inumerous vulnabiralities in "primary" server (http, sql and others). If you have a vulnerability in a server that is not started it does not affect your system, and redhat (I don't know about others) has been folloing the police of defaulting services to off state since vs. 7.0.

      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

    3. Re:Not only that, but... by Anonymous Coward · · Score: 0

      And if you firewall the X font server, it will render it useless as a font server. Your point is exactly what?

      My point is simply that nobody in their sane mind in either the Unix or Windows worlds runs those sorts of services over the public Internet.

    4. Re:Not only that, but... by unclefucknut · · Score: 1

      Lets not forget that most of the security holes found in Windows are in conjunction with other Microsoft products such as Office and the Explorer (I still consider IE to be a product and not a part of the OS, despite what Microsoft says...)

      All in all, I think the dudes over at the kernel department is pretty aware of the security threats. Just look at the security model which NT/Win2k employs. It's far more advanced than the traditional UNIX security model, and still not too complex to understand. I think the problem lies in all of the other "loser" departments within Microsoft (which are mostly VB hackers which has no clue about security). They just don't care about security. Perhaps Bill has whipped them enough now to make a change.

      [Offtopic]
      I'd take a win2k kernel w/o all the messy gore surrounding it any day for serious work if it was possible. Why? The hardware support is much better for Windows than any other UNIX derivatives (and I don't have the knowledge nor time to produce a driver either), and the core OS isn't that bad.

      And when customers have specific demands, you have to comply. You can't just stuff a UNIX os down their throat against their will.. (that is probably one of the fastest ways to lose your customer). But if the customer is willing and there is hardware support for what the customer wants built, I'd rather go for FreeBSD (or OpenBSD depending on situation) any day. (I don't trust many of the flaky Linux driver hackers out there.. and I don't know how and don't have time to do something about it. Tough shit I guess, but I'm lucky to have alternatives)

    5. Re:Not only that, but... by Cyno · · Score: 1


      Redhat's also made a lot of other improvements? to 7.0 that we just won't mention here. ;) But firewalling is good idea when you have a desktop system that only serves one port to the network and wants to maintain security or if you want to prevent anyone from connecting to non-service ports such as in a DMZ environment. If you want to secure a web server, mail server, sql server, etc. You can use both a DMZ/firewall network architecture as well as a chroot environment to trap any hackers inside a quaranteened area to keep them from accessing the systems' main configuration files. So, in other words, if your database gets hacked, all that gets hacked is your database, not the server it relies on, etc. And the hacker most likely would not have the tools they need to move your data, so you would be relatively secure.

      Between chroot and some virtual machine software you can secure a unix system pretty well. I'd like to see examples of how windows or any alternative OS can be configured as securely.

    6. Re:Not only that, but... by bogado · · Score: 3, Insightful

      Since linux usualy comes with many more packages then windows all those packages are accounted for security bugs, but they are not used by many people. And since redhat has a policy of not starting servers by default, even if you actualy installed a package that has a bug, it will not affect you unless you have started it your self (witch mean that you at least have an idea of what you're doing).

      Window in the other hand comes with very few servers bundled and they are all on by default (as far as I know, I not a win expert). And even worst the security bugs are usualy in packages that are vital to the work the machine supose to be doing. I can make, and I bet many people do, a server machine without a font server, but I can't take out (or firewall) the server it self from the machine.

      --
      []'s Victor Bogado da Silva Lins

      ^[:wq

    7. Re:Not only that, but... by ljaguar · · Score: 1

      Sorry, i've a question, not a troll or anything, just curious.

      What exactly would win2k kernel security model would that be? I'm just not aware that nt kernels had that unix-secure-and-extendible philsophy.

    8. Re:Not only that, but... by sparkz · · Score: 1
      And when customers have specific demands, you have to comply. You can't just stuff a UNIX os down their throat against their will.. (that is probably one of the fastest ways to lose your customer).

      Whereas letting them stay with an insecure OS is a slow, painful death... advise them about what they need, don't just give them what they think they want - or what are they paying you for?! And whatever you end up giving them, secure it! Behind a firewall, but also on-box (and don't forget that far more cracks are done internally than from external sources).

      --
      Author, Shell Scripting : Expert Re
    9. Re:Not only that, but... by RallyDriver · · Score: 2

      NT's kernel does indeed have a rich security model - it was done by the guys who did VMS, and it plagiarises VMS extensively. It is neither more nor less flexible or powerful than simple Unix models (Linux setgid) nor the more complex ones (Unicos MLS, Trusted Solaris).

      All the security models in the world are however worthless if every damn thing installs and runs with full root (Administrator) privilege, as everything on NT does, IIS included. I will cheerfully bet that less than 0.1% of NT based web servers have *any* daemons (services) which *don't* run with full Administrator.

      Even *MS-Office* requires root privilege to install, no single-user option; it's not kernel modules, it's a damn word processor!

      Have you ever tried running user NT desktops without giving them Administrator? I have, and it's a support nightmare. They can't install so much as a screensaver, which may be fine for controlled environments like a telesales CTI terminal bank "Would you like the porn channel?", but it doesn't work in an office environment; the masses rebel.

      Your wonderful NT kernel security model is a waste of bits.

      Likewise, your $100k Checkpoint firewall isn't going to do anything about Code Red, port 80 is supposed to be open to the world. You need secure web server software. Period. IIS is not that. If anyone ought to be a MSFT shill it's analysts like Gartner who they commission in droves to write unbiased "studies", and Gartner has broken ranks to say IIS sucks for security, lose it and use Apache.

      The fact is, as they come out of the box, Unix-like systems are in general more secure than NT, and require more skills to administer. Red Hat is probably the least secure of the Unices (you can't say Linux - this is a distro thing, not the kernel), but it isn't intended as a real server OS any more than NT, and to give them credit it is more secure than a default load of Win2K server.

      The fact also is that most people running servers out there on the web, NT, Unix or otherwise, do not have the security skillset to do it properly.

      NT = more holes out of the box = more worms.

    10. Re:Not only that, but... by lsdino · · Score: 1

      Sorry, i've a question, not a troll or anything, just curious.

      What exactly would win2k kernel security model would that be? I'm just not aware that nt kernels had that unix-secure-and-extendible philsophy.



      Here's a link on MSDN which explains NT security.

      But basically you have ACLs - Access Control Lists, associated with objects (files, registry keys, pipes, processes, etc...). An ACL describes who can do what with the object - eg, create, open, read, write, full control, etc... You can set them in 1 of 3 states: Allow, not set, or Deny. Denying overrules allowing too...

      It's all pretty extensive. "The Mythical Man Month" describes NT as suffering from 2nd-system syndrome, where a project gets over designed. Along these lines NT has a very extensive process / thread model.

      Of course, I'm no NT security expert, so read the article, 'cuz I might not have gotten all the details right.

    11. Re:Not only that, but... by posmon · · Score: 1
      damn thing installs and runs with full root (Administrator) privilege, as everything on NT does, IIS included

      no it fucking doesn't. it runs under its own account.

      --

      update comments set karma=-1, reason='offtopic' where sid=26315

    12. Re:Not only that, but... by unclefucknut · · Score: 1
      Have you ever tried running user NT desktops without giving them Administrator? I have, and it's a support nightmare. They can't install so much as a screensaver, which may be fine for controlled environments like a telesales CTI terminal bank "Would you like the porn channel?", but it doesn't work in an office environment; the masses rebel.

      Your wonderful NT kernel security model is a waste of bits. You don't need admin rights damnit! NT supports capabilities, much like Linux. In NT your process is given some default priveliges, everything else must be asked for. If your user profile allows the specific privelige you ask for, you get it. And this is a very good thing since you can then get the privelige when you need it, and release it when you don't. Thus you are eliminating many big risks associated with buffer underruns.

      Unfortunately, many windows programmers are VB weenies or totally ignorant, so they choose to:

      • Require administrator rights for their application (i.e. programmer too stupid to read anything but the VB reference manual...)
      • After (luckily) have found the man pages for acquiring privelige tokens, they keep it open during the whole lifetime of the application (thus leaving it wide open for potential attacks)

      The thing is, it's not hard to do this! It's childs play. There are API functions which you can call to acquire a privelige token and release them. And the ACL model is probably one of the simplest access control models out there. Someone who cannot grasp that, should not be producing public software IMHO.

      Sadly, many of the redmond programmers are totally ignorant when it comes to security. My bet is that it's because most of their programmers are freshmen "hackers" whose only non-fake experience entry in their CV is Visual Basic.

      Last time I checked, Linux implemented a capability model as well. I have not yet fully familiarised myself with it, but I can't remember that the programmer has to specifically ask for a privelige.

  190. that means nothing by jbrelie · · Score: 1

    What they SHOULD do is look at the percentage that were FIXED. Linux development rolls out more stuff each year, so naturally, there are more security notices. But they get fixed. Micro$oft drops a golden turd every few years, calls it an operating system, and pays people to keep quiet about the exploits.

  191. Bad comparsion by Anonymous Coward · · Score: 0

    Invalid statement, Linux is just a kernel. Now if they compared Windows to a distribution then that would be valid. Compare it to say Redhat for a decent comparision, not every damn distribution verus just one windows release(distribution).

  192. Well ok... by Bob+Smith+157 · · Score: 2, Redundant



    Sigh...

    I can't read the original article, It's been Slashdotted to death. But I think I can make a pretty good guess as to what happened.

    First off, we host Bugtraq, not NTBugtraq, which is Russ Cooper's list. (Any chance we can get that fixed in the story intro? Anyone know if the same mistake is in the original article?)

    Secondly, I'm constantly amazed at how people mis-read our stats page. The Linux aggregate stats are the total of all unique bugs across all the various distributions we track. It's supposed to answer the question "How many Linux-related bugs were there that year." It's based on things like which distro ships a particular package, and when that package is found to have a hole, it also gets attached to the distro. This is so you can look up your distro, and see what bugs you might need to patch.

    Take a look at the top of the page, our script hasn't been running since August, when we switched from Roxen to Apache. So, we're missing the whole last quarter of 2001 stats.

    Regardless of anything else, using these number to declare that one thing is more secure than another is a mistake. Based on our numbers, why didn't they declare that everyone should run MacOS for security? Or that if you want to be more secure, run Debian instead of Win2K?

    --


    "It's funny. On the outside, I was an honest man. Straight as an arrow. I had to come to prison to be a crook."
    1. Re:Well ok... by Anonymous Coward · · Score: 0

      Not informative.

      This is a copy of this, real, comment

  193. damn... by marco_craveiro · · Score: 1

    man, this all story is kinda sad. first, the sillyness of using this figures without actually doing any analysis on them first. irresponsible, to say the least. second, we have this pissing contests so regularly that i'm beginning to suspect there is a formula capable to predict when the next one is going to be.

    what i really want to see is something very simple. a little application, distro-specific, that downloads data from a central, trust-worthy website and then does a check on each of the applications on a computer and certifies it. if the computer does not pass the check, management gets a mail. if you have a non-certified computer, your sysadmin is liable for any damanges.

    thats what i would do if i was a security dude.

    soup

  194. Here's my analysis: by cavemanf16 · · Score: 1
    Virus' or other malicious programs on my brother's web/CounterStrike/email/FTP/SSH/file server running Linux in the last 2 years?
    none

    Virus' or other malicious programs on my other brother's WinME machine in the last year? 1, and it took a week for my brother running the Linux server (who is more knowledgeable than my other brother and myself when it comes to computers) a week to find and isolate the virus to keep it from running itself. Even then, there's nothing that can wipe it out so far except a total HDD reformat. Norton can find it, but won't clean it.

    Now you tell me which system is more secure? A buggy system with all kinds of networking insecure options inherently on and a brother too busy to go to WindowsUpdate.com every 2 weeks for the latest security fixes, or a Linux system with very few networking options turned on by default and a brother who knows what he's doing when he turns on a service that could potentially allow virus' in?

    It's great that Windows is pretty simple to use, but for goodness sake, why turn on things a typical user won't ever need to use when you could prevent more bugs this way. And another thing. I'm tired of proprietary webpage coding. Those damn 'best viewed in IE4.0+' pages are usually so damn annoyingly not rendered well except in IE that I just won't buy stuff from websites where I have to use IE to use the website. If you ask me, that alone is a malicious virus built into IE that threatens future use of the web for the less fortunate who don't want to pay $399 for "WinowsUltra64! Home Upgrade Edition"

    1. Re:Here's my analysis: by Anonymous Coward · · Score: 0

      Cool! Are your brothers as fucking geeky as you are? NERD!!! Go out and have a beer

  195. And your argument is?.... by coyote-san · · Score: 2

    I'm sorry, I just don't understand your argument.

    Are you still defending them counting a single bug in the source code up to four times if all distros fixed it? And that it's legitimate to count the same bug fewer times if some distros never issued an advisory for it? (Shades of the usual closed source "it's not a bug until we admit its a bug!" attitude!)

    Or are you using the author's inability to add a few two-digit numbers as some perverse proof that we should trust those numbers? Unless we have a list of the vulnerabilities behind those numbers, that explanation makes as much sense as anything else I've heard.

    Ultimately, it's all irrelevant anyway since Microsoft itself has come out strongly against public discussion of vulnerabilities. Some vulnerabilities are undeniable because of exploits, but there's a huge grey area where it's not clear if its a bug or a vulnerability - and many people defer to the authors on these reports. This policy wasn't as explicitly stated at the time in question, but it's obviously been their policy for some time.

    --
    For every complex problem there is an answer that is clear, simple, and wrong. -- H L Mencken
    1. Re:And your argument is?.... by jareds · · Score: 2

      Note: I just checked and noticed that Security Focus changed the page. Basically, they used to have a row in the table for "Linux (aggregate)". With the exception of 1998, if you added the numbers of bugs for each distribution, you got a number greater than in the aggregate row. This would seem to indicate that were removing duplicates.

      However, I'm repeating myself, so I'll try a concrete example with small numbers. Suppose they listed RedHat as having 10 bugs and Debian as having 5 bugs, and those were the only distributions that they listed. If they then listed Linux (aggregate) as having 15 bugs, then it would be clear that they were double counting. On the other hand, if they listed Linux (aggregate) as having 12 bugs, then they clearly might have been removing duplicates from the total, so there is no evidence from their statistics alone that they are counting duplicates. The latter situation is analogous to what was on their site.

      I was never intending to argue that the numbers were useful. For example, they probably were counting bugs in any package in a distribution as a Linux bug, whereas they probably would not have counted a bug in IIS or SQL Server as a Windows OS bug. However, I was getting annoyed at everyone claiming that they were double counting when there wasn't any evidence given to back up that claim.

      Now, this is all moot, because they've removed the Linux (aggregate) statistic, so there's no way for them to be double counting.

  196. I don't know about this by verrol · · Score: 1

    but wasn't there some issue before about Microsoft hindering how and which bugs are reported to the bugtrack web site? if so, then there u go. Another thing is the Linux source being open. So bugs may be easier to find. but with windows, most users won't know if they are seeing a bug or not much less where to report it.

  197. You got trolled by Error27 · · Score: 2
    The wininformant article is just meant to tick you off.

    The title of this story is "SecurityFocus says windows is more secure than Linux" but that is a clear lie. SecurityFocus said nothing of the sort.

    Look at the chart on security focus and count the local root exploits... Oh wait! Windows 98 doesn't have any protection to begin with so how can the protection fail?

    It's embarassing when Linux weenies can't see that they are being trolled.

  198. Bias works both ways(Re:bias) by TechnoLust · · Score: 3, Insightful

    Securityfocus is the definitive sight for security news. To say the numbers are "purely for entertainment" is the most ridiculous thing I've ever heard. You only proved your ignorance later in the post when you said, "the WinInformant site is Slashdotted (they must be running Windows, haha)" when OBVIOUSLY this would have more to do with their BANDWIDTH than their OS. I know I'll get modded down for posting this, but I don't care. I hate to see people discount anything that doesn't agree with their opinions. Oh, and I run Windows NT at work, Windows2000 and Mardarke 8 at home. I love Linux, but I love MS more for some things (games, word processing, etc.)

    --
    "Da ist ein Technölüst in mein Unterpanten!"
    1. Re:Bias works both ways(Re:bias) by Anonymous Coward · · Score: 0

      Nobody cares what you think. You USE CAPITOL LETTERS way to much to EMPHESISE things (also based on your ~user webpage).

    2. Re:Bias works both ways(Re:bias) by ichimunki · · Score: 1

      Thank you for flaming. Or is it trolling? Who can tell... you kids mix this stuff up so much these days. I assume you'll sort that out right after you learn that it's spelled "site" and that capital letters don't help make your point.

      SF's numbers are not there to do anything but provide some rough counts, i.e. amusement. As I pointed out at length, they contain no real information and therefore provide no real help in making security decisions. Security Focus will tell you the same thing--in fact someone from SF did so in this very discussion. Or don't you trust them on that?

      Second, the word "haha" means that I'm making a joke. A joke means I'm not being serious. But what would you know? You run Windows at home. Your opinion is obviously suspect. It's also apparent why you're so easily upset. Hehe.

      --
      I do not have a signature
  199. Glass half full... by gnovos · · Score: 5, Interesting

    They are looking at this from the wrong perspective. Instead of saying "Linux had more bugs than Windows in 2001" it should say "Linux *fixed* more bugs than Windows in 2001". Simply becuase those Windows bugs haven't been found yet does *NOT* mean tha they are not there waiting to be exploited (or are already being exploited).

    --
    "Your superior intellect is no match for our puny weapons!"
    1. Re:Glass half full... by prankster · · Score: 1

      Instead of saying "Linux had more bugs than Windows in 2001" it should say "Linux *fixed* more bugs than Windows in 2001". Simply becuase those Windows bugs haven't been found yet does *NOT* mean tha they are not there waiting to be exploited (or are already being exploited).

      So what you are saying is that closed source software is more secure because it is closed and the bugs can't easily be found?

      Your argument seems to suggest that opening the source compromizes your security. Which by the way is what Microsoft have been saying all the time.

    2. Re:Glass half full... by Tony-A · · Score: 2

      closed source software is more secure because it is closed and the bugs can't easily be found?
      Closed source is more secure until somebody wants in. Producing an exploit requires a reasonable competence with machine language. Source is almost a liability. Fixing the vulnerability requires the source.
      Opening the source compromizes your security about like lighting your perimiter helps burglers see what they are doing. You lose a little short term, and that's mostly a false sense of security, but gain enormously in the long term. If security is to become a high priority, the drill is to first publish the exploit. Then later publish the fix. Other than that, you've just got a bunch of people fooling themselves.

  200. Wininformant can't even keep their site up by restive · · Score: 1

    Considering they're running IIS (netcraft lookup), it isn't surprised that the site got /.ed so easily...fine secure OS they're running though apparently.
    THAT must explain why the web services are slower...all that "security" checking!

    We don't need to get all up in arms over this article. People who believe this at face value obviously smoke crack.

  201. One can only hope by Anonymous Coward · · Score: 0
    That such a shit & shill site pays for bandwidth by the bit. The slashdotting will cost them mega-bucks!

    I mean does anyone really thing that comparing the sum of all bugs across all Linux distros against the number of bugs M$ acknowledges for WinXX means diddly squat?

  202. Own up to it. by tqbf · · Score: 3, Informative
    Secondly, I'm constantly amazed at how people mis-read our stats page. The Linux aggregate stats are the total of all unique bugs across all the various distributions we track. It's supposed to answer the question "How many Linux-related bugs were there that year." It's based on things like which distro ships a particular package, and when that package is found to have a hole, it also gets attached to the distro. This is so you can look up your distro, and see what bugs you might need to patch.

    Easy.

    Because you didn't say so.

    We know who SecurityFocus is. It's Alfred Huger and Oliver Friedrichs and Art Wong, the Secure Networks, Inc. crew.

    Secure Networks dealt with exactly the same problem we're talking about now: the trade press doesn't know a damn thing about technology and software engineering. Everything in the trade press is based off of newswire press releases and superficial articles. Alf and Art and Oli had to deal with this problem constantly as their competitors made bogus claims about SNI and their products.

    Towards the end of their work on the Ballista product, Alf had gotten pretty good about educating the trade press about the issues, or at least at swaying them towards his way of thinking.

    Alf and Oli and Elias are scrupulous guys, and they know how the world works. It is simply an embarassing oversight that there aren't loud disclaimers on the vulnerability report at your site explaining how to interpret the results. You all know how the page is going to be interpreted. You just saw Slashdot interpret it the wrong way. Slashdot is dumb, but InfoWorld is a million times dumber.

    You could fix this problem right away, and pre-empt unethical use of your data, by releasing a statement explaining that the numbers on the page aren't a legitimate security metric. It won't cost you anything and it will help (us, and you!),

    Or you could act like Russ Cooper and try to use the polarizing effect of the unexplained numbers to generate controversy, page hits, and press.

    It's all a question of how much your credibility means to you.

  203. Apples and organges by nowt · · Score: 2
    Or windows and penguins..whatever.


    Comparing the two on security issues is tough. With windows-based systems, your 'configurable' options are limited (unless prepared to scour ms knowledge base for occasional registry fixes + patches - of course the patches typically lock you in to a certain behaviour.. not always desired).


    With linux, you can make a system as secure or insecure as you wish - with the 'HOWTO's' coming from a wide variety of sources. So..


    Limited security configurability and limited knowledge base or massively configurable system in terms of security with large knowledge base? I'll stick to linux (or *bsd ;)

    --
    A strange game. The only winning move is not to play. How about a nice game of chess? - Joshua (Wargames)
  204. IE's not a threat until you use it. by NanoGator · · Score: 2

    Until you start using IE, it doesn't create a vulnerability. You could immediately go get Netscape or Opera and boom, no more need for IE. Even if it is part of the OS, until you go to the internet with it, it's not much of a vulnerability.

    Should it be better out of the box? Certainly!! But I consider that a bug of IE rather than a bug in the OS, even if the OS is dependent on it.

    --
    "Derp de derp."
    1. Re:IE's not a threat until you use it. by Danse · · Score: 2

      Until you start using IE, it doesn't create a vulnerability.


      It's not just IE the browser, but any app that uses the IE DLLs to provide functionality that is at risk.


      But I consider that a bug of IE rather than a bug in the OS, even if the OS is dependent on it.


      That's just semantics. Any way you cut it, you have an unsecure app (and potentially many) on your machine, and you can't get rid of it. Not to mention that certain MS applications will invoke IE even if you've set up another browser as your default.

      --
      It's not enough to bash in heads, you've got to bash in minds. - Captain Hammer
  205. I refuse to believe. by Anonymous Coward · · Score: 0

    Possly an accurate argument, if the Linux in question is anything but Slackware.

    Anonymous Coward

  206. Re:Statistics.... count the bugs in fixpacks too by Anonymous Coward · · Score: 0

    Hey Locutus - I've never seen you trolling this hard before. Have you become an Adequacy editor or something? Add some funny links and your post would fit right in on their front page.

    Either that or your tinfoil hat is out of adjustment.

  207. Re:Simply put youre an idiot by Anonymous Coward · · Score: 0

    You're talking as if crackers are the only ones checking out source code.

    I'm pretty sure there are more white hats than black hats.

    proactive?? reactive?? I'll take proactive, thanks.

  208. Wrong, DUH! by Penguinoflight · · Score: 0

    A idiot with a 2k box is obvioulsy less secure than an idiot with a linux box. Besides, there's less idiots on linux than windows. It seems to me that skilled sysadmins would be better off with a system that gets patched as soon as the vulnerability is found, instead of 2 weeks-2 months later. Plus you could make your own patch on Linux.

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
    1. Re:Wrong, DUH! by Anonymous Coward · · Score: 0

      You're not making a very solid case for your "less idiots on linux" point.

  209. I wonder... by slashzero · · Score: 1

    I wonder how many buffer overflow errors go unreported in windows. Closed source software may obfuscate many potential security errors that open source software make blantenly obvious. Although I'm sure it's harder to find those errors in closed source software but with so many windows applications it's hard to believe they are not there.

  210. TruSecure not SecurityFocus by lesinator · · Score: 2, Informative

    NTBugtraq is actually part of TruSecure, not SecurityFocus. What SecurityFocus has in a separate list called BugTraq. Very confusing...

  211. It's the default install. by Aloekak · · Score: 1

    Security of the system, in the hands of society is really based on the installation. Sure, a good admin can secure Windows or Linux. The fact is that most people that install either are not good admins. Most people here on /. are.

    If linux stopped bundling bind, and other exploit-happy software, or atleast didn't install it by default, we would easily be more secure. The default install of Windows usually doesn't include all sorts of fun exploit happy software(with the exception of IIS).

    Plus, what are we talking about here? Are they counting the number of exploits against Windows and trying to compare them to all the different packages in linux? Most people don't install bind and other exploit-happy software by default.

    We ought to think about software that goes into default installs, based on their prior exploits, and see if they should be included, or use an alternative.


  212. Sometimes by Ironfist_ironmined · · Score: 1

    Sometimes i wonder if they just make up numbers like this to get slashdotted and get some throughput...

    I recall a popup somewhere there on that page...

    The limits of my language are the limits of my world -- Wittgenstein

    --
    0xC3
  213. 2k vs. Slackware by Penguinoflight · · Score: 0

    Try some numbers of Slackware linux vs. windows nt. Redhat is probably the least secure of the linux distributions, however there have been less security flaws in Slackware Linux in it's entire history, than Windows nt in it's best year.

    --
    "And we have seen and do testify that the Father sent the Son to be the Savior of the World"
    1 John 4:14
  214. Original article's dissapearance explained? by Dell+Brandstone · · Score: 1
    It's too bad the Wininformant website went down. I wonder if BSD or Linux would have gone down in flames the way their IIS/NT server did.

    What with all of these informed responses, you'd think the original article by wininformant was available or something.


    -DB
    --
    [ a directive occured while processing this error ]
  215. A more scientific aproach by C0vardeAn0nim0 · · Score: 3, Interesting

    requires some methods, and since I'm too lazy today to look for the mothods they used to compile all that data, I'll create my own.

    1- let's stablish what's a windows OS and what's a Linux OS (and the nots too)

    1.1 Windows 3.1 is NOT an operational system. is a graphic user interface (GUI) for DOS. let's assume win 95/98/me and NT 3.5/4.0/2000/XP are OSes.

    1.2 Linux is NOT an OS. Is a KERNEL. the combination between Linux and GNU OS makes the operational system we know as GNU/Linux

    2 Let's determine the minimum instalation of each one that's capable of doing usefull work, including user tasks such as reading e-mail and browsing the web and server tasks such as serving web pages, sharing files, routing e-mail, et al.

    2.1 Both in Windows and GNU/Linux you'll have to select all the packages neccessary to the proposed tasks using the minimum ofered by the standard install CD. If the CD doesn't ofer some of the functionalities they must be downloaded from the manufacturer's site.

    2.2.1 for windows you'll keep only:
    - networking drivers;
    - the standard MS file sharing;
    - Internet Explorer;
    - Outlook express/MS mail;
    - IIS/personal web server
    - Exchange server;

    2.2.1 For GNU/Linux:
    - Network modules and associated tools;
    - NFS or Samba;
    - Mutt os pine (remember, in GNU/Linux you can read e-mail/browse from command line, so XFree is not installed);
    - Lynx or Links
    - Apache;
    - Sendmail;

    3 count the number of security holes in the test systems, including:
    - vulnerabilities to e-mail virii;
    - vulnerabilities to malicious web-pages;
    - remote exploits that grant root/administrator access;
    - local exploits that grant root/administrator access;
    - holes that allows an atacker to succesfully launch a DoS atack, freezing the machine;
    - unauthorized read and/or write access to files;
    - any other vulnerability you can think of;

    In a test like this who do you think'll win ? please post your comments.

    --
    What ? Me, worry ?
    1. Re:A more scientific aproach by Anonymous Coward · · Score: 0

      Windows 3.1 controlled memory management and had a device driver interface.

      I have no idea why it wouldn't be considered an operating system, and 9x would -- they are pretty much the same architecture.

    2. Re:A more scientific aproach by Vegeta99 · · Score: 1
      Blockquoth the poster:
      3 count the number of security holes in the test systems, including:
      - vulnerabilities to e-mail virii;
      - vulnerabilities to malicious web-pages;
      - remote exploits that grant root/administrator access;
      - local exploits that grant root/administrator access;
      - holes that allows an atacker to succesfully launch a DoS atack, freezing the machine;
      - unauthorized read and/or write access to files;
      - any other vulnerability you can think of;


      EMail? No. THE USER MUST RUN IT. OOh, attatchment from someone I don't know, I'll run it!
      Web pages? No. Ooh, www.haxx0rzrusss.com! Lets go there.

      Other than those two, the rest sound fine. And use a default install. No changing any options, whatsoever. so if your Linux distribution has telnet, leave it, etc.
    3. Re:A more scientific aproach by C0vardeAn0nim0 · · Score: 1

      actually Outlook Express has (had) some nasty bugs that allows some atachments to be automatically executed and IExplorer up to 5.5 IIRC would automatically execute scripts in an .eml file atached to web pages.

      The default install could be a good idea to test the security for desktop installs, in this case a linux machine would have to include XFree (wich had its share of security holes in the past), but for a server only install I'd keep XFree out.

      --
      What ? Me, worry ?
  216. Oh.. by dusanv · · Score: 0, Flamebait

    Update: 02/04 16:54 GMT by T: Looks like the WinInfo site has gone down since the story was submitted

    .. sweet revenge ;)

    D.

  217. Come on! by mat33 · · Score: 1

    According to the Netcraft survey, it is 49% WIN and 45%*NIX. That is not a big deal, and we can say that the *nix have about the same server marketshare than windows. Espescially that we dont know the margin of error of this survey. It may be very high, so it may be possible that *nix are more (or fewer) than that.

    1. Re:Come on! by RazzleFrog · · Score: 1

      The original poster is actually talking about Linux's market share and uses Apache as an example. Linux is only at 29% versus 49% for Windows.

      Either way, that isn't the point. The point is that Windows is a lot more prolific as a web server than is apparent from the regular netcraft survey.

      The article also states that the error margin is probably under +-10%.

  218. Open Source airs its laundry by Anonymous Coward · · Score: 2, Insightful

    Open Source projects use the public internet to keep everyone well informed of software weaknesses and we're not afraid to keep doing that because it makes the software stronger.

    Besides the fact that it is unfair to count 6 releases of Red Hat as one OS and not count NT and Win2k as one release over the same period, the initial period for a Linux distro is going bring issues to the surface, that is part of the process.

    The linux bug finders are, as a rule, supported, appreciated and recognised in the open source community as pioneers. There findings are widely shared and listenned to -- I'm glad you can find the reports.

    The Windows Bug Finders are threatenned, hushed, denied information, ignored and actively discouraged. Furthermore any recovery data is typically horded till a shiny executable can be sent out in a subdued and 'professional' manner when it wont embarrass Microsoft.

    Where would you rather be???

    I'll take linux any day.

  219. *arg* by Anonymous Coward · · Score: 0

    why can't we stop this linux window whatever bullshit, post some funny cmr taco story's something about aibo or whatever, but we have to face it, some windows people see themself as geeks, and this is news for geeks. We all know linux and windows zealots exist and both parties are to stuborn to admit there faults. No side wishes to learn from the comment the other side gives. I know, some find it entertaining to read this kind of endless, useless discussions, but please, i don't think it's fun anymore... especially since there seem to be more and more windows zealot(marketing trained msce's) too out. I just mean, aibo like stuff is cool, fo windows and linux users alike. Discussions about which is less worse than the other ed nowhere. they both have ther faults, and both sides are to stupid to admit it. And the way most discussions start??? by pointing out to a stupid article writen by some housemom/dad(not to discriminate anyone) who recently installed nt/linux and thinks he's a nt-admin/linux-root journalist that has the right to spread his cheap talk (as opposed to free speech). Ow please... So like i care if linux would have more bugs, it never failed me, and probabley just the same way, a good nt-admin has never been letten down by his nt. Crap, with the bullshit and (mostly-)unmotivated arguments i could break down just as easy a linux user as i could break down a windows user... It's not a matter of which one is best, they are both equal. even when it comes to 'the-microsoft-asshole-attitude', i think most linux newbie-zealots are capable of compiting with that attitude (linux-zealot-newbie-...-ashole-i-think-i-know-it- all-asshole attitude'?).. it's all just a matter of what you like and what you are best at... personally

  220. Bought and Paid For "Study" by Anonymous Coward · · Score: 0

    No time to track it down now, but I saw an article about two weeks ago about this soon-to-be-released "study", which clearly indicated that the authors of the study had been hired by MS.

    I think it may have been linked through Wired or CNet.

  221. wininformant.com eats its own dog food ... by mr_death · · Score: 2, Funny
    ... by using IIS as its web server.

    As of this morning, however, the dog seems to be dead (www.wininformant.com.) Coincidence? You tell me.

    --
    It's Linux, damnit! Pay no attention to renaming attempts by self-aggrandizing blowhards.
    1. Re:wininformant.com eats its own dog food ... by wholesomegrits · · Score: 3, Insightful

      What the fuck, chuck? So what? I don't care if the thing is running SupaOS/Linux/HP-UX et al. Put Google on a T1 and it too will dry heave and puke. I don't suspect that Any Old Bush League site is equipped to get about 40,000 hits in a 2 hour period.

      It has nothing to do with it being IIS or Tux or Apache or anything.

      But you already knew this, and just got lucky that some zealot with moderation points fell for the Typical Windows Slam. Don't think I'm slamming you. Its not like you modded yourself up, so my beef isn't with you. It's with the Fanatics.

      --
      No sig is worth reading.
    2. Re:wininformant.com eats its own dog food ... by mr_death · · Score: 2
      Well, my original post was a joke, not serious.

      However, given that wininformant.com purports to be "Windows news and information. No fluff.", and has multiple publications, I expect some level of site professionalism -- more than simply plunking an IIS box on a random DSL or T1 line.

      I can't tell whether the site was down because of insufficient bandwidth (as you suggested), or because the box(en) couldn't handle the load (or had insufficient load balancing.) Either way, I'm not impressed with the site design.

      According to netcraft.com, serious sites (Most Requested Sites, or Top Hosting Locations) use mostly apache on solaris, linux, freebsd, or netbsd. Microsoft corporate-related sites are the obvious exception.

      --
      It's Linux, damnit! Pay no attention to renaming attempts by self-aggrandizing blowhards.
  222. Re:What?!? by Anonymous Coward · · Score: 0

    I agree

  223. The patches included with SRP1 for Win2k ... by JoeGee · · Score: 1

    For those who are curious I listed the information below from Microsoft's own site. You'll note that Windows 2000 alone had considerably more than one bug that required a patch.

    Before anyone criticizes the patches below for including apps like telnet and IIS, many of the bugs that are cited by Bugtraq in Linux distributions also have nothing to do with the OS itself, and everything to do with installed packages that are included with the distribution.

    Q252795 MS01-046: Windows 2000 Does Not Support Mapping Virtual COM Ports to Infrared Ports

    Q273854 MS00-077: Denial of Service Can Occur with Microsoft NetMeeting

    Q276471 MS00-079: Patch for "HyperTerminal Buffer Overflow" Vulnerability In Windows 2000

    Q282806 MS01-031: Telnet Service Prevents an Idle Telnet Session from Timing Out

    Q285156 MS01-013: Windows 2000 Event Viewer Contains an Unchecked Buffer

    Q285851 MS01-007: Patch Available for Network DDE Agent Request Vulnerability

    Q285985 MS01-004: Patch Available for New Variant of File Fragment Reading via .HTR Vulnerability

    Q286043 MS01-051: Patch Available for Telnet Logging Vulnerability

    Q287397 MS01-011: Patch Available for Malformed Domain Controller Service Request Vulnerability

    Q287912 MS01-031: Predictable Named Pipes Could Enable Privilege Elevation with Telnet

    Q288855 MS01-026: FTP Service Allows Login to Domain Guest Account

    Q289243 MS02-001: Forged SID Could Result in Elevated Privileges in Windows 2000

    Q289782 INFO: Post Windows 2000 Service Pack 2 COM+ Rollup Hotfix 8 Is Available

    Q292435 MS01-040: Invalid RDP Data Can Cause Memory Leak in Terminal Services

    Q293826 MS01-026: Pattern-Matching Function Can Cause Access Violation on FTP Server

    Q294370 MS01-026: Updated Patch for Microsoft Security Bulletin MS00-060

    Q294379 Addressees Appear in Body of SMTP Message Instead of the Header If You Specify Many Addressees

    Q294391 MS01-024: Malformed Request to Domain Controller Can Cause Memory Exhaustion

    Q294774 MS01-044: IIS Loads ISAPI Extension In-Process Even When Application Is Marked for High Isolation

    Q295534 MS01-026: Superfluous Decoding Operation Can Allow Command Execution Through IIS

    Q296185 MS01-025: Patch Available for New Variant of the "Malformed Hit-Highlighting" Vulnerability

    Q297860 MS01-044: IIS 5.0 Security and Post-Windows NT 4.0 SP5 IIS 4.0 Patch Rollup

    Q298009 Cipher.exe Security Tool for the Encrypting File System

    Q298012 MS01-041: Malformed RPC Request Can Cause Service Problems

    Q298340 MS01-044: Patch Available for WebDAV Denial of Service

    Q299553 MS01-031: Logon Command That Contains a Particular Malformation Causes an Access Violation in the Telnet Service

    Q299687 MS01-036: Function Exposed By Using LDAP over SSL Could Enable Passwords to Be Changed

    Q299796 MS00-077: Denial-of-Service Attack on Port 1720 May Cause a Memory Leak in Conf.exe

    Q300477 MS01-035: FPSE: Potential Buffer Overrun Vulnerability in Visual Studio RAD (Remote Application Deployment)

    Q300855 MS01-031: Windows 2000 Telnet Security Rollup

    Q300901 MS01-031: Telnet Service Allows Logging On to Domain Guest Account

    Q300905 MS01-031: Handle Leak in Telnet Service Causes a Denial-of-Service Vulnerability

    Q300908 MS01-031: Program Running with Normal Privileges Can Terminate a Telnet Session

    Q300972 MS01-033: Unchecked Buffer in Index Server ISAPI Extension Can Enable Web Server Compromise

    Q301625 MS01-044: Patch Available for SSI Privilege Elevation Vulnerability

    Q302755 MS01-037: Authentication Error in SMTP Service Could Allow Mail Relaying

    Q303984 MS01-043: NNTP Service in Windows 2000 Contains a Memory Leak

    Q304867 MS01-044: Patch Available for MIME Header Denial of Service Vulnerability

    Q305601 MS01-060: FIX: CRT String Format Functions May Underwrite Buffer

    Q306118 FPSE2000: List of Issues Fixed in FrontPage Server Extensions Service Release 1.3

    Q306121 MS01-051: Malformed "Dotless" IP Address Can Cause a Web Page to Be Handled in the Intranet Zone

    Q307454 MS01-052: Invalid RDP Data Can Cause Terminal Services Failure

    Q308268 .IDA and .IDQ Mappings Restored After You Install Service Pack or Add/Remove a Windows Component

    Q308414 MS01-051: Patch Available for HTTP Request Encoding Vulnerability

    Q311355 MS01-041: The Danish Version of Security Hotfix MS01-041 Is Not Installed

    Q311371 Terminal Services Sessions Are Disconnected Because of a Decryption Error

    Q315404 MS01-052: Clients with an Expired Temporary License May Be Unable to Connect to Terminal Services

    --

    Get off my virtual lawn, you damned virtual kids!
  224. C'mon! by Anonymous Coward · · Score: 0

    I want to see 1,000,000 COMMENTS by the end of the day! Trolls, crapflooders, Linux zealots! Post, post, post! Post soon, post often! One million comments!!!

  225. The versions are all irrelivent by strAtEdgE · · Score: 1

    It seems from reading the comments here that a very unfair comparison between 'everything Linux' and specific versions of Windows is being made. You have to take into account all of the versions of the moderm windows OS (95/98/NT/2000/XP) to begin to compare to the range of uses for Linux, and even then you're not doing Linux's flexability justice. Although they use the phrase 'Windows' from time to time I am led to believe they are actually comparing any kind of Linux vulnerability to specifically only Win2K and WinNT vulnerabilities. And on top of it, although I'm admittedly not sure, I get the feeling this comparison only took into account perhaps IIS on the Windows side while lumping into Linux the vulnerabilities of a great many more applications.

    How about someone produce a more useful article such as a comparison of vulnerabilities between WinXP and Linux kernel 2.4.17, and this time take into account the most important factor of all; how long the vulnerabilities are known in the wild before a fix is available.

    --
    ----- sXe
  226. I believe it.. by Anonymous Coward · · Score: 0

    Why?

    The moronic Winnuts will include vulnerabilities such as, say, ICQ clients, P2P crap, E!.. Shit that we're smart enough to not let near a server... but they'll insist are server vulnerabilities.

    Then there's the many other reasons why we can't trust anything out of the mouth of Winnuts.. How many of the bugs are from third party software? How can there be more vulnerabilities for Linux when SecuriTeam keeps shoving Windows bugs in my mailbox?

    In the end, bugs or no bugs, a Linux box can be secured appropriately. A Windows box?

    "Ha ha ha, that's some funny shit."

  227. If Windows is so secure.... by inkless1 · · Score: 1

    ...then why did my Win98 box die without me touching it? It got that virus from somewhere

    ...why am I finding ways to filter out all the Win virus spiders from the apache logs

    ...was Outlook the cause of millions of dollars in damages for corporate IT security?

    ALL of the major viruses that came out this year, and this was a stellar year for security and virus growth, were Windows. We all know that Linux isn't fundamentally virus-proof, but the big security blunders of 2001 were Windows.

    This is the real danger of internet reporting. No need for subscribers. At least when /. gets something wrong, or puts it's foot in it's mouth, it's just a bunch of geeks pointing at each other.

    This is just outright FUD, but if people had to pay for the FUD, it wouldn't be around. Ah well, good and the bad I guess. Hopefully the real press has done it's job in reporting Windows' security flaws to make this kind of brochure-ware journalism ineffective.

    The next time someone asks "Why do you have to point out EVERY Microsoft flaw" ... THIS IS WHY.

    inky

  228. Those are application flaws, not OS flaws. by exceed · · Score: 2

    The three names you mentioned are all viruses in APPLICATIONS ran on Windows, not the operating system itself.

    Nimda was an Outlook virus (...right?)
    Code Red was an IIS virus,
    and I Love You was an Outlook virus as well.

    All of these are not flaws in the operating system, rather they exploit the applications running on Windows. Consider this: is Linux itself insecure because a large majority of Linux computers exploited are running BIND, and BIND runs on Linux?

    --

    void women (int money, time_t time);
    1. Re:Those are application flaws, not OS flaws. by kaladorn · · Score: 2

      Whereas I agree with the sentiment that these are application bugs and app bugs can't be blamed on the OS, one _can_ take the OS to task for failing to adequately protect itself (ie allowing the applications to do horrible things to it).

      Things like MAPI are a lovely opportunity for crapulent software apps to make the OS perform in a similarly crapulent fashion. Is this good OS design? This is like the question of whether it is solely the criminal to blame when your house with the doors open and windows flung wide is burgled.... yes of course we blame the crook! But does that make your security practice laudible? I think not.

      --
      -- Mal: "Well they tell you: never hit a man with a closed fist. But it is, on occasion, hilarious."
    2. Re:Those are application flaws, not OS flaws. by vegardolsen · · Score: 0

      Viruses in Applications bundled with Windows. When so many applications are bundled with the OS, the higher the posibility for viruses gets. I can bet my grandmothers eye on that most Windows users use Outlook as theire e-mail client. When this .NET system realy gets many users and is final, we will see viruses much worse then Nimda, I_Love_You and Code Red. In Linux there isn't a standard E-mail client, there isn't a standard browser, so viruses don't spread as fast as Viruses on the Windows platform. And thats a fact

      --
      Sig e godt =)
    3. Re:Those are application flaws, not OS flaws. by fuess · · Score: 1

      Given Microsoft's internet strategy in which the distinction between internet application and the OS are blurred by extreme integration, it is less certain that the flaws are indeed unrelated to the OS. Both IIS and Outlook are provided with the OS.

    4. Re:Those are application flaws, not OS flaws. by MaxieZ · · Score: 1

      Well I love you is the users problem, but default settings in Outlook Express which is bundled with the OS, helped it to be more of a problem. Nimba and Code Red would not have existed, except for a security vulnerability (buffer overflow) in IIS

  229. Windows doesn't have shell user security by Anonymous Coward · · Score: 0

    Linux security vulnerabilities come in two flavors, those remote exploitable, and those locally exploitable.. The latter of these vulnerabilities shouldn't be considered since Windows doesn't have security for local users.(You can get admin rights pretty easy sitting at the keyboard, and you can't really use a windows system remotely except via external services such as SMB networking)

    I think if you compare the externally exploitable holes on linux vs externally exploitable on windows it would come out more favorable..

    It's also a fair comparison, on my servers on my uses only hit the box via POP3, IMAP, SMB, etc. They have no shell access so I don't really have to worry as much about that side of security matters.

    Just a few thoughts.

  230. Um.. No... by Anonymous Coward · · Score: 0

    OK.. 2 years ago around april 13th.. A BIG security hole was found within Microsoft IIS/Front Page Where a user could a) cause a buffer overrun in IIS and b) be able to fetch files off of the webserver before being parsed (ie pulling ORIGINAL VBScript ..asp source code) using a encypt/passord of "NetscapeEngineersAreWeenies". The following Day Microsoft sends a press release denieng the bug, only saying the bugger overrun exists.. I had downloaded the exploit code from SecurityFocus and tried it out on our servers.. The bug was there.. I even tried changing the "password" and it didn't work.. only when the password was NetscapeEngineersAreWeenies..
    Hmm... Microsoft NEVER released a patch..
    That password was inside several of the frontpage dlls!!!.. The Microsoft solution to the "buffer overrun" was to remove a few key dlls from FrontPage.. thus disabling Most of the functionality of frontpage but preventing the exploit..

    Microsoft plays the game of "deny the bug". They've been going after organizations that find security holes and "making" them NOT release info about security holes in Microsoft products...

    And when Code Red came out.. I hunted around their blastes site for like an HOUR trying to find the fix.. it was WELL hidden.. I mean it wasn't even IN the Critical Updates...DUH!!!!

    1. Re:Um.. No... by Anonymous Coward · · Score: 0

      Your facts are wrong -"NetscapeEngineersAreWeenies" was not a password. It was an XOR hash to obscure the normal user password that HTTP would normally send in cleartext. Nobody denied that the preferrable solution would be to run over HTTPS.

  231. Opensource OS's have more problems initially.. by btellier · · Score: 2

    but over time the bugs will be found by the thousands of people who are looking at the code every week. Meanwhile Windows will continue to have a steady stream of bugs that will never begin to taper off.

    The amount of code that is being generated by Microsoft is much greater than the amount of lines Windows hackers can disassemble. Therefore the number of bugs is growing, but the number discovered is staying the same. IMO, I have written exploits and done disassembly for both Linux/BSD/Opensource and Solaris/Microsoft/ClosedSource and naturally it takes TONS more time to look over your average daemon in the latter. There are more holes, but they're more difficult to find. Eventually they will be found and the disparity will become more clear.

  232. Figures dont lie, but liars sure can figure by Lew+Pitcher · · Score: 1
    C'mon people. We've been here before ("Fred Moody Says Linux Worst Operating System Ever"), and gone through the reasons why these figures are suspect.

    The story, for what it's worth, is just another FUD troll by a Microsoft supporter, and has nothing to do with real life.

    --

    "values of beta will give rise to dom!"

  233. The Number One Cause of Security Flaws by NeuroManson · · Score: 2

    Windows users who jump in without having a single idea what they're doing, who download and run countless virii...

    Linux users who jump in without having a single idea what they're doing, who ignore security updates entirely because they live under the myth that Linux is all that is good in the world, and can do no wrong...

    In the end, it's user error on both sides that cause the security prolems, and the skript kiddiez who exploit them...

    --
    Just because you can mod me down, doesn't mean you're right. Shoes for industry!
  234. counting the beans you find by Anonymous Coward · · Score: 0


    Even if the numbers were counted fairly/correctly, the fact that the Linux numbers were as close to NT as they were says something. After all, the code can be reviewed for vulnerabilities whereas NT bug hunting seems to be more of a 'shot in the dark' effort. And yet the numbers were still comparable. Silly.

  235. The free software credo by Anonymous Coward · · Score: 0
    "No software should work correctly out of the box".

    e.g. I just downloaded a GNU program and followed the instructions to compile it under Windows. This failed. I guess that's what the distro companies are for...

    Unfortunately this credo is also taken up by a large number of PC game writers, so I'll stick with Nintendo for a while yet... their stuff actually works.

  236. Month of Security Coding by MikeJ9919 · · Score: 1

    Now I get it. Microsoft is actually devoting a month to working on security...both by (yeah right) trying to fix the holes in the code and by trying to rewrite history. You do have to admire their multi-pronged approach.

    -Mike-

  237. Are Open Source vs Closed Source Comparisons Valid by Eric+Damron · · Score: 1

    Like so many, I've been slashdotted out of the article so I'll have to make some guesses about the data. It would be reasonable to assume that more errors are found by the many thousands of eyes pouring over open source code than the few looking at closed source code. So, finding more errors in an open source OS is no proof that Windows is more secure. The numbers that I would like to see are: Of the Windows vulnerabilities reported, how many of them actually came from Microsoft and how many of them were first reported by a victim who reports "My Windows box has been hacked! There must be a vulnerability!"

    --
    The race isn't always to the swift... but that's the way to bet!
  238. Let's poll: is Linux less secure than Windows? by Anonymous Coward · · Score: 0

    1) yes
    2) no
    3) depends on admin
    4) cow boy neal

  239. RE: Update: 02/04 16:54 GMT by hyyx · · Score: 1

    "Update: 02/04 16:54 GMT by T: Looks like the WinInfo site has gone down since the story was submitted, so you may have to content yourself in the meantime with the Bugtraq numbers."

    I don't mean to complain, but this is an opportunity I can't sit on. Why is it important to update everyone that the site was slashdotted? Doesn't this happen to over 75% of the front page stories? Every time I come to Slashdot to read a few interesting articles, I can't because they always get slashdoted. Isn't it about time to implement some sort of mirror system? Maybe some readers can donate some time and resources to get this started (I would...). What fun is it to keep "wishing" that I could read all these interesting articles, when the whole point is to have stories that people can actually read? Is anyone with me here?

  240. Re:Statistics.... count the bugs in fixpacks too by Locutus · · Score: 2

    just sick of the crap streaming from Redmond. without their monopoly on the OS, they would be a much smaller application company. MUCH SMALLER. And by reading the dial on the FUD METER, it looks like Linux is THE target. Therefore Bill and Steve are FUD-WRESTLING again and the media is at ringside taking notes. A tinfoil hat is all I need to keep the FUD from getting on me. It's THAT weak these days. ;/

    LoB

    --
    "Anyone who stands out in the middle of a road looks like roadkill to me." --Linus
  241. Only through August by futuresheep · · Score: 1

    Did anyone else notice that the listing only goes through August 2001? That would put this before several very nasty Windows vulnerabilties were released or attacked by virii and worms.

    1. Re:Only through August by Drestin · · Score: 2, Informative

      Actually, there have been no new vulnerabilites for IIS since August and very few "nasty" ones at all for all of MS products since August. I think you'll find there are WAY more RedHat ones since then...

  242. IE subcomponent or "integral part"? by Mojo+Geek · · Score: 2, Insightful

    I'm confused here. Is IE just an application or "subcomponent" of a MS operating system? That's not what they've been argueing in court. They say they've "integrated" it with the operating system, that it's an "integral part"! They even went on to argue (unsucessfully) that the operating system cannot function without it.

    And why does which ever answer I get smell like an Enron balance sheet?

    1. Re:IE subcomponent or "integral part"? by Not+The+Real+Me · · Score: 1

      IE is not an application because IE does replace system DLL's. It's a form of creative accounting when an organization does what they did.

  243. There is more to this Story by jasonrfink · · Score: 1

    In the BSD community we pride ourself on disclosure. Besides, I do not think most administrators take as much issue with windows security as it may seem (although it seems funny at times). Here is a question, on service packs that come out, how many bugs are fixed those binary patches that could be security flaws that no one knows about?

    After disclosure the next issue most people overlook is the level of granularity most UNIX systems patch to, for example, lets say there is a 1 byte overflow in the less pager. If microsoft had less (they do have more though!) would they bother posting that as a security flaw or even a possible security flaw? Most likely not, yet we see these bugs posted all the time with open source software.

    Without looking at the difference in granularity and disclosures - there can never be a real comparison between windows and any other system in the world, open source or not.

  244. Something else I noticed at the site... by FyRE666 · · Score: 1


    Exchange Server Hits 100 Million Users

    Given that the company announced its 75 millionth seat just this past October, that's a lot of new seats. There's a joke here waiting to happen, but I don't know what it is.


    I think it's something along the lines of "Microsoft consider their customers to be assholes". Reading the laughably inacurate reporting plastered across the site, it would seem they're not far wrong...

  245. Macs: useless or crack proof or both? by Anonymous Coward · · Score: 0

    And apparently an idiot with Mac OS X Server needn't worry at all. Lets see the debian HURD developers pull that off. All I have to say is long live Apple and Linux.

  246. *rolls eyes* by automatic_jack · · Score: 1

    Haven't we been over this already?

    --

    -- Have you ever noticed that at trade shows, Microsoft is always the company that is handing out stress balls?

  247. This just in: by nice · · Score: 0, Offtopic

    Satan claims his fires aren't all that hot, come roast some marshmallows with us.

  248. one thing to consider... by Shads · · Score: 2, Insightful

    ... is when a windows exploit comes out, it effects most windows systems in opperation. When a linux exploit comes out (proftpd, apache, etc) it rarely effects all the systems in the field. I know about 90% of the bugs that show up in bugtraq and else where dont apply at ALL to my system because I dont run those daemons. Where in windows... how many people DONT run activex scripting or diable javascript in outlook?

    --
    Shadus
  249. maybe a more detailed report is needed? by ryusen · · Score: 1
    i don't know if you have the resources to do it (or even if you already do), but to keep this kind of misrepresentation in the future, maybe you could provide more data than aggregate sums?
    a few suggestions i think would be usefull:
    • # of vulnerbilities that have not been patched
    • average time to patch a vulnerbility
    • number of local vs remote exploits
    • number of of exploits that are from included software packages and services (ie, wu-ftp, bind, etc.)
    --

    I believe sex is highly over rated... unless it involves me
  250. Linux Aggregate removed from the list by p7 · · Score: 2, Informative

    I was just at the Security Focus Vulnerabilities page and the page has had the linux aggregate stat removed from the list, sometime between 9am pdt and 12:30pm pdt. I guess some good came out of the article.

  251. come on people! by gol64738 · · Score: 1

    first of all, this article was NOT written by security focus.
    this article was written by the same idiot that always writes a bunch of misguided FUD about Linux.
    I forget his name now, and the site is down.
    don't believe me? read all the other stories this author has written. it's all in the wininformant page. and it is ALL FUD and misinformation.

    the fact that a slashdot editor posted this drivel on slashdot tells me a LOT about slashdot editors....

  252. Thurrott by IsoRashi · · Score: 2, Interesting

    www.WinInformant.com came back up a little while ago, the text of the "article" is basically what was quoted for the topic subject. I tried to do a little digging to find out if the author or the company he works for is affiliated/owned by MS, but wasn't able to really turn up a lot. However, I did find this little rant at one site talking about how the credibility of the author is pretty much nil. Can anyone else turn up other info?

    --
    This is not the greatest sig in the world, no. This is just a tribute.
  253. Re:What?!? by MrWinkey · · Score: 0, Flamebait

    Do the names "Nimda", "Code Red" and "I Love You" ring a bell?

    Thoes were FEATURES not security flaws!

    Sheesh I wish people would get it right. That's why MS has less bugs. They count half of them as hidden features!

    --
    Vote early. Vote often. Vote CowboyNeal.
  254. Screw it by AdmrlNxn · · Score: 1

    I think this is totally biased.

    Of course every Linux user and their mom is going to go up in arms over a review. Especially when it attacks their OS of choice.

    Vice versa man. If you had a windot.org site where peole ranted and raved against Linux and an article of the same magnitude came out. Then Windows users will do the exact same thing.

    How about we try this. Why don't you just believe in what you know. Follow what you know is right. And for fucks sake, not get a hair up your ass and freak when a simple article says one is better than the other.

    I mean I know we are children here but one would think that at some point you can just let go. Stop rolling your eyes and just say fuck it.

    --
    ~Admrlnxn
    "I got your mom in my trunk"
  255. Can't be all that much more secure by trenton · · Score: 2

    If Microsoft halts all new feature development for a month to fix bugs!

    http://www.ntsecurity.net/Articles/Index.cfm?Artic leID=23971

    Posted by the same author of the misleading bug brief, Paul Thurrott.

    --
    Too big to fail? Does that make me to small to succeed?
  256. Yea right! These are good numbers....(wink, wink) by CyberPsyko · · Score: 0

    It is plainly stated that the numbers aren't necessarily accurate...

    There is a distinct difference in the way that vulnerabilities are counted for Microsoft Windows and other operating systems. For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers.


    That's good enough for me.

  257. Oh yeah. by ikekrull · · Score: 3, Interesting

    All the servers infected with a virus hitting my web server requesting http://www/root.exe are UNIX machines, uh huh.

    Why not try this.
    With any of the following IPs, type 'smbclient -L 207.88.220.61'

    If you're more of a cracker than I am, you might then try smbclient //WORKGROUP/C\$ -I 207.88.220.61

    and just hit return when prompted for a password.

    this also works with:

    203.228.232.188
    203.231.119.70
    203.231.166.49
    203.233.20.86
    203.231.216.208
    203.199.54.26
    203.231.217.5
    203.231.122.227
    203.244.13.72

    and countless others.

    These machines (all Win2K) have their entire filesystems exposed over the internet, and are promiscuously advertising their presence because they are infected by a virus that leaves a clear trail in the logs of any web server they attempt to infect.

    These machines are engaged in abuse of my web services, and I hold Microsoft at least partly responsible for this situation.

    Presumably the virus itself is responsible for opening their shares with guest access, but maybe it's M$'s lame out-of-the-box security.

    If your machine's IP is on this (small fragment of my) list of machines banned from accessing my web server due to virus infection, then i suggest you replace your hopelessly insecure OS with a decent one.

    I was incredulous when i analysed my web-servers logfiles and found the sheer number of virus-infected hosts, all Windows NT and 2000, and most of which were sharing the entire contents of their hard-drives over the public internet.

    I know Windows can be secure as the admin is competent, but the ease with which it's security is breached through Outlook/IE is breathtaking.

    The idea that Windows is somehow more secure than Linux/UNIX is laughable to me.

    --
    I gots ta ding a ding dang my dang a long ling long
    1. Re:Oh yeah. by Anonymous Coward · · Score: 0

      not all of those are win2k some are NT 4.0.

    2. Re:Oh yeah. by supertsaar · · Score: 1

      Well, I get tons of Nimda and the occasional CodeRed on my webserver too. I did the hard drive mapping thingie to C$ as well (using MacOs I have to use Virtual PC for that, from MacOsX its done with smbutil or from within finder). More than just a "bad" webserver / OS combination, I think that its the users that cause this. I ask you: would _you_ be unaware of your machine making hundreds of http connections all the time? Right. And we all know the amount of publicity Nimda has gotten. You must have been living under _two_ rocks not to know about it. So my point would be: these people would end up having compromised machines no matter _what_ OS they choose. They'd just be running stuff as root _all_the_time. Script kiddies are so damn smart these days....

      --
      The Bigger The Headache The Bigger the Pill
  258. A Treatise on Fishing by Malor · · Score: 5, Insightful

    I posted a couple years ago on this topic. My hypothesis at the time was that Open Source would show more bugs for quite some time, as people poked through the code, but would gradually settle down and become very secure. I also believed that Windows vulnerabilities would continue to be discovered at a more or less constant rate.

    The jury is still out.

    The SecurityFocus statistics broke in August, 2001, per their web page, so one has to extrapolate the partial 2001 total to get the projected total for the year.

    In that extrapolation, one sees that the expected number of bugs (assuming the 96 reported bugs cover through the end of August) would be 144. There were 153 the year prior, which is likely well within the margin of error. In addition, many of the black hats have STOPPED REVEALING their exploits, so in fact there may be many more than what we see.

    Now, it's worth pointing out that this is not necessarily a good measurement of security. We may be measuring the wrong thing.

    An example of bad measurement is the one the government used to determine how many cod were left out in the ocean, to prevent overfishing. Year after year, the catches were about the same, so the government assumed that the fish stocks were constant. But suddenly there were no more fish -- the industry collapsed.

    Why? Because they were measuring the wrong thing. They weren't measuring the total number of fish, they were measuring the fish that were caught. They didn't realize, as the fish stocks dwindled rapidly, that the fishers were getting newer and better technology to fish with. The total number of fish coming out of the water was constant -- but as a fraction of the total fish in the water, was going up very quickly. Eventually the fish were all but wiped out.

    Measuring security by bugs reported is very similar. It may or may not reflect the number of bugs in the 'ocean'. It is an indirect measurement at best.

    We need to differentiate between fish 'caught' and fish 'available'. From a security perspective, I think we are talking about TRUE security (the number of fish in the water) versus FUNCTIONAL security (the number of fish actually being caught).

    Now, as security people, our goal is to reduce the fish catch as much as possible. There's two ways to do this; we can reduce the number of fish, or we can somehow control, limit, or damage the profession of fishing.

    The real professonals are trying to reduce the number of fish in the water. That's the true long-term solution. But from a short-term perspective, what I care about personally is how many fish are CAUGHT. Every time they come up with a new exploit, I have to run around like a maniac patching systems.

    However, the fishing analogy starts to break down, as most do eventually. Truly secure systems are still run by people, and people make mistakes. Even if the OS is perfect, the attack will often come against the weakest link, the employees. Thus, even though I would prefer to have true security, I have to argue that it isn't really necessary. The OS just has to be stronger than the other avenues of attack. ("Why are you putting on tennis shoes? You can't outrun a bear!" "I don't have to. I just have to outrun you.")

    Security through obscurity, in other words, may be adequate for most uses. It slows down the rate of fish catching. If nobody discovers the bug until the next version of the OS is out, the bug is less important. The longer it takes to discover the bug, in general, the less damage it will do -- at least as long as we're on the upgrade treadmill.

    But, a counter-argument to that just occurred to me: Security through obscurity may be long-term counter-productive -- making it hard to catch fish may have the effect of increasing the fish supply. Every time a fish is caught, it can't breed, and reduces the total population by that much. Likewise, in code, once a vulnerability is discovered, many related vulnerabilities may also be patched. Thus, security through obscurity may work well for a long time, but may actually be making the fundamental problem worse.

    Another observation I have to add is that programmers like to create new programs. Very few of them like to audit code. New projects and programs are being added to the Open Source world at an amazing speed, and I don't think they're being stringently audited. In other words, they're adding to the fish stocks every day. There is no QA department in Open Source, and the code is getting more complex than individual people can understand anymore. I think, unless we come up with a better development method, Microsoft's ability to fund a billion dollar a year QA department is likely to reduce their fish count below that of Open Source.

    So I think I will need to expand on my original hypothesis. I now believe that Open Source will probably lag behind closed source in terms of FUNCTIONAL security. In terms of TRUE security (absolute number of exploitable bugs, known or unknown) -- there's no easy way to tell. If catching fish reduces the fish supply, and if the programmers don't add too many new fish, eventually Open Source will start winning. But if Microsoft's QA department does a good job with their nets and lures, their fish supply may drop just as fast or faster. Money is definitely a good way to motivate people, and Microsoft has a lot of it.

    It's also worth pointing out that even if things are getting more secure, the catch rates may be roughly constant, because presumably the crackers will get better and better, catching a higher and higher percentage of the fish. If the analogy holds, and I suspect it may, then eventually the fish stocks will be exhausted and the black hats will be very suddenly unable to crack machines anymore.

    It's going to take at least five more years to know -- and twenty might be a more reaonable time frame. It took a long time to wipe out all those billions of cod. It may take just as long to wipe out the pool of security flaws.

    <<RON>>

    1. Re:A Treatise on Fishing by swillden · · Score: 3, Insightful

      Nice post.

      One additional idea to consider, one which I'm unfortunately not creative enough to fit into your analogy.

      The idea is the "window of vulnerability". You say that as a sysadmin you want to see less fish caught because that means you don't have to run around patching as often. Running around patching is bad, but getting rooted is worse, so if fish are going to be caught, we want the good guys to catch them first, because the bad guys prefer to gill-net them and leave them underwater as long as possible (okay, there's my lame attempt to keep the analogy going).

      I would argue that the good guys aren't generally willing to fish as deep as the bad guys, but there are more of them and they share. The bad guys (some of them, anyway) are willing to work harder, but they keep their catch to themselves. In an open source world, the fish are shallower and easier for both sides to catch which seems likely to help the good guys more than the bad guys.

      As you point out, though, this is all theoretical, and it will take years for the hard data to become available.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    2. Re:A Treatise on Fishing by Tony-A · · Score: 2

      Nice post.

      How many fishes in the sea?
      Maybe the best measure is how hard is it to catch one. To mix metaphors, seems like the low-hanging fruit has been pretty well fished out for Linux and especially the BSDs.
      With open source there is a tendency to catch as many from the same pool as possible.
      With closed source, the tendency is to catch one and leave the others still in the pool.

  259. "Uniformed"? by Anonymous Coward · · Score: 0
    No fucking wonder you're afraid of Linux - you can't even figure out how to type and use a CLI. You're stuck with GUIs - the coloring books of the computer world!

    Let us know when you're mature enough to come out of your playpen, put away your toy computers, and use the real thing!

  260. Its Paul Thurrot. Don't expect logic. by Nailer · · Score: 4, Interesting

    I'm not really surprised by this. Following the recent long Microsoft DNS outage when it was revealed that quite a few of Micrposoft's own DNS servers were running Linux (not to mention they use akamai for their downloads), Paul Thurrot came out with the classic report that although this might be true `its proves Open Source zealots wrong as Linux wasn't being used for anything mission critical'

    What the fuck? According to WHAT kind of logic is DNS not mission critical? If it its not critical, let's take those DNS servers offline (both Microsoft's and WinInfo's) and see how long either MS or Thurrot last.

    1. Re:Its Paul Thurrot. Don't expect logic. by Thatman311 · · Score: 1

      To correct you they aren't saying they are using linux for there DNS servers they are saying they are using FreeBSD. FreeBSD != Linux even though FreeBSD can run most linux software.

      --
      Silly Rabbit...Sig's are for kids.
    2. Re:Its Paul Thurrot. Don't expect logic. by Nailer · · Score: 2

      Microsoft have FreeBSD servers running parts of hotmail, but also have Linux servers providing some of their DNS service for microsoft.com, as their DNS is outsourced to another company that chooses their own OS.

      I honestly can't remember which PT was talking about when he said this - just that he famously said DNS wasn't a critical function of a network (right after a DNS outage proved hm very very wrong).

      I'm well aware that FreeBSD isn't Linux, just as I'm sure you're aware of the difference between `their' and `there', although we're both a little confused right now ; )

    3. Re:Its Paul Thurrot. Don't expect logic. by Anonymous Coward · · Score: 0

      Also remember that they only did the outsourcing when they had problems with their DNS systems. So Linux came in after MicroSofts problems.

  261. Re:And the difficulty of fixing the problems by tz · · Score: 1

    Many NT shops won't apply a service pack since they will break more things than they fix. Or you have to be very careful and verify that things still work. Hot fixes have similar problems.

    Linux/GNU/sendmail/BSD/etc. vulnerabilities tend to affect one item which is fixed without bothering anything else.

    The other statistic which isn't mentioned is how many sites ARE STILL VULNERABLE to all the common exploits.

    If the result of Mr. Bill's focus on trustworthiness is a series of huge service packs that break everything yet again it will only be good for Linux. Robustness and compatibility are not in focus right now but probably will be about 48 hours after super service pack is released.

    Oh, and will they do that for NT or will they force everyone to upgrade to 2K or XP to fix all the vulnerabilities?

  262. ICS Bind (was Re:Simply put,) by nixnixnix · · Score: 0, Flamebait

    BIND is a horrible project. It is such a piece of dewdew, I can't believe it hasn't been replaced yet. There are alternatives to BIND on Unix, (DJDNS for one) but they are new and as yet not as flexible.

    1. Re:ICS Bind (was Re:Simply put,) by Anonymous Coward · · Score: 0

      Bravo. After installing the latest BIND and having it refuse to allow me to run it as non-root (complains that I have older than 2.2.x version, but I'm running 2.4.17) I'm thinking about giving it the boot. Also, I love all the mysterious ports the latest versions open up that I have been unable to find out how to close.

  263. In other news by duren686 · · Score: 0, Offtopic

    Satan has bought a ski lift.

    In a press conference held earlier today, he stated, "Slashdot needed an excuse to post something good about Windows."

    --
    Y2K Compliant since the late 1890s
  264. I agree yet disagree by Mr.roboto · · Score: 1

    If you notice he mentions Redhat and mandrake, the two RH based distributions. "Linux" is not Redhat, nor any other distribution. If you look at Slackware for instance, he fails to mention the fact that it has less than 1/4 of the exploits of windows NT. The reason; Slackware pimps NT, not to mention (I bet I'm gonna get a ton of people calling me a troll for this, but it's the truth) RH is not really a "serving" OS, it's more of a workstation setup without being tweaked a good bit. I'm not even speaking of SuSE, connectiva, OpenLinux, deb or TurboLinux, all of which have a better average security record then Windows NT or RH, which I believe still has Wu-FTPd installed by default, the script kiddie's best friend. and I am through.

    --
    Don't call my crazy, that's what they called me back in the home!
  265. This is a sham. Relevant snippits: by fR0993R-on-Atari-520 · · Score: 3, Informative

    [Here's what I posted to the comments section of wininformant.com. Doubtful they'll display it.]

    Excellent satire.

    One only needs to look at the SecurityFocus stats referenced to find holes in most (if not all) statements made by Paul's article. An example:

    "A look at the previous 5 years [there were only four previous years reported on - tsmith]--for which the data is more complete--also shows that each year, Win2K and Windows NT had far fewer security vulnerabilities than Linux..."

    Lets take a look at the previous "five" years, starting with 2000. Redhat Linux 6.2 i386, listed as the most vulnerable of the linux flavors with 65 vulns, is bested outright by MS Windows NT with a whopping 71 vulnerabilities. To compare apples to apples requires adding in MS IIS 4.0, with 29 reported vulns, for a total of 100 vulns, or over %50 more vulnerabilities than the _buggiest_ distribution of linux. Even the combination of the lowly, four-years-on-the-market, mature Windows95 with IIS (if such a combination were possible - it matters not, because if not then W95 cannot honestly be compared to RHL) results in 64 vulns. Note that Win95 had the least vulns reported (at 35) of all the Wins. Also not that despite it being out a solid 3 years longer than RHL, it can only best the mark by 1 vuln. Not quite what I'd describe as "far fewer".

    Paul's statement is even more humorous in light of the data from 1999. In that year, Microsoft's products fill the top of the list almost exclusively, with the exception of Solaris 7.0 having slightly more vulnerabilities than IIS and NT4.0SP5. That's right folks, IIS _alone_ had more vulns than any flavor of Linux and most of the Solari. NT4.0 without a service pack? 75 vulns.

    1998 is the only year during which Paul may have a contention regarding NT besting Linux. 8 vulns vs RHL's 10. Note, however, that this is not including bugs from IIS, and is akin to comparing apples to oranges. In any case a difference of two is not what I would consider "far fewer". The comparison of RHL to Win95 is laughable in this case - what does a count of security vulnerabilities show in a system which has virtually no security?

    Once again in 1997, RHL's 6 bests WinNT's 10.

    Paul, how exactly are we to interpret the phrases "five", "each year", and "far fewer"? Perhaps as "four", "maybe one year", and "a little bit"? I suppose your wording was close enough though - I mean, it _is_ just your journalistic integrity on the line, right?

    "Win2K had fewer vulnerabilities than RedHat Linux 7.0 or MandrakeSoft Mandrake Linux 7.2"
    Note that niether BO nor IIS are reported on in the 2001 tables, thus no conclusion may be drawn.

    "...despite the fact that Windows is deployed on a far wider basis than any version of Linux"
    Excellent heresay. Well un-supported by reliable references. After reading the prior claims in your article, I'll be sure to give this little tidbit all the credit it deserves (incidentally, none).

    Thanks again for the good laugh Paul! What's next week? "WinXP Embedded Has Smaller Footprint Than vxWork? Yepppp!" I can almost imagine you shaking your pom-poms in the air.

    --
    There are 11 types of people in the world: those who understand unary, and those who don't.
  266. Bogus statistics by tuxlove · · Score: 1

    Sure, more security flaws are discovered in Linux than in Windows... which is precisely the reason Linux is more secure.

    Because Linux is open source, millions of eyes scan the code on a daily basis. This is where the old rule of QA applies: the number of bugs found in any piece of software is directly proportional to the amount of testing (or scrutiny) applied to that software. In other words, there is no such thing as bug-free software, and you will continue to find bugs with asymptotic frequency as long as you continue looking for bugs. You find the easy, obvious ones first, followed by ever-more-rare bugs.

    Because Linux has been scrutinized so heavily, it follows that many more bugs will be found than with Windows products. That doesn't mean Windows has less bugs than Linux, it just means they haven't yet been discovered. Microsoft, despite the fact that they are a behemoth, has a finite number of engineers and testers. My guess is that a relatively small percentage of them spend any time whatsoever looking for security flaws. That leaves the bulk of the job to the security community, which doesn't have the luxury of being able to scrutinize the Windows source code. No source code makes finding security flaws significantly harder. That, in combination with the fact that there are far fewer people investigating security flaws means Windows cannot possibly be as secure as Linux or any other open-source OS.

    I think the claim that MS products are more secure than Linux is just more MS propaganda.

  267. Bogus statistics? by B.D.Mills · · Score: 2

    From the article:

    A look at the previous 5 years--for which the data is more complete--also shows that each year, Win2K and Windows NT had far fewer security vulnerabilities than Linux

    Win2K had zero reported security vulnerabilities before it was released....

    --

    The only thing necessary for the triumph of evil is for good men to do nothing. - Edmund Burke
  268. Re:While you're in the forest, watch for the trees by broter · · Score: 1
    • Aren't you really saying that those security flaws are less critical because script kiddies and crackers are less likely to come across a Linux box than a Windows one?

    Actually, I think leonbev was refering the psychology of the script kiddie/script kiddie tool writer. They tend to target MS targets out of politiccal/cultural affiliation w/ Free Software, Open Source, anarchist, whatever.

    This would be the same thing as not wearing red of blue back when the bloods and cryps targeted people wearing the other color.

    --
    "One man can change the world with a bullet in the right place."
    - Mick Travis, "If..."
  269. It is *WIN*informant, after all by Anonymous Coward · · Score: 0

    So it's just like any other informant - willing to say anything for a price.

  270. Mod this up! by Anonymous Coward · · Score: 0

    Finally some analysis of the figures!

  271. There is another issue here ... by nachas · · Score: 0

    I wonder if anybody can still remember how Microsoft threatened several security companies telling them not to publish the flaws discovered in Windows? Maybe that had something to do with the "less bugs" picture painted by Microsoft?

  272. 171 Security bulletins?! by Drestin · · Score: 1

    I had no idea it was that bad for RedHat - MS only had 51 in all of 2001 (and not all for the OS itself or even a particular version - that's 51 across all MS products).

    Why don't people look at these stuff and make the obvious connection?

    1. Re:171 Security bulletins?! by sheldon · · Score: 2

      I don't think you can say that Redhat had 171 bulletins in 2001. They seem to have a bizarre numbering scheme and skip numbers occasionally. Maybe this is because the issue turned out to be a non-issue or something.

      On the other hand while looking through 2001 I did notice that some of the bulletins replaced other ones, and in those cases they deleted the original from the web site.

      So Redhat definately does make it confusing. Their bulletins also don't have much detail, they don't attribute to who found the problem, on what date it was first reported to them, etc.

      From what I could find, across all of the Redhat products they had somewhere around 80-90. Now I count 60 bulletins from Microsoft, not sure where you got the 51 number from.

      Or are you taking these from the securityfocus article?

  273. Here are some figures for 2002 - open your eyes! by Drestin · · Score: 1

    I stole this from someone else's post:

    Microsoft security bulletins released in 2002:
    MS02-001

    Redhat security bulletins released in 2002:
    2002-018
    2002-015
    2002-014
    2002-012
    2002-011
    2002-009
    2002-007
    2002-004
    2002-005
    2002-003
    2002-002
    2001-171
    2001-168
    2001-165

    Hmm... you like them apples now?

  274. To Whom it may concern at Security Focus/BugTraq by Astralmind · · Score: 2, Insightful

    Please change the way inwhich stats are reported. IIS, IE, Index Server, and the like all ship now with Windows 2000/XP just like Apache, WuFTP ship with most Linux Distros. Since this is the case, those security flaws are also security flaws in Windows 2000/XP in the much in the same way that Apache, WuFTP and other packages security flaws are being reports with Linux Distros.

    Thank You.

  275. after reading this by Anonymous Coward · · Score: 0

    ha ha ha ha ha ahaha ah ha hah ah (tears running down face) ha ha ha ha ha aha ah

  276. Re:Here are some figures for 2002 - open your eyes by Anonymous Coward · · Score: 0

    Could it be that RedHat is more diligent and open in acting on security flaws than its slower-moving competitor?

  277. Personal Experience by Anonymous Coward · · Score: 0

    From my own personal experience I've had numerious break ins on various Linux boxes, where the hacker had root (uid0) privledges. Thankfully they never did too much damage.

    I've never had a break in on my FreeBSD box, nor on my WinNT/2k boxes.

    You all seem to forget that the first Internet worm spread on UNIX boxes.

    Don't blame the OS for all of these security breaches, blame the langauge C/C++. Thanks for a shitty implementation of an array.

  278. Shiny Says Slashdot Better Than Trimethylxanthine by Shiny+Metal+S. · · Score: 1
    Nothing wakes me up better than seeing that someone Says Windows (More Secure|Faster|More Stable|Better) Than Linux.

    I don't need caffeine anymore!

    And when I see 734 comments I'm just in heaven!

    Thank you Slashdot! :)

    --

    ~shiny
    WILL HACK FOR $$$

  279. In other news... by Sean+Clifford · · Score: 1

    Evil is better than good, dark is brighter than light, less is more, and the Earth is flat. Fnord.

  280. What a sad world... by Anonymous Coward · · Score: 0

    I can't believe there are people that actually stand-up for microsoft garbase!

    Don't kid yourself - everything microsoft has done/will do is indeed garbage.

    That my friends, is a fact.

  281. Re:My problem with Linux is hd space by fferreres · · Score: 0

    Our Apache web server keeps on logging attempts to execure cmd.exe and files like that. We are logging about 100.000 records a day. We already counted like 7 GB of those logs...

    One time, our colocation provider asked us to monitor our system because someone on the subnet was abusing the link. They couldn't find the problem until i asked "are there any NT servers on the subnet?". 1 hour later apologies where in my mailbox :-) toghether with a huge discount.

    --
    unfinished: (adj.)
  282. Lots of misinformation going on around here. by jon_c · · Score: 3, Informative

    Lots of misinformation going on around here.

    It seems that the site(s) are back up, I've appended the meat of both in case they go down again. The good deal of the posts I'm reading stat the stats are invalid because it is an aggregate of all linux distros in comparison to windows 2k. This is not true, the stats make a clear distinction between distro's and count them separately, for example Redhat 7.2 had 28 exploits in 2001 where Win2k had 24.

    Which is what this article was attempted to exploit itself. Its very clear that the original article (as shown below) is a blatant attempted to drum of a flame war between linux and windows supporters. With a headline like 'Windows More Secure Than Linux? Yep!' it doesn't try to hide that fact either. The entire basis is of the article is a 4 "exploit" difference between Redhat linux and win2k within the last year. Of course the severity of these exploits are not detailed.
    Considering that windows has dramatically improved its numbers from the previous years I think a more accurate headline would have been "Windows security much improved from previous years"
    As many people has said far my eloquently them myself, these statistics do nothing to prove or disprove a superiority between linux and windows security, as there are so many problems with even trying to prove such a thing.
    -Jon

    below is the full text of the article and the stats from Security Focus.
    ------------------- WinInfo artical ------------------
    Thanks to David Byrne for this tip: For at least the first 8 months of 2001, open-source poster child Linux was far less secure than Windows, according to the reputable NTBugTraq, which is hosted by SecurityFocus, the leading provider of security information about the Internet. (The company's 2001 statistics are available only through August 2001 for the time being.) According to NTBugTraq, Windows 2000 Server had less than half as many security vulnerabilities as Linux during the reported period. When you break the numbers down by Linux distribution, Win2K had fewer vulnerabilities than RedHat Linux 7.0 or MandrakeSoft Mandrake Linux 7.2, and it tied with UNIX-leader Sun Microsystems Solaris 8.0 and 7.0. A look at the previous 5 years--for which the data is more complete--also shows that each year, Win2K and Windows NT had far fewer security vulnerabilities than Linux, despite the fact that Windows is deployed on a far wider basis than any version of Linux. So once again, folks, you have to ask yourselves: Is Windows really less secure than Linux? Or is this one of those incredible perception issues? For more information and the complete stats, visit the SecurityFocus Web site. I'll check back on this story to see how all of 2001 shapes up.

    -------------------SecurityFocus Stats -------------

    Number of OS Vulnerabilities by Year
    OS 1997 1998 1999 2000 2001
    AIX 21 38 10 15 6
    BSD/OS 7 5 4 1 3
    BeOS 0 0 0 5 1
    Caldera 4 3 14 28 27
    Connectiva 0 0 0 0 0
    Debian 3 2 31 55 28
    FreeBSD 5 2 17 36 17
    HP-UX 9 5 11 26 16
    IRIX 28 15 9 14 7
    MacOS 0 1 5 1 4
    MacOS X Server 0 0 1 0 0
    Mandrake 0 0 2 46 36
    NetBSD 2 4 10 20 9
    Netware 1 0 4 3 1
    OpenBSD 1 2 4 17 14
    RedHat 6 10 47 95 54
    SCO Unix 3 3 10 2 21
    Slackware 4 8 11 11 10
    Solaris 24 33 34 22 33
    SuSE 0 1 23 31 21
    TurboLinux 0 0 2 20 2
    Unixware 2 3 14 4 9
    Windows 3.1x/95/98 3 1 46 40 14
    Windows NT/2000 10 8 78 97 42

    Top Vulnerable Packages 2001
    Packages # Vulns
    MandrakeSoft Linux Mandrake 7.2 33
    RedHat Linux 7.0 28
    MandrakeSoft Linux Mandrake 7.1 27
    Debian Linux 2.2 26
    Sun Solaris 8.0 24
    Sun Solaris 7.0 24
    Microsoft Windows 2000 24
    MandrakeSoft Linux Mandrake 7.0 22
    SCO Open Server 5.0.6 21
    RedHat Linux 6.2 i386 20
    MandrakeSoft Linux Mandrake 6.1 20
    MandrakeSoft Linux Mandrake 6.0 20
    Wirex Immunix OS 7.0-Beta 19
    Sun Solaris 2.6 19
    RedHat Linux 6.2 sparc 18
    RedHat Linux 6.2 alpha 18
    Debian Linux 2.2 sparc 18
    Debian Linux 2.2 arm 18
    Debian Linux 2.2 alpha 18
    Debian Linux 2.2 68k 18

    Top Vulnerable Packages 2000
    Packages # Vulns
    Microsoft Windows NT 4.0 71
    RedHat Linux 6.2 i386 65
    RedHat Linux 6.2 sparc 53
    RedHat Linux 6.2 alpha 53
    Microsoft Windows 2000 52
    Debian Linux 2.2 48
    RedHat Linux 6.1 i386 47
    Microsoft Windows 98 40
    RedHat Linux 6.1 sparc 39
    RedHat Linux 6.1 alpha 39
    MandrakeSoft Linux Mandrake 7.0 37
    Microsoft Windows 95 35
    RedHat Linux 6.0 i386 33
    Microsoft IIS 4.0 29
    Microsoft BackOffice 4.5 29
    Microsoft BackOffice 4.0 29
    RedHat Linux 7.0 28
    MandrakeSoft Linux Mandrake 7.1 26
    RedHat Linux 6.0 alpha 25
    Conectiva Linux 5.1 25

    Top Vulnerable Packages 1999
    Packages # Vulns
    Microsoft Windows NT 4.0 75
    Microsoft Windows 98 44
    Microsoft Windows 95 40
    Microsoft Windows NT 4.0SP3 33
    Microsoft Windows NT 4.0SP1 32
    Microsoft Windows NT 4.0SP2 31
    Microsoft Windows NT 4.0SP4 30
    Microsoft Internet Explorer 5.0 for Windows 98 29
    Microsoft Internet Explorer 5.0 for Windows NT 4.0 28
    Microsoft Internet Explorer 5.0 for Windows 95 28
    Microsoft BackOffice 4.0 28
    Microsoft BackOffice 4.5 27
    Sun Solaris 7.0 26
    Microsoft IIS 4.0 25
    Microsoft Windows NT 4.0SP5 23
    RedHat Linux 5.2 i386 22
    Sun Solaris 7.0_x86 21
    Sun Solaris 2.6_x86 21
    Sun Solaris 2.6 21
    RedHat Linux 6.0 i386 21

    Top Vulnerable Packages 1998
    Packages # Vulns
    IBM AIX 4.3 36
    IBM AIX 4.2.1 29
    IBM AIX 4.2 29
    Sun Solaris 2.6 28
    Sun Solaris 2.6_x86 25
    IBM AIX 4.1 25
    IBM AIX 4.1.5 24
    IBM AIX 4.1.4 24
    IBM AIX 4.1.3 24
    IBM AIX 4.1.2 24
    IBM AIX 4.1.1 24
    Sun Solaris 2.5.1_x86 23
    Sun Solaris 2.5.1 23
    Sun Solaris 2.5_x86 22
    Sun Solaris 2.5 21
    Sun Solaris 2.4 18
    Sun Solaris 2.4_x86 17
    Sun Solaris 2.3 13
    Sun Solaris 2.5.1_ppc 10
    SGI IRIX 6.4 10

    Top Vulnerable Packages 1997
    Packages # Vulns
    SGI IRIX 6.2 25
    Sun Solaris 2.5.1 23
    Sun Solaris 2.5 23
    SGI IRIX 5.3 23
    Sun Solaris 2.5_x86 22
    Sun Solaris 2.5.1_x86 22
    Sun Solaris 2.4 22
    Sun Solaris 2.4_x86 21
    SGI IRIX 6.3 20
    IBM AIX 4.1 19
    Sun Solaris 2.3 18
    SGI IRIX 6.1 18
    IBM AIX 4.2 17
    SGI IRIX 5.2 15
    SGI IRIX 6.4 14
    IBM AIX 4.1.5 14
    IBM AIX 4.1.4 14
    IBM AIX 4.1.3 14
    IBM AIX 4.1.1 14
    Sun Solaris 2.5.1_ppc 13

    Privacy Statement
    Copyright © 1999-2001 SecurityFocus

    --
    this is my sig.
  283. Even Security Focus says: by Karza · · Score: 1

    "The numbers presented below should not be considered a metric by which an accurate comparison of the vulnerability of one operating system versus another can be made."

    To me, this just shows that you should always take into account WHO you get your information from as well as the information itself.

    --
    --I don't mind the school of hard knocks, it's those darned refresher courses I hate. =)
  284. Apples anyone, or how about some tasty Oranges? by TheFlu · · Score: 4, Informative
    How about some different numbers...everyone loves statistics. "The following numbers were obtained by counting web site defacements as listed at Attrition.org from June 2000 through May 2001:" Breakin Stats


    The trouble with comparing Linux distros to Windows lies in the fact that Linux distros include so many different applications. I just did a count of installed packages on a RedHat box I am using, and I got 780 installed packages. I'd like to see a comparison of the number of exploits between the RedHat distro and Windows installed with 700 of the most common applications for it. That might be a more useful comparison. Also, I will readily acknowledge the weakness and lack of true usefulness of the numbers below, so no need to flame me for the lack of usability...I'm only posting the info I found, so no need to stone the messenger.


    Windows
    4336 Windows NT
    1070 Windows 2000
    2 Windows 95
    5408 Windows total

    All UNIX and Like
    1185 Linux Red Hat
    999 Linux unknown distributions
    36 Linux Connectiva
    23 Linux Debian
    17 Linux Cobalt
    17 Linux SuSE
    13 Linux ALZZA
    12 Linux Mandrake
    1 Linux Slackware
    2304 Linux total

    485 Solaris & Sun OS (1)
    267 IRIX
    163 FreeBSD
    121 BSDI
    44 SCO
    28 Generic UNIX
    18 Compaq Tru64 UNIX
    9 AIX
    7 HPUX HP
    4 Digital UNIX DG
    3 OpenBSD
    2 NetBSD
    1 PowerBSD
    1 Digital OSF1
    1153 UNIX & Like total

    3457 UNIXs & Linux

    8865 Total Windows and all UNIX

    Other
    2 Mac OS
    1 Netware

    63 unidentified

    1. Re:Apples anyone, or how about some tasty Oranges? by MikeBabcock · · Score: 2

      Does anyone want to cross-reference those stats against their market saturation on netcraft?

      For example, if 50% of defaced sites are hosted on Windows but 70% of sites are hosted by Apache then Windows had more defacements than Apache (for example).

      --
      - Michael T. Babcock (Yes, I blog)
  285. Re:What?!? by cakoose · · Score: 1

    I agree with most of what you said, but while more people run Windows, there is probably more intelligent scrutiny on an Linux because people have access to the source code.

    Of course, it may be more valuable to developers to have more mindless bug reporters than fewer knowledgable ones.

  286. hrm but what is cheaper to license by unlocked · · Score: 1

    Bugs aren't fun. But which is cheaper to license and maintain. You paid good money for windows software and should be recieving a secure product.
    While linux is free with free bug fixs or you can fix the bug yourself. In the end it's just cheaper to run linux.

  287. how do you define linux? by Anonymous Coward · · Score: 0

    When i have read the title of the article,i wondered. Is windows more secure than the linux kernel? or maybe is it more secure than a specific distro. Or is it more secure than certain applications? you know it makes a whole lot difference when we know what we are talking about.

  288. Re:Here are some figures for 2002 - open your eyes by yomegaman · · Score: 1

    Would you still say that if it were the other way around? Or would it still be proof that "M$ suX0rz"?

    --
    ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
  289. Where's your heads? by ICMP_FRAGMENT · · Score: 2, Informative

    I have a few points to make.

    1: Linux is a kernel. Name the last security hole in the kernel.

    2: There are TONS of Linux distributions. Hundreds. There's also gobs of software includd in your standard Windows distribution. If you count ALL of their security vulnerabilities from ALL DISTRIBUTIONS and ALL SOFTWARE PACKAGES, I'm not surprised it's a bit higher than the number of holes in the *core Windows OS*.

    3: The rate of release of Linux is much faster.

    4: Linux distributors are still relying on the wrong software (sendmail/bind/inetd).

  290. Liars figure and figures lie by Anonymous Coward · · Score: 0

    It's like they say, "Liars figure and figures lie"

  291. Time to switch the fight to BSD. by Anonymous Coward · · Score: 0

    OpenBSD - Four years without a remote hole in the default install! Linux is nice but BSD is the future. Just ask Steve Jobs.

  292. Well, it's too early for April Fools'... by LunarQT · · Score: 1

    First of all, let's put this in perspective. Take a look at the top right corner of that site: "Windows Network & .NET Magazine".

    This spin is almost as amusing as the Redmond claim that "we're not coding anything new for a month so we can concentrate on 'security'". One whole month? Wow.

    SecurityFocus now warns that the data upon which these assumptions are based "should not be considered a metric by which an accurate comparison of the vulnerability of one operating system versus another can be made." Yet I don't see an update on the WinInformant site acknowledging this, disputing it, or ANYthing.

    If one actually READS the data, Windows came in at #1 for the year 2000, and Microsoft products grab 14 of the top 15 vulnerabilities for 1999.

  293. how many were fixed? by Anonymous Coward · · Score: 0

    Could it be that these vunerabilites were found from people looking a the code, and then emailing someone "hey theres an error", and then fixing it? I mean how many holes would there be in windows if we could see the code. Finally microsoft doens't admit theres a whole until someone finds, there not going to volenteer it like some writing a program

  294. But...statistics don't lie! by Emb · · Score: 1

    Mr. W and Mr. L each have a spouse and 3 kids.

    Mr. W has been moderately sick this past year, and had to make 3 trips to the doctor. He really had to go - his boss was going to fire him if he didn't do something about the grapefruit-size abscess festering on the back of his head and the odour from the gangrene in his left foot was getting unbearable. We suspect he has an undiagnosed brain tumour, but since nobody can smell that he hasn't had it checked out. His kids have had to make 3 trips to the doctor as well: 1 required an MRI, one has cystic fibrosis, and one of the poor dears needs a liver transplant. His wife Explora has been very ill and had to make emergency trips to the hospital 7 times.

    Mr. L and his family each made two trips to the doctor. The whole family got the flu, plus they each had their yearly checkup.

    STATISTICS SAY:

    Q: Mr. W, how many trips to the doctor have you had this year?

    A: 3 trips.

    Q: Mr. L, how many trips to the doctor have you had this year?

    A: 10 trips, but that includes my family.

    CONCLUSION:

    (drumroll please)

    Mr. W is healthier than Mr. L.
    Let's give him health insurance.

  295. Comment on Article with Caution! by marktwain · · Score: 2, Interesting

    I happened to be using a Mac running OS X and Classic (OS9).

    I wanted to comment on the article (I still think it's some sort of joke) and use of I.E. (X), Mozilla (X), iCab (X), WannaBe (9), Mozilla (9), and iCab (9) all crashed on the "add comment link."

    Well, at least it was a good exercise in net-non-compatibility and the non-coder who wrote the html for that pop up window you get clearly knows what he's doing.....coding html exclusively for a Windoze world.

  296. Put up or shut up, toadies. by jthill · · Score: 1
    If Linux had the marketshare of Windows, you can bet there would be lots and lots of scriptkiddies writing Code-Red style worms.
    Unh huh. So, IBM puts it on their mainframes and sells it into big telecomms shops, MS is waging an all-out toady war against it, and ... there still hasn't been an exploit to compare with any of the headliner MSTDs.

    It's time for MS and their thralls to put up or shut up, and stop trying to bullshit their way out of Code Red and SirCam and their hordes of incestuous cousins. Have them demo one security hole as kick-me-i'm stupid as the holes those exploited, by writing their own.

    --
    As always, all IMO. Insert "I think" everywhere grammatically possible.
  297. troll by agentk · · Score: 1

    I moderate this story -1, Troll.

    --

    VOS/Interreality project: www.interreality.org

  298. Some /.ers are starting to get it... by /Idiot\ · · Score: 1

    but mod this up because some people still, sadly miss the point :-(

    An OS is hardly "secure" or "insecure".

    To illustrate my point, lets just imagine that the default install of my Win2K server is more "secure" than the default install of my debian box.

    Neither of them are connected straight to DSL!

    Your whole environment (firewall, router, switch, servers etc) can be secure or unsecure, that's true, but one componant can't rate the whole environment.

    "I'm better than you because my Win2k box is tighter than your debian box" won't cut it here either, for the simple fact that you just can't get to my debian box so it dosen't matter if it has a hole that you can throw a cat through (which it dosen't)

    So if we believe that stats, it could read more things than OS security anyway because it's about which holes are known (M$FT dosen't always feel the same open-ness as the rest on this topic, remember)

    Anyway, don't let me get in the way of the flames :-)

    --
    /dev/Idiot/
  299. what about the time to fix by SlvrClk · · Score: 1

    how about the fact that there are people all around the world who find the bugs in linux, and make fixes for them. Ive found that bug in linux is fixed almost right away as opposed to waiting for microsoft to decide that there is a security hole, hold a meeting about it, prepare statements for the world about it, fix it, then release a patch.

  300. Conspiracy! by ralian · · Score: 1

    Possible scenario
    ------------------
    Problem: We have a large group of linux users, we need them to use windows, or at least stop developing linux and making other people not use windows.

    Solution: We use a manufactured and obviously inflammatory story, posted to a shrine of the linux-worshippers, to cause the (generally) obese linux crowd's blood pressure to blow. Problem Solved!

    :)

    --

    -raph

  301. Excellent post! by Futurepower(tm) · · Score: 2


    Excellent. Mod parent up.

    --
    Bush's education improvements were
  302. Observations by sbakker · · Score: 1

    Has any one else noticed that winformant.com is running Linux? Apparently they don't think it is all that unsecure. The site winformant.com is running Apache/1.3.3 Cobalt (Unix) (Red Hat/Linux) on Linux. I also like the notice on securityfocus.com in BOLD type. The numbers presented below should not be considered a metric by which an accurate comparison of the vulnerability of one operating system versus another can be made.

  303. February 2 by Anonymous Coward · · Score: 0

    26 days to go. We are now finding out what Bill means when he said that February will be focussed on security.

    Derek

  304. interpreting the numbers. by Anonymous Coward · · Score: 0

    Linux has more reported security problems because there is a community working to uncover problems in order to get them corrected. While Microsoft, on the other hand, gets mad if people make bugs/vunerabilites known to the public and tries to prevent it (I have heard that they want it to be illegal to spread info on security vunerabilites, although I don't see how this wouldn't violate the 1st ammendment).

    The real difference in the statistics is that they just don't deal with their software in the same way.

  305. Does this take all into account? by Tyreth · · Score: 1

    They say that it talks about all distributions. Distrubution security flaws then would not be related to linux itself but the applications that each distribution includes.

    This has a couple of problems then:
    1. Wininformant would then include all sendmail, etc, security holes as linux bugs. I don't think that they would include extra Microsoft products that a user may/may not choose to install - they are probably talking about the machine after installation. As such, IIS, Sendmail, Outlook, etc, on a windows installation would not be counted towards the number of bugs.
    2. The increased number of security holes reported for linux may actually not be representative of the number of holes present, but instead be a measurement of the amount of exposure that linux receives, therefore eliminating more bugs. Following this logic you could conclude that linux was more secure for that 8 months. Of course, you could probably never measure this, making it pure hypotheses.

  306. Re:Here are some figures for 2002 - open your eyes by Mr+Z · · Score: 1

    If Microsoft weren't actively advocating non-disclosure of vulnerabilities, then sure -- I'd say it the other way around as well. The point is, RedHat seems eager to fix and disclose their own vulnerabilities (to the point of accidentally jumping the gun), and Microsoft seems eager to squelch discussion on theirs.

    Given their stances, who would you trust to release advisories in a timely manner?

    --Joe
  307. obviously bogus by markj02 · · Score: 2
    Comparing that kind of data to assess security is obviously bogus: the set of packages being considered is different, vulnerabilities are discovered differently (NT doesn't come with sources), and the user communities are different.

    Both Linux and NT have plenty of security holes to go around. But Linux is also clearly far preferable from a security point of view: it is much easier to run only the software/servers you actually need on Linux, it comes with full sources, and serious security holes are fixed usually within hours of being reported.

    Claims like those on WinFormant mainly demonstrate the incompetence and inexperience of their authors.

  308. A virus a day! by Anonymous Coward · · Score: 0

    Boy oh boy, and Aids didn't happen from sleeping around with monkeys. What next? Bill Gates gives away millions. The idiot troll that posted this and the idiot troll editor that accepted it --
    do you know how many MS-is-better-than-Linux articles I can find in a day? If I wanted to read
    this crap I'd go on google and search for it.
    If you can't keep /. focused on
    stealing someone else's "decent" stories instead of the fermented hogwash that you post just close shop and go try to understand Zorn's lemma again! For the 3350th time!

  309. Re:More interesting Blah blah by Rooktoven · · Score: 1

    What was contained in each bulletin, how was it resolved? Numerical titles sans text is pointless.

    Enronian (en-RAHN-ee-an) adj.
    1 : Presenting misleading numbers for purposes of aggrandizement.
    ex.: The microserf resorted to an Enronian argument to back up his false implications.

    --

    Acquiescence leads to obliteration
  310. default redhat 6.2 plenty secure by vipw · · Score: 1

    a redhat 6.2 install is plenty secure if you use the right tools. http://victim.cylant.com
    yeah, i work there.

  311. Must be that 'New Math' by DarkProphet · · Score: 1

    Like the electorial college uses.. heh. Or claiming that a processor with a higher clock speed means it can process faster. Blah.

    So am I to understand that WinXX has had less reported vulnerabilities over the last 5 years? I believe that. MS believes in security thru obscurity, and god only knows how many hidden security flaws there are in say, Win9x that have never even been discovered.

    However, that doesn't mean they won't be. Anyone who's got a clue (the meager minority, I'm afraid) seem to understand that reporting and fixing bugs is kinda how open-source works. I'd be MUCH more concerned if Linux (distros)_didn't_ have more reported security problems, for an unreported security flaw is the one that goes unfixed. Microsoft can probably tell you all about it.

    --
    What could possibly hurt the security of the American people more than giving our own government the ability to hide its
  312. Some Additional Info for the WinInformant by WildThing · · Score: 1

    Just what was that 'Site Migration' Mentioned on the Security Focus page?
    - Security Focus migrated TOLinux!

    I wonder why?!?

  313. Re:What?!? by fuess · · Score: 1

    While the citing of the many viruses to which Windows alone is vulnerable may not be sufficient. As a programming and computer security professional I can state with confidence that Microsoft's corporate position on security has indeed contributed to a less secure product. Further, the underlying system design (complete reliance on DLL's that any SW provider can replace) has been, and continues to be basically unsecure. I am not an MS basher, but one must be a realist when it comes to computer security. Hopefully MS new security first development strategy will eventually yield a secure MS product.

  314. Re:More interesting Blah blah by sheldon · · Score: 2

    The numerical titles are merely references to the bulletins posted at www.redhat.com. There ye shall find the text and become enlightened.

    I checked my dictionary and there is no such word as enronian. The only reference I could find to it on the web was in discussing President Bush's deficit spending package.

  315. My experience matched that :-( by billstewart · · Score: 3, Interesting
    I had a DSL line in my lab, and several machines on it, including out-of-the-box Redhat 6.2 and somewhat-modified Win95 or Win98 (running an out-of-date virus scanner, but not running a MS mail client). Nobody appears to have bothered the Windoze machine, probably because there's not much useful you can do with it. Meanwhile, I named the Linux box "Kenny" because every week it was killed brutally and senselessly :-) Some weeks it was just installing DDOS clients, but at one point they wiped the machine after I'd thrown them off a couple of times in a row.


    Later I upgraded Kenny to a recent Redhat release, either 7.1 or maybe 7.2, running in a medium-security configuration. I didn't notice any problems after that - whatever the popular security holes were had been patched or they were in services I hadn't turned on. I had some other serious problems with those distributions - basically they're not made to be installed on small machines unless you do one big partition or a lot of hand-tuning, and you can't netinstall from a single CDROM drive any more, so you'd better have at least one machine with a lot of disk space. But the security was much improved.


    By the way, a couple of the intrusion detection techniques I used were:

    • Keep a machine on the lan running tcpdump and look at it occasionally. That's how I noticed all the ping-responses to a university in Sweden during the first DDOS round.
    • Don't trust ls or ps to tell you about all of your files or processes. Crackers with rootkits will install friendly replacements - but somehow they didn't think to change /proc, so there were processes that /proc showed that weren't in ps, and there were files that "find" found that ls didn't list. I don't remember if they replaced "top", but the hidden processes were using some hidden files as well as CPU time.
    • If a given network or tcp/udp port keeps bothering you, it's easy to set a router to filter it out.
    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  316. I agree by Anonymous Coward · · Score: 0

    % wide I would bet that linux has more systems unpatched that MS does. Face it the patching of linux in general is horrible. I want patches not. hmm bug in cvs...better go upgrade cvs, yeah right...no I want a patch...add patch...done. And I want it tested.

    Besides most of the linux software that comes out is crap for the first couple years. Far less that want MS puts out the first run. Lets see it took Sendmail 10 years to be developed so it worked without major flaws...It took MS 3 years to get exchange perfected, and now exchange can handle and do more that sendmail does.

    mysql, its nice but small and it still has bugs...sql server first run was bad but from then on it screams.

    Come on folks get off your high horse, linux is a nice toy and a niche here and there, but it has a LOT!!!! farther to go that MS does.

  317. Approriate Mark Twain quote. by Rhinobird · · Score: 1


    t this thread needs is an appropriate Mark Twain quote:


    There are lies, damned lies and statistics.

    --
    If Mr. Edison had thought smarter he wouldn't sweat as much. --Nikola Tesla
  318. Wrong (Re:These numbers aren't really relevant) by Anonymous Coward · · Score: 0

    The numbers are relevant. They are simply completely misinterpreted by WinDesInformant.

    The compare accumulated bugs of all Linux Distributions to those of NT/2000 or 3.1/95/98

    even Redhat, with the largest number of reported bugs of all compared Linux distributions, breaks even with NT/2000.

    But that's not all. SecurityFocus themselves admit that application related bugs are likely to be left out of the count of Windows bugs but not of the Linux bugs count.

  319. The conclusion ignores the *severity* of the bug by DunbarTheInept · · Score: 2

    Have you ever *seen* these lists of bugs found in Linux and published publicy? While the occasional real bad humdinger is found, most are of the form, "I read the source and found out that someone could in theory do such-and-such, but I don't know if anyone has actually done this yet."

    In linux, the white-hat hackers and the black-hat hackers operate on equal footing with regards to
    access to the information. That's the key difference.

    --

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

  320. Crying with your hat on by Anonymous Coward · · Score: 0

    It's a Flemish expression wich means something like not knowing if you should cry or laugh.

    Face it, this article is the ultimate proof most Windows related magazines and websites are full of bogus information.

    1. They are pointing to a website (securityfocus) wich itself claims the figures are highly disputable and incomplete.

    2. WHO! in his right mind would consider using UNreliable data to make a statement as such.

    3. I cannot believe they are adding up every distro to point out Linux is less secure ! It's like counting all versions of windows to accumulate a number illustrating it's robustness.

    4. Really not very long ago (day or two) Microsoft released a 17MB patch with security updates for Windows 2000.

    I'd start a flamewar on that website if i could but their servers don't seem to able to keep up with the load for now.

  321. Plug a computer into the network... by Alex+Belits · · Score: 2

    ...run an HTTP server on it. Don't tell anyone that it's there. What will you see?

    In my case it was few hundreds of Code Red requests from few tens of hosts per day.

    --
    Contrary to the popular belief, there indeed is no God.
  322. Apples vs Oranges by RichLooker · · Score: 1

    The tally of Linux security issues, in addition to remotely exploitable ones, includes each and every buffer overflow bug which could allow a non-privileged local user to get root access, even ones not known to have been exploited. For Windows, the number indicates only remotely exploitable security holes, and only the ones publicly known. Ever seen Microsoft admit there is a scurity problem before it has been heavily exploited ?

    --
    "And you are dying so slowly, you believe to be living" - Bertrand Besigye
  323. Re:Exactly (it deserves to be rediculed and ignore by Anonymous Coward · · Score: 0
    Sadly, we have very little editorial control over other people's websites.

    Sadly? Well, pull out that bug list. I'm sure you could have plenty of control over other people's web sites :^)

  324. and the earth is flat ! by Anonymous Coward · · Score: 0

    bwaahahahahahaha !!!

  325. Quantify the exploitation. by yehti · · Score: 1

    Another question that should be addressed, but can't be quantified, is how many times an individual bug has been exploited to compromise the security of a system.



    The summation of the time a bug was exploitable, as well as the quantified exploitation would be revealing figures (heh heh...figuratively).



    For each OS, the exploitation figures would have to be divided by the number of machines running the OS.

    --
    If you patch a mess, you get a patched mess.
  326. Quantity vs Quality by Stonan · · Score: 0

    What do the numbers really represent?

    From what little I know of Linux (I will be going over after 20+ years with Microsoft) it's rather hard to break security or get a virus to do anything. I understand it depends on the 'state' of Linux at the time (who's logged in, etc).

    I would rather run Linux with more security holes than Windows if those holes are hard to find and even harder to exploit.

    'A charging bull will fly thru an open door but won't get very far going thru a cheese grater.'

    --
    The GEEK shall inherit the earth...
  327. How cheesy by Anonymous Coward · · Score: 0

    Administrative Contact, Billing Contact:
    Hostmaster (HO7948-ORG) billgates@microsoft.com
    Penton Media, Inc.
    1300 E. 9th St.
    Cleveland, OH 44114-1503
    USA
    (216) 931-9350
    Fax- (216) 931-9149

    vi /etc/hosts
    i
    www.wininformant.com 127.0.0.1
    ^:wq

  328. Zealotry by underpaidISPtech · · Score: 3, Insightful

    Just to cut throught the FUD on both sides here:

    Paul: Fuck You. You don't know shit. How's the page views today? That's what I thought.

    CmdTaco: Stop feeding the trolls. This guy just made $x money because you decided to link to his crappy site. Now everyone is here literally frothing at the mouth. If this was real life someone would've been stoned to death by now or branded a witch. Is /. a tabloid now?

    Everyone:
    Lies and statistics. August 2001 huh? So the stats were last compiled just after Code Red, but not since Code Red II, not since the UPnP fiasco, not since the most secure Windows OS ever? Nice to see "journalists" grouping distros together on the basis of which *kernel* they use. If you want to assess the security of *linux* then only focus on expoits that compromise the kernel. If it's just another BIND or wuFTP vulnerability, count it just once for "OSes that use that GPL'd kernel*" *note: packages included with each distro are not uniform across platforms. Not all Linux distros are alike.

    But that is rational and fair, and we can't have that can we? No. We need to increase page views and banner hits, we need to convince so-and-so in management that *OS-not-right-for-the-job* is the right tool for the job.

    Windows on the desktop and *nix in the server room; the Buddha smiled and farted. And God said "It is Good".

    1. Re:Zealotry by quey · · Score: 1

      Let's not forget that in an open source OS and open source software in general have open source bugs and vulnerabilities.

      It's not *that* easy to find these flaws in a hidden source OS. Even though, these bugs are in deed found in Windows OS's and they are a *lot* more problematic than the (mostly) minor security problems in Linux and other open source systems.

      We can always wait (sometimes forever) for a stupid 'patch' from Microsoft to solve _half_ the problem. In the meantime let's waste time and money. Or change to open source. Hard choice, isn't it?

  329. Windows vs Nintendo by Anonymous Coward · · Score: 0

    I would say the same about windows and its many variants and device drivers and service packs. If I buy an application for Windows there is a chance it may work, or it may not (for instance my sound sequencer Cubasis VST does not like Windows XP). If I buy a game for the Gameboy Advance, plug it into the machine and turn the machine on, it works. (Of course you may say I cheated by choosing the GBA because other consoles have horrible regional coding schemes :-)

  330. Waste of time? by Futurepower(tm) · · Score: 2


    If you have just begun reading this discussion, maybe you shouldn't waste your time. Basically, the original article is a troll, or a paid MS public relations stunt, and Slashdot fell for it.

    If you must read this discussion, just browse at +5.

    --
    Bush's education improvements were
    1. Re:Waste of time? by LinSux · · Score: 1, Interesting

      Why would I want to do that? If I read it at +5 then it will almost completely be pro-linux.

      This is a good article. It's controversial, only because it goes against the grain of the normal /. mentality. And that's a good thing!

      What you're asking me to do is against my viewpoint. I'd prefer to read every discussion raw and uncut, and make my decision based on what I see. Not what the /. editors want me to see.

      But, that's just me.

      (Trying to stay outta trouble. Hand slaps hurt, folks.)

      --
      Slashdot. News for Zealots, Stuff that matters (if you're a linux zealot!)
  331. Re:Why page widening is evil by jeff_bond · · Score: 1

    Offtopic I know, but:

    If the friend/foe system worked as I think it

    should, then I could still browse at -1 but

    have all my foes disappear because I've given them a -6 bias.

    Why doesn't it work like this?

    Jeff

    --
    stty erase ^H
  332. Has anybody read the article? by Anonymous Coward · · Score: 1, Interesting

    According to the beginning Bugtrack statements, the WinInfo article is completely backwards. I quote:

    There is a distinct difference in the way that vulnerabilities are counted for Microsoft Windows and other operating systems. For instance, applications for Linux and BSD are often grouped in as subcomponents with the operating systems that they are shipped with. For Windows, applications and subcomponents such as Explorer often have their own packages that are considered vulnerable or not vulnerable outside of Windows and therefore may not be included in the count. This may skew numbers.

    This means that all of the Outlook and Internet Explorer vunerabilities are not included in the Win 2000 numbers, but appearently, any Sendmail, Apache, or Modzilla numbers are included with Linux.

    Unless I am reading this wrong, the article is not comparing apples to apples, and shows that there are about as many bugs in the Win 2000 kernel as there are in all of Linuxdom!

  333. Simply put, this is smoke by SgtChaireBourne · · Score: 1
    (To nit pick, the WinInformant links to a written sound bite not an article.)

    MS really only cares about the bottom line and obviously security issues are about to bite them financially. Right now, Bill can't do much except blow smoke. The distraction is really needed right now. Especially when you consider:

    That the effort to squelch bug reporting is a tacit admission that none of the products in the current development cycle are likely to be secure

    Prestigious and influential groups like the National Academy of Sciences are calling for punishment of software firms that skimp on security.

    MS products will be magically secure and stable after February.

    They've been found guilty of illegally maintaining a monopoly and the punishment is under discussion.

    Several U.S. states and some European governments and commissions are pursuing / considering their own legal action.

    The MS legal counsel is stepping down

    MS-Passport, their new cash cow, can't even be made secure (thus their hop to Kerberos)

    Revenue from upgrades is nil and given that Intel is not expecting to do well either the next few quarters will be for MS also.

    Simply put, Bill is on so many people's shit list with no easy way off. A few decades ago, IBM used to have most computing centers by the short-n-curlies, but pushed it too far and more or less disappeared. MS is in a prime position to do the same.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  334. windows isn't secure by Anonymous Coward · · Score: 0

    Security is relative, Windows just like any other operating system can be made to be fairly secure, however I have to disagree with your comments in your article about it being impossible for Linux to be more secure than Windows. Windows as an operating system is flawed when it comes to security. Sure Windows eventually added slightly better filesystem security, but Microsoft have always made security an after thought to features. The reason your article received a knee-jerk reaction from the slashdot crowd is that you are comparing apples to oranges. If you look at the majority of Windows related security problems, they have not been blown out of proportion because Windows is used more, they are fairly serious security issues that effect the operating system itself (eg. stuff you cannot NOT install). On the other hand, if you look at the security problems that are logged under Linux, they are for applications and tools that distribution companies add into the distribution. Comparing most of the security problems in Linux distributions would be like adding up all the application problems that might get installed on Windows. If you did that, there would be hundreds if not thousands of security problems under Windows, but half of them wouldn't be an issue because not everyone has or installed that application. So to do a fair comparision, you would need to compare OS level problems, so you would compare security problems with the Linux kernel itself, core libraries such as glibc, and components needed for networking. I think if you did that you'd see that Windows has far too many security problems.

    On this continued stance about Windows having more users, sure it does, why? Well it helps if your operating system is sold on the majority of PC and servers that have been sold in the past 10+ years, however, look at the expense one has to go to to "make" windows secure. You need to purchase firewall software (yes lets be realistic here, XP firewalling doesn't cut it), thats about $4k+ for Checkpoint FW-1, you need anti-virus software to make sure your server doesn't get trashed, thats at least $50+, depending on your choice, then you have licensing fees, but here is the thing that I don't understand, all of that stuff eats up system resources. You have the GUI eating resources, you have the AV software eating resources, you have the firewall software eating resources, you'll probably have something like PC anywhere to remote control the server eating resources. Why do people think this is a viable server system? Take Linux or BSD, or even solaris, you can install debian down to take up about 50MB of disk space, have your firewall protection, and slim down the kernel since you have the source code, eliminating support for stuff you don't need. If its done properly you can get hundreds of more users on a server, whether its pop3/smtp users, more web traffic, etc.

    Windows just doesn't make business sense, it costs more money, its less secure, its less scalable and it provides less capacity than something thats well, free. The only thing that is keeping Windows in places is IT managers who aren't smart enough (or don't have the time) to learn linux, who have the trust of the executives of companies. Windows is there because the people who should be experts, aren't experts, sooner or later, that is going to catch up to the Windows folks, and when business people see that they are paying $200k a year for someone who has been making very poor IT decisions, lets just say, there might be a couple more MCSEs working in fast food industry :)

  335. [OT] To the moderators by opkool · · Score: 2

    What is the problem with the moderators?

    When I posted my comment there was no comments at all on this story. You know, it takes time to write a message longer than 2 lines, preview, correct and send ... specialy if your first language it is not English.

    And, then, I see no other previous post with the same ideas. Maybe there are some in the answers to previous comments, but sended way after mine.

    What's all this "redundant" thing?

    Please, check the timestamp of the comment before being ridiculous.

  336. Re:Exactly (it deserves to be rediculed and ignore by FreeUser · · Score: 2

    We didn't write the article in question, nor are we hosting, nor did we have any opportunity to see it ahead of time. (Or now... still can't see it.)

    I'm curious why you would like to an article without reviewing it. If this is to be believed, you linked to an article without even reading it. While I expect that sort of looseness with slashdot to some degree, I confess I'd always held Security Focus in a little higher regard, and consiquently expected more selectivity in what articles they choose to headline and link to.

    Unfortunately this thread is already ancient history and probably no longer being followed, but if you see this I would very much like some clarification on exactly how articles like this are selected for inclusion in SecurityFocus' headlines. Following the /. link did make it look like your article to the casual glance (though the /. effect did preclude many of the banners, etc. from ever loading, and a more precise look at the URL does reveal it to be hosted elsewhere).

    --
    The Future of Human Evolution: Autonomy
  337. Not Bad! by 4of12 · · Score: 2

    With that many vulnerabilities and that much press, I would say that Linux has arrived! (All the *BSD folks are green with envy and wish they had such attention)

    You could say that old distros and less experienced sysadmins are facing a hacker culture that probably is more adept with open source tools than they are shooting bullets into Windows and IIS for BO's.

    So, then, how much monetary loss is attributed to Windows insecurities vs Linux insecurities, eh?

    --
    "Provided by the management for your protection."
  338. Microsoft public relations employee by Futurepower(tm) · · Score: 2


    Another Microsoft public relations employee. Look at the name: LinSux.

    --
    Bush's education improvements were
    1. Re:Microsoft public relations employee by LinSux · · Score: 1, Insightful

      Another closed-minded Linux Zealot. The kind I bitch about all the time.

      Pull your head out of your ass, Moron. Linux is just a play-toy. If they actually made a halfway decent and usable desktop OS it'd actually be a worthy competitor. MS has no real competition. It's a monopoly by choice. And if you could see more than 2 inches in front of your own pimply face, you'd see that.

      Read the sig. Friggin moron!

      --
      Slashdot. News for Zealots, Stuff that matters (if you're a linux zealot!)
    2. Re:Microsoft public relations employee by LinSux · · Score: 0

      Oh, yeh, BTW... I have news, I'm in no way shape or form associated with MS. I just happen to think Linux and its following of zealots sucks.

      --
      Slashdot. News for Zealots, Stuff that matters (if you're a linux zealot!)
  339. Re:Exactly (it deserves to be rediculed and ignore by ryanr · · Score: 2

    I'm curious why you would like to an article without reviewing it. If this is to be believed, you linked to an article without even reading it. While I expect that sort of looseness with slashdot to some degree, I confess I'd always held Security Focus in a little higher regard, and consiquently expected more selectivity in what articles they choose to headline and link to.

    What makes you think that we linked to it? We didn't, they linked to us. We run a little stats page because people were asking us for the numbers all the time. These other people wrote a short blurb and claimed, based on their misunderstanding of the numbers, that SecurityFocus was claiming that Windows was more secure than Linux. We make no such claim, that's their conclusion.

    The article in question was not linked to by us, was not in our headlines, was not endorsed by us, wasn't even known to us until the Slashdot story.

  340. sometimes u have to laugh by Anonymous Coward · · Score: 0

    "WinInformant" lol! what an ironical name

  341. Re:And meanwhile, in the real world... by Anonymous Coward · · Score: 0

    I disagree about that 99%. There are bad programmers everywhere! not just in open source, i am sure ms has thier share of bad programmers as well. I have worked at many companies, and have seen my share of bad programmers on company payrolls. Just because they get a paycheck does not make them better programmers. In fact, in my experiences, people who code for the love coding (of which i am one, and so are many other oss developers) tend to take better care of their code than those who only code for the love of money. I certainly cannot speak for other oss programmers, i only know my own motivations, but i develop software for the love of programming, and when i undertake a project, my goal is to make the best program i can. None of my programs have ever had serious flaws, because i took the time to test them thouroughly before letting anybody else having them. I am not saying there were no bugs, but there were none that caused a serious impediment to the use of the program. Certainly they never crashed! Just like me, i am sure there are many other oss developers who also care about their work, just as sure that there are some who do not. And that goes for programmers on company payrolls as well, the good and bad are there too! In the case of MS products that have been bad (in my opinion, due to crashes) i am sure is not totally fault of the programmers, but marketing who insists on shipping products when they are not ready. MS seems to me to be far more interested in takeing as much money as they can from their customers at every opportunity rather than serious stabalize their code. This is not just a problem with MS, but nearly every large software company! or even OSS projects. The need to be constantly rushing to market is the problem that needs to be dealt with. not the methodology of how software is produced (whether open or closed source).

  342. You are Right, I was wrong by FreeUser · · Score: 2

    The article in question was not linked to by us, was not in our headlines, was not endorsed by us, wasn't even known to us until the Slashdot story.

    I went back and looked at the article more thoroughly (now that it isn't slashdotted, and the grafics, etc. come up, ie. it is no longer filled with blank spaces). Amazing how much more obvious these relationships become once you can see the whole thing without 10 minute lags (and once someone has pounded you over the head with a clue stick).

    You are absolutely right, I was absolutey mistaken, and my comments misaimed. My sincere apologies. The diatribe to which you replied should have been directed at WinInformant, not Security Focus which, as you clearly point out, remained above reproach in this fiasco. Sorry about that ... I'm usually better at attributions, and I shouldn't have gotten that one wrong.

    Thanks for your reply, and pointing out what should have been obvious (but apparently wasn't, to me at least, on that day).

    --
    The Future of Human Evolution: Autonomy