<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>packet m0nkey</title>
	<atom:link href="http://blog.willurbanski.com/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.willurbanski.com</link>
	<description>Will Urbanski&#039;s Blog</description>
	<lastBuildDate>Tue, 03 Apr 2012 01:25:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Mapping IPv6 hosts using inaddr.arpa</title>
		<link>http://blog.willurbanski.com/archives/15</link>
		<comments>http://blog.willurbanski.com/archives/15#comments</comments>
		<pubDate>Tue, 03 Apr 2012 01:25:37 +0000</pubDate>
		<dc:creator>wuadmin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blog.willurbanski.com/?p=15</guid>
		<description><![CDATA[There&#8217;s been an interesting thread on the ipv6hackers mailing list lately discussing how to use inaddr.arpa to map an IPv6 subnet. The code, available on github, will query a nameserver to find live hosts on a given subnet. Support for the ip6.arpa mapping technique has already been added to the thc-ipv6 suite!]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been an interesting thread on the ipv6hackers mailing list lately <a href="http://lists.si6networks.com/pipermail/ipv6hackers/2012-March/000526.html">discussing how to use inaddr.arpa to map an IPv6 subnet.</a> The code, <a href="https://github.com/habbie/ip6-arpa-scan/">available on github</a>, will query a nameserver to find live hosts on a given subnet. Support for the ip6.arpa mapping technique has already been added to the thc-ipv6 suite!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.willurbanski.com/archives/15/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Finding live hosts on an IPv6 network</title>
		<link>http://blog.willurbanski.com/archives/8</link>
		<comments>http://blog.willurbanski.com/archives/8#comments</comments>
		<pubDate>Mon, 26 Mar 2012 23:59:41 +0000</pubDate>
		<dc:creator>wuadmin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[network]]></category>

		<guid isPermaLink="false">http://blog.willurbanski.com/?p=8</guid>
		<description><![CDATA[Today I was re-watching Marc Heuse&#8217;s 2012 CCC presentation on recent insecurities in IPv6 (if you know anything about IPv6 skip the first 30 slides). In case you don&#8217;t already know, blanket port scanning for host identification in Ipv6 is essentially useless. Due to the address space it&#8217;s infeasible that you will find someone if they [...]]]></description>
			<content:encoded><![CDATA[<p>Today I was re-watching <a href="http://events.ccc.de/congress/2010/Fahrplan/attachments/1808_vh_thc-recent_advances_in_ipv6_insecurities.pdf">Marc Heuse&#8217;s 2012 CCC presentation on recent insecurities in IPv6</a> (if you know anything about IPv6 skip the first 30 slides). In case you don&#8217;t already know, blanket port scanning for host identification in Ipv6 is essentially useless. Due to the address space it&#8217;s infeasible that you will find someone if they are trying to hide. That is the key though, the massive, unconventional hex-based IPv6 addressing scheme is in some senses more of a hassle than helpful when you consider the numerous layer X technologies it is replacing (ARP, IPv4, NAT). Because of unconventional (and hard to remember) address scheme network administrators seem to have taken a simplification approach to the problem. Heuse outlines how to scan for hosts if you are looking for IPv6 addresses, the strategies are outlined here:</p>
<p>1) Check ::1-X, where X is a larger number {1000,&#8230;}</p>
<p>To make networks more organized network admins have been caught numbering their hosts sequentially. While these numbers are essentially worthless without reverse DNS they make administration easy, and scanning easier!</p>
<p>2) Check ::X:p, ::p, where X is a large number {1,2,3,..}, and p is a common port {80,443,22,23,445,3389, etc}</p>
<p>Again, same reasoning as above. Network admins want to make Ipv6 maintainable and using a simple networking scheme makes network and firewall management more convenient. <a href="http://www.google.com">One major IPv6 deployment is guilty of using this strategy.</a></p>
<p>3) Check ::X:Y, where X and Y are in the set of english, leet-speak words that can be spelled in hexadecimal format.</p>
<p>Dead beef, b00b, babe, all abound in this namespace.</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.willurbanski.com/archives/8/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

