<?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 II</title>
	<atom:link href="http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/</link>
	<description>Application security testing, analysis, and metrics</description>
	<lastBuildDate>Thu, 09 Feb 2012 11:59:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: coz</title>
		<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/comment-page-1/#comment-7608</link>
		<dc:creator>coz</dc:creator>
		<pubDate>Fri, 03 Jun 2011 21:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=530#comment-7608</guid>
		<description>Yeah I can&#039;t get it to work either. I&#039;m on a win7 computer if that has anything to do with it but I doubt it. I wouldn&#039;t use it as an anti-debug.</description>
		<content:encoded><![CDATA[<p>Yeah I can&#8217;t get it to work either. I&#8217;m on a win7 computer if that has anything to do with it but I doubt it. I wouldn&#8217;t use it as an anti-debug.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian</title>
		<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/comment-page-1/#comment-5565</link>
		<dc:creator>Adrian</dc:creator>
		<pubDate>Sun, 15 Aug 2010 17:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=530#comment-5565</guid>
		<description>Hi, Tyler.

I tried your approach to detect debugger by calling OutputDebugString and checking LastError value. It seems to me that value never changes, no matter if there was debugger attached or not. Are you sure this approach is correct? Frankly, I didn&#039;t found anything in OutputDebugString help page about setting LastError value.</description>
		<content:encoded><![CDATA[<p>Hi, Tyler.</p>
<p>I tried your approach to detect debugger by calling OutputDebugString and checking LastError value. It seems to me that value never changes, no matter if there was debugger attached or not. Are you sure this approach is correct? Frankly, I didn&#8217;t found anything in OutputDebugString help page about setting LastError value.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler Shields</title>
		<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/comment-page-1/#comment-2426</link>
		<dc:creator>Tyler Shields</dc:creator>
		<pubDate>Wed, 07 Jan 2009 17:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=530#comment-2426</guid>
		<description>@cd-MaN Definitely a very interesting technique. In this series I&#039;m outlining a small selection of methods from each of the different anti-debugging areas defined. There are certainly other ways, one of which you outline in your link. Thanks for the information!

@daniel reznick That might be another series down the line. At this point I plan on writing up interesting methods in which developers can add layers to the security of their application. As we all know there is no fool proof method of securing client side code, these can all be bypassed. People can feel free to leave comments on bypassing techniques if they are so inclined.</description>
		<content:encoded><![CDATA[<p>@cd-MaN Definitely a very interesting technique. In this series I&#8217;m outlining a small selection of methods from each of the different anti-debugging areas defined. There are certainly other ways, one of which you outline in your link. Thanks for the information!</p>
<p>@daniel reznick That might be another series down the line. At this point I plan on writing up interesting methods in which developers can add layers to the security of their application. As we all know there is no fool proof method of securing client side code, these can all be bypassed. People can feel free to leave comments on bypassing techniques if they are so inclined.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: daniel reznick</title>
		<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/comment-page-1/#comment-2424</link>
		<dc:creator>daniel reznick</dc:creator>
		<pubDate>Wed, 07 Jan 2009 12:55:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=530#comment-2424</guid>
		<description>How about including information on how to defeat these techniques as well?  It would make your series much more interesting.</description>
		<content:encoded><![CDATA[<p>How about including information on how to defeat these techniques as well?  It would make your series much more interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cd-MaN</title>
		<link>http://www.veracode.com/blog/2008/12/anti-debugging-series-part-ii/comment-page-1/#comment-2415</link>
		<dc:creator>Cd-MaN</dc:creator>
		<pubDate>Fri, 02 Jan 2009 09:25:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.veracode.com/blog/?p=530#comment-2415</guid>
		<description>Here is an other &quot;API based&quot; way to detect debuggers: http://hype-free.blogspot.com/2009/01/detecting-user-mode-debuggers-under.html

Best regards.</description>
		<content:encoded><![CDATA[<p>Here is an other &#8220;API based&#8221; way to detect debuggers: <a href="http://hype-free.blogspot.com/2009/01/detecting-user-mode-debuggers-under.html" rel="nofollow">http://hype-free.blogspot.com/2009/01/detecting-user-mode-debuggers-under.html</a></p>
<p>Best regards.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

