<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/networkminer/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/networkminer/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 14 Dec 2010 15:13:02 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/networkminer/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>PFlog header parsing</title><link>https://sourceforge.net/p/networkminer/feature-requests/105/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The PF firewall offers a facility called pflog which allows users to define traffic which will be logged to a file that matches certain rules.  This traffic is written to the file in tcpdump format, so it should be readable with this program, however the pflog program inserts a new header into each logged packet which states the firewall rule matched and the action (pass/block) taken on the packet.  This appears to be causing problems with the parsing that Network Miner performs on the packet as it only lists the traffic under the "Frames" tab and declares the packet to be of unknown type.  This format is currently parsed by Wireshark, so it should be feasible to implement here.  The fact that this new header makes the entire packet fail to be analyzed might suggest that the parsing code could use a review in order to allow it to continue to parse subsequent known header types after failing to recognize one of the headers (in fact this would be an acceptable alternative to actually parsing the PFlog header, in my case).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 14 Dec 2010 15:13:02 -0000</pubDate><guid>https://sourceforge.net094b9c69acd7bbd3f8244a76e45ddd0555b9ea90</guid></item><item><title>Support for compressed PCAP files</title><link>https://sourceforge.net/p/networkminer/feature-requests/104/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It'd be nice to be able to load the compressed files (the ones that I use are compressed with GZip) directly.  This is a feature currently implemented in Wireshark, so the technical limitations should be minimal.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 14 Dec 2010 15:06:36 -0000</pubDate><guid>https://sourceforge.netc902540f70dec6cefeb7b1378b36ad36ac4d0891</guid></item><item><title>Add support for Google's SPDY protocol</title><link>https://sourceforge.net/p/networkminer/feature-requests/103/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;SPDY is "an application-layer protocol for transporting content over the web, designed specifically for minimal latency".&lt;br /&gt;
&lt;a href="http://www.chromium.org/spdy" rel="nofollow"&gt;http://www.chromium.org/spdy&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 08 Nov 2010 14:43:42 -0000</pubDate><guid>https://sourceforge.net7d9bca3e23e174089f3f4686ad5c4b800e281c49</guid></item><item><title>Add "decode as" feature</title><link>https://sourceforge.net/p/networkminer/feature-requests/101/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Add the ability for the user to select which server IP-port pairs to decode as what protocol.&lt;br /&gt;
This could be done from the sessions tab (right-clicking and selecting "decode as") or possibly also from the hosts tab under "open ports".&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Erik Hjelmvik</dc:creator><pubDate>Thu, 08 Jul 2010 18:47:22 -0000</pubDate><guid>https://sourceforge.net036af62a539062d7acec0f68bce701bb703c8661</guid></item><item><title>Read capture data from a pipe</title><link>https://sourceforge.net/p/networkminer/feature-requests/100/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Include functionality to read capture data from a pipe instead of from a file or NIC.&lt;/p&gt;
&lt;p&gt;Wireshark supports this functionality, which is explained here:&lt;br /&gt;
&lt;a href="http://wiki.wireshark.org/CaptureSetup/Pipes" rel="nofollow"&gt;http://wiki.wireshark.org/CaptureSetup/Pipes&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 29 Jun 2010 19:55:58 -0000</pubDate><guid>https://sourceforge.netd19eef092d706e4a4e694057f794028fa0801cc5</guid></item><item><title>Parse Meterpreter payload reverse shell transfer protocol</title><link>https://sourceforge.net/p/networkminer/feature-requests/99/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Parse the file transfer protocol used by Metasploit to establish a Meterpreter reverse shell. It seems as if the shellcode from Metaspliot causes the victim to connect to a dropper server and download the binary for the meterpreter reverse shell.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 27 Jun 2010 20:25:37 -0000</pubDate><guid>https://sourceforge.net1568d636c16f8541347f030b14dc2080d359df96</guid></item><item><title>Parse RFB protocol (VNC)</title><link>https://sourceforge.net/p/networkminer/feature-requests/98/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Parse the RFB protocol used by VNC.&lt;br /&gt;
&lt;a href="http://www.realvnc.com/docs/rfbproto.pdf" rel="nofollow"&gt;http://www.realvnc.com/docs/rfbproto.pdf&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 14 Jun 2010 12:43:15 -0000</pubDate><guid>https://sourceforge.net4dd2c7e87bdad97c81d79d6d2eabe2069e792497</guid></item><item><title>Search-filter for Parameters tab</title><link>https://sourceforge.net/p/networkminer/feature-requests/97/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Add a search box to the parameters tab that can be used to filter what is being displayed.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 06 May 2010 18:27:04 -0000</pubDate><guid>https://sourceforge.netfe530b90bb7ac94df248a60b426b4df428d5f352</guid></item><item><title>Extract MAC vendor from autoconfigured IPv6 addresses</title><link>https://sourceforge.net/p/networkminer/feature-requests/96/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Extract MAC address vendor from IPv6 adresses generated through autoconfiguration.&lt;br /&gt;
The vendor's 3 byte MAC-vencor-code can be found at bytes 8,9 and 10 (prior to ff:fe as described in &lt;a href="http://standards.ieee.org/regauth/oui/tutorials/EUI64.html\" rel="nofollow"&gt;http://standards.ieee.org/regauth/oui/tutorials/EUI64.html\&lt;/a&gt;) in the IPv6 addresses&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 09 Apr 2010 15:38:57 -0000</pubDate><guid>https://sourceforge.net471f15ffc939006f5ecf91fd1b08dea504e8526c</guid></item><item><title>Show webmail on Messages tab</title><link>https://sourceforge.net/p/networkminer/feature-requests/95/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Decode Yahoo, Hotmail, Microsoft Live, etc. in the same manner as Gmail and Google chat is decoded and displayed on the Messages tab&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Erik Hjelmvik</dc:creator><pubDate>Wed, 17 Feb 2010 17:33:18 -0000</pubDate><guid>https://sourceforge.netd2291459c4b37be21323f154eadabaaa09da904a</guid></item></channel></rss>