Slashdot Mirror


The Annual US-CERT FUD Festival

Joe Barr writes "Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux. Pamela Jones did a similar report at Groklaw over the weekend." From the article: "One figure represents the vulnerabilities found in Windows operating systems: XP, NT, 98, and so on. The other represents a total figure not just for Solaris, AIX, HP-UX, the BSDs, and Linux, but for a hundred different versions of Linux. The sum of all the unique vulnerabilities from all the Linux distros does not equate to the sum of vulnerabilities in any single Linux distro, and one could say the same about the various versions of Windows. That's why it is a completely meaningless exercise to discuss those totals as if they present an accurate picture of the relative security of Windows and Linux. " We've reported on the US-CERT list already this year. NewsForge is a sister site to Slashdot.org, both of whom are owned by OSTG.

152 comments

  1. Windows by the+computer+guy+nex · · Score: 0, Troll

    Every time you download a new security update for Windows you should consider that a new "version" if each Linux Distro is considered a version.

  2. Well.. by Sheetrock · · Score: 1, Insightful
    The sum of all the unique vulnerabilities from all the Linux distros does not equate to the sum of vulnerabilities in any single Linux distro

    No, but it sounds like they're adding the vulnerabilities to represent Linux. Much as they're adding the unique Windows vulnerabilities to represent Windows.

    --

    Try not. Do or do not, there is no try.
    -- Dr. Spock, stardate 2822-3.




    1. Re:Well.. by theonlyholle · · Score: 3, Insightful

      But that's not the same - we're talking about basically one Windows product with its associated unique vulnerabilities, but when we talk about Linux distros, we talk about several different ones that have the *same* vulnerability counted multiple times because it exists in multiple distros. Just one look at the CERT list and you will see all the duplicates in there. And then of course, even if you remove the duplicates, you are still left with vulnerabilities that were only present in one distribution, but got counted against "Linux/Unix" although 99% of the distros were never affected.

    2. Re:Well.. by rubycodez · · Score: 2, Informative

      heh, "several" Linux distros, there's over 90 of them!

    3. Re:Well.. by Audacious · · Score: 1

      US-CERT on the fishing industries:

      CERT: You have 62,000,000 fish caught last year.
      Fishermen: No we don't. We have so many sardines, tuna, flounder, and what not.
      CERT: They are all fish aren't they?
      Fishermen: Yeah....
      CERT: So you have 62,000,000 fish caught last year.

      --
      Someone put a black hole in my pocket and now I'm broke. :-)
    4. Re:Well.. by Thuktun · · Score: 1

      From TFA: Microsoft wants you to read the headlines as "Windows 3X safer than Linux."

      Did anyone else read that as "Windows 3.X safer than Linux"? I immediately thought, "Yeah, that's probably right; it doesn't DO anything..."

    5. Re:Well.. by Anonymous Coward · · Score: 0

      Umm, I looked at the list and they weren't counting the same vulnerability multiple times. They had one entry for each vulnerability which listed each affected operating system, but it was still counted as one vulnerability. The list was inflated somewhat because they didn't filter out the update entries, but that applies to both the Windows and *nix lists.

    6. Re:Well.. by LnxAddct · · Score: 1

      You might be interested in this post of mine from the other day.
      Regards,
      Steve

    7. Re:Well.. by Anonymous Coward · · Score: 0

      Huh? Windows is not monolithic. Windows 95, Windows 98, Windows 98se, Windows ME (shudder), Windows NT 3.51, Windows NT 4.0, Windows 2000, Windows XP Home, Windows XP Pro, Windows 2000 Server, Windows 2003 Server, Windows MCE, Windows 2005 MCE ... please try to look past your personal biases a bit. I love how WHENEVER anything is written favorably about Windows relative to *nix it's FUD ...

    8. Re:Well.. by Anonymous Coward · · Score: 0

      That is so damn insigthful I peed myself.

    9. Re:Well.. by sorak · · Score: 1

      But that's not the same - we're talking about basically one Windows product with its associated unique vulnerabilities, but when we talk about Linux distros, we talk about several different ones that have the *same* vulnerability counted multiple times because it exists in multiple distros. Just one look at the CERT list and you will see all the duplicates in there. And then of course, even if you remove the dupli0cates, you are still left with vulnerabilities that were only present in one distribution, but got counted against "Linux/Unix" although 99% of the distros were never affected.

      It would be much more effective if they would either take representative systems and count the bugs. For example, they might come up with common functionality such as "web server" "database" or "remote file server" and count the number of vulnerabilities in (using "web server" as an example)

      • Windows 2003 Server with IIS
      • Red Hat with apache (included for its popularity)
      • NET BSD with apache (included because it is security themed)
      • One of the more popular commercial UNIX systems, such as AIX (chosen because it is a high-end commercial system, that is __EXPECTED__, in some circles, to be better than windows or linux)
  3. Downright Disingenuous by TripMaster+Monkey · · Score: 3, Informative

    The act of contrasting the vulnerabilities found in the few Windows operating systems with the vulnerabilities found in hundreds of Linux/Unix is bad enough, but when you consider that the Unix/Linux list contains duplicate items, it becomes positively shameful.

    From the Groklaw article:
    Second, the Unix/Linux list duplicates items, counting a vulnerability more than once in the list. For an example, note that it lists Eric Raymond Fetchmail POP3 Client Buffer Overflow (Updated). However, the same vulnerability is listed, under the same title, four times. That's because it was reported in the week of August 10-15, again in the week of August 17-23, in September 6-13, and the week of November 9-16. Worse, for any comparison purposes, the same vulnerability is also reported as Fetchmail POP3 Client Buffer Overflow, so in reality one vulnerability is listed 5 times, making the total of 2328 meaningless unless you carefully comb through it to weed out duplications.


    I honestly expected better from the CERT folks. I don't know why, but I really did.
    --
    ____

    ~ |rip/\/\aster /\/\onkey

    1. Re:Downright Disingenuous by greg_barton · · Score: 2, Interesting

      I honestly expected better from the CERT folks. I don't know why, but I really did.

      Coming from the same government that denuded a slam dunk settled lawsuit against Microsoft? PuhLEASE!

    2. Re:Downright Disingenuous by User+956 · · Score: 4, Informative

      The act of contrasting the vulnerabilities found in the few Windows operating systems with the vulnerabilities found in hundreds of Linux/Unix is bad enough, but when you consider that the Unix/Linux list contains duplicate items, it becomes positively shameful.

      It looks like we both posted at the same time. At any rate, you have a point to a certain degree. My post here shows that if you go through the list and subtract out all the items with "updated" after them, Subtract OSX and Solaris, the Linux/Unix group category is about par with windows, not 3x worse.

      Whether "different" OSes should be lumped together is another discussion entirely (how "different" are they if they have the same kernel?)

      --
      The theory of relativity doesn't work right in Arkansas.
    3. Re:Downright Disingenuous by winterlong · · Score: 3, Insightful

      I would have expected better *if* CERT was still in the hands of a university. I wouldn't trust a government analysis as far as I could throw a CRAY.

    4. Re:Downright Disingenuous by MindStalker · · Score: 3, Funny

      And yes I did just search the internet for a 1U or 2U cray for you to throw. Can't find any yet... I'll let you know when I do.

    5. Re:Downright Disingenuous by MindStalker · · Score: 4, Insightful

      Whats worse is the fact that a POP3 Client Buffer Overflow on Windows would not be included at all as one doesn't ship with Windows. Linux distros generally ship with thousands of clients and servers while Windows ships with the bare minimum. To do a true security comparion you would have to compare either just kernel exploits with OS exploits, then compare all popular software for windows with all popular software for Linux side by side in a catagory basis (POP3 clients being a catagory)

    6. Re:Downright Disingenuous by MyDixieWrecked · · Score: 3, Interesting

      Whether "different" OSes should be lumped together is another discussion entirely (how "different" are they if they have the same kernel?)

      then you need to consider the fact that x86 linux has a different kernel than PPC linux. And what about all the people running 2.4.x versus 2.6.x versus everyone still running older versions, still?

      What about the fact that if a version of apache has some flaw that it [generally] affects the entire Apache installbase of that version. Whether it's BSD, Linux, OSX, Windows or BeOS. I say "generally" because some flaws may only affect x86 versions or PPC versions exclusively due to endian issues and ways that the kernels handle the stack and whatnot.

      There really is no fair way of gauging and quantifying the number of flaws found in computers per-OS unless you go by installation package. Make lists of XP, make lists of win2k, make lists for OSX (10.2, 10.3 and 10.4 as well as server), make a list for each distro and every installation type for each of the lastest couple of versions. Sure it's a lot of work... but at least it'll be more accurate.

      --



      ...spike
      Ewwwwww, coconut...
    7. Re:Downright Disingenuous by Anonymous Coward · · Score: 0

      Whether "different" OSes should be lumped together is another discussion entirely (how "different" are they if they have the same kernel?).

      It depends how you look at it. Most definitely the Darwin, FreeBSD, Solaris, Linux, and other Posix-like systems should be seperated. Even if they help each other out, they are definitely seperate source bases and different kernels. One should be able to compare FreeBSD to Linux just as people are comparing Linux to Windows. As for Linux and the ten ton of kernel versions, if we lump kernel versions together, does this mean we should lump all versions of Windows together? Do we lump all Linux distributions together to compare to all versions of Windows? These questions are much tougher since they really aren't comparable at all. And, we still havn't covered all the issues of seperating application vulnerabilities from OS vulnerabilities as well as what sort of damage can be done based on the vulnerability . These reports are good for two things: a useful overview of the vulnerabilities found in the past year (not from a "my OS is better" perspective, but from a "this is the sort of issues we should look out for in our code") and creating useless fodder than can be interpreted in many ways to push a point

    8. Re:Downright Disingenuous by Anonymous Coward · · Score: 0

      I suppose, when you put it that way, Windows doesn't ship with a HTTP client either?

      (here's a clue: Outlook Express)

    9. Re:Downright Disingenuous by poot_rootbeer · · Score: 1

      a POP3 Client Buffer Overflow on Windows would not be included at all as one doesn't ship with Windows.

      Outlook Express...

    10. Re:Downright Disingenuous by Anonymous Coward · · Score: 0

      score -1, offtopic: i am in chuck norris tears now i made it may home norris page

    11. Re:Downright Disingenuous by just_another_sean · · Score: 1

      That's true but according to PJ at Groklaw third party products for Windows that had vulnerabilities were included in the Windows list.

      To be fair, the Windows list isn't really an accurate list of Windows vulnerabilities either, not the way I would think of it. It also has duplicative items, such as for Microsoft ASP.NET Canonicalization (Updated). And it includes Apple, F-Secure, IBM WebSphere, McAfee and other third-party vendor issues. If it can happen to you if you use Windows and the third party software, it's on the list, I guess.

      Neither the Windows or the Linux version gives you a true picture of OS security. It just goes to show that there are a lot of vuknerable software packages out there.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
    12. Re:Downright Disingenuous by FailedTheTuringTest · · Score: 1

      "I honestly expected better from the CERT [us-cert.gov] folks. I don't know why, but I really did."

      Maybe you were thinking of the original CERT http://www.cert.org/ at Carnegie Mellon.

  4. easier by Ragein · · Score: 1, Funny

    Simply just find out who counted the numbers and steal all his personal data, give him an option on which os to leave it on (add 100mb and no firewall) and there u go simple answers from statisticians.

    --
    They fitted George Orwell's coffin with rollers so he could turn over more easily years ago.
    1. Re:easier by Magic5Ball · · Score: 1

      I would pick OSX, QNX, in that order.

      --
      There are 1.1... kinds of people.
    2. Re:easier by Kadin2048 · · Score: 1

      I would pick an Apple IIc.

      I could be wrong, but I'm pretty sure there's no way to remote-root a system that doesn't have a networking stack. Or a network interface, for that matter.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  5. Should Compare A Single Version Of Windows Too by Anonymous Coward · · Score: 5, Insightful

    It's equally unfair to lump Windows 98, NT, 2000, XP all together. They could be looked at as different "distros" of Windows. Should pick the best or latest OS from each group with the least vulnerabilities to compare.

    1. Re:Should Compare A Single Version Of Windows Too by theonlyholle · · Score: 2, Interesting

      In principle, you are right - but you will have to agree that lumping say 4 or 5 versions of Windows together is an order of magnitude less stupid than lumping say 100 distros of Linux, plus assorted flavors of Unix (including MacOS) together...

    2. Re:Should Compare A Single Version Of Windows Too by Anonymous Coward · · Score: 0

      Here we go again... Mod someone down who makes a valid point about windows. Not that I don't agree with the parent post, but let's be fair about this.

    3. Re:Should Compare A Single Version Of Windows Too by MyDixieWrecked · · Score: 3, Insightful

      It's equally unfair to lump Windows 98, NT, 2000, XP all together.

      well... you're half right. I'd say it's better to lump 95/98 together and NT/2000/XP together since most of the later versions of windows are pretty much the same thing on the inside...

      however, it's really unfair to quantify the vulnerabilities for any OS as a whole. There are so many facets of any computer system that many vulnerabilities don't affect most people.

      Saying that a exploit for Apache affects the entire linux/unix/osx install base is an unfair statement. Desktop linux users probably don't have apache running or a bug in X11/xorg won't affect most *nix servers. Likewise, a bug in MSSQL or web services won't directly affect most XP users, although a bug in explorer will affect nearly every windows user (who's running an affected version of explorer).

      You can't even really create lists of vulnerabilities that affect "server" versus "desktop" users, either, because just because something is a server doesn't mean they're necessarily running every server daemon they can.

      There needs to be a list of servertypes (ie: web, email, file, database, etc exclusively) showing not only the quantity of vulnerabilities but also the severity of said vulnerabilities. Perhaps even a table separating different applications.

      I mean, you shouldn't really lump every proftpd vulnerability with every other ftp server software. All it takes is one bad egg to poison the overal results.

      --



      ...spike
      Ewwwwww, coconut...
    4. Re:Should Compare A Single Version Of Windows Too by GuyverDH · · Score: 3, Informative

      It's valid, and yet invalid - all rolled into one.

      No they aren't many different distros, only 2.

      Windows 1.x -> ME are all different versions of windows management systems based on MSDOS.

      Windows NT 3.x -> 2003 are all different versions of windows management systems based on NT.

      So only 2 distros, with lots of versions.

      Now Linux has had how many distros? I've read as high as 90, and no, I haven't done the research myself to come up with my own answer, but I know personally of at least 20.

      Add to that the BSD distros, of which I know of 3 personally.

      Then they lumped in 4 completely different Operating systems - not even distributions.
      AIX, Solaris, HP-UX and MacOSX - all of these are true UNIX operating systems - not the complete list by far - Tru-64, Centix, C-TIX, the pre-caldera UNIXWare, OpenServer, Xenix, UNIX, etc...

      Remember, Linux ISN'T UNIX. So why the hell would they lump them together. Here's why - it's the only way they could get the numbers to add up to anything close to a large margin above the count from the 2 distros of Windows.

      --
      Who is general failure, and why is he reading my hard drive?
    5. Re:Should Compare A Single Version Of Windows Too by dpilot · · Score: 2, Interesting

      For the moment, I'm going to lump a response to this together with "Skewed, Oh yeah..." thread ( http://it.slashdot.org/comments.pl?sid=173159&cid= 14409257 ) and say that it would be interesting to have a little better detail - for Windows and Linux both.

      For instance, Windows has 2 distinct kernel families, Win9X and WinNT. Linux has 1. Within each of these families there is then versioning, Win95, Win98, WinME, WinNT, Win2k, WinXP, 2.4, 2.6, etc.
      Beyond that, it appears that all Windows versions share things like GDI.dll (WMF, anyone?) while all Linux versions share things like glibc. Some are distinct, like Linux modutils, and I've heard that Windows has similar, but can't enumerate.

      Then there are applications on top of both, both bundled with the OS, and not.

      The CERT numbers are a mess, a disservice to all.

      --
      The living have better things to do than to continue hating the dead.
    6. Re:Should Compare A Single Version Of Windows Too by spitzak · · Score: 1

      I would agree, but including OS/X and Solaris as "Linux" is equivalent to including all bugs in WINE and FreeDos as "Windows" bugs.

    7. Re:Should Compare A Single Version Of Windows Too by m50d · · Score: 1

      So divide the windows vulnerabilities by 5 and the linux ones by 400. But actually it won't really affect windows counts because the inflation of linux counts comes from different vendors announcing the problem at different times - something that won't happen with different versions of windows since they're all from MS.

      --
      I am trolling
    8. Re:Should Compare A Single Version Of Windows Too by GuyverDH · · Score: 1

      Update...

      I did a little research, and according to www.distrowatch.com, there are 359 distinct Linux distributions (as of 1/6/2006)

      --
      Who is general failure, and why is he reading my hard drive?
    9. Re:Should Compare A Single Version Of Windows Too by GuyverDH · · Score: 1

      Parsed the list a little better.

      350 Linux
      7 BSD
      1 Solaris
      1 HP-UX
      1 AIX
      ----
      360 Distinct Linux/UNIX Distributions/Variants

      With 6 times the bugs listed, divided by 360 that's only .016 bugs per distro, per bug in windows.

      Now factor that windows is 2 distros, that's .032 bugs per linux distro vs. 1 bug per windows distro.

      That appears to change the results a tad.

      For each bug found in Linux/Unix, there's 32 in Windows.

      --
      Who is general failure, and why is he reading my hard drive?
  6. the rich play, the poor pay by Anonymous Coward · · Score: 0

    so, what did you expect, honesty and integrity ... sheesh, grow up

    our institutions are corrupt, just get over it

  7. So..... by Anonymous Coward · · Score: 0

    Let's settle on ONE (1) linux distribution....You brought this on yourselves with appix, bppix, cppix, and so on....

    Crying about it isn't going to make it go away.

  8. Skewed? Oh yeah... by fak3r · · Score: 4, Interesting

    Considering Linux is a Kernel, to say there were 1000s of bugs again Linux is silly. Let's see how many were against the Linux kernel vs all the userland apps that don't touch anything system level. Now I'll admit bugs show up, and I think that's Open Source's strength; there's constantly ppl combing over the code finding f'd up stuff that no one would think to look at. This is only achieved through constant gazing at the source code, whereas with Windows a bug is usually found out after it's a vuln. Also, I'm happy that MS patched the issue so quickly, even if they were beaten to the punch, perhaps they'll take things (security) more seriously now that they're pushing 'trusted computing'. Not that I care that much, I'm sold on Linux, OS X on the desk and freeBSD on the server, but I did play with ReactOS the other night, and see a future for x-Windows folks who don't want to lose Windows compat when XP support goes away...

  9. The numbers are unimportant by Billosaur · · Score: 4, Insightful

    Shouldn't we be asking the more pertinent question: why do all the various operating systems have so many vulnerabilities? When it comes to such things, this shouldn't be a competition. OS builders should be striving for zero tolerance to vulnerabilities and there shouldn't be an quibbling over the number that exist.

    --
    GetOuttaMySpace - The Anti-Social Network
    1. Re:The numbers are unimportant by jdunn14 · · Score: 3, Insightful

      That sounds great and all, but do you have any idea of the complexity, and therefore cost involved? Ever tried to debug something consisting of 10000 lines, let alone something the size of an OS? No bugs is just not realistic, and truly a better goal is to ensure that when bugs are found they have minimal impact (like ensure users aren't running as root) and patch them in reasonable time (days to weeks, not months to years).

      Now on the topic of this bug counting, if windows is lumped together then linux should be to some degree too, but on the same order of magnitude. A half dozen distros, maybe even mirror the windows counting a little more and make some of those distros be older but still supported ones. Also, the various unixes and linux are entirely different beasts. Just because they try and present a somewhat compatible user interface and APIs doesn't mean that they should be grouped into one object when counting bugs.

    2. Re:The numbers are unimportant by Pollardito · · Score: 1
      take a look at the vulnerabilities list before you get upset. here's one from the UNIX list :
      Clam Anti-Virus ClamAV Mac OS X Command Execution
      someone is going to need to explain to me why an error in A. an add-on antivirus software for B. Mac OS X is in any way a reflection on the quality of UNIX. almost all the vulnerabilities are apps like this, there are about 15 tacked onto the UNIX list that are just errors with acrobat reader. so now Linus is responsible for the quality of Adobe's software?
    3. Re:The numbers are unimportant by Coryoth · · Score: 1

      That sounds great and all, but do you have any idea of the complexity, and therefore cost involved? Ever tried to debug something consisting of 10000 lines, let alone something the size of an OS?

      Interestingly there was just an article about exceptionally low defect rates for software, with cases running from a mere 10,000 up to almost 200,000 SLOC, all done for very reasonable time frames and costs. That, of course, is still signficantly less than the complexity of, say, the entire Linux kernel - but then no one said the whole thing had to be perfect, why not just start with the critical parts? Does it matter if every single obscure device driver is perfect? Under the circumstances that's forgivable, and porbably isn't so important. Making sure the core parts are exploit free using solid techniques does make some sense though. There are such projects underway - see Coyotos and Singularity.

      a better goal is to ensure that when bugs are found they have minimal impact (like ensure users aren't running as root)

      Indeed, but we can do better than this - there are more modern architectures for isolating problems, and they are available right now in Linux, SELinux being the most visible example. The problem is that right now applications often aren't written to respect, or take advantage of the benefits SELinux offers, so the improvement just isn't that great (a very loose policy is required). That is to say Linux is in a state with SELinux similar to where Windows is with Administrator accounts: the technology is there, and if used would represent a huge step in improving security, but because of lagging applications and users it's failing to take the required steps to e more secure.

      Jedidiah.

    4. Re:The numbers are unimportant by Arandir · · Score: 1

      You are still talking about a shitload of work. I don't know how Praxis manages their low rate, and haven't read that article, but Praxis is a lone exception. Even OpenBSD, which audits its code almost continuously, has bugs.

      Software has bugs. It's a fact of life. It is hard to find them and even harder not to write them in the first place. Start writing software for the real world and you will see what I mean. The larger the code base, the more bugs you will get. The more complex the code base the more bugs you will get. A system (such as a Unix) is incredibly complex because you have an immeasurable number of component interactions.

      Very few bugs are typos, syntax errors, or or coding mistakes. The vast majority of bugs are instead misbehaviors. There is nothing wrong with the code, it just doesn't perform exactly in the manner expected in every circumstance. Often these bugs don't arise from the coding, but from the specifications or requirements.

      Expecting bug-free software is like expecting dirt-free children.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    5. Re:The numbers are unimportant by GileadGreene · · Score: 1
      I don't know how Praxis manages their low rate, and haven't read that article...

      Perhaps you should. You may well learn something useful. As you correctly point out,

      "The vast majority of bugs are instead misbehaviors. There is nothing wrong with the code, it just doesn't perform exactly in the manner expected in every circumstance. Often these bugs don't arise from the coding, but from the specifications or requirements."
      The techniques used by Praxis are specifically intended to address specification and requirement errors before they can become bugs, and to catch potential misbehaviors before the code is even executed. That's how they manage their low defect rates: by directly addressing the issues you have identified as the root causes of bugs. Wouldn't you like to know how they do that?
    6. Re:The numbers are unimportant by Brandybuck · · Score: 1

      Believe it or not, the notorious buffer overflow falls into this category. It isn't a coding error, it is a specification error. It was written because the (usually unstated and implicit) specification was that the string would never be larger than 255 bytes, or the file never grow beyond the size of the partition, or something similar. However, writing specifications/apis to this level of detail is counter productive. You may be able to get the code out fast, but you're now spending twenty times the effort writing the specifications.

      --
      Don't blame me, I didn't vote for either of them!
    7. Re:The numbers are unimportant by Coryoth · · Score: 1

      It really depends on what you are writing. If you're implementing a security protocol, or a network service, then taking the extra time to spell things out and be able to prove there aren't any buffer overflows is probably entirely worth your time.

      For projects that aren't as critical you can still get significant benefits from a slightly scaled back approach - things like Design by Contract help developers to spell out their intentions more clearly and can go a long way toward catching and isolating bugs earlier. If you're using the right tools (like, say JML combined with ESC/Java2) you can even do extended static checking and catch a lot of other bugs, where what you've coded doesn't match your stated intentions (usually in the form of annotations) much, much earlier.

      No, there's no silver bullet. That doesn't mean, however, that there aren't things that can be done that make things better than they are now.

      Jedidiah.

    8. Re:The numbers are unimportant by Achromatic1978 · · Score: 1
      so now Linus is responsible for the quality of Adobe's software?

      No more than Bill is, but what do you know, Windows still has to wear them in this list, too.

    9. Re:The numbers are unimportant by Pollardito · · Score: 1

      exactly, neither of them is responsible for the quality of programs on their OS. the list is totally worthless except for what it's intended: a central clearinghouse to find out any software that you might have that has bugs. it's not an evaluation of operating systems, and it's not a reflection of the quality of them.

  10. From the sumary by alex_guy_CA · · Score: 0, Offtopic
    The second "it" in the second sentence (below) refers to nothing at all in the paragraph.

    "Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.

    1. Re:From the sumary by CodeHog · · Score: 1

      Actually it's the third "it" and I noticed this also. I had to read the summary several times to figure out what "it" meant. It also helped that I saw the CERT release this summary is referring to and thought it was strange that Linux beat out Windows for number of vulnerabilities. Now I know why, sigh!

      --
      Fat, drunk, and stupid is no way to go through life, son.
  11. the thing about the list... by User+956 · · Score: 3, Insightful

    Part of the contention is the repeat entries with the "updated" notation. So if you throw out all 141 "updated" occurrences in the Microsoft section, that leaves 671 (812-141=671).

    If you throw out all 1437 "updated" occurences in the linux/unix secion, that leaves 891 (2328-1437=891). Subtracting Apple OS X (130) and Sun Solaris (77), Linux/Unix ends up with 13 more vulnerabilities than Windows (891-130-77=684), but it's for more operating systems, so it may be fair to divide that 684 further.

    --
    The theory of relativity doesn't work right in Arkansas.
    1. Re:the thing about the list... by hattig · · Score: 2, Insightful

      So if I release ShitLinux(tm) and purposely put security holes in it, I can negatively affect every other Unix vendor (not just other Linux vendors, but Sun, Apple, ...), at least in terms of the US-CERT list?

      Great. Where's me phone? Ah.... "Hey Bill, how much are you willing to pay ..."

    2. Re:the thing about the list... by just_another_sean · · Score: 1

      How about when you take the third party applications out of each list? For Windows, anything that doesn't ship with the OS. For Linux (tough, because distro's ship a lot of third party apps) you could remove applications that rarely, if ever, get installed by a typical end user distribution by default.

      Both numbers decrease significantly at this point.

      --
      Creationist Textbook Stickers Declared Unconstitutional by CowboyNeal
  12. The Register fell for it too by Anonymous Coward · · Score: 2, Insightful

    Suckers ...

    But it is true, engage intellect and you can see at a glance how useless the figures are.

    - No ranking by severity levels, or weighting of overall score by severity
    - No individual OS scores

    I can't see how this 'report' is useful to anyone except marketing droids who work for Microsoft.

  13. Patch Time by ndtechnologies · · Score: 4, Insightful

    Good point and I'd like to add, What about the time length between when vulnerabilities are found, and then patched? Surely, they thought about that. Linux and Unix can continue to have more "reported" vulnerabilities than Windows, but if they are patched faster than Windows, doesn't that count for something?

    --
    I have nothing clever to put here...
    1. Re:Patch Time by Capt.+Caneyebus · · Score: 1

      That really isn't the question at hand though. They released it to the public, it should have been patched up prior to release. That is what most complaints about Microsoft are about on here. If a Linux distro is released with the same amount of holes and they just patch them faster, they are still releasing unfinished software. that is just my 2 cents, wasn't attempting to troll

      --
      -- Yes, I work for the government, and yes I am watching you.
  14. Take a deep breath and count to ten... by pieterh · · Score: 4, Insightful

    They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.

    What is "it"? Slight tinge of paranoia here, maybe?

    Let's review the score here:

      - It does not matter what material is published, the fact of the matter is that every Windows PC in the world regularly has visible and non-trivial security issues, while on Linux and OS/X these issues are generally theoretical.

      - People's perceptions of Windows are very simple: it's a piece of crap that they use because it came with the box and everyone else uses it.

      - The relative security of Windows vs. the World is not a deciding factor in most people's use of Windows. It's largely a captive, neutered market.

      - For people who actually do care, no amount of statistics can change the visible and perceived situation. When I choose to ban Windows in my company, it's not because I read some website or article. It's because I'm sick and tired of removing spyware from people's PCs.

    Complaining about these statistics is to give them credibility. Those who chose on the basis of security will ignore this data, and those who chose on other criteria won't care about this data.

    1. Re:Take a deep breath and count to ten... by DogDude · · Score: 0

      Complaining about these statistics is to give them credibility. Those who chose on the basis of security will ignore this data, and those who chose on other criteria won't care about this data.

      Is that kind of like you complaining about Window's "security" while saying that your stupid users keep installing spyware on their computers? My company has -zero- spyware (I should know... I just checked each individual machine).

      --
      I don't respond to AC's.
    2. Re:Take a deep breath and count to ten... by Anonymous Coward · · Score: 0

      Lies, damn lies, and statistics.

    3. Re:Take a deep breath and count to ten... by westlake · · Score: 1
      People's perceptions of Windows are very simple: it's a piece of crap that they use because it came with the box and everyone else uses it.

      It could just be that everyone uses Windows because it is not such a piece of crap after all:

      Windows XP had 72% of the market in December. Up 1% from November 2005. Linux 3%. Up 1% since March 2003. OS Platform Stats

      This from a developer's site that shows very good numbers for Firefox.

    4. Re:Take a deep breath and count to ten... by Arandir · · Score: 1

      Windows XP had 72% of the market in December. Up 1% from November 2005.

      That's because they're upgrading from older unsupported versions of Windows. People are using Windows (all varieties) not because they think is isn't crap, but mainly because they think crap is a normal and unavoidable attribute of operating systems.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  15. Take what the CERT says with a grain of salt... by dpmccoy · · Score: 5, Insightful

    I'm an automation officer in the U.S. Army, and I know for a fact that we're full of Microsoft shills and contractors with Microsoft loyalties. We don't employ Unix/Linux in an enterprise manner; the government sold its soul to Microsoft years ago. Unix is used on some Army tactical platforms, though. Food for thought.

    1. Re:Take what the CERT says with a grain of salt... by shmlco · · Score: 1
      As opposed to other organizations who're full of F/OSS shills and Linux loyalists who've sold their souls to SourceForge? Oh, wait, sorry, I meant F/OSS supporters and Linux advocates.

      People REALLY need to watch what words they use. To many loaded sentences with words like "shill" tend to mark their speakers as fanatics, and do little more than cause others to discount their opinions accordingly. If you're going to convince people, do so with more facts and less rhetoric.

      Otherwise, as Lindsey said in The Abyss, "Hippy, I know you're trying to help, but get off my side."

      --
      Any sect, cult, or religion will legislate its creed into law if it acquires the political power to do so.
    2. Re:Take what the CERT says with a grain of salt... by peterfa · · Score: 1

      Ouch. I know how you feel. I used to be a HelpDesk Technician for a school where I had to go visit offices (as opposed to solving problems over the phone). All ran Windows. I've cleaned up more malware than you can shake a stick at.

  16. No OS is perfect by digitaldc · · Score: 1

    They both have duplicate vulnerabilities listed in their totals.
    It is also not a level playing field in the OS market.
    Once more people are using Linux, it will be a more fair comparison.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
  17. From the article.... anti-FUD stats by CodeShark · · Score: 5, Informative
    Not intending to "karma whore" here, but look at the stats from an already done analysis:
    • 22 Technical Cyber Security Alerts were issued in 2005
      • 11 of those alerts were for Windows platforms
      • 3 were for Oracle products
      • 2 were for Cisco products
      • 1 was for Mac OS X
      • None were for Linux
      , and secondarily look at this quote
    • "Here's more of the same. US-CERT's list of current vulnerabilities contains a total of 11 vulnerabilities, six of which mention Windows by name, and none of which mentions Linux.

    Folks, as other /. posters have already discussed better than I can, most of the supposed Linux bugs are either duplicates or in user- space software. That would be akin to saying a Firefox browser vulnerability is a Windows OS security problem,as opposed to an underlying OS vulnerability that would affect any and all software on the platform.
    --
    ...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
    1. Re:From the article.... anti-FUD stats by Nahor · · Score: 1
      That would be akin to saying a Firefox browser vulnerability is a Windows OS security problem

      You do realize that Firefox runs on Linux too, don't you? ;)

      Some part are Windows specific so some bugs could affect Windows only. But some other bug affect only Linux too, or any other OS that can run Firefox.

  18. My Own Research by vjmurphy · · Score: 4, Funny

    Using the patent-pending method of determining worth by comparing terms plugged into Google, I get the following:

    Search for "Windows Bugs": 45,800
    Search for "Linux Bugs": 23,400
    Search for "Bunny Bugs": 31,100

    From this method, I can determine that I should NOT watch Looney Tunes cartoons on my Windows Media Center PC. Or drink while posting.

    --
    Vincent J. Murphy
    Spandex Justice
    1. Re:My Own Research by muellerr1 · · Score: 1

      Google search for "bugs" returns 163,000,000

      windows AND bugs: 41,000,000
      linux AND bugs: 39,100,000

      Then we subtract:
      windows AND linux AND bugs: 3,570,000
      TOTAL: 76,530,000


      Windows and Linux together account for about 47% of the bugs in the world. The number of individual insects estimated to be alive in the world at any one time is 10 quintillion, or 10,000,000,000,000,000,000. That's 4,700,000,000,000,000,000 of the Windows or Linux variety.

      Get to work, programmers.

    2. Re:My Own Research by eheimer · · Score: 1

      I have employed a similar system in inversely determining the best operating system.

      Search for "Windows Sucks": 143,000
      Search for "Linux Sucks": 44,800
      Search for "Mac Sucks": 25,100

      Wait, let me try that again...

  19. CERT contact page by zogger · · Score: 1
  20. Re:Skewed? Oh yeah... by Anonymous Coward · · Score: 3, Insightful

    Considering Linux is a Kernel, to say there were 1000s of bugs again Linux is silly.

    It would be interesting to see all of the Windows application vendors lumped into the "Microsoft security flaws" category in a similar manner. I've seen quite a few Windows applications from all sorts of software vendors with issues this last year and noticed they weren't listed. While one might argue at first that this would be unfair because of all of the commercial products available for Windows, I'm not sure Windows wouldn't still have an advantage. Just go to sourceforge.net and start counting up all the projects available there that could be lumped into Linux "security flaws."

    Looking just at core operating system applications, Fetchmail doesn't make the cut. In fact, it's inappropriate to include GCC in there since I'm certain they didn't include Microsoft development environment tools in the Microsoft count. An apples-to-apples comparison isn't appropriate and perhaps for those uneducated technical journalists that like to make comparison stories, a kernel-to-kernel, browser-to-browser (e.g. IE vs. Mozilla vs. Opera), office suite to office suite, and other category-based comparison is the only appropriate approach.

  21. I wonder: Definition of security vulnerability? by scottsk · · Score: 2, Insightful

    I've seen these numbers, and wonder what counts as a "Linux" vulnerability - does every little PHP bulletin board package that generates hundreds of bug reports a month on bugtraq count towards the total? All vulnerabilities aren't in the same class, although these numbers seem to lump them all together. Something like this WMF thing affects every machine running Windows. It's not like the Linux kernel, Apache, etc have bugs of this class. (Plus, most "little PHP bulletin board package" things for Windows are proprietary, and there is no master list of vulnerabilities the way there is for open source stuff. It's almost like these numbers are more "found vulnerabilities" than anything else, and a higher number would be good.)

    1. Re:I wonder: Definition of security vulnerability? by peterfa · · Score: 1

      Hmm, you said that the higher numbers of found vulnerabilities would be better. I must say, that makes sense. I wonder what experienced hackers would have to say about this list though. Comparing notes they might say something like, "10 thousand security holes in Windows that we can use. 20 or so security holes in Linux..."
      Keep in mind that this is found security holes in 2005, not accumulative either. There is also the philosophy that Linux developers report bugs and they are public. Microsoft doesn't always report them. They often abandon software.
      I'd expect just about every vulnerability in Windows 95 to be found by now. So if there isn't a whole lot of vulnerabilites found in this operating system, I wouldn't be surprised.

  22. Bitching contest and formal request by vettemph · · Score: 2, Insightful

    Sure, everyone enjoys a good bitching contest but this is not helping.

    Formal request:
    Someone needs to count the vulnerabilities in:

    1) XP
    2) Minimal SUSE linux install
    3) XP with specific of Apps, servers, etc.
    4) SUSE linux with specific Apps, servers, etc.

    Give us these numbers and then we have something to talk about.

    --
    The government which is strong enough to protect you from everything is strong enough to take everything from you.
  23. SecurityFocus article by alanxyzzy · · Score: 1

    There's another debunking over at SecurityFocus

  24. Post an article in Newsforge by ch-chuck · · Score: 0, Flamebait

    Yeah, that'll set millions of high rolling executives straight.

    "Newsforge? WTF's a 'Newsforge'???"

    Let us know when it's above the fold on the Wall Street Journal.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  25. Re:Huh? by minus_273 · · Score: 1

    i was about to post the same thing. I guess the poster means OSX which i think is more secure...

    --
    The war with islam is a war on the beast
    The war on terror is a war for peace
  26. The answer is in your quotation. by Anonymous Coward · · Score: 0

    "unless you carefully comb through it"

    Want smart answers with minimal labor? Create smarter methods of storing, aggregating, and retrieving data. This is the future, and it's 1996. Could always outsource the tedious work to someone you doesn't make as much a cloth jockey at the local carwash, but still has the investment of time and expertise to understand the subject well enough to to do it for you. But really, that's a temporary economic solution that results in massive economic pain later at the expense of innovation now.

  27. Lots of Unixes by dlefavor · · Score: 0, Flamebait
    The mere fact that there are many Unixes and Linux distros should be alarming in itself.

    Anyway, "measuring quality by counting defects" is a fool's errand to begin with.

  28. Jack Ryan is back ... by thaerin · · Score: 1

    Jack Ryan returns in 2006 for "The Sum of all FUD" : 27,000 fact stretched FUDs. One is misleading. CIA analyst Jack Ryan hunts down a group of US-CERTs who plan to announce a hawguash of FUD at the Superbowl.

    --
    If big boobed women work at Hooters do one legged women work at IHOP?
  29. The list count flaws at windows app AND "unix" app by bubulubugoth · · Score: 1

    FTA, there are 3 lists, Windows vulnerabilities, that count, from Iexplorer to Wheresjames camera software, incluiding Adobe...

    The "Unix", incluiding, AIX, Mac OSX, Solaris, Linux, Freebsd, and any thing that looks like unix...

    and Multiplataform vulnerabilities...

    The main issue, is the way they pack together all kind and from different vendors the Unix thing... Also, there are reported vulnerabilities about Adobe and isnt listed as multiplataform vulnerabilities...

    This article, DOESNT become a defacto FUD, it CAN be used as a "FUD Source" (You see, CERT reports that "unix" is worse than "windows")...

    So to be carefull when PR announcements link to thi s "list"...

    --
    Â_Â
  30. Not true. by fireboy1919 · · Score: 3, Informative

    They've got Apache vulnerabilities listed on the Linux side, but not on the Windows side - vulnerabilities that affected both places, I might add.

    This is true of most of the *nix vulnerabilities, actually.

    So what we're really seeing is Windows-only vulnerabilities being compared to ones that are OS neutral. Not that its very suprising, though. Its 2006.
    With the exception of software written specifically for Windows, most software is cross-platform.

    This is the only really meaningful way to do this kind of a report because of this characteristic. The important thing to keep in mind in that, though, is that Windows has all of its own vulnerabilities AND most of the others. :)

    --
    Mod me down and I will become more powerful than you can possibly imagine!
    1. Re:Not true. by Anonymous Coward · · Score: 0

      With the exception of software written specifically for Windows, most software is cross-platform.

      With the exception of most software, most software is cross-platform...

  31. Did they mention how.... by STDOUBT · · Score: 1

    You can *make* Linux more secure by customizing it, and how you can't do that with Windows (any version)?

    1. Re:Did they mention how.... by Anonymous Coward · · Score: 0

      Actually it is fairly easy to customize a Windows box to be more secure.

      1) remove network ability (NIC, Modem)
      2) remove removable-disk drives (CD/DVD drives, floppy drives)
      3) remove or weld USB and Firewire ports closed

      for extra security
      4) remove power supply, monitor, keyboard, mouse, harddrive

      These security messures can be applied equally to Linux, Unix, and BSD. You have to skip step 3 on a Mac unless your ready to jump to step 4 though.

    2. Re:Did they mention how.... by Jaysyn · · Score: 1

      Sure you can, let me show you my custom NICless, concrete filled Windows box.

      Jaysyn

      --
      There is a war going on for your mind.
    3. Re:Did they mention how.... by peterfa · · Score: 1

      Yes you can. Go to How to Costomize Windows XP for Security for a howto on costomizing Windows to be as secure as you want it!

  32. Joe Barr is a writer? by wk633 · · Score: 1
    Can someone please explain what the second 'it' in the second sentence refers to?

    Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.


    If the intro isn't clear, why bother reading the article?
    1. Re:Joe Barr is a writer? by Kadin2048 · · Score: 1

      If the intro isn't clear, why bother reading the article?

      To figure out what the hell they're talking about in the intro, perhaps? That's the main reason I read the articles.

      --
      "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  33. Re:Huh? by Call+Me+Black+Cloud · · Score: 1


    But OSX is BSD-based, so wouldn't that fall under the Unix category? I assumed Windows, because that's usually what gets people worked up around here.

  34. Re:Skewed? Oh yeah... by fak3r · · Score: 1

    ...and I completely agree, Microsoft shouldn't be held accountable for crappy software produced by a third party causing issues; don't think I'm just defending Linux, this report is silly for everyone. Plus things like Gator can hardly be faulted to MS.

  35. The Press Does Not Get It!! by cs668 · · Score: 1

    The mainstream press never differentiates the type of vulnerability. I would say that 1 remote root exploit is worth at least a 100 local root exploits, maybe more if there is no remote exploit for the system at all.

    The mainstream media does not get this. But, neither do most computer users.

  36. Revisionist history by Shoten · · Score: 0, Troll

    Does nobody remember when everyone was gloating over how these numbers showed many more vulnerabilities on the Windows side than on the Linux side? All those years we yelled at Microsoft, asking them to get better on security...were we ever planning to be happy if they actually DID? The notion that their vulnerability count is declining on a yearly basis isn't all that mysterious; they've really been doing a lot of work, from coding practices to architecture (for example, Microsoft Security Center, "Microsoft Update" replacing "Windows Update," their attempt at disabling raw sockets, etc.). So maybe they really are improving...what's so awful about that? It's not a zero-sum solution, everyone...if any single player in the OS field improves security, then that's good, no matter who it is.

    Or, is this not really about security, but just trying to bash Microsoft despite the stats? Nawwwwww.... :)

    --

    For your security, this post has been encrypted with ROT-13, twice.
    1. Re:Revisionist history by Anonymous Coward · · Score: 0

      Obvious Troll but what the hell.
      The number of patches and flaws found in Microsoft Windows XP should be dropped rapidly! It was released in 2001 so has been in production for 5 years now without a major overhaul to it's underlying code base.

      The same can of course be said about Linux, by now the 2.6 kernel's should be pretty stable with very few bugs.

  37. I'm richer than you are by SHP · · Score: 1, Funny

    I've got fifty one dollar bills, all you have is two hundreds. I've clearly got more money than you. Shine my shoes.

    -SHP

  38. Uptime vs Maintneance vs Vulnerabilities by BoRegardless · · Score: 1

    Anyone who uses multiple platforms knows where he has to spend most of his maintenance and fixer-upper time. I spend almost no time on MacOSX keeping it running. I gave up on my WinXP and it simply doesn't connect to the Internet, and it now has no maintenance time either. Bo

    1. Re:Uptime vs Maintneance vs Vulnerabilities by Opie812 · · Score: 1

      I spend almost no time on MacOSX keeping it running. I gave up on my WinXP and it simply doesn't connect to the Internet, and it now has no maintenance time either. Bo

      Does that mean XP sucks?

      I have XP on the internet and have never had a single problem. Not one. I also spend "next to no time keeping it up and running". Maybe your story means you're an idiot more than it means XP sucks.

      Not knowing you, I can't say for sure. Just food for thought.

      This isn't flamebait or a troll or whatever.

      --
      I'm not a nerd. Nerds are smart.
  39. Re:Huh? by honor,+not+armor · · Score: 1

    It seems to me as if you are getting a little bent out of shape over something so small.

    Would you agree that I have made a valid sentence (even if you disagree with my statement)? The "it" I used at the beginning of that sentence is the same as the "it" you took issue with. This is a common English grammatical construction akin to the passive voice, and the "it" herein is typically understood to mean "the situation", "the current course of events", or something similar.

    This is a fairly common construction, and I'm surprised you haven't run into it before. I'm guessing that you have, and simply didn't realize it. I'd love to point you to an article on it, but the wikipedia one is very unhelpful for this particular usage, and google didn't give me anything either, so you're stuck with just my explanation.

  40. This Is Good News! by mpapet · · Score: 2, Insightful

    Really, it is.

    Yeah the spin is ugly, but if the *nix's "stick to their knitting" this too shall pass.

    They do the same thing when they talk about Mac's too. The last time I saw figures (which was a couple of years ago) Apple was far and away the #1 shipper of laptops by brand. But, they would compare ALL laptops shipped by all brands to come up with Apple's "miniscule" market share.

    The reality was that Apple was creaming the Windows-based brands. They would do this with all of the various market segments apple competed in. Funny how they don't do it with MP3 players.

    OT Comment:
    I never understood why anyone who branded computers wanted their numbers in the market research. It just gives HP a target to destroy.

    --
    http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
  41. What a bullshit "article" by Call+Me+Black+Cloud · · Score: 2, Insightful


    The "article" is not an article but rather an opinion piece. For example:

    Microsoft wants you to read the headlines as "Windows 3X safer than Linux." (If Microsoft is being quiet about the US-CERT numbers, it's because the company is too busy trying to come up with a fix for the Windows Meta File (WMF) vulnerability.)

    The authors apparently know what Microsoft wants, even though they admit the company hasn't commented on the summary of vulnerabilities. I guess the authors assume the MS marketing department is working on this bug fix, which at the time the article was posted was fixed (but no patch had been released).

    Reading further, the authors reference the "Technical Cyber Security Alerts", saying, "That's quite a different picture than the one the Microsoft press machine wants you to see." Once again MS is referenced, even though they had nothing to do with the summary of vulnerabilities and have issued no press release on the matter.

    MS is mentioned twice though the company has not issued any press releases or new ads reflecting these numbers. On the other hand, the article repeatedly mentions the press:

    Everywhere you look in the trade press today, you'll find glowing misrepresentations...
    ...many scribes sympathetic to the Microsoft cause go out of their way to make sure the real picture never emerges...
    ...you'd think that the mainstream tech press could get it right when reporting on security...
    ...scribes in the trade press are once again playing the US-CERT FUD game...
    Shame on them for purposely -- or ignorantly, as the case may be -- misleading their readers.


    Yet in the links below the article there is only one direct link to an example of how the press has been misleading their readers.

    Guys, if you're going to write something, call it an article, then post it to Slashdot, at least try to be a little more objective. I think most people are tired of MS vs the world now...it's so last year (this year it's Google vs the world). People are interested in performance, ease of use, security - getting the job done. Who has time for these pissing matches?

    The piece does fit on a site named "NewsForge". Why report the news when you can manufacture it?

  42. Agreed! by Medievalist · · Score: 3, Insightful
    Let's settle on ONE (1) linux distribution....You brought this on yourselves with appix, bppix, cppix, and so on....

    I vote for the "solves-my-problem-but-not-yours" distribution, which is clearly the best.

    Incidentally, I am also in favor of settling on ONE (1) tool for all mechanical uses.
    I favor the two-handed hewing axe, but I might be persuaded to vote for the claw hammer.

  43. So what? by Anonymous Coward · · Score: 0

    Statistics can be produced to prove anything.
    Understanding where those statistics come from is the more important action (which rarely happens in this day and age).

    I'm absolutely no MS supporter, but in general and not refering to anything specifically...

    Saying that a OS with ~90% of the desktop market share can be statistically compared to an OS with ~2% of the market in terms of vulnerabilities is bogus to begin with (regardles of which OS has the lion's share). The 2% share OS will never recieve the level of vetting or attention that the 90% share does.

    No matter what the OS is, if you believe that the 2% share OS is more secure based on found vulnerabilities or alerts and would still remain that way if said 2% share OS suddenly moved to a 90% share OS, you are on quite shakey ground.

    On a basic level, what constitues an alert?
    Would a medium impact bug for the 90% share OS generate the same type of alert as a medium impact bug for the 2% share OS? I think not.

    Quote all the stats you want, the real answer will never be there, it is in the code.

    1. Re:So what? by Nahor · · Score: 1
      The 2% share OS will never recieve the level of vetting or attention that the 90% share does.

      I could the same thing against an OS for which you can't see the source code.

    2. Re:So what? by Anonymous Coward · · Score: 0

      Read the post.
      It has nothing do with who has the 90% share.
      Read my last line.
      The proof is in the code, not faulty statisical comparisons, regardless of who they support or don't support.

      I'm arguing on the validity of the method for saying what system is "safer", not the results.

  44. What an admittance! by Anonymous Coward · · Score: 0, Insightful

    I can't believe that there are so many people posting about this.

    You really had trouble figuring out what the article is about?

    Shame on you! Admitting this at Slashdot too! All of these intellectual people here making a note of your name and marking it with a mental note of 'moron'.

  45. Re:Huh? by Call+Me+Black+Cloud · · Score: 1

    "it" herein is typically understood to mean "the situation", "the current course of events", or something similar

    That doesn't make sense. Replacing that "it" with what you say it represents, the sentence now reads:

    They're doing it again this year to make it appear as if [the situation] is more secure than UNIX/Linux.

    See what I mean? That "it" has to refer to something. From reading the article I assume you meant "it" to refer to Windows, so the sentence could read, "...to make it appear as if Windows is more secure than UNIX/Linux."

  46. Re:From the summary by Medievalist · · Score: 1


    I am amused that you were modded "offtopic" when you commented directly on the newsitem and even included a reference.

    But to clear up any confusion, the "IT" referred to in the OP is of course the famous Segway motorized scooter. See how the whole thing makes sense now?

  47. Re:Skewed? Oh yeah... by Anonymous Coward · · Score: 0

    If Linux is a kernel then everybody needs to stop comparing it to any other OS. The reason being that without a partitioning program, a mkfs program, a boot-loader, an init program, etc. your Linux kernel does nothing. At all. Zero. Zip. Nada. Can't do a single thing. There is absolutely nothing that your Linux kernel can do by itself. NNNNOOOOTTTHHHIINNNGGGG.

    So either you're being a pedantic asshat loser who has intentionally chosen the wrong "definition" of "linux" or Linux isn't more stable than Windows. It's not faster than Windows. So which is it? Is linux more than a kernel, that is an OS or are you an asshole?

  48. FALSE. by WindBourne · · Score: 4, Informative
    Umm, I looked at the list and they weren't counting the same vulnerability multiple times.

    Very false. just look for Larry Wall Perl Insecure Temporary File Creation (Updated). Three instances of the exact same item. And only in *nix even though ActiveState perl for Windows had the same issue. So, there are LOTS of issue with this report. Cert is more SNAFU, than not.

    --
    I prefer the "u" in honour as it seems to be missing these days.
    1. Re:FALSE. by Magic5Ball · · Score: 1

      The summaries in the article, and the one it links, are more messed than not.

      One alert that lists six different vulnerabilities for Windows:
      http://www.us-cert.gov/cas/techalerts/TA05-229A.ht ml

      Another alert that lists two (or three) different vulnerabilities:
      http://www.us-cert.gov/cas/techalerts/TA05-180A.ht ml

      An alert that only summarizes previous vulnerabilities, but lists no new ones:
      http://www.us-cert.gov/cas/techalerts/TA05-102A.ht ml

      An alert that covers a product for three operating systems, and includes Linux by name:
      http://www.us-cert.gov/cas/techalerts/TA05-224A.ht ml

      Counting alerts as a measure of vulnerabilities in operating systems is illegitimate since there is no fixed relationship between the two.

      --
      There are 1.1... kinds of people.
    2. Re:FALSE. by WindBourne · · Score: 1

      You would think by now, with some odd 3 years of critisism about this report, they would have done a DB with the ability to select based on OS vs. version vs. threat level. And yet, they leave it as a joke. Very sad.

      --
      I prefer the "u" in honour as it seems to be missing these days.
    3. Re:FALSE. by Anonymous Coward · · Score: 0

      Not false at all. If you had actually read my whole post the you would know that I did mention the updated entries as making the list longer than it should be. Yes, many of these simply update the original alert with information about other distros that are affected but this is not always the case. Furthermore, the Windows list also contains updated entries.

      My main gripe here is that many posters imply that the *nix list is about eleventy billion times longer than it should be because CERT counted once for each flavor of *nix that was affected. That is false. Many, if not most, of the vulnerabilities on the list have exactly one entry.

  49. Fundamental Problems, not numbers by Anonymous Coward · · Score: 0

    All this talk about absolute number of vulnerabilities gives me a pain in sensitive areas. Like most technical issues, it simply cannot be boiled down to a this number versus that number comparison.

    One assumption behind these kinds of comparisons is that there is some sort of parity between the two OS's that implies that any problems in code cause equal damage to users of either OS.

    This is simply not true and the latest Microsoft blunder (as mentioned in the referenced article by: If Microsoft is being quiet about the US-CERT numbers, it's because the company is too busy trying to come up with a fix for the Windows Meta File (WMF) vulnerability.) illustrates this perfectly.

    If you look at this vulnerability closely, it is NOT a programming error, it is NOT a careless oversite that happens to allow access where none should be, it IS a deliberate and stupid design decision made by Microsoft with no concern for security problems!

    WMF files are allowed to register a callback function that will be executed in certain situations. The code for such a callback function can be embedded in the WMF file itself! Allowing a graphics data file to execute arbitrary code when being viewed is the height of stupidity and just begging for an attack exactly like the current vulnerability.

    Now, for a number of reasons, there probably will never be a similar problem for any *nix system.

    First and foremost, standard file formats promoted and used in the *nix community are designed to be used cross-platform. There is no desire to lock users down to one specific OS or architecture. Why do you think this is called Windows Meta File (WMF)? This is a file format created and used by Microsoft, in defiance of all standard file formats that they might have used instead, that was crafted to run only on Windows, only on x86 architectures and doomed to fail (at least this feature of the format) anywhere else! Imagine, if you will, the necessity of building a format that would include error code specific to PPC, x86, SUN Sparc and every other processor that runs *nix.

    Secondly, programmers for *nix systems are accustomed to thinking of data files as data files, not some arbitrary data on a disc that may be read, written or even executed without regard to a permissions system that the OS overlays on top of them. Imagine trying to view a file format like WMF from another user for which the current user had no execute priviliges. At Microsoft, this is a holdover from the old DOS and early Windows days when the only permission attributes for files was "read-only" or "system". NT (and by extension, XP) has added a much richer level of file security permissions settings BUT legacy code from the bad old insecure days of Win9x prevent them from even using file permissions to protect the OS as much as would be prudent! A little bit of logical thinking will tell you that MS simply cannot protect the OS from things like this WMF vulnerability without killing some functionality built into Windows in the days of 9x and migrated to XP.

    In short, regardless of the sheer numbers of vulnerabilities that may be discovered, Windows has some severe security limitations that are designed in and nothing anyone can say or do will make *nix look as bad in comparison.

  50. I am doing better than most by WindBourne · · Score: 1

    I only had about 10 flies in my windows, and 1 fly in my door.

    --
    I prefer the "u" in honour as it seems to be missing these days.
  51. Re:Huh? by Anonymous Coward · · Score: 0

    Maby it is time to get a damned life.
    If you are that senceitive to the littlest damn think you need to live in a anal retentive bubble and leave normal people alone.

  52. Re:So what? My job is what by CodeShark · · Score: 1
    So what?

    The company with 90% market share consisently and nearly constantly distorts every piece of negative press they get, and trumpets all the negative press about the 2%. But a vulnerability in the 90% software threatens not only my core business (if it is found on the WinX platform), but that of any and all of my customers if they are.

    That's what.

    --
    ...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
  53. Lies, Damned Lies and Statistics by erroneus · · Score: 1

    I don't care. I just know one thing. I'm not easily targetted. Vulnerabilities be damned -- I'm a minority [Linux] user and I don't suffer from the crap that Windows users do. Even if there were only 5 vulnerabilities in Windows and 5000 in Linux, at present, since I'm not being targetted, I'm still safer.

    1. Re:Lies, Damned Lies and Statistics by CrazedWalrus · · Score: 1

      You will be. You will beeee. -- Yoda

  54. Vulnerability density by Anonymous Coward · · Score: 0

    Since we all *know* how bloated Windows is, this implies that the Vulnerability per Line-of-Code metric must be dramatically better for Windows than it is for Linux. What does this say about the open source development model?

  55. I prefer my way. by khasim · · Score: 2, Informative

    Simply evaluate each vulnerability in a simple hierarchy. When evaluating a distribution or a version of Windows, use only the apps installed by default.

    1. Remote--root access that does NOT require human intervention or other app running.

    2. Remote non-root access that does NOT require human intervention or other app running.

    3. Local root access that does NOT require human intervention or other app running.

    4. Local non-root access that does NOT require human intervention or other app running.

    5. Remote root access that requires some human interaction or some combination of apps.

    6. Remote non-root access that requires some human interaction or some combination of apps.

    7. Local root access that requires some human interaction or some combination of apps.

    8. Local non-root access that requires some human interaction or some combination of apps.

    9. Remote OS crash.

    10. Remote app crash.

    11. Local OS crash.

    12. Local app crash.

    There, now it should be easy to [b]exactly[/b] compare different systems. A thousand #12's (local app crash vulnerability) is still not worth a single #1 (remote root access).

    SECURITY is about REDUCING the avenues of attack. A default Ubuntu install will never have any vulnerability above a #3 simply because it has no open ports, by default. This is extremely important when your machine is connected to the Internet.

    1. Re:I prefer my way. by charlesnw · · Score: 1

      This is a very good way to assess risk. A great way to build a threat matrix. A couple comments: I would add another qualification to your evaulation criteria. Has this bug been actively exploited and/or is exploit code (even proof of concept) available? So: A Level 1 or 2 would get immediate attention from me. I would drop what I was doing file an emergency ECN and then test and deploy the patch. Anything 3 or below would be updated during my next regular update cycle/maintence window (twice a month). However anything with an active exploit regardless of severity level would be patched immediately. Just my input.

      --
      Charles Wyble System Engineer
  56. Reading comprehension... by Anonymous Coward · · Score: 0

    Again, read the post, it has nothing to do with who has the 90% share, it has everything to do with the environment.

    The 2% share OS not having the number of alerts as the 90% share doesn't intrinsically mean the software is safer.

    Don't switch the subject; your job is one thing, but claiming you are right because of intrinsically faulty statistical comparisons is another.

    1. Re:Reading comprehension... by CodeShark · · Score: 1
      I don't think there is a problem with my comprehension per se, I think that perhaps you and I are talking in two different directions that aren't antithetical to each other.

      My point about the statistics is merely an adjunct commentary, and if you will permit the biblical analogy, is that the 90% market leader is effectively trying to "point at the mote in the other guy's eye" while simultaneously "ignoring the beam" in his own, and using a faulty statistically analysis to do it. The question of safety favoring OSS is much more in the realm that the more eyes that can see and test the code, the fewer bugs (which sometimes become vulnerabilities) exist and the shorter their surviveal time in "the wild".

      Perhaps a more useful analogy is this: the Windows hegemony is more like the general populace in terms of risk -- the first uncaught airborn super-flu or other pandemic virus is likely to kill millions and cost billions of dollars to fight, control, etc.. But those millions are unlikely to include (statistically speaking) an equal amount of the first responders (the OSS 'nixes, etc.) who take the adequate precautions of masks, gloves, etc..

      Now then, who do you want taking care of YOUR interests -- a first responder with all of the medical expertise in nasty bug stomping and control, or are you okay trying to survive with the Campbell's (hidden recipe) version of grandma's chicken soup?

      --
      ...Open Source isn't the only answer -- but it's almost always a better value than the alternatives...
    2. Re:Reading comprehension... by Anonymous Coward · · Score: 0

      "I think that perhaps you and I are talking in two different directions that aren't antithetical to each other."

      Ok, I think my "reading comprehension" may have been a bit harsh; I guess I was just trying to signify that we were on two different tangents.

      "My point about the statistics is merely an adjunct commentary, and if you will permit the biblical analogy, is that the 90% market leader is effectively trying to "point at the mote in the other guy's eye" while simultaneously "ignoring the beam" in his own, and using a faulty statistically analysis to do it."

      Sure, but any company, regardless of market share does that; it's rare to see one that doesn't. Everyone steers the customer by presenting the most flattering data. All I'm saying is not to be taken in by any of it and to dig deeper...in this case that trying to solely statistically compare two systems, one of which has a hugely disproportionate market share is not a good way to do things.

      If you want to argue open vs. closed source, thats ok by me -- take a look at my last sentence, the answer is in the code, not the stats!

      All things being equal, however, with software, the market leader more than likely will always have the greatest number of issues simply through % of use (even comparing open-source to open-source).

  57. Depends on the meaning of what "it" is by SiliconEntity · · Score: 1

    Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.

    "it is more secure than UNIX/Linux"? What is it? I guess it goes without saying? (Or should that be, it goes without saying?)

  58. Simple pre-processing would help by Kelson · · Score: 2, Informative

    one vulnerability is listed 5 times, making the total of 2328 meaningless unless you carefully comb through it to weed out duplications.

    They could have cut it down to a more manageable list by piping it through "grep -vF '(Updated)' | sort -u".

    That brings it down to just 871, which is much easier to comb for further duplicates.

    The same process on Windows vulnerabilities brings it down from 831 to 659. Both lists still need to be checked for duplicates with different names (say, "Apache HTTP Request Smuggling" and "Apache HTTP Request Smuggling Vulnerability"), but we're now looking at a much more comparable set of numbers.

  59. who is secure? by drew · · Score: 1

    Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.

    I don't get it. Are they saying that US-CERT is more secure than UNIX/Linux? Or is 'it' referring to the mainstream and trade press?

    Come on guys. If you write this kind of stuff for a living, would it kill you to proofread?

    (Never mind that the whole article looks to be nothing more than flamebait to generate ad revenues.)

    --
    If I don't put anything here, will anyone recognize me anymore?
  60. What is "It"? AKA Crappy Editors. by Ahnteis · · Score: 1

    "Joe Brockmeier and I have teamed up in a story on NewsForge to point out how the mainstream and trade press misrepresent the annual summary of vulnerabilities from US-CERT. They're doing it again this year to make it appear as if it is more secure than UNIX/Linux.

    What the @#$@# does this (bolded) it refer to? Did someone clip out a reference to Microsoft Windows? Please -- 5 minutes of proofreading?

  61. Just curious by fleaboy · · Score: 1

    Why do you read it then?

    --
    Life is a gift. And my Karma couldn't possibly be 'Positive'
  62. Disingenuous Discussion by Captain+McCrank · · Score: 1
    This is absurd.

    If you don't tend to your garden, your vegetables may perish.

    If you don't take care of your herd, you cattle might fall ill.

    If you don't properly manager your systems, regardless of OS, your boxes might get compromised.

  63. Re:Skewed? Oh yeah... by JPriest · · Score: 1
    If you would have looked at the report you would see there are non-ms products lumped in as Windows vuls (with Firefox being one of them)

    There is also more than 5 or 6 versioins Windwos. There were probably 6 versions of Windows 2000 alone counting the server lineup. They lumped in Linux/UNIX, but the total figure for it was also about 3 times higher (812 vs 2328) than the figure for windows.

    Also, while I am at it, I did a grep -i | wc -l for "Firefox" and "Internet Explorer" and found that there were 150 vuls lited for Firefox and only 50 listed for IE.

    --
    Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
  64. US Cert's connection with Homeland Security by ZENMacster · · Score: 1

    Some time back, I saw a speaker from US Cert at a data security conference put together by one of my coworkers. When the US Cert guy spoke, one of his first comments were that "US Cert" does not recommend that you use Firefox instead of IE. Our speaker did say that is what he used personally though. His explanation for this contrast was this: Homeland security is a part of the US Cert's goals and after the announcement to use an "alternative browser", Microsoft's stock went down a noticable amount. MS is a big part of our economy and this did not go unnoticed by his superiors. This latest press release from Cert does diminish my respect for their words. This line intentially left blank

  65. The FUD starts here by 1u3hr · · Score: 1

    How about Slashdot's own flamebait heading Linux/Unix Tops Charts for Vulnerabilities in 2005. Which was based on a similarly inflammatory Information Week article "Linux/Unix Vulnerabilities Outnumber Microsoft Windows' 3 To 1", even though in the final paragraph, they mention how fucked the counting is. All goes to show that news sites, and Slashdot, can't resist running an obviously bogus story. Integrity? They've heard of it.

  66. Re:Huh? by Anonymous Coward · · Score: 1, Funny

    "anal-retentive" should be hyphenated. That is all.

  67. Let it go already by geekee · · Score: 1

    The number of known vulnerabilities isn't an accurate figure of merit for security anyway. So why bother complaining about the way vulnerabilites are counted?

    --
    Vote for Pedro
  68. I'll bet... by Anonymous Coward · · Score: 0

    I honestly expected better from the CERT folks.

    I'll bet the residents of New Orleans expected better from the FEMA folks, too.

    This one seems worse than simple incompetence. One wonders what CERT is getting out of Microsoft for this.

    <TinFoilHat>
    Hmmm... the DOJ "caves in" to Microsoft after kicking their ass in court, and the news just came out that the NSA is spying on American citizens.

    Could all those Windows vulnerabilities be features rather than bugs?
    </TinFoilHat>

    (MRC="monopoly")

  69. Bug Days by Kadin2048 · · Score: 1

    Yeah I'd be interested to see a metric of "bug days" per distribution/OS. If a bug goes unpatched for a day, that's 7 bug days. Maybe we could be nice and only count business days, but it's not like the virus writers are taking weekends off.

    Perhaps also there could be a factor for the seriousness of the bug. So for every day that a critical bug is unpatched, it's worth 14 days of a non-critical unpatched bug. Or something like that -- the factor is inherently arbitrary, but maybe we could agree on something that seems to be a fair measure of how much effort a company ought to put into fixing a critical bug, relative to a noncritical one, and use that.

    I'd be very curious to see even how various distributions of Linux stack up against each other in this regard.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:Bug Days by Ragingguppy · · Score: 1

      Oh man,

      If you did that some of the bugs that have been in windows for 20 years would ultimately skew the results.

  70. Correction! by Kadin2048 · · Score: 1

    If a bug goes unpatched for a day, that's 7 bug days.

    Should have read:

    If a bug goes unpatched for a week, that's 7 bug days.

    And I even used Preview that time...

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
  71. See how the number adds up when you install apps. by brainchill · · Score: 1

    In order to accurately compare the number of errata associated with a single typical linux distro and windows in terms of security vulnerabilities you would have to compare the linux distro with a windows OS fully installed with every piece of productivity and server software that exists for it ... like having photoshop, office 2003 full install, microsoft sql server, IIS, exchange, ssh/telnet daemon, printing services, audio editing software, and on and on and on. A typical linux distro represents the full gamut of roughly all software you will ever need to use in your linux life and they generate errata for all of it. Windows on the other hand is just an os. To be fair you would have to combine the bugtrackers from Windows XP with that of Adobe, MAcromedia, Sony, Cakewalk, Maya, Nero, etc -- a windows equiv of every application included in the distro and then present a real total.

  72. Re:Skewed? Oh yeah... by fak3r · · Score: 1

    Nice sig, I agree.

  73. Why the comparison is misleading by unixfan · · Score: 1

    is that to start with most of the Windows vulnerabilities are at a much higher risk level than most of the OSS holes.
    Then never mind that the OSS community is more honest about reporting bugs, which in turn are patched long before even found in the wild.
    When you manage both sides you quickly notice how much more of a problem Windows is. One can easily maintain lot's of OSS machines whereas one doesn't even know what's been broken with the last patch from MS and spend a lot more time maintaining just one Windows box.
    With Windows you are forced to only have one single function on it. With OSS you can easily load it up with several functions that are not going to overload it, not going to conflict with each other, and easy to patch withour fear that something else has now been broken.
    No, you could never compare the two sides. If you are going to rely on numbers only, you can only compare OSS s/w with other OSS s/w.

  74. Why are slashdot posts black on black today? by Anonymous Coward · · Score: 0

    Why the hell are all slashdot posting now black on black, and so unreadable?

    Does it only work on Microsoft Internet Explorer now (which I'm not using)?