<?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: Anti-Debugging Series &#8211; Part III</title>
	<atom:link href="http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/</link>
	<description>Application security testing, analysis, and metrics</description>
	<lastBuildDate>Mon, 01 Mar 2010 15:54:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jn</title>
		<link>http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/comment-page-1/#comment-3297</link>
		<dc:creator>jn</dc:creator>
		<pubDate>Tue, 23 Feb 2010 03:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=589#comment-3297</guid>
		<description>&quot;If a debugger is attached and we pass in 0x11 to NtSetInformationProcess, our process will immediately detach any attached debugger and terminate the process.&quot;
This statement is not correct:
1) you are actually referring to NtSetInformationThread
2) the process is not terminated but debug events for the specified thread are not received by the debugger anymore.</description>
		<content:encoded><![CDATA[<p>&#8220;If a debugger is attached and we pass in 0&#215;11 to NtSetInformationProcess, our process will immediately detach any attached debugger and terminate the process.&#8221;<br />
This statement is not correct:<br />
1) you are actually referring to NtSetInformationThread<br />
2) the process is not terminated but debug events for the specified thread are not received by the debugger anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HuRrIcAnE</title>
		<link>http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/comment-page-1/#comment-2502</link>
		<dc:creator>HuRrIcAnE</dc:creator>
		<pubDate>Sat, 31 Jan 2009 04:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=589#comment-2502</guid>
		<description>I&#039;m one of the fan here, and I wanna said that these type of subjects are increduble .. And I agree the abover&#039;s comment that these functions are not that much difficult to bypass its. But what I&#039;m trying to said that the Art of REC is not just for having fun on CRACKING programs and protections, It&#039;s like to learn, to improve something, even if it&#039;s useless.

what I&#039;m agree here is that many private and public schemes will at less use this art of protection in somehow, somewhere to but it at that greatfull steps .

I hope Mr. Shields to continue your path and I&#039;m one of your followers.

Thanks</description>
		<content:encoded><![CDATA[<p>I&#8217;m one of the fan here, and I wanna said that these type of subjects are increduble .. And I agree the abover&#8217;s comment that these functions are not that much difficult to bypass its. But what I&#8217;m trying to said that the Art of REC is not just for having fun on CRACKING programs and protections, It&#8217;s like to learn, to improve something, even if it&#8217;s useless.</p>
<p>what I&#8217;m agree here is that many private and public schemes will at less use this art of protection in somehow, somewhere to but it at that greatfull steps .</p>
<p>I hope Mr. Shields to continue your path and I&#8217;m one of your followers.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A John Doe</title>
		<link>http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/comment-page-1/#comment-2429</link>
		<dc:creator>A John Doe</dc:creator>
		<pubDate>Thu, 08 Jan 2009 23:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=589#comment-2429</guid>
		<description>Meh, API anti-debugging techniques are fairly useless. Reverse engineers are very familiar with them and they are exceedingly easy to bypass. Might as well use them a bit anyway because they are so easy to implement, but they should be a part of a MUCH MUCH stronger defensive scheme. If they form a notable percentage of the defensive scheme, time is being wasted that could be spent making the defended asset better IMO.</description>
		<content:encoded><![CDATA[<p>Meh, API anti-debugging techniques are fairly useless. Reverse engineers are very familiar with them and they are exceedingly easy to bypass. Might as well use them a bit anyway because they are so easy to implement, but they should be a part of a MUCH MUCH stronger defensive scheme. If they form a notable percentage of the defensive scheme, time is being wasted that could be spent making the defended asset better IMO.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Leyshon</title>
		<link>http://www.veracode.com/blog/2009/01/anti-debugging-series-part-iii/comment-page-1/#comment-2428</link>
		<dc:creator>Adam Leyshon</dc:creator>
		<pubDate>Thu, 08 Jan 2009 14:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=589#comment-2428</guid>
		<description>Very informative, I wish MS would document these functions better as they can be quite handy sometimes.</description>
		<content:encoded><![CDATA[<p>Very informative, I wish MS would document these functions better as they can be quite handy sometimes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
