<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for mishou.org</title>
	<atom:link href="http://mishou.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://mishou.org</link>
	<description>A site about learning.</description>
	<lastBuildDate>Tue, 27 Dec 2011 23:32:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Insecure Programming by Example: abo4.c POINTER MADNESS by InsecureProgramming – ABOF – 4 &#171; secpractice</title>
		<link>http://mishou.org/2010/08/09/insecure-programming-by-example-abo4-c-pointer-madness/#comment-109</link>
		<dc:creator><![CDATA[InsecureProgramming – ABOF – 4 &#171; secpractice]]></dc:creator>
		<pubDate>Tue, 27 Dec 2011 23:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=220#comment-109</guid>
		<description><![CDATA[[...] Like many other problems there can be multiple ways to solve this one. In one approach, the second strcpy() is used to write the address of an environment variable which contains the shellcode. http://mishou.org/2010/08/09/insecure-programming-by-example-abo4-c-pointer-madness/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Like many other problems there can be multiple ways to solve this one. In one approach, the second strcpy() is used to write the address of an environment variable which contains the shellcode. <a href="http://mishou.org/2010/08/09/insecure-programming-by-example-abo4-c-pointer-madness/" rel="nofollow">http://mishou.org/2010/08/09/insecure-programming-by-example-abo4-c-pointer-madness/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Insecure Programming by Example: abo2.c, not vulnerable&#8230;o rly? by InsecureProgramming – ABOF – 2 &#171; secpractice</title>
		<link>http://mishou.org/2010/02/13/insecure-programming-by-example-abo2-c-not-vulnerable-o-rly/#comment-108</link>
		<dc:creator><![CDATA[InsecureProgramming – ABOF – 2 &#171; secpractice]]></dc:creator>
		<pubDate>Mon, 26 Dec 2011 10:16:36 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=148#comment-108</guid>
		<description><![CDATA[[...] is the link http://mishou.org/2010/02/13/insecure-programming-by-example-abo2-c-not-vulnerable-o-rly/ Share this:TwitterFacebookLike this:LikeBe the first to like this post.    Categories: [...]]]></description>
		<content:encoded><![CDATA[<p>[...] is the link <a href="http://mishou.org/2010/02/13/insecure-programming-by-example-abo2-c-not-vulnerable-o-rly/" rel="nofollow">http://mishou.org/2010/02/13/insecure-programming-by-example-abo2-c-not-vulnerable-o-rly/</a> Share this:TwitterFacebookLike this:LikeBe the first to like this post.    Categories: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Insecure Programming by Example: shellcode &amp; stack5.c by 2010 in review &#171; mishou.org</title>
		<link>http://mishou.org/2009/12/12/insecure-programming-by-example-shellcode-stack5-c/#comment-102</link>
		<dc:creator><![CDATA[2010 in review &#171; mishou.org]]></dc:creator>
		<pubDate>Sun, 02 Jan 2011 15:15:37 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=96#comment-102</guid>
		<description><![CDATA[[...] Insecure Programming by Example: shellcode &amp; stack5.c December 2009 1 comment [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Insecure Programming by Example: shellcode &amp; stack5.c December 2009 1 comment [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Insecure Programming by Example &#8211; controlling EIP, stack4.c by 2010 in review &#171; mishou.org</title>
		<link>http://mishou.org/2009/12/07/insecure-programming-by-example-controlling-eip-stack4-c/#comment-101</link>
		<dc:creator><![CDATA[2010 in review &#171; mishou.org]]></dc:creator>
		<pubDate>Sun, 02 Jan 2011 15:15:34 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=68#comment-101</guid>
		<description><![CDATA[[...] Posts (24-48 hrs.) Insecure Programming by Example - controlling EIP, stack4.c      &#171; Insecure Programming by Example: abo6/7/8 Ménage [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Posts (24-48 hrs.) Insecure Programming by Example &#8211; controlling EIP, stack4.c      &laquo; Insecure Programming by Example: abo6/7/8 Ménage [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Insecure Programming by Example: Advanced Buffer Overflows 1 by 2010 in review &#171; mishou.org</title>
		<link>http://mishou.org/2009/12/23/insecure-programming-by-example-advanced-buffer-overflows-1/#comment-100</link>
		<dc:creator><![CDATA[2010 in review &#171; mishou.org]]></dc:creator>
		<pubDate>Sun, 02 Jan 2011 15:15:32 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=122#comment-100</guid>
		<description><![CDATA[[...] Insecure Programming by Example: Advanced Buffer Overflows 1 December 2009 5 comments and 1 Like on WordPress.com, 4 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Insecure Programming by Example: Advanced Buffer Overflows 1 December 2009 5 comments and 1 Like on WordPress.com, 4 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on automagic Python urllib basic HTTP authentication by 2010 in review &#171; mishou.org</title>
		<link>http://mishou.org/2009/12/10/automagic-python-urllib-basic-http-authentication/#comment-99</link>
		<dc:creator><![CDATA[2010 in review &#171; mishou.org]]></dc:creator>
		<pubDate>Sun, 02 Jan 2011 15:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=88#comment-99</guid>
		<description><![CDATA[[...] automagic Python urllib basic HTTP authentication December 2009 3 [...]]]></description>
		<content:encoded><![CDATA[<p>[...] automagic Python urllib basic HTTP authentication December 2009 3 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive DNS mining from PCAP with dpkt &amp; Python by 2010 in review &#171; mishou.org</title>
		<link>http://mishou.org/2010/04/13/passive-dns-mining-from-pcap-with-dpkt-python/#comment-98</link>
		<dc:creator><![CDATA[2010 in review &#171; mishou.org]]></dc:creator>
		<pubDate>Sun, 02 Jan 2011 15:15:26 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=210#comment-98</guid>
		<description><![CDATA[[...] The busiest day of the year was October 28th with 77 views. The most popular post that day was Passive DNS mining from PCAP with dpkt &amp; Python. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The busiest day of the year was October 28th with 77 views. The most popular post that day was Passive DNS mining from PCAP with dpkt &amp; Python. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive DNS mining from PCAP with dpkt &amp; Python by alfonso</title>
		<link>http://mishou.org/2010/04/13/passive-dns-mining-from-pcap-with-dpkt-python/#comment-92</link>
		<dc:creator><![CDATA[alfonso]]></dc:creator>
		<pubDate>Fri, 03 Dec 2010 23:13:03 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=210#comment-92</guid>
		<description><![CDATA[12 for ts, buf in pcap:]]></description>
		<content:encoded><![CDATA[<p>12 for ts, buf in pcap:</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive DNS mining from PCAP with dpkt &amp; Python by alfonso</title>
		<link>http://mishou.org/2010/04/13/passive-dns-mining-from-pcap-with-dpkt-python/#comment-91</link>
		<dc:creator><![CDATA[alfonso]]></dc:creator>
		<pubDate>Fri, 03 Dec 2010 23:11:24 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=210#comment-91</guid>
		<description><![CDATA[Traceback (most recent call last):
  File &quot;./parserdns.py&quot;, line 12, in 
    for ts, buf in pcap:
  File &quot;build/bdist.linux-i686/egg/dpkt/pcap.py&quot;, line 141, in __iter__
  File &quot;build/bdist.linux-i686/egg/dpkt/dpkt.py&quot;, line 75, in __init__
dpkt.dpkt.NeedData]]></description>
		<content:encoded><![CDATA[<p>Traceback (most recent call last):<br />
  File &#8220;./parserdns.py&#8221;, line 12, in<br />
    for ts, buf in pcap:<br />
  File &#8220;build/bdist.linux-i686/egg/dpkt/pcap.py&#8221;, line 141, in __iter__<br />
  File &#8220;build/bdist.linux-i686/egg/dpkt/dpkt.py&#8221;, line 75, in __init__<br />
dpkt.dpkt.NeedData</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive DNS mining from PCAP with dpkt &amp; Python by mmishou</title>
		<link>http://mishou.org/2010/04/13/passive-dns-mining-from-pcap-with-dpkt-python/#comment-77</link>
		<dc:creator><![CDATA[mmishou]]></dc:creator>
		<pubDate>Sun, 12 Sep 2010 23:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://mishou.org/?p=210#comment-77</guid>
		<description><![CDATA[Lou,

First, sorry for the delay in response.

Thanks for the tip.  I&#039;m trying to figure out why an A record wouldn&#039;t be 4-bytes.  Do you have a sample you can show me?  I haven&#039;t found this on our network at work, which is pretty large, but that&#039;s not saying it couldn&#039;t happen.

There is mention on the Wikipedia page here of some RFC&#039;s that might explain the issue, http://en.wikipedia.org/wiki/List_of_DNS_record_types.  Notably, they talk about &quot;Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101, etc.&quot;.  A subnet mask should still be 4 bytes.  But in reading the RFC 1035, I came across this in section 3.4.1:

Hosts that have multiple Internet addresses will have multiple A
records.

Maybe you&#039;re seeing packets with multiple A record addresses in one response?  I haven&#039;t tested that, I might have to iterate over answer.rdata, maybe it comes back as an array if there are multiple responses or something.  Will test it and report back here.

An example of this:

8	0.658817	192.168.1.1	192.168.1.5	DNS	Standard query response CNAME www.l.google.com A 72.14.204.147 A 72.14.204.104 A 72.14.204.99 A 72.14.204.103

And:

31	242.110444	192.168.1.1	192.168.1.5	DNS	Standard query response A 74.200.243.253 A 76.74.255.123 A 72.233.2.58 A 72.233.2.59 A 76.74.254.123 A 74.200.243.251

Whereas:

21	106.408197	192.168.1.1	192.168.1.5	DNS	Standard query response A 64.85.164.40

Thanks again!]]></description>
		<content:encoded><![CDATA[<p>Lou,</p>
<p>First, sorry for the delay in response.</p>
<p>Thanks for the tip.  I&#8217;m trying to figure out why an A record wouldn&#8217;t be 4-bytes.  Do you have a sample you can show me?  I haven&#8217;t found this on our network at work, which is pretty large, but that&#8217;s not saying it couldn&#8217;t happen.</p>
<p>There is mention on the Wikipedia page here of some RFC&#8217;s that might explain the issue, <a href="http://en.wikipedia.org/wiki/List_of_DNS_record_types" rel="nofollow">http://en.wikipedia.org/wiki/List_of_DNS_record_types</a>.  Notably, they talk about &#8220;Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101, etc.&#8221;.  A subnet mask should still be 4 bytes.  But in reading the RFC 1035, I came across this in section 3.4.1:</p>
<p>Hosts that have multiple Internet addresses will have multiple A<br />
records.</p>
<p>Maybe you&#8217;re seeing packets with multiple A record addresses in one response?  I haven&#8217;t tested that, I might have to iterate over answer.rdata, maybe it comes back as an array if there are multiple responses or something.  Will test it and report back here.</p>
<p>An example of this:</p>
<p>8	0.658817	192.168.1.1	192.168.1.5	DNS	Standard query response CNAME <a href="http://www.l.google.com" rel="nofollow">http://www.l.google.com</a> A 72.14.204.147 A 72.14.204.104 A 72.14.204.99 A 72.14.204.103</p>
<p>And:</p>
<p>31	242.110444	192.168.1.1	192.168.1.5	DNS	Standard query response A 74.200.243.253 A 76.74.255.123 A 72.233.2.58 A 72.233.2.59 A 76.74.254.123 A 74.200.243.251</p>
<p>Whereas:</p>
<p>21	106.408197	192.168.1.1	192.168.1.5	DNS	Standard query response A 64.85.164.40</p>
<p>Thanks again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

