<?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 on: Wireshark 1.2.0 available</title>
	<atom:link href="http://hackaday.com/2009/06/29/wireshark-1-2-0-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: tjhooker</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79790</link>
		<dc:creator><![CDATA[tjhooker]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79790</guid>
		<description><![CDATA[I use it for reversing sometimes. Like with key gens that return from a server. I can use the data to patch jumps in ollydbg etc]]></description>
		<content:encoded><![CDATA[<p>I use it for reversing sometimes. Like with key gens that return from a server. I can use the data to patch jumps in ollydbg etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: saimhe</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79773</link>
		<dc:creator><![CDATA[saimhe]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 10:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79773</guid>
		<description><![CDATA[During capture, use tshark -w instead. Afterwards, to speed up handling, turn off any irrelevant protocols (however a more restrictive capture filter might do better).]]></description>
		<content:encoded><![CDATA[<p>During capture, use tshark -w instead. Afterwards, to speed up handling, turn off any irrelevant protocols (however a more restrictive capture filter might do better).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: babylon_zoo</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79751</link>
		<dc:creator><![CDATA[babylon_zoo]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 05:48:21 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79751</guid>
		<description><![CDATA[WS is not for huge packet capturing safari. You certainly would not use notepad to code a project like firefox...


They worked on this memory usage problem:

Several memory leaks have been found and fixed. 


But at the time you are trying to display every packet on the screen and wanted to be able to scroll over them, you need to put those on memory... Using the ngrep method you put it on a file (and WS can do that too if you disable the display of packets in the gui)]]></description>
		<content:encoded><![CDATA[<p>WS is not for huge packet capturing safari. You certainly would not use notepad to code a project like firefox&#8230;</p>
<p>They worked on this memory usage problem:</p>
<p>Several memory leaks have been found and fixed. </p>
<p>But at the time you are trying to display every packet on the screen and wanted to be able to scroll over them, you need to put those on memory&#8230; Using the ngrep method you put it on a file (and WS can do that too if you disable the display of packets in the gui)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: h_2_o</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79746</link>
		<dc:creator><![CDATA[h_2_o]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 05:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79746</guid>
		<description><![CDATA[harvie hit it on the head, wireshark is nice for small grabs, but if you try and do large data grabs with it, forget about it.]]></description>
		<content:encoded><![CDATA[<p>harvie hit it on the head, wireshark is nice for small grabs, but if you try and do large data grabs with it, forget about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79742</link>
		<dc:creator><![CDATA[Jack]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 04:02:12 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79742</guid>
		<description><![CDATA[The easiest way to do WEP cracking is just to get a hold of a wireless card that supports packet injecting, and to use a BackTrack3/4 live cd or run it off of a USB thumb drive.
http://www.wildpackets.com/support/hardware/airopeek_12
those are some cards, google around and I&#039;m sure you&#039;ll find more.]]></description>
		<content:encoded><![CDATA[<p>The easiest way to do WEP cracking is just to get a hold of a wireless card that supports packet injecting, and to use a BackTrack3/4 live cd or run it off of a USB thumb drive.<br />
<a href="http://www.wildpackets.com/support/hardware/airopeek_12" rel="nofollow">http://www.wildpackets.com/support/hardware/airopeek_12</a><br />
those are some cards, google around and I&#8217;m sure you&#8217;ll find more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TJHooker</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79732</link>
		<dc:creator><![CDATA[TJHooker]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 03:18:33 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79732</guid>
		<description><![CDATA[Go do a attack on a WEP point from a NT machine and you&#039;ll see why nobody bothers. It takes forever without injection. I forget why but you can&#039;t put the chip into the mode it needs from NT without heavy reverse engineering.

I could be wrong.]]></description>
		<content:encoded><![CDATA[<p>Go do a attack on a WEP point from a NT machine and you&#8217;ll see why nobody bothers. It takes forever without injection. I forget why but you can&#8217;t put the chip into the mode it needs from NT without heavy reverse engineering.</p>
<p>I could be wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nanoc</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79728</link>
		<dc:creator><![CDATA[nanoc]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 02:29:44 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79728</guid>
		<description><![CDATA[WEP cracker? You can crack WEP in windows with aircrack-ng. I believe if your card is supported you can also capture packets with it too but i believe aircrack-ng discontinued windows support a few years back. Cain n Able also for Windows.]]></description>
		<content:encoded><![CDATA[<p>WEP cracker? You can crack WEP in windows with aircrack-ng. I believe if your card is supported you can also capture packets with it too but i believe aircrack-ng discontinued windows support a few years back. Cain n Able also for Windows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: googfan</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79726</link>
		<dc:creator><![CDATA[googfan]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 01:51:53 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79726</guid>
		<description><![CDATA[but there really needs to be a wep cracker for windows]]></description>
		<content:encoded><![CDATA[<p>but there really needs to be a wep cracker for windows</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harvie</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79725</link>
		<dc:creator><![CDATA[Harvie]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 01:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79725</guid>
		<description><![CDATA[i don&#039;t like whireshark since it eats lot of memory (especialy when capuring lot of packets or for a long time).

go and try ngrep! for both windows and *nixes.
very handy:

ngrep -d eth0
or eg.:
ngrep -d wlan0 dst port 21 &quot;USER&#124;PASS&quot; &gt; ftp.txt]]></description>
		<content:encoded><![CDATA[<p>i don&#8217;t like whireshark since it eats lot of memory (especialy when capuring lot of packets or for a long time).</p>
<p>go and try ngrep! for both windows and *nixes.<br />
very handy:</p>
<p>ngrep -d eth0<br />
or eg.:<br />
ngrep -d wlan0 dst port 21 &#8220;USER|PASS&#8221; &gt; <a href="http://ftp.txt" rel="nofollow">http://ftp.txt</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: googfan</title>
		<link>http://hackaday.com/2009/06/29/wireshark-1-2-0-available/comment-page-1/#comment-79722</link>
		<dc:creator><![CDATA[googfan]]></dc:creator>
		<pubDate>Tue, 30 Jun 2009 01:32:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=12178#comment-79722</guid>
		<description><![CDATA[now all it needs is a wep cracker.

totally unrelated, i just built a tater gun that shoots spuds 350 yards!]]></description>
		<content:encoded><![CDATA[<p>now all it needs is a wep cracker.</p>
<p>totally unrelated, i just built a tater gun that shoots spuds 350 yards!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

