[Yang Luo <hsluoyb@xxxxxxxxx>]

Thanks for info, Graham! It seems that WinPcap will view stability as the primary goal. While as a Summer of Code project, NPcap will try to move as fast as possible especially for these months. I am even planning to add loopback packet capturing for NPcap and have made some progress these days, and Wireshark will be a perfect tool to test this function. Given that it's no short-term effort to migrating to trunk, as the ways Gerald suggested, NPcap will choose the "Make NPcap obviously separate. Give it a separate name and modify Wireshark to try to load it first." way. I will try to make a patch for Wireshark to support NPcap recently.

Cheers,

Yang

On Sat, Jul 4, 2015 at 12:46 AM, Graham Bloice <graham.bloice@xxxxxxxxxxxxx> wrote:

On 3 July 2015 at 17:29, Yang Luo <hsluoyb@xxxxxxxxx> wrote:

Hi list,

Since the last mail about how to make NPcap available for Wireshark, I have been waiting for WinPcap's official repo's news and I fortunately found this these days: https://github.com/wireshark/winpcap, is this the official WinPcap repo now? If yes, then what's the review policy? Like recently we have added the "Admin-only mode" into NPcap, it restricts the capturing access only to Administrators for security purpose (see details in: https://github.com/nmap/npcap and http://nmap.org/soc/#winpcap). I don't know if the review party would like this idea? (and like other parts of NPcap like current NDIS 6 implementation). And how hard would it be for NPcap to be merged into WinPcap upstream? I noticed that this repo used gerrit for code review and it is kind of strict system in my mind:)

Cheers,

Yang

Hi,

As discussed elsewhere, and at Sharkfest with Fyodor, the Wireshark project is now hosting the "official" WinPCap repo (https://code.wireshark.org/review/winpcap) and are using Gerrit for code reviews, etc.  The github repo is a read-only copy.  This repo is basically a dump from the internal Riverbed\Cace repo.

The current "plan" is to make minimal changes to this code to get it compiling with a modern compiler (VS2013) and do whatever is necessary to make it run on Win 10.  XP support *might* be lost during this.  This will likely be WinPCap 4.1.4.

After that all, things are up for consideration, including rewriting WinPCap for NDIS6, moving over to NPCap, synchronising with current libpcap, the security enhancement you mention etc.

--

Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe