<?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: Am I an Accessory?</title>
	<atom:link href="http://eternallyoptimistic.com/2009/05/31/am-i-an-accessory/feed/" rel="self" type="application/rss+xml" />
	<link>http://eternallyoptimistic.com/2009/05/31/am-i-an-accessory/</link>
	<description></description>
	<lastBuildDate>Wed, 21 Apr 2010 14:34:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: yungchin</title>
		<link>http://eternallyoptimistic.com/2009/05/31/am-i-an-accessory/comment-page-1/#comment-529</link>
		<dc:creator>yungchin</dc:creator>
		<pubDate>Mon, 22 Jun 2009 09:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://eternallyoptimistic.com/?p=1200#comment-529</guid>
		<description>&gt;&gt; So while the version of libssl0.9.7-sarge5, it should nevertheless
&gt;&gt; incorporate all the security fixes present in 0.9.8k.
&gt;
&gt; So, the good news is that I’m probably safe, and the team is on top 
&gt; of it.  The bad new is that I simply have to trust it is so, I don’t &gt; see a way to easily independently verify.

Given that it&#039;s Debian, where all business is done in the open, it is very easy to independently verify things. The &lt;a href=&quot;http://www.debian.org/releases/sarge/&quot; rel=&quot;nofollow&quot;&gt;sarge release&lt;/a&gt; page will tell you that in fact security-updates for sarge have been discontinued over a year ago. Furthermore, you can subscribe to the &lt;a href=&quot;http://www.debian.org/security/dsa&quot; rel=&quot;nofollow&quot;&gt;Debian Security Advisories feed&lt;/a&gt;, which shows the most recent update for OpenSSL was &lt;a href=&quot;http://www.debian.org/security/2009/dsa-1763&quot; rel=&quot;nofollow&quot;&gt;this year&lt;/a&gt;, and indeed did not include updates for sarge anymore...</description>
		<content:encoded><![CDATA[<p>&gt;&gt; So while the version of libssl0.9.7-sarge5, it should nevertheless<br />
&gt;&gt; incorporate all the security fixes present in 0.9.8k.<br />
&gt;<br />
&gt; So, the good news is that I’m probably safe, and the team is on top<br />
&gt; of it.  The bad new is that I simply have to trust it is so, I don’t &gt; see a way to easily independently verify.</p>
<p>Given that it&#8217;s Debian, where all business is done in the open, it is very easy to independently verify things. The <a href="http://www.debian.org/releases/sarge/" rel="nofollow">sarge release</a> page will tell you that in fact security-updates for sarge have been discontinued over a year ago. Furthermore, you can subscribe to the <a href="http://www.debian.org/security/dsa" rel="nofollow">Debian Security Advisories feed</a>, which shows the most recent update for OpenSSL was <a href="http://www.debian.org/security/2009/dsa-1763" rel="nofollow">this year</a>, and indeed did not include updates for sarge anymore&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
