\nIf you really want to compare apples and apples, one should compare Microsoft and FreeBSD or OpenBSD, since these ship a complete base OS, like Microsoft does.<\/em><\/p>\n<\/blockquote>\nI find this comment to be the most humorous one of all. Really humorous, the more I think about it. Microsoft is a company, FreeBS and OpenBSD are OSes. But getting past that, Windows XP vs FreeBSD is no more an apples to apples comparison than Windows XP vs RHEL4WS or RHEL4WS versus FreeBSD. Each of them have different feature set and value\/benefits that they promote to customers, and each have to accept both the positives and the negatives of the product choices made by the vendors. One would have to make a set of assumptions to do an analysis and readers would need to be aware of the context of the comparison in order to interpret it – exactly the same situation as here.<\/font> <\/p>\nMoving on I’ll respond to a different from JNF:<\/p>\n
\nInteresting, but misleading, while I don’t doubt your numbers in the least, I think its inaccurate to not point out that the majority of all of those bugs reported in windows affects everyone running windows, whereas a minority of those affecting RHEL affects everyone running RHEL.<\/em><\/p>\n<\/blockquote>\n\nFurthermore, you need to also ask how many patches has MS released for other peoples products? How many has RH released? How many of the bugs left unpatched in RHEL are for products created by RH or products that RH has a significant interest in (i.e. linux kernel [how many linux kernel developers work for RH?]). How many of those unpatched bugs in RHEL are being actively exploited? How many of those unpatched bugs are being actively exploited in MS products (i.e. msjet40.dll), How many of those products that RHEL has not patched are produced by third party vendors when there are no patches released by the vendor, so on and so forth.<\/em> <\/p>\nThat isn’t to say RH is not responsible for releasing patches, I’m just saying that this post is misleading because of the metrics it leaves out in its analysis- of course, all of these types of articles normally are (regardless of which side of the debate the author is on)<\/em><\/p>\n<\/blockquote>\nJNF – I think some of the discussion above helps set context here too, but primarily, I’d say that I think my results are less misleading than the easy to access data that was available prior to my analysis efforts. I have heard people specifically point out that Secunia shows RHEL has “zero unpatched issues” and then ask why Microsoft can’t achieve the same. That is not just misleading, but specifically inaccurate.<\/font> <\/p>\nI do think that several of your other questions are interesting and might be interesting to pursue as separate research, but I don’t think the fact that I didn’t answer questions that I wasn’t trying to answer<\/strong><\/em> invalidates the results for the question I was focusing on – accuracy of unpatched data for Linux distros as represented by RHEL.<\/font> <\/p>\nBest regards and thanks for taking the time to comment! ~Jeff<\/font><\/p>\n","protected":false},"excerpt":{"rendered":"Once again, my effort to explore common misperceptions (more recently exploring unpatched statistics) has brought out some of the common objections from those that don’t necessarily like the results. Very rarely do I get comments that can find a substantive problem with the analysis – instead the arguments tend to be detailed variations of “your comparison […]<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","footnotes":""},"content-type":[3659],"topic":[],"products":[],"threat-intelligence":[],"tags":[3822,3819],"coauthors":[3653],"class_list":["post-679","post","type-post","status-publish","format-standard","hentry","content-type-best-practices","tag-microsoft-security-insights","tag-windows"],"yoast_head":"\n
Common Objections - Comparing Linux Distros with Windows | Microsoft Security Blog<\/title>\n \n \n \n \n \n \n \n \n \n \n \n\t \n\t \n\t \n \n \n \n\t \n\t \n\t \n