"Study: Linux Security Problems Outstrip Microsoft's"???
Hi All! I was sent a link to this article with the above title and I was curious what others that about it: http://www.osopinion.com/perl/story/19996.html There is a lot of hand-waving, but it did say "16 out of the 29 advisories published (by CERT) during the first 10 months of 2002" were for "Linux Software". At first that is suprtising, even shocking, but my bet is that "Linux Software" actually means "open source", so it applies to more than just Linux (even Microsoft). It also said that "only seven security problems were documented in Microsoft products." However, if you look at the CERT site there are references to many Windows-only products which are obviously not included in the MS stats, but it seems that open-source is always included in the Linux stats. I would love to hear what others have to say about this whole article. Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
James Mohr wrote:
There is a lot of hand-waving, but it did say "16 out of the 29 advisories published (by CERT) during the first 10 months of 2002" were for "Linux Software". At first that is suprtising, even shocking, but my bet is that "Linux Software" actually means "open source", so it applies to more than just Linux (even Microsoft).
An obvious piece of nonsense: it's like concluding that red cars are more likely to develop faults than pink ones. If the samples taken were representative (not very plausible) and there were equal numbers of software product in each category (not true) and the null hypothesis was that CERT advisories were equally likely in both categories, then the result (16/29) would not be statistically significant even at 20%. Usually, we look for 5% or lower significance before drawing conclusions. In this case, no conclusions can reasonably be drawn and there is good reason to suspect bias against 'linux and opensource software'. The study is not worth the paper it isn't printed on and the consultants who published it are either incompetent or guilty of unprofessional conduct. JDL
Objectivity by CERT is a misnomer, they are not objective in the least. They are, however, a for profit organizaton open to the highest bidder. Case in point: They did a report on AMD flaw where they cited numerous reasons why Intel made a better product. Fact of the matter they never did one interview with anyone at AMD and derived their "facts" for the study base on perceptions commonly subscribed to by the general public. So, what we see with CERT reports is more often due to its mission of fulfilling it's own market strategy - that is to reports with a "wow" factor in order to get people to subscribe to their service. They're all about producing reports with a marketing target and they are not a objective research organization. The report is for the purpose of telling people what they want to hear - namely those the work for or support M$. It isn't worth the time it takes to read it. They lack completely any sort of meaningful data and offer up antecdotal evidence that is weakingly, if at all, confirmable. I'm not saying this because I'm a Linux supporter. I'm saying this because their research methods are not mentioned, given, and no real analysis techniques are offered in support of the "data" they claim in the story/report. Curtis On Monday 30 December 2002 07:56, John Lamb wrote:
James Mohr wrote:
There is a lot of hand-waving, but it did say "16 out of the 29 advisories published (by CERT) during the first 10 months of 2002" were for "Linux Software". At first that is suprtising, even shocking, but my bet is that "Linux Software" actually means "open source", so it applies to more than just Linux (even Microsoft).
An obvious piece of nonsense: it's like concluding that red cars are more likely to develop faults than pink ones.
If the samples taken were representative (not very plausible) and there were equal numbers of software product in each category (not true) and the null hypothesis was that CERT advisories were equally likely in both categories, then the result (16/29) would not be statistically significant even at 20%. Usually, we look for 5% or lower significance before drawing conclusions.
In this case, no conclusions can reasonably be drawn and there is good reason to suspect bias against 'linux and opensource software'.
The study is not worth the paper it isn't printed on and the consultants who published it are either incompetent or guilty of unprofessional conduct.
JDL
-- Billboard Writer vs. Literature = Micorsoft vs. Computing,
On Monday 30 December 2002 16:38, Curtis Rey wrote:
Objectivity by CERT is a misnomer, they are not objective in the least. They are, however, a for profit organizaton open to the highest bidder.
Case in point: They did a report on AMD flaw where they cited numerous reasons why Intel made a better product. Fact of the matter they never did one interview with anyone at AMD and derived their "facts" for the study base on perceptions commonly subscribed to by the general public. So, what we see with CERT reports is more often due to its mission of fulfilling it's own market strategy - that is to reports with a "wow" factor in order to get people to subscribe to their service. They're all about producing reports with a marketing target and they are not a objective research organization. The report is for the purpose of telling people what they want to hear - namely those the work for or support M$. It isn't worth the time it takes to read it. They lack completely any sort of meaningful data and offer up antecdotal evidence that is weakingly, if at all, confirmable. I'm not saying this because I'm a Linux supporter. I'm saying this because their research methods are not mentioned, given, and no real analysis techniques are offered in support of the "data" they claim in the story/report.
Curtis
Hang on there. Aberdeen did the report, not CERT. (If memory serves me correctly.) However, what you are saying is basically true, but about Aberdeen. I personally think their "research methods" **were** mentioned and that was simply to quote numbers based on the CERT advisories and create some interesting, if not confusing, statistics. Using raw numbers, independent of any real frames of reference and then creating a set of statistics is a common and (unfortunately too offen) acceptable "reasearch method". Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
Sorry, I stand corrected. I mislabelled the researcher as CERT rather than Aberdeen. But, you comments are in line with my thoughts. <rant> I work as a clinical practitioner in health care (R.N.) and research and the analysis of "conclusions" and possiblities for implementing the conclusions of research into practice is a primary function of my profession. Therefore I was taught to be critical of studies due to the implications on my patient healths status. Furthermore, I was taught in the scientific method and though the scientific method is actually fairly poor at really "proving" anything it is moreover designed to disprove things (as well as replicate - which is used as a form of proof). One of the primary methods of disproving or debunking studies is to look at methods used to derive data in a meaningful way and then pair this with the conclusions of the study. Using raw data that is not properly put into context is the oldest trick in the book related to making things appear to make sense without really using techniques used to relate data to the variables and the study question and is poor work and cannot be relied upon. Just spewing forth numbers, putting them into a table or graph, and then using this to support one's claims does not make it valid. There is no mention of techniques, groups. selection of groups, selections of variables (or what the variables are - such as the "constant") or the manner in which the data is collected - at least in a manner that I would take seriously as valid and worth consideration. They bank on the fact that most people don't know about or forget that "correlation is not causation". Unfortuanately, especially in marketing and advertising, this technique is preferred (using raw data in graphs and tables to support antecdotal claims). An example is the claim "4 out of 5 dentist prefer <insert product>". The reality is that they send out samples of a product as a marketing tool with instructions to participate with the data gathering process. The problem with this is that often the case is that 4 out of 5 dentist don't return the item or respond to any included media from the company that sent the sample product. This plays right into the hands of the marketers and advertisers that in turn translate this into the statement that since the dentist (or M.D. or whatever) didn't return the sample that they A) they must be using it and B) prefer it. This couldn't be farther from the truth. The fact is most of these samples go in the trash or a drawer and the marketing departments are quite aware of this. None the less they use this behavior to further their claims about a products or service. This seems to be the case in much of the analysis I see about IT and computing products and services. This is fine (well sort of) if your trying to sell the latest and greatest Video card or NIC (except in the case of M$ new line of Routers, Hubs, etc... which are buggy and call home way too much - arghhh). But if it involves liability related to data loss/theft, commerce, online transaction of any sort, or just secure and cost effective day to day business use then it is akin to negligence on the part of the supposed researcher. People often rely on these groups and organizations in order to make decision about what to use and how to spend their money. And it's all about the money. CIO's and IT managers need to understand and have reliable sources of information that is both properly collected and in a form that is concise and understandable. This is why poeple that really want to understand things of this nature use multiple sources of information and look at such things as who has funded these studies and what are the affiliations of the researchers. I just wish people had both a respository in which to go where they could compare and contrast information and also had the understanding of the importance of doing so. <end rant> Cheers, Curtis. On Monday 30 December 2002 11:16, James Mohr wrote:
On Monday 30 December 2002 16:38, Curtis Rey wrote:
Objectivity by CERT is a misnomer, they are not objective in the least. They are, however, a for profit organizaton open to the highest bidder.
Case in point: They did a report on AMD flaw where they cited numerous reasons why Intel made a better product. Fact of the matter they never did one interview with anyone at AMD and derived their "facts" for the study base on perceptions commonly subscribed to by the general public. So, what we see with CERT reports is more often due to its mission of fulfilling it's own market strategy - that is to reports with a "wow" factor in order to get people to subscribe to their service. They're all about producing reports with a marketing target and they are not a objective research organization. The report is for the purpose of telling people what they want to hear - namely those the work for or support M$. It isn't worth the time it takes to read it. They lack completely any sort of meaningful data and offer up antecdotal evidence that is weakingly, if at all, confirmable. I'm not saying this because I'm a Linux supporter. I'm saying this because their research methods are not mentioned, given, and no real analysis techniques are offered in support of the "data" they claim in the story/report.
Curtis
Hang on there. Aberdeen did the report, not CERT. (If memory serves me correctly.) However, what you are saying is basically true, but about Aberdeen. I personally think their "research methods" **were** mentioned and that was simply to quote numbers based on the CERT advisories and create some interesting, if not confusing, statistics. Using raw numbers, independent of any real frames of reference and then creating a set of statistics is a common and (unfortunately too offen) acceptable "reasearch method".
Regards,
jimmo
-- Billboard Writer vs. Literature = Micorsoft vs. Computing,
On Monday 30 December 2002 14:56, John Lamb wrote:
James Mohr wrote:
There is a lot of hand-waving, but it did say "16 out of the 29 advisories published (by CERT) during the first 10 months of 2002" were for "Linux Software". At first that is suprtising, even shocking, but my bet is that "Linux Software" actually means "open source", so it applies to more than just Linux (even Microsoft).
An obvious piece of nonsense: it's like concluding that red cars are more likely to develop faults than pink ones.
Didn't Churchhill say that there are three kinds of lies: regular lies, damned lies and statistics?
If the samples taken were representative (not very plausible) and there were equal numbers of software product in each category (not true) and the null hypothesis was that CERT advisories were equally likely in both categories, then the result (16/29) would not be statistically significant even at 20%. Usually, we look for 5% or lower significance before drawing conclusions.
If you look at some of the comments to the article they mention the fact that there are are 50K+ open source projects (at least on SourceForge) but only 250 MS "products". Even if the numbers in the Aberden report are true there are about 100 times more MS security bugs (by percentage). I liked the fact that Linux trojans "doubled" between 2001 and 2002 (from 1 to 2).
In this case, no conclusions can reasonably be drawn and there is good reason to suspect bias against 'linux and opensource software'.
Of course you can draw a conclusion. One is that the author of the article is either himself paid by MS or didn't bother to check the "facts" in the Aberdeen report. ;-)
The study is not worth the paper it isn't printed on and the consultants who published it are either incompetent or guilty of unprofessional conduct.
Not necessary. If someone pays me to write a "report" that skews statistics and praises Microsoft and I do just that, why is that unprofessional? I am doing what I am paid to do. ;-) Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
James Mohr wrote:
Didn't Churchhill say that there are three kinds of lies: regular lies, damned lies and statistics?
No. The quote is earlier. It has been attributed to several people including Disraeli and George Bernard Shaw but is probably due to Mark Twain, who used the phrase in his autobiography. JDL
On Monday 30 December 2002 17:14, John Lamb wrote:
James Mohr wrote:
Didn't Churchhill say that there are three kinds of lies: regular lies, damned lies and statistics?
No. The quote is earlier. It has been attributed to several people including Disraeli and George Bernard Shaw but is probably due to Mark Twain, who used the phrase in his autobiography.
JDL
Now that you mention it, I think is was Mark Twain. regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
Seurity is a concern but not as much as the report below claims. However, the security problems will be fixed in due course by open source community. Linux will remain my preferred platform, not windows. In any case, the article is too pro-Microsoft and too anti-Linux. Draw your own conclusions. ----- Original Message ----- From: "James Mohr" <suse_mailing_list@jimmo.com>
Hi All!
I was sent a link to this article with the above title and I was curious what others that about it:
http://www.osopinion.com/perl/story/19996.html
There is a lot of hand-waving, but it did say "16 out of the 29 advisories published (by CERT) during the first 10 months of 2002" were for "Linux Software". At first that is suprtising, even shocking, but my bet is that "Linux Software" actually means "open source", so it applies to more than just Linux (even Microsoft).
It also said that "only seven security problems were documented in Microsoft products." However, if you look at the CERT site there are references to many Windows-only products which are obviously not included in the MS stats, but it seems that open-source is always included in the Linux stats.
I would love to hear what others have to say about this whole article.
Regards,
jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
On Monday 30 December 2002 16:12, you wrote:
I think the key is Paragraph 4:
"During those same 10 months, only seven security problems were documented in Microsoft products."
What the article does not go in to is the severity nor the UNIX break down for the 16. Saying 16 were for Linux and Open Source is a pretty broad definition, where Microsoft is a much narrower area.
The article said "Linux software" and "Microsoft products". When you consider that a number of the bug/problems listed in the CERT advisories apply to both Linux and Windows, they are classified as "Linux software". However, they do not come from Microsoft and are therefore not "Microsoft products". The same bug **should** be counted against Microsoft, but isn't simply because it was not produced by Microsoft. However, since the software runs on Linux (and therefore "Linux software") it is counted as a bug against Linux. Also, counting the software bugs as "Linux problems" is like saying the PC-cillen bug is a Windows' bug simply because PC-cillen runs **only** on Windows.
I would say, look at the reports, and decide for yourself which is better for you. Inparticular, read the section on Vendor Information. For example: CA-2002-36 (December, hence no in the report) covers BOTH Unix/Linux/*BSD and MS implimentations.
Assuming I made no mistakes, from 1/2002 - 12/2002 and 37 total reports, I get:
<table snipped>
At least 1 of the SSH reports covers MS products, but if SSH is not used in your environment, you eliminate 4 reports that are of concern.
I cannot figure out how the article or Aberdeen came up with these exact numbers, no matter how you look at it. However, check out: http://cooper.stevenson.name/aberdeen.html. This addresses the issue of "absolute" numbers and puts the shoe on the other foot.
Some of the questions I would raise would be:
1) How many MS (and other) incidents are NOT reported?
An obviously key issue here. You can bet that unless MS has to, it will never report a bug that it discovers itself. It will just silently "fix" it in the next service pack.
2) Which community is better at diagnosing and responding to problems?
Obvious, for two reasons. One we Linux-folks typically have more technical skill than the average Windows user. Second, we have the source code.
3) In which area, does the functionality YOU need to worry about (either by choice, or necessity) has the fewest issues.
Careful. I would rather have 10 different bugs that crash a user's browser than a single virus that propogates via MS Outlook. Numerically fewer is not always better.
4) Which areas would cause your IT group the least grief? Personally, Chat, Email and Web-browsing based vulnerabilties are the most troublesome to me. They are hard to diagnose, hard to find, and virutally impossible to get the general user base to diagnose and report properly. If they even detect it. At least with a BIND flaw, something has to come attack you, directly. Virus problems propogate themselves!
That's the issue: What causes you and company the most problems?
5) How good are your security people?
Good enough to know that for security relevant issues, we don't rely on Microsoft products. Regards, jimmo -- --------------------------------------- "Be more concerned with your character than with your reputation. Your character is what you really are while your reputation is merely what others think you are." -- John Wooden --------------------------------------- Be sure to visit the Linux Tutorial: http://www.linux-tutorial.info --------------------------------------- NOTE: All messages sent to me in response to my posts to newsgroups, mailing lists or forums are subject to reposting.
James Mohr wrote:
I cannot figure out how the article or Aberdeen came up with these exact numbers, no matter how you look at it. However, check out: http://cooper.stevenson.name/aberdeen.html. This addresses the issue of "absolute" numbers and puts the shoe on the other foot.
That was my problem as well. Thank you for the URL! Saves me the time from doing the same.
An obviously key issue here. You can bet that unless MS has to, it will never report a bug that it discovers itself. It will just silently "fix" it in the next service pack.
As many vendors tend to. In a competitive environment, you don't want to spread bad press about yourself. Of course, reporting issues to CERT for positive press is not unknown from any vendor. "Gee, we found a problem and we just happen to already have a fix!" ;-)
Obvious, for two reasons. One we Linux-folks typically have more technical skill than the average Windows user. Second, we have the source code.
This is generally true, but it is changing. Unfortunately.
Careful. I would rather have 10 different bugs that crash a user's browser than a single virus that propogates via MS Outlook. Numerically fewer is not always better.
So true! In my years of IT work, viruses cause more effort, headache and lost time/resources then all of the security breaches I've had to deal with, either directly, or peripherally. (3 in 16 years. Only 1 was my problem, and it was shut down before the intrusion proceeded further. The other 2 I had to take defense actions when corporate HQ was breached.) I've admined both UNIX/Linux/*BSD and Windows 3.1/NT/2K/XP. For security, I'll take the UNIX side. For certain functionality, I can see some Windows applications, but it is protected by UNIX or variant.
That's the issue: What causes you and company the most problems?
Exactly my point!
Good enough to know that for security relevant issues, we don't rely on Microsoft products.
And knowledgeable staff! They may be expensive, but they keep your fat out of the frying pan! JRSM -- _ | John Raymond Stone Mascio _|_|_) | mascio@ryu.com (_|_| | 214.725.7518 | 972.240.5040 >^. .^< >^..^< -----------------------------------------------------------------
participants (5)
-
Curtis Rey
-
James Mohr
-
John Lamb
-
John R. S. Mascio
-
Linux World 999