<?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: IPv6 And Security Architecture Changes</title>
	<atom:link href="http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/</link>
	<description>Ruminations on Information Technology</description>
	<lastBuildDate>Thu, 26 Feb 2009 14:43:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Sean</title>
		<link>http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/comment-page-1/#comment-52</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Tue, 29 Apr 2008 21:30:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/#comment-52</guid>
		<description>Hi Ed,

I think the biggest initial deployment challenge will quite simply be inexperience with the technology. There is very little understanding of IPv6 in the networking community, let alone IPv6 security considerations.

I do agree that there will be implementation flaws and we&#039;re probably only beginning to detect them. In the meantime, dual-stack systems with IPv4 and IPv6 running concurrently represent a very interesting attack vector as you can use a potentially insecure IPv6 stack to get onto the IPv4 network. In my testing back in 2004 there were instances of personal firewalls only protecting the IPv4 portion of the connectivity and leaving the IPv6 portion completely wide open.

Fuzzing IPv6 stacks will certainly yield some flaws, not sure if anyone&#039;s done anything comprehensive yet.</description>
		<content:encoded><![CDATA[<p>Hi Ed,</p>
<p>I think the biggest initial deployment challenge will quite simply be inexperience with the technology. There is very little understanding of IPv6 in the networking community, let alone IPv6 security considerations.</p>
<p>I do agree that there will be implementation flaws and we&#8217;re probably only beginning to detect them. In the meantime, dual-stack systems with IPv4 and IPv6 running concurrently represent a very interesting attack vector as you can use a potentially insecure IPv6 stack to get onto the IPv4 network. In my testing back in 2004 there were instances of personal firewalls only protecting the IPv4 portion of the connectivity and leaving the IPv6 portion completely wide open.</p>
<p>Fuzzing IPv6 stacks will certainly yield some flaws, not sure if anyone&#8217;s done anything comprehensive yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward Vielmetti</title>
		<link>http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/comment-page-1/#comment-53</link>
		<dc:creator>Edward Vielmetti</dc:creator>
		<pubDate>Tue, 29 Apr 2008 15:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.seanconvery.com/weblog/2008/03/31/ipv6-and-security-architecture-changes/#comment-53</guid>
		<description>Sean -

Do you think that the biggest initial deployment security issues in IPv6 will revolve around implementation correctness, and the ability to test for same?

What comes to mind quickly is things like IPv6 fuzzing a la

http://seclists.org/pen-test/2008/Apr/0136.html

which calls for the need for systematic ways to test correctness without knowing a priori what parts of the system are likely to break first.</description>
		<content:encoded><![CDATA[<p>Sean -</p>
<p>Do you think that the biggest initial deployment security issues in IPv6 will revolve around implementation correctness, and the ability to test for same?</p>
<p>What comes to mind quickly is things like IPv6 fuzzing a la</p>
<p><a href="http://seclists.org/pen-test/2008/Apr/0136.html" rel="nofollow">http://seclists.org/pen-test/2008/Apr/0136.html</a></p>
<p>which calls for the need for systematic ways to test correctness without knowing a priori what parts of the system are likely to break first.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

