<?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>[blog.rayfoo] &#187; defense in depth</title>
	<atom:link href="http://blog.rayfoo.info/tag/defense-in-depth/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.rayfoo.info</link>
	<description>Infosec, DFIR, tech geekery, thoughts and whatnot</description>
	<lastBuildDate>Wed, 25 Jan 2012 00:36:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Changing internal network IP address range</title>
		<link>http://blog.rayfoo.info/2009/10/changing-internal-network-ip-address-range</link>
		<comments>http://blog.rayfoo.info/2009/10/changing-internal-network-ip-address-range#comments</comments>
		<pubDate>Tue, 13 Oct 2009 18:20:59 +0000</pubDate>
		<dc:creator>ray</dc:creator>
				<category><![CDATA[Everything]]></category>
		<category><![CDATA[CSRF]]></category>
		<category><![CDATA[defense in depth]]></category>
		<category><![CDATA[DHCP]]></category>
		<category><![CDATA[GNUCITIZEN]]></category>
		<category><![CDATA[migration]]></category>
		<category><![CDATA[router]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[thoughts]]></category>
		<category><![CDATA[wifi]]></category>

		<guid isPermaLink="false">http://blog.rayfoo.info/?p=258</guid>
		<description><![CDATA[Finally gotten my lazy busy ass down to implementing some of those stuff that I've always wanted to (like they say: eat your own dog food). For tonight it was the changing and limiting of the DHCP address range served by my router to be a non-standard one (i.e. not in the 192.168.1.0/24 range), as [...]]]></description>
			<content:encoded><![CDATA[<p>Finally gotten my <del datetime="2009-10-13T18:10:47+00:00">lazy</del> busy ass down to implementing some of those stuff that I've always wanted to (like they say: eat your own dog food).</p>
<p>For tonight it was the changing and limiting of the DHCP address range served by my router to be a non-standard one (i.e. not in the 192.168.1.0/24 range), as one of the defences against <a href="http://en.wikipedia.org/wiki/Cross-site_request_forgery">CSRF</a> attacks against the router.</p>
<p>The change turned out to not to be as smooth as I thought it would be, even though I had very few devices in the network as compared to an office one.  Would keep this in mind as I think about/recommend this to others.</p>
<p>Additional reading on the topic of CSRFing home routers, for those who're interested:<br />
<a href="http://www.gnucitizen.org/blog/bt-home-flub-pwnin-the-bt-home-hub/">GNUCITIZEN: BT HOME FLUB: PWNIN THE BT HOME HUB</a><br />
<a href="http://www.gnucitizen.org/blog/router-hacking-challenge/">GNUCITIZEN: ROUTER HACKING CHALLENGE</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.rayfoo.info/2009/10/changing-internal-network-ip-address-range/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

