<?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 endeavormac</title>
	<atom:link href="http://myw3b.net/blog/index.php/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://myw3b.net/blog</link>
	<description>Code, Thoughts, Stuff</description>
	<lastBuildDate>Fri, 23 Apr 2010 20:23:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on Making Perfect Rainbow Tables Faster by Mike</title>
		<link>http://myw3b.net/blog/index.php/2010/03/making-perfect-rainbow-tables-faster/comment-page-1/#comment-87</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 23 Apr 2010 20:23:31 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=130#comment-87</guid>
		<description>Can you contact me?  I&#039;m currently using project-rainbowcrack&#039;s rtgen to build a large number of rainbow tables for later perfection.  Having a tool such as yours would be immensely helpful.</description>
		<content:encoded><![CDATA[<p>Can you contact me?  I&#8217;m currently using project-rainbowcrack&#8217;s rtgen to build a large number of rainbow tables for later perfection.  Having a tool such as yours would be immensely helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by endeavormac</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-74</link>
		<dc:creator>endeavormac</dc:creator>
		<pubDate>Tue, 13 Apr 2010 17:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-74</guid>
		<description>BX is simply the 16 least significant bits of the EBX register. Actually, I&#039;m not entirely sure if it&#039;s the least or most significant bits. In any case, you can use BX to access the 16 (most&#124;least) significant bits of the EBX register (assuming a current 32bit intel CPU).

This url may provide some enlightenment: http://www.arl.wustl.edu/~lockwood/class/cs306/books/artofasm/Chapter_4/CH04-1.html#HEADING1-42

A short is 16 bits, so make sure your printf string is adjusted (You&#039;ll need %h) http://www.opengroup.org/onlinepubs/000095399/functions/printf.html

So if you want to print out BX, you&#039;ll need to push BX onto the stack, followed by a pointer to a string &quot;%h&quot;, and then call printf. Because BX is only 16 bits and, assuming a 32 bit platform, you&#039;re pushing BX onto a 32 bit word, you may want to mov a 0x0 into that stack space first, or otherwise insure that it is empty, to account for whatever may already be in place of the other 16 bits. I&#039;m not positive that would be necessary, you would have to experiment.

You may have better luck creating a simple C app that does all this and then &quot;gcc source.c -S&quot; to see what you get.</description>
		<content:encoded><![CDATA[<p>BX is simply the 16 least significant bits of the EBX register. Actually, I&#8217;m not entirely sure if it&#8217;s the least or most significant bits. In any case, you can use BX to access the 16 (most|least) significant bits of the EBX register (assuming a current 32bit intel CPU).</p>
<p>This url may provide some enlightenment: <a href="http://www.arl.wustl.edu/~lockwood/class/cs306/books/artofasm/Chapter_4/CH04-1.html#HEADING1-42" rel="nofollow">http://www.arl.wustl.edu/~lockwood/class/cs306/books/artofasm/Chapter_4/CH04-1.html#HEADING1-42</a></p>
<p>A short is 16 bits, so make sure your printf string is adjusted (You&#8217;ll need %h) <a href="http://www.opengroup.org/onlinepubs/000095399/functions/printf.html" rel="nofollow">http://www.opengroup.org/onlinepubs/000095399/functions/printf.html</a></p>
<p>So if you want to print out BX, you&#8217;ll need to push BX onto the stack, followed by a pointer to a string &#8220;%h&#8221;, and then call printf. Because BX is only 16 bits and, assuming a 32 bit platform, you&#8217;re pushing BX onto a 32 bit word, you may want to mov a 0&#215;0 into that stack space first, or otherwise insure that it is empty, to account for whatever may already be in place of the other 16 bits. I&#8217;m not positive that would be necessary, you would have to experiment.</p>
<p>You may have better luck creating a simple C app that does all this and then &#8220;gcc source.c -S&#8221; to see what you get.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by Min</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-69</link>
		<dc:creator>Min</dc:creator>
		<pubDate>Tue, 06 Apr 2010 07:32:37 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-69</guid>
		<description>is there a way to make the output 16 bit instead of 32 bit? For example i want bx instead of ebx</description>
		<content:encoded><![CDATA[<p>is there a way to make the output 16 bit instead of 32 bit? For example i want bx instead of ebx</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1.1, Reddit Follow-up by nobody</title>
		<link>http://myw3b.net/blog/index.php/2009/10/x86-fcp-1-1-reddit-follow-up/comment-page-1/#comment-11</link>
		<dc:creator>nobody</dc:creator>
		<pubDate>Wed, 18 Nov 2009 08:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=82#comment-11</guid>
		<description>Here&#039;s a very similar to yours but much more complete tutorial in russian.  Don&#039;t you know russian by chance?  It would be great if it would be traslated to english!
&lt;a href=&quot;http://ru.wikibooks.org/wiki/%D0%90%D1%81%D1%81%D0%B5%D0%BC%D0%B1%D0%BB%D0%B5%D1%80_%D0%B2_Linux_%D0%B4%D0%BB%D1%8F_%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%81%D1%82%D0%BE%D0%B2_C&quot; rel=&quot;nofollow&quot;&gt;link&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Here&#8217;s a very similar to yours but much more complete tutorial in russian.  Don&#8217;t you know russian by chance?  It would be great if it would be traslated to english!<br />
<a href="http://ru.wikibooks.org/wiki/%D0%90%D1%81%D1%81%D0%B5%D0%BC%D0%B1%D0%BB%D0%B5%D1%80_%D0%B2_Linux_%D0%B4%D0%BB%D1%8F_%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%81%D1%82%D0%BE%D0%B2_C" rel="nofollow">link</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1.1, Reddit Follow-up by endeavormac</title>
		<link>http://myw3b.net/blog/index.php/2009/10/x86-fcp-1-1-reddit-follow-up/comment-page-1/#comment-10</link>
		<dc:creator>endeavormac</dc:creator>
		<pubDate>Sun, 08 Nov 2009 16:10:07 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=82#comment-10</guid>
		<description>I&#039;m glad you found it useful. I&#039;ve started on part 2, but other things have gotten into the way of me finishing it.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you found it useful. I&#8217;ve started on part 2, but other things have gotten into the way of me finishing it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1.1, Reddit Follow-up by Tom</title>
		<link>http://myw3b.net/blog/index.php/2009/10/x86-fcp-1-1-reddit-follow-up/comment-page-1/#comment-9</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 08 Nov 2009 06:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=82#comment-9</guid>
		<description>Just wanted to thank you for your tutorial.  I found myself staring at assembly and forgetting all I had ever learned about it, and you helped me immensely. I was even able to make a blog post about it http://ritter.vg/n.php?page=code_adventures_clr2</description>
		<content:encoded><![CDATA[<p>Just wanted to thank you for your tutorial.  I found myself staring at assembly and forgetting all I had ever learned about it, and you helped me immensely. I was even able to make a blog post about it <a href="http://ritter.vg/n.php?page=code_adventures_clr2" rel="nofollow">http://ritter.vg/n.php?page=code_adventures_clr2</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by inter</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-8</link>
		<dc:creator>inter</dc:creator>
		<pubDate>Thu, 29 Oct 2009 22:49:53 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-8</guid>
		<description>gcc -O0 -g -c one.c
objdump -C -M intel -S one.o

This gives an even better result (asm code with source code side by side).</description>
		<content:encoded><![CDATA[<p>gcc -O0 -g -c one.c<br />
objdump -C -M intel -S one.o</p>
<p>This gives an even better result (asm code with source code side by side).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by endeavormac</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-6</link>
		<dc:creator>endeavormac</dc:creator>
		<pubDate>Fri, 23 Oct 2009 21:13:23 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-6</guid>
		<description>I didn&#039;t know about this feature for gcc, and this is awesome. Thanks!</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t know about this feature for gcc, and this is awesome. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by jldugger</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-5</link>
		<dc:creator>jldugger</dc:creator>
		<pubDate>Fri, 23 Oct 2009 20:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-5</guid>
		<description>gcc -S -masm=intel -o one.asm one.c

For writing your own code, use the compiler instead of the object analyzer. You get jump targets, which is damn handy.


Also stack alignment has more to do with processor design than memory segmentation.</description>
		<content:encoded><![CDATA[<p>gcc -S -masm=intel -o one.asm one.c</p>
<p>For writing your own code, use the compiler instead of the object analyzer. You get jump targets, which is damn handy.</p>
<p>Also stack alignment has more to do with processor design than memory segmentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on x86 Assembly for C Programmers 1 by drill</title>
		<link>http://myw3b.net/blog/index.php/2009/10/assembly-for-c-programmers-1/comment-page-1/#comment-4</link>
		<dc:creator>drill</dc:creator>
		<pubDate>Fri, 23 Oct 2009 19:27:48 +0000</pubDate>
		<guid isPermaLink="false">http://myw3b.net/blog/?p=7#comment-4</guid>
		<description>Two requests:

1) Give this series its own special tag on your blog so it&#039;s easy to access the whole thing when you&#039;re done ;)

2) some ideas of simple projects a beginner could do that are actually doable
  a) in assembly
  b) by someone with the knowledge level this is aimed at.

I&#039;m bookmarking your site.</description>
		<content:encoded><![CDATA[<p>Two requests:</p>
<p>1) Give this series its own special tag on your blog so it&#8217;s easy to access the whole thing when you&#8217;re done <img src='http://myw3b.net/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>2) some ideas of simple projects a beginner could do that are actually doable<br />
  a) in assembly<br />
  b) by someone with the knowledge level this is aimed at.</p>
<p>I&#8217;m bookmarking your site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
