<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Ballmer Confuses Linux, Unix, BSD Security</title>
	<link>http://www.emailbattles.com/2004/10/29/security_ajiijfcaji_da/</link>
	<description>Spam, Security, Privacy, Spyware, Phishing &#038; Viruses from the Front Lines.</description>
	<pubDate>Wed, 17 Mar 2010 02:52:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Chad Perrin</title>
		<link>http://www.emailbattles.com/2004/10/29/security_ajiijfcaji_da/#comment-11</link>
		<pubDate>Sun, 05 Feb 2006 15:15:20 +0000</pubDate>
		<guid>http://www.emailbattles.com/2004/10/29/security_ajiijfcaji_da/#comment-11</guid>
					<description>I ran across that study when it was new, and was unimpressed.  One question in particular that arose in my mind was this: How do you measure the time from "disclosure" to patch?  Considering that, often enough, vulnerability discoverers are prevented from publicly disclosing what they've found until after Microsoft has released a patch, this can mean a period of months of vulnerability, potentially with exploits in the wild, before a patch is provided -- and yet, if patch turnaround time is measured from the date of public disclosure, Microsoft's record will show another zero-day lag.&lt;br&gt; &lt;br&gt; We see now another reason for Microsoft's relentless chastisement of anyone that discloses a vulnerability "too soon".  This isn't about protecting customers: it's about protecting Microsoft's image.&lt;br&gt; &lt;br&gt; That completely leaves aside problems with the Forrester study, such as the fact that Forrester is a Microsoft lackey, and that the RHEL patches include support for a great many non-Linux-specific software while Microsoft patch times only include Windows-specific software, and of that only Microsoft-distributed software.</description>
		<content:encoded><![CDATA[<p>I ran across that study when it was new, and was unimpressed.  One question in particular that arose in my mind was this: How do you measure the time from &#8220;disclosure&#8221; to patch?  Considering that, often enough, vulnerability discoverers are prevented from publicly disclosing what they&#8217;ve found until after Microsoft has released a patch, this can mean a period of months of vulnerability, potentially with exploits in the wild, before a patch is provided &#8212; and yet, if patch turnaround time is measured from the date of public disclosure, Microsoft&#8217;s record will show another zero-day lag.</p>
<p> We see now another reason for Microsoft&#8217;s relentless chastisement of anyone that discloses a vulnerability &#8220;too soon&#8221;.  This isn&#8217;t about protecting customers: it&#8217;s about protecting Microsoft&#8217;s image.</p>
<p> That completely leaves aside problems with the Forrester study, such as the fact that Forrester is a Microsoft lackey, and that the RHEL patches include support for a great many non-Linux-specific software while Microsoft patch times only include Windows-specific software, and of that only Microsoft-distributed software.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
