<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What Ordinary Users Think About IE: Debunked</title>
	<atom:link href="http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/</link>
	<description>Made with only the finest 1's and 0's</description>
	<lastBuildDate>Thu, 26 Jan 2012 21:20:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Firefox not IE, Please! &#171; Katamat at Home</title>
		<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/comment-page-1/#comment-37792</link>
		<dc:creator>Firefox not IE, Please! &#171; Katamat at Home</dc:creator>
		<pubDate>Fri, 26 Mar 2010 18:27:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=437#comment-37792</guid>
		<description>[...] article says it all. Down with IE and up with [...]</description>
		<content:encoded><![CDATA[<p>[...] article says it all. Down with IE and up with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sander</title>
		<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/comment-page-1/#comment-6605</link>
		<dc:creator>Sander</dc:creator>
		<pubDate>Sun, 21 Dec 2008 18:45:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=437#comment-6605</guid>
		<description>@Sebastian: you&#039;re absolutely right that making assertions on software security needs to be done with accurate information. That accurate information would, for example, have to include Mozilla&#039;s policy of creating an advisory for _every_ security issue found, including the large number which are discovered by Mozilla developers themselves.
Microsoft will frequently fail to creates advisories for those security issues which aren&#039;t reported to it from the outside. The number of reported security issues in an open product like Firefox will thus frequently be higher than those in a closed product like MSIE, and this is a _strength_ of the open product, not a weakness. For more on this, see for example this recent blog post by the Mozilla security team: http://blog.mozilla.com/security/2008/12/15/the-importance-of-good-metrics/

More importantly than that still is the issue m0j0 already mentioned: what&#039;s the average time between a security issue becoming publicly known (thus likely to be exploited), and when a release happens which fixes that security issue?
I don&#039;t have any terribly recent data for this, but here&#039;s a report from early 2007 (so at least a year better than the one m0j0 posted above) which looks at the situation in 2006: http://blog.washingtonpost.com/securityfix/2007/01/internet_explorer_unsafe_for_2.html
To summarize: During the entire year of 2006, IE had 284 days during which it was unpatched for a publicly known critical vulnerability, and 98 days during which it was known that those vulnerabilities were used in the wild for stealing personal or financial data. In contrast, Firefox had a grand total of 9 days in which it was unpatched for a publicly known critical vulnerability.</description>
		<content:encoded><![CDATA[<p>@Sebastian: you&#8217;re absolutely right that making assertions on software security needs to be done with accurate information. That accurate information would, for example, have to include Mozilla&#8217;s policy of creating an advisory for _every_ security issue found, including the large number which are discovered by Mozilla developers themselves.<br />
Microsoft will frequently fail to creates advisories for those security issues which aren&#8217;t reported to it from the outside. The number of reported security issues in an open product like Firefox will thus frequently be higher than those in a closed product like MSIE, and this is a _strength_ of the open product, not a weakness. For more on this, see for example this recent blog post by the Mozilla security team: <a href="http://blog.mozilla.com/security/2008/12/15/the-importance-of-good-metrics/" rel="nofollow">http://blog.mozilla.com/security/2008/12/15/the-importance-of-good-metrics/</a></p>
<p>More importantly than that still is the issue m0j0 already mentioned: what&#8217;s the average time between a security issue becoming publicly known (thus likely to be exploited), and when a release happens which fixes that security issue?<br />
I don&#8217;t have any terribly recent data for this, but here&#8217;s a report from early 2007 (so at least a year better than the one m0j0 posted above) which looks at the situation in 2006: <a href="http://blog.washingtonpost.com/securityfix/2007/01/internet_explorer_unsafe_for_2.html" rel="nofollow">http://blog.washingtonpost.com/securityfix/2007/01/internet_explorer_unsafe_for_2.html</a><br />
To summarize: During the entire year of 2006, IE had 284 days during which it was unpatched for a publicly known critical vulnerability, and 98 days during which it was known that those vulnerabilities were used in the wild for stealing personal or financial data. In contrast, Firefox had a grand total of 9 days in which it was unpatched for a publicly known critical vulnerability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Santos</title>
		<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/comment-page-1/#comment-6528</link>
		<dc:creator>Jacob Santos</dc:creator>
		<pubDate>Fri, 19 Dec 2008 16:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=437#comment-6528</guid>
		<description>This article is hard to consume, mostly I wouldn&#039;t forward it to anyone, unless I was using it of an example of bias. You make no distinction of which IE version you are speaking of. If you would have said IE 6, then I would follow it immediately to everyone I know.

You are right in that the majority of businesses do require IE 6 because of commercial products that require it. The good news is that once businesses have switched to Vista, IE 7, which is marginally better with standards and less annoying bugs (but other more obscure standards bugs). IE 8 is extremely better, with both security (of course there was a patch for Beta 2 a few days ago.

The issue is that for end users, they don&#039;t really care. We care, but until they upgrade to new PCs, they are going to use what they have.</description>
		<content:encoded><![CDATA[<p>This article is hard to consume, mostly I wouldn&#8217;t forward it to anyone, unless I was using it of an example of bias. You make no distinction of which IE version you are speaking of. If you would have said IE 6, then I would follow it immediately to everyone I know.</p>
<p>You are right in that the majority of businesses do require IE 6 because of commercial products that require it. The good news is that once businesses have switched to Vista, IE 7, which is marginally better with standards and less annoying bugs (but other more obscure standards bugs). IE 8 is extremely better, with both security (of course there was a patch for Beta 2 a few days ago.</p>
<p>The issue is that for end users, they don&#8217;t really care. We care, but until they upgrade to new PCs, they are going to use what they have.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m0j0</title>
		<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/comment-page-1/#comment-6469</link>
		<dc:creator>m0j0</dc:creator>
		<pubDate>Thu, 18 Dec 2008 18:09:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=437#comment-6469</guid>
		<description>Right. Now go back and figure out the number of days that users of IE vs. Firefox were actually left vulnerable due to vulnerabilities being unpatched. This all comes back to users being vulnerable. It&#039;s not about flawed code. It&#039;s all flawed. It&#039;s about how many vulnerabilities are unpatched, multiplied by the number of days they are unpatched. I&#039;m not sure if secunia has that information, and I can&#039;t take any more time today to find links for you, but if you really want to research it, don&#039;t think about the problem so much as an engineering problem but a customer service one. The question isn&#039;t how many vulnerabilities are reported, but how many are reported multiplied by the number of days they are left unpatched, thereby leaving a user at risk. 

Also, for the links I posted, the dating is mostly irrelevant. The fact is that there has never been a time when Firefox has spent a full year leaving users at risk 98% of the time. IE has. You&#039;ll remember that the initial discussion was &quot;track record&quot;, which necessarily includes historical data.</description>
		<content:encoded><![CDATA[<p>Right. Now go back and figure out the number of days that users of IE vs. Firefox were actually left vulnerable due to vulnerabilities being unpatched. This all comes back to users being vulnerable. It&#8217;s not about flawed code. It&#8217;s all flawed. It&#8217;s about how many vulnerabilities are unpatched, multiplied by the number of days they are unpatched. I&#8217;m not sure if secunia has that information, and I can&#8217;t take any more time today to find links for you, but if you really want to research it, don&#8217;t think about the problem so much as an engineering problem but a customer service one. The question isn&#8217;t how many vulnerabilities are reported, but how many are reported multiplied by the number of days they are left unpatched, thereby leaving a user at risk. </p>
<p>Also, for the links I posted, the dating is mostly irrelevant. The fact is that there has never been a time when Firefox has spent a full year leaving users at risk 98% of the time. IE has. You&#8217;ll remember that the initial discussion was &#8220;track record&#8221;, which necessarily includes historical data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastien Lambla</title>
		<link>http://www.protocolostomy.com/2008/12/17/what-ordinary-users-think-about-ie-debunked/comment-page-1/#comment-6467</link>
		<dc:creator>Sebastien Lambla</dc:creator>
		<pubDate>Thu, 18 Dec 2008 17:55:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=437#comment-6467</guid>
		<description>Not being funny, but a reliable source would have to be up-to-date, and your link dates back from 2005.

Secunia is fair enough, let&#039;s detail. Firefox 2 has been released at the same time as IE7, so I&#039;ll add up secunia&#039;s vulnerabilities for ff2+3 and compare to IE7. I  have double-checked all the FF3 vulnerabilities and removed the one that was common to FF2 and FF3, so I think you&#039;ll find the numbers accurate.

IE: 33 advisories, 70 vulnerabilities
Firefox: 36 advisories, 195 vulnerabilities


IE Extremely: 9%
Firefox Extremely: 0%

IE Highly: 36%
Firefox Highly: 56% (20)

IE Moderatly: 9%
Firefox Moderatly: 5% (2)

IE Less: 36%
Firefox Less: 22% (8)

IE Not: 9%
Firefox Not: 17% (6)

So according to secunia, Highly and Extremely critical together put IE at 45% of advisories, and FF at 56. Taking anything above moderate advisories puts it at 54% and FF at 61%.

The number of advisories and vulnerabilities is also higher in the firefox family of products.

Let&#039;s make it clear that I do not care much for the browser wars in general, whatever works for you. But making assertions on software security needs to be done with accurate information.

The difference in numbers and seriousness of vulnerabilities between firefox and IE is not significant. What is significant is the number of attackers that choose to attack IE, and with that I will fully agree.

If you want to recommend people to switch, it would be less of an insult to their intelligence to recommend a less mainstream browser because there are less attacks, not because there are less flaws. And certainly not for an alleged abyssimal security record.</description>
		<content:encoded><![CDATA[<p>Not being funny, but a reliable source would have to be up-to-date, and your link dates back from 2005.</p>
<p>Secunia is fair enough, let&#8217;s detail. Firefox 2 has been released at the same time as IE7, so I&#8217;ll add up secunia&#8217;s vulnerabilities for ff2+3 and compare to IE7. I  have double-checked all the FF3 vulnerabilities and removed the one that was common to FF2 and FF3, so I think you&#8217;ll find the numbers accurate.</p>
<p>IE: 33 advisories, 70 vulnerabilities<br />
Firefox: 36 advisories, 195 vulnerabilities</p>
<p>IE Extremely: 9%<br />
Firefox Extremely: 0%</p>
<p>IE Highly: 36%<br />
Firefox Highly: 56% (20)</p>
<p>IE Moderatly: 9%<br />
Firefox Moderatly: 5% (2)</p>
<p>IE Less: 36%<br />
Firefox Less: 22% (8)</p>
<p>IE Not: 9%<br />
Firefox Not: 17% (6)</p>
<p>So according to secunia, Highly and Extremely critical together put IE at 45% of advisories, and FF at 56. Taking anything above moderate advisories puts it at 54% and FF at 61%.</p>
<p>The number of advisories and vulnerabilities is also higher in the firefox family of products.</p>
<p>Let&#8217;s make it clear that I do not care much for the browser wars in general, whatever works for you. But making assertions on software security needs to be done with accurate information.</p>
<p>The difference in numbers and seriousness of vulnerabilities between firefox and IE is not significant. What is significant is the number of attackers that choose to attack IE, and with that I will fully agree.</p>
<p>If you want to recommend people to switch, it would be less of an insult to their intelligence to recommend a less mainstream browser because there are less attacks, not because there are less flaws. And certainly not for an alleged abyssimal security record.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

