<?xml version="1.0" encoding="UTF-8"?><!-- generator="lyceum/1.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Risk report: Two years of Red Hat Enterprise Linux 4</title>
	<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/</link>
	<description>Red Hat Magazine</description>
	<pubDate>Thu, 24 Jul 2008 15:57:39 +0000</pubDate>
	<generator>http://lyceum.ibiblio.org/?v=1.0.2</generator>

	<item>
		<title>by: Prashant</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-59231</link>
		<pubDate>Wed, 19 Mar 2008 10:10:03 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-59231</guid>
					<description>Very use full document for risk mang.</description>
		<content:encoded><![CDATA[<p>Very use full document for risk mang.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Steven Pass</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-9809</link>
		<pubDate>Wed, 06 Jun 2007 02:22:37 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-9809</guid>
					<description>The title of the report is "Risk report: Two years of Red Hat Enterprise Linux 4". It's only toward the end where it states that the report was for "security risks".
There was a lot of talk about updates for security and vunerabilities. What about updates for stability issues? Updates due to coding issues, memory leaks, etc. For an enterprise, these are also "risks" in deciding to use Red Hat.</description>
		<content:encoded><![CDATA[<p>The title of the report is &#8220;Risk report: Two years of Red Hat Enterprise Linux 4&#8243;. It&#8217;s only toward the end where it states that the report was for &#8220;security risks&#8221;.<br />
There was a lot of talk about updates for security and vunerabilities. What about updates for stability issues? Updates due to coding issues, memory leaks, etc. For an enterprise, these are also &#8220;risks&#8221; in deciding to use Red Hat.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Peter K</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-5558</link>
		<pubDate>Fri, 04 May 2007 06:58:24 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-5558</guid>
					<description>First I'd like to say thank you for a very well written summary. I'm looking forward to future summaries (EL5 one yesr, EL3, EL4 3 or 4...).

I also found the security feature table interesting. It would have been great to have a column for EL5.</description>
		<content:encoded><![CDATA[<p>First I&#8217;d like to say thank you for a very well written summary. I&#8217;m looking forward to future summaries (EL5 one yesr, EL3, EL4 3 or 4&#8230;).</p>
<p>I also found the security feature table interesting. It would have been great to have a column for EL5.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Eric Feldhusen</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-4349</link>
		<pubDate>Thu, 26 Apr 2007 16:56:17 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-4349</guid>
					<description>Another interesting metric would be to see how a "minimal" install does for security.  Most of my RHEL3/4/5 servers are done with a minimal install specifically for security reasons.</description>
		<content:encoded><![CDATA[<p>Another interesting metric would be to see how a &#8220;minimal&#8221; install does for security.  Most of my RHEL3/4/5 servers are done with a minimal install specifically for security reasons.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark Cox</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3689</link>
		<pubDate>Mon, 23 Apr 2007 02:46:56 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3689</guid>
					<description>It is actually interesting to look at RHEL3.  Because of our policy of backporting security fixes where possible, as the distribution gets older we are affected by a lower proportion of vulnerabilities:  RHEL3 in its 3.4 years has only had 3 more critical vulnerabilities than RHEL4 in its 2 years.  I'll look at doing a summary this year, or at least "4 years of RHEL3" by November, thanks for the feedback.</description>
		<content:encoded><![CDATA[<p>It is actually interesting to look at RHEL3.  Because of our policy of backporting security fixes where possible, as the distribution gets older we are affected by a lower proportion of vulnerabilities:  RHEL3 in its 3.4 years has only had 3 more critical vulnerabilities than RHEL4 in its 2 years.  I&#8217;ll look at doing a summary this year, or at least &#8220;4 years of RHEL3&#8243; by November, thanks for the feedback.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: jason andrade</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3639</link>
		<pubDate>Sun, 22 Apr 2007 17:22:43 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3639</guid>
					<description>Will there be a risk report for RHEL3 also ? It would be extremely useful to have this sort of report being released annually for each of the main releases (3/4/5).

-j</description>
		<content:encoded><![CDATA[<p>Will there be a risk report for RHEL3 also ? It would be extremely useful to have this sort of report being released annually for each of the main releases (3/4/5).</p>
<p>-j
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Colin Wilson</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3507</link>
		<pubDate>Fri, 20 Apr 2007 10:43:56 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3507</guid>
					<description>This is a very well constructed summary.  It is both informative and objective, and sets the standard for what to expect from any OS vendor.  Thank you for doing such a professional job on it.</description>
		<content:encoded><![CDATA[<p>This is a very well constructed summary.  It is both informative and objective, and sets the standard for what to expect from any OS vendor.  Thank you for doing such a professional job on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mark Cox</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3499</link>
		<pubDate>Fri, 20 Apr 2007 07:24:04 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3499</guid>
					<description>Various reports have tried to compare operating systems from different vendors, some by comparing numbers of vulnerabilities, others looking at days of risk, some recent ones even written by the competing vendor themselves.  You can pretty much get whatever results you like from such comparisons by simply carefully choosing the initial conditions or ignoring differences in disclosure and policies.  I think it's far more useful to let RHEL4 users get a good picture of the risk they faced, and with our raw data available they can tailor it to their environment and way they use RHEL4.  For example we treat an issue as severity important if an local user can cause a machine to crash, but if you are in an environment where that isn't an issue (maybe you don't have untrusted local users or maybe crashes are not a big deal) then you can rerun our stats accordingly.</description>
		<content:encoded><![CDATA[<p>Various reports have tried to compare operating systems from different vendors, some by comparing numbers of vulnerabilities, others looking at days of risk, some recent ones even written by the competing vendor themselves.  You can pretty much get whatever results you like from such comparisons by simply carefully choosing the initial conditions or ignoring differences in disclosure and policies.  I think it&#8217;s far more useful to let RHEL4 users get a good picture of the risk they faced, and with our raw data available they can tailor it to their environment and way they use RHEL4.  For example we treat an issue as severity important if an local user can cause a machine to crash, but if you are in an environment where that isn&#8217;t an issue (maybe you don&#8217;t have untrusted local users or maybe crashes are not a big deal) then you can rerun our stats accordingly.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: midi-man</title>
		<link>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3497</link>
		<pubDate>Fri, 20 Apr 2007 07:04:18 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/04/18/risk-report-two-years-of-red-hat-enterprise-linux-4/#comment-3497</guid>
					<description>Nice article I would have like a side by side comparison with windows it might have been a nice think to have to see which OS is better at security.</description>
		<content:encoded><![CDATA[<p>Nice article I would have like a side by side comparison with windows it might have been a nice think to have to see which OS is better at security.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
