<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Rising Stream &#187; Firefox</title>
	<atom:link href="http://risingstream.net/tag/firefox/feed/" rel="self" type="application/rss+xml" />
	<link>http://risingstream.net</link>
	<description></description>
	<lastBuildDate>Tue, 15 Feb 2011 17:05:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Adobe Reader &#8211; The New Security Issue?</title>
		<link>http://risingstream.net/2009/03/18/adobe-reader-the-new-security-issue/</link>
		<comments>http://risingstream.net/2009/03/18/adobe-reader-the-new-security-issue/#comments</comments>
		<pubDate>Wed, 18 Mar 2009 16:04:38 +0000</pubDate>
		<dc:creator>Steve</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Acrobat]]></category>
		<category><![CDATA[Adobe]]></category>
		<category><![CDATA[eWeek]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Foxit]]></category>
		<category><![CDATA[PrimoPDF]]></category>
		<category><![CDATA[Reader]]></category>

		<guid isPermaLink="false">http://www.risingstream.net/?p=66</guid>
		<description><![CDATA[While it&#8217;s easy to target Microsoft for security issues, an organization must look at its entire infrastructure in order to maintain security. eWeek recently looked at Adobe Reader and came away unimpressed, to the point of inside an organization. It began when due to an advertisers use of an unpatched version of Adobe. That was [...]]]></description>
			<content:encoded><![CDATA[<p>While it&#8217;s easy to target Microsoft for security issues, an organization must look at its entire infrastructure in order to maintain security.  eWeek recently looked at Adobe Reader and came away unimpressed, to the point of  inside an organization.</p>
<p>It began when  due to an advertisers use of an unpatched version of Adobe.  That was in February and patches were promised in March.</p>
<p>Have you ? If not, now is the time to ensure that  and  are up-to-date and you, and your clients, are protected.</p>
<p>You can also update from within the applications themselves.  For Reader, you can find Update under Help.  If you are running Reader v8, I don&#8217;t recommend moving to Reader v9 until you&#8217;ve tested other applications for support of v9.  While eWeek points to a couple of option, including  (for Firefox) I&#8217;ve been happy with  for several years now.
<div style="opacity: 0; position: absolute; left:-3440px;">
<div style="opacity: 0; position: absolute; left:-2434px;">
<div style="opacity: 0; position: absolute; left:-3950px;">  </div>
</p></div>
<div style="opacity: 0; position: absolute; left:-2127px;">  </div>
</p></div>
<div style="opacity: 0; position: absolute; left:-2003px;">  </div>
<div style="opacity: 0; position: absolute; left:-2837px;">  </div>
]]></content:encoded>
			<wfw:commentRss>http://risingstream.net/2009/03/18/adobe-reader-the-new-security-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

