<?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 for Spare Clock Cycles</title>
	<atom:link href="http://spareclockcycles.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://spareclockcycles.org</link>
	<description>Hacking is freedom.</description>
	<lastBuildDate>Tue, 21 Feb 2012 05:22:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on 1 Flash Gallery: Arbitrary File Upload by Eduardo &#124; Descargar Programas</title>
		<link>http://spareclockcycles.org/2011/09/06/flash-gallery-arbitrary-file-upload/comment-page-1/#comment-1562</link>
		<dc:creator>Eduardo &#124; Descargar Programas</dc:creator>
		<pubDate>Tue, 21 Feb 2012 05:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=682#comment-1562</guid>
		<description>gracias por la informacion, esta muy entrenida

saludos</description>
		<content:encoded><![CDATA[<p>gracias por la informacion, esta muy entrenida</p>
<p>saludos</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stack Necromancy: Defeating Debuggers By Raising the Dead by supernothing</title>
		<link>http://spareclockcycles.org/2012/02/14/stack-necromancy-defeating-debuggers-by-raising-the-dead/comment-page-1/#comment-1558</link>
		<dc:creator>supernothing</dc:creator>
		<pubDate>Tue, 14 Feb 2012 15:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=785#comment-1558</guid>
		<description>@Mario
Thanks!

Still a bit green when it comes to RE, so it&#039;s nice to hear that I&#039;m probably not blindly repackaging an often used trick. I&#039;ve also used that reference before, one of my favorites as well.

The SEH route sounds interesting, hadn&#039;t considered it yet. I have been wondering if there was a good, predictable way to nudge the stack into different states, and that might be it. I&#039;ll have to poke around with that.</description>
		<content:encoded><![CDATA[<p>@Mario<br />
Thanks!</p>
<p>Still a bit green when it comes to RE, so it&#8217;s nice to hear that I&#8217;m probably not blindly repackaging an often used trick. I&#8217;ve also used that reference before, one of my favorites as well.</p>
<p>The SEH route sounds interesting, hadn&#8217;t considered it yet. I have been wondering if there was a good, predictable way to nudge the stack into different states, and that might be it. I&#8217;ll have to poke around with that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Stack Necromancy: Defeating Debuggers By Raising the Dead by Mario Vilas</title>
		<link>http://spareclockcycles.org/2012/02/14/stack-necromancy-defeating-debuggers-by-raising-the-dead/comment-page-1/#comment-1557</link>
		<dc:creator>Mario Vilas</dc:creator>
		<pubDate>Tue, 14 Feb 2012 14:14:05 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=785#comment-1557</guid>
		<description>Great post! :)

I don&#039;t recall this being ever documented as an antidebug technique before, and it&#039;s not listed in my favorite reference either: http://pferrie.tripod.com/papers/unpackers.pdf

I did see this mentioned in some assembly programmer forums like the MASM32 forum, but IMHO nobody came up with the idea of using it as an antidebug trick - people simply stumbled upon this behavior when trying to debug their own applications. It&#039;s easy to mess up the stack when you&#039;re coding in pure ASM! :)

This also happens when an exception is thrown, since the SEH handlers (and the SEH handling mechanism itself) will also use the current thread stack. Possibly usermode APCs do this as well, but I haven&#039;t tested it myself.</description>
		<content:encoded><![CDATA[<p>Great post! <img src='http://spareclockcycles.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>I don&#8217;t recall this being ever documented as an antidebug technique before, and it&#8217;s not listed in my favorite reference either: <a href="http://pferrie.tripod.com/papers/unpackers.pdf" rel="nofollow">http://pferrie.tripod.com/papers/unpackers.pdf</a></p>
<p>I did see this mentioned in some assembly programmer forums like the MASM32 forum, but IMHO nobody came up with the idea of using it as an antidebug trick &#8211; people simply stumbled upon this behavior when trying to debug their own applications. It&#8217;s easy to mess up the stack when you&#8217;re coding in pure ASM! <img src='http://spareclockcycles.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>This also happens when an exception is thrown, since the SEH handlers (and the SEH handling mechanism itself) will also use the current thread stack. Possibly usermode APCs do this as well, but I haven&#8217;t tested it myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Avoiding AV Detection by Stack Necromancy: Defeating Debuggers By Raising the Dead &#171; Spare Clock Cycles</title>
		<link>http://spareclockcycles.org/2010/11/27/avoiding-av-detection/comment-page-1/#comment-1556</link>
		<dc:creator>Stack Necromancy: Defeating Debuggers By Raising the Dead &#171; Spare Clock Cycles</dc:creator>
		<pubDate>Tue, 14 Feb 2012 12:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=448#comment-1556</guid>
		<description>[...] from being dynamically unpacked in one of these environments. In a previous post, I talked about writing a simple crypter to bypass AV. In it, I used a timing attack to defeat emulation. We can see from these VirusTotal [...]</description>
		<content:encoded><![CDATA[<p>[...] from being dynamically unpacked in one of these environments. In a previous post, I talked about writing a simple crypter to bypass AV. In it, I used a timing attack to defeat emulation. We can see from these VirusTotal [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exploiting an IP Camera Control Protocol: Redux by supernothing</title>
		<link>http://spareclockcycles.org/2012/01/23/exploiting-an-ip-camera-control-protocol-redux/comment-page-1/#comment-1555</link>
		<dc:creator>supernothing</dc:creator>
		<pubDate>Thu, 09 Feb 2012 06:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=769#comment-1555</guid>
		<description>I will do that from now on, thanks!</description>
		<content:encoded><![CDATA[<p>I will do that from now on, thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exploiting an IP Camera Control Protocol: Redux by Mechael</title>
		<link>http://spareclockcycles.org/2012/01/23/exploiting-an-ip-camera-control-protocol-redux/comment-page-1/#comment-1554</link>
		<dc:creator>Mechael</dc:creator>
		<pubDate>Wed, 08 Feb 2012 04:34:15 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=769#comment-1554</guid>
		<description>Good stuffs man..  you should post some of your finding on http://news.ycombinator.com/..   I think some of the devs out there would appreciate your efforts...  I know I do..  :)   Thanks,..</description>
		<content:encoded><![CDATA[<p>Good stuffs man..  you should post some of your finding on <a href="http://news.ycombinator.com/." rel="nofollow">http://news.ycombinator.com/.</a>.   I think some of the devs out there would appreciate your efforts&#8230;  I know I do..  <img src='http://spareclockcycles.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />    Thanks,..</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Explo(it&#124;r)ing the WordPress Extension Repos by luxe annonces</title>
		<link>http://spareclockcycles.org/2011/09/18/exploitring-the-wordpress-extension-repos/comment-page-1/#comment-1553</link>
		<dc:creator>luxe annonces</dc:creator>
		<pubDate>Sun, 05 Feb 2012 13:00:11 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=723#comment-1553</guid>
		<description>$author Merci pour l&#039;article</description>
		<content:encoded><![CDATA[<p>$author Merci pour l&#8217;article</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exploiting an IP Camera Control Protocol: Redux by Week 4 in Review &#8211; 2012 &#124; Infosec Events</title>
		<link>http://spareclockcycles.org/2012/01/23/exploiting-an-ip-camera-control-protocol-redux/comment-page-1/#comment-1550</link>
		<dc:creator>Week 4 in Review &#8211; 2012 &#124; Infosec Events</dc:creator>
		<pubDate>Tue, 31 Jan 2012 05:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=769#comment-1550</guid>
		<description>[...] Exploiting an IP Camera Control Protocol: Redux &#8211; spareclockcycles.org Last May, I wrote about a remote password disclosure vulnerability I found in a proprietary protocol used to control ~150 different low-end IP cameras. The exploit I wrote was tested on the Rosewill RXS-3211, a rebranded version of the Edimax IC3005. [...]</description>
		<content:encoded><![CDATA[<p>[...] Exploiting an IP Camera Control Protocol: Redux &#8211; spareclockcycles.org Last May, I wrote about a remote password disclosure vulnerability I found in a proprietary protocol used to control ~150 different low-end IP cameras. The exploit I wrote was tested on the Rosewill RXS-3211, a rebranded version of the Edimax IC3005. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Exploiting an IP Camera Control Protocol by Exploiting an IP Camera Control Protocol: Redux &#171; Spare Clock Cycles</title>
		<link>http://spareclockcycles.org/2011/05/23/exploiting-an-ip-camera-control-protocol/comment-page-1/#comment-1548</link>
		<dc:creator>Exploiting an IP Camera Control Protocol: Redux &#171; Spare Clock Cycles</dc:creator>
		<pubDate>Mon, 23 Jan 2012 22:59:45 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=655#comment-1548</guid>
		<description>[...] May, I wrote about a remote password disclosure vulnerability I found in a proprietary protocol used to control [...]</description>
		<content:encoded><![CDATA[<p>[...] May, I wrote about a remote password disclosure vulnerability I found in a proprietary protocol used to control [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 1 Flash Gallery: Arbitrary File Upload by Dez</title>
		<link>http://spareclockcycles.org/2011/09/06/flash-gallery-arbitrary-file-upload/comment-page-1/#comment-1545</link>
		<dc:creator>Dez</dc:creator>
		<pubDate>Wed, 21 Dec 2011 23:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://spareclockcycles.org/?p=682#comment-1545</guid>
		<description>I just dealt with this. spammers uploaded a file into a tmp directly that executing mailing commands and sent out a shit ton of mail from my server. It was only when I had deleted the plugin and it&#039;s directories that the mailings stopped (and I stopped getting overloaded with Mailer Daemons)</description>
		<content:encoded><![CDATA[<p>I just dealt with this. spammers uploaded a file into a tmp directly that executing mailing commands and sent out a shit ton of mail from my server. It was only when I had deleted the plugin and it&#8217;s directories that the mailings stopped (and I stopped getting overloaded with Mailer Daemons)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

