On Wed, Jul 8, 2015 at 12:56 AM, Guy Harris wrote:
>
> On Jul 7, 2015, at 8:56 AM, Joerg Mayer wrote:
>
> > While I understand the logic behind our argument, I don't agree with it:
> > With the possibility of winpcap and npcap diverging, that may at one
> point
> > in time mean diverging and inc
> The Wireshark suite doesn't hard-code npf.sys per se, it just uses the
> Service Control Manager (SCM) to check the state of the "npf" service. To
> allow co-existence of both WinPCap and NPcap on the same machine that
> service name should be different for the two libraries.
>
> Arguably that c
On Tue, Jul 7, 2015 at 11:56 PM, Joerg Mayer wrote:
> On Mon, Jul 06, 2015 at 10:42:50AM +0800, Yang Luo wrote:
> > The first reason is causing more efforts for apps. Nearly all apps I know
> > have hard-coded the DLL file name, wpcap.dll by implicitly linking the
> .lib
> > or LoadLibrary call.
On Tue, Jul 07, 2015 at 09:56:24AM -0700, Guy Harris wrote:
>
> On Jul 7, 2015, at 8:56 AM, Joerg Mayer wrote:
>
> > While I understand the logic behind our argument, I don't agree with it:
> > With the possibility of winpcap and npcap diverging, that may at one point
> > in time mean diverging
On Jul 7, 2015, at 8:56 AM, Joerg Mayer wrote:
> While I understand the logic behind our argument, I don't agree with it:
> With the possibility of winpcap and npcap diverging, that may at one point
> in time mean diverging and incompatible APIs. Also, what happens if a user
> wants to use Wires
On 7 July 2015 at 16:56, Joerg Mayer wrote:
> On Mon, Jul 06, 2015 at 10:42:50AM +0800, Yang Luo wrote:
> > The first reason is causing more efforts for apps. Nearly all apps I know
> > have hard-coded the DLL file name, wpcap.dll by implicitly linking the
> .lib
> > or LoadLibrary call. If I cha
On Mon, Jul 06, 2015 at 10:42:50AM +0800, Yang Luo wrote:
> The first reason is causing more efforts for apps. Nearly all apps I know
> have hard-coded the DLL file name, wpcap.dll by implicitly linking the .lib
> or LoadLibrary call. If I changed this name, all apps will need
> modification for NP
On Sat, Jul 04, 2015 at 10:26:13AM +0800, Yang Luo wrote:
> Given that current Wireshark can't make use of NPcap because of the DLL
> search path problem mentioned in
> https://www.wireshark.org/lists/wireshark-dev/201506/msg00030.html, I'd
> like to make a patch for Wireshark. As it is a security
The first reason is causing more efforts for apps. Nearly all apps I know
have hard-coded the DLL file name, wpcap.dll by implicitly linking the .lib
or LoadLibrary call. If I changed this name, all apps will need
modification for NPcap. LoadLibrary is easy to change, just add another
file name for
As WinPcap and NPcap seem to be diverging, in the short-term at least,
should the dll's be named differently?
The following is just an observation, not intended as any criticism.
As NPCap has chosen to co-exist with WinPCap by using a (non-standard)
Windows directory, although that (currently) do
Good question, Graham. This is simply because WinPcap has taken the
System32\SysWow64
dirs and NPcap wants to coexist with WinPcap. As NPcap has the same file
names (wpcap.dll and packet.dll) for compatibility, we just can't put the
the-same-name files in the same folder with WinPcap. Though I pers
Out of interest why does NPcap not place its DLL's in System32\SysWow64 as
that is on the standard DLL search path?
On 4 July 2015 at 17:28, Yang Luo wrote:
> Hi Pascal, I hold the same opinion with you, because a user installing
> NPcap implies that he wants to use it, I think I will make it
Hi Pascal, I hold the same opinion with you, because a user installing
NPcap implies that he wants to use it, I think I will make it this way:)
Cheers,
Yang
On Sat, Jul 4, 2015 at 6:07 PM, Pascal Quantin
wrote:
>
> Le 4 juil. 2015 4:26 AM, "Yang Luo" a écrit :
> >
> > Hi list,
> >
> > Given th
Le 4 juil. 2015 4:26 AM, "Yang Luo" a écrit :
>
> Hi list,
>
> Given that current Wireshark can't make use of NPcap because of the DLL
search path problem mentioned in
https://www.wireshark.org/lists/wireshark-dev/201506/msg00030.html, I'd
like to make a patch for Wireshark. As it is a security co
Hi list,
Given that current Wireshark can't make use of NPcap because of the DLL
search path problem mentioned in
https://www.wireshark.org/lists/wireshark-dev/201506/msg00030.html, I'd
like to make a patch for Wireshark. As it is a security consideration that
Wireshark don't want to search the DL
15 matches
Mail list logo
