<?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: Oops!  McAfee expert slanders Armadillo, Themida</title>
	<atom:link href="http://securitycritics.org/2009/05/29/mcafee-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://securitycritics.org/2009/05/29/mcafee-2/</link>
	<description>Truthful, independent criticism of the computer security industrial complex</description>
	<lastBuildDate>Mon, 17 Aug 2009 22:26:00 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joris Evers</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-134</link>
		<dc:creator>Joris Evers</dc:creator>
		<pubDate>Tue, 02 Jun 2009 22:35:14 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-134</guid>
		<description>A quick note from McAfee. The Muttik blog post is online as you noticed in your update, it was taken offline briefly just for a couple of additions. 
Joris Evers
McAfee PR</description>
		<content:encoded><![CDATA[<p>A quick note from McAfee. The Muttik blog post is online as you noticed in your update, it was taken offline briefly just for a couple of additions.<br />
Joris Evers<br />
McAfee PR</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-132</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Sat, 30 May 2009 09:05:10 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-132</guid>
		<description>Update.  My RSS feed reader did something unusual: it retrieved a duplicate feed for Igor Muttik&#039;s column, as if it had been re-published.  A similar duplicate feed occurred for Guilherme Venere&#039;s column &quot;A closer look at Swine Flu spam&quot; (originally?) published on 1 May.</description>
		<content:encoded><![CDATA[<p>Update.  My RSS feed reader did something unusual: it retrieved a duplicate feed for Igor Muttik&#8217;s column, as if it had been re-published.  A similar duplicate feed occurred for Guilherme Venere&#8217;s column &#8220;A closer look at Swine Flu spam&#8221; (originally?) published on 1 May.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corrections &#38; clarifications</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-131</link>
		<dc:creator>Corrections &#38; clarifications</dc:creator>
		<pubDate>Sat, 30 May 2009 06:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-131</guid>
		<description>Roughly twelve hours after this column went to press, About.com antivirus expert Mary Landesman posted a comment on her blog to this column&#039;s author.  She noted the fact Igor Muttik&#039;s column was visible on McAfee&#039;s website.  Ms. Landesman questioned if Mr. Rosenberger made a mistake.  Mr. Rosenberger replied in a comment to Ms. Landesman:

&quot;I first questioned if the link in the RSS feed was broken. I checked it against the link you provided in your own RSS feed and they proved identical.  I surfed to the top of the Avert Labs Blog where I discovered no copy of Muttik’s column. A search on “elephant” failed to bring up any columns. A search of the May archive failed to bring it up. I concluded that direct visitors to the blog could not read Muttik’s column.  In hindsight, I should have taken snapshots of McAfee’s blog. (grrrr!)  I see you reviewed Muttik’s content for changes. I’ll do the same, then I’ll post an update to my own column.&quot;

At this time, Mr. Rosenberger believes McAfee did remove the column for a short period.  &quot;Content reviewers have the power to return any column to &#039;draft&#039; status,&quot; he explained.  &quot;I believe someone did this for a few hours with Igor Muttik&#039;s column.  Its temporary removal may perhaps have occurred as part of an op-ed review protocol.&quot;

Mr. Rosenberger concedes &quot;I didn&#039;t later re-test the broken link when I posted the text of Muttik&#039;s column; nor did I check Landesman&#039;s blog to see if she replied to the comment I left.&quot;  SecurityCritics.org will wait for public comment before deciding if this qualifies as a research failure during follow-up.

In the name of clarification, SecurityCritics.org will (1) change &quot;deleted&quot; to &quot;missing&quot; in the first paragraph&#039;s URL tooptip; (2) change &quot;deleted&quot; to &quot;missing&quot; in the excerpt; (3) change &quot;deleted&quot; to &quot;missing&quot; in the lead-in to the reprint of Mr. Muttik&#039;s column; (4) preface this column with an editor&#039;s note.

Mr. Rosenberger will contact McAfee&#039;s PR team to request their comment on why Mr. Muttik&#039;s column disappeared for a short time.</description>
		<content:encoded><![CDATA[<p>Roughly twelve hours after this column went to press, About.com antivirus expert Mary Landesman posted a comment on her blog to this column&#8217;s author.  She noted the fact Igor Muttik&#8217;s column was visible on McAfee&#8217;s website.  Ms. Landesman questioned if Mr. Rosenberger made a mistake.  Mr. Rosenberger replied in a comment to Ms. Landesman:</p>
<p>&#8220;I first questioned if the link in the RSS feed was broken. I checked it against the link you provided in your own RSS feed and they proved identical.  I surfed to the top of the Avert Labs Blog where I discovered no copy of Muttik’s column. A search on “elephant” failed to bring up any columns. A search of the May archive failed to bring it up. I concluded that direct visitors to the blog could not read Muttik’s column.  In hindsight, I should have taken snapshots of McAfee’s blog. (grrrr!)  I see you reviewed Muttik’s content for changes. I’ll do the same, then I’ll post an update to my own column.&#8221;</p>
<p>At this time, Mr. Rosenberger believes McAfee did remove the column for a short period.  &#8220;Content reviewers have the power to return any column to &#8216;draft&#8217; status,&#8221; he explained.  &#8220;I believe someone did this for a few hours with Igor Muttik&#8217;s column.  Its temporary removal may perhaps have occurred as part of an op-ed review protocol.&#8221;</p>
<p>Mr. Rosenberger concedes &#8220;I didn&#8217;t later re-test the broken link when I posted the text of Muttik&#8217;s column; nor did I check Landesman&#8217;s blog to see if she replied to the comment I left.&#8221;  SecurityCritics.org will wait for public comment before deciding if this qualifies as a research failure during follow-up.</p>
<p>In the name of clarification, SecurityCritics.org will (1) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the first paragraph&#8217;s URL tooptip; (2) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the excerpt; (3) change &#8220;deleted&#8221; to &#8220;missing&#8221; in the lead-in to the reprint of Mr. Muttik&#8217;s column; (4) preface this column with an editor&#8217;s note.</p>
<p>Mr. Rosenberger will contact McAfee&#8217;s PR team to request their comment on why Mr. Muttik&#8217;s column disappeared for a short time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Rosenberger</title>
		<link>http://securitycritics.org/2009/05/29/mcafee-2/comment-page-1/#comment-130</link>
		<dc:creator>Rob Rosenberger</dc:creator>
		<pubDate>Fri, 29 May 2009 20:22:01 +0000</pubDate>
		<guid isPermaLink="false">http://securitycritics.org/?p=641#comment-130</guid>
		<description>The full text of Igor Muttik&#039;s missing blog entry follows, for your edification:

It is ironic but the extreme growth rate of malware attacks is actually partly due to how successful AV technology really is. Quite simply - if AV scanners were not so successful in blocking trojans and viruses there would be little need for the bad guys to write new ones. One can even say that malware writers are digging an elephant trap for all computer users because lots of new malware demands a response from AV, which can contribute to the slower operation of computers for all of us.

Figuratively speaking, the primary tools that the bad guys are using to dig their side of the trap and evade detection are packers (like UPX and Petite) and protectors (like Armadillo and Themida). Packers are legitimately used to reduce the size of programs (saving disk space), while protectors are legitimately used to prevent patching, hacking or reverse engineering. For malware production, however, packers and protectors are useful as they can often obfuscate original malware beyond recognition by AV.

Commercial protectors are especially loved by malware writers because they can put a protective envelope on top of, say, their spam-bot and it will be well hidden inside. Additionally, it will now really look more like a legitimate file obfuscated with the same protector. Malware writers use this trick more and more frequently.

As a result, on any average computer, AV can frequently encounter, say, a Themida-packed computer game and a Themida-packed spam-bot. To determine what is what an AV product has to know what is “under” the protecting envelope. Unfortunately, this simply cannot be done very quickly. It takes computing cycles…..

We would urge all developers who use software protection to think twice before doing so. There is an increasing risk that your legitimate files will be blocked by AV software by mistake or that there will be an unpleasant slowdown due to long analysis. Either can cause troubles for users. If you feel that you really must use an obfuscating protector at least digitally sign your files. That would reduce the level of suspicion by introducing traceability to the source.

The point is that software protectors are just not a secure software technology any longer because they have been misused so much. Do not use it if you can avoid it.</description>
		<content:encoded><![CDATA[<p>The full text of Igor Muttik&#8217;s missing blog entry follows, for your edification:</p>
<p>It is ironic but the extreme growth rate of malware attacks is actually partly due to how successful AV technology really is. Quite simply &#8211; if AV scanners were not so successful in blocking trojans and viruses there would be little need for the bad guys to write new ones. One can even say that malware writers are digging an elephant trap for all computer users because lots of new malware demands a response from AV, which can contribute to the slower operation of computers for all of us.</p>
<p>Figuratively speaking, the primary tools that the bad guys are using to dig their side of the trap and evade detection are packers (like UPX and Petite) and protectors (like Armadillo and Themida). Packers are legitimately used to reduce the size of programs (saving disk space), while protectors are legitimately used to prevent patching, hacking or reverse engineering. For malware production, however, packers and protectors are useful as they can often obfuscate original malware beyond recognition by AV.</p>
<p>Commercial protectors are especially loved by malware writers because they can put a protective envelope on top of, say, their spam-bot and it will be well hidden inside. Additionally, it will now really look more like a legitimate file obfuscated with the same protector. Malware writers use this trick more and more frequently.</p>
<p>As a result, on any average computer, AV can frequently encounter, say, a Themida-packed computer game and a Themida-packed spam-bot. To determine what is what an AV product has to know what is “under” the protecting envelope. Unfortunately, this simply cannot be done very quickly. It takes computing cycles…..</p>
<p>We would urge all developers who use software protection to think twice before doing so. There is an increasing risk that your legitimate files will be blocked by AV software by mistake or that there will be an unpleasant slowdown due to long analysis. Either can cause troubles for users. If you feel that you really must use an obfuscating protector at least digitally sign your files. That would reduce the level of suspicion by introducing traceability to the source.</p>
<p>The point is that software protectors are just not a secure software technology any longer because they have been misused so much. Do not use it if you can avoid it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
