<?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: McAfee&#039;s newest weapon in the fight against malware</title>
	<atom:link href="http://blogs.mcafee.com/mcafee-labs/2006/11/06/mcafees-newest-weapon-in-the-fight-against-malware/feed" rel="self" type="application/rss+xml" />
	<link>http://blogs.mcafee.com/mcafee-labs/mcafees-newest-weapon-in-the-fight-against-malware</link>
	<description></description>
	<lastBuildDate>Wed, 16 May 2012 22:25:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jon Chorney</title>
		<link>http://blogs.mcafee.com/mcafee-labs/mcafees-newest-weapon-in-the-fight-against-malware/comment-page-1#comment-6189</link>
		<dc:creator>Jon Chorney</dc:creator>
		<pubDate>Fri, 10 Nov 2006 21:42:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.labs.com/research/blog/?p=126#comment-6189</guid>
		<description>A pity no attempt was made to let users know in advance of this update. In the past, engine updates have been released with deleterious results in complex environments, such as our Accounting and Consulting firm. Though I am on the Avert mailing list, I got no such information.
Having been burned before, I have learned the value of testing before rolling new sofwtare out in a production environment.
This time we were lucky - so far, no one has reported any anomalies of which I am aware.
However, in self-defense, I have now disabled the auto-update on all stations for anything except the DAT files.
I&#039;d rather be late to the party than crash because McAfee chose not to tell me road had been changed!</description>
		<content:encoded><![CDATA[<p>A pity no attempt was made to let users know in advance of this update. In the past, engine updates have been released with deleterious results in complex environments, such as our Accounting and Consulting firm. Though I am on the Avert mailing list, I got no such information.<br />
Having been burned before, I have learned the value of testing before rolling new sofwtare out in a production environment.<br />
This time we were lucky &#8211; so far, no one has reported any anomalies of which I am aware.<br />
However, in self-defense, I have now disabled the auto-update on all stations for anything except the DAT files.<br />
I&#8217;d rather be late to the party than crash because McAfee chose not to tell me road had been changed!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

