Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Graham Bloice
On 22 July 2015 at 22:13, Guy Harris wrote: > > On Jul 22, 2015, at 1:49 PM, Graham Bloice > wrote: > > > > > > > On 22 July 2015 at 18:37, Guy Harris wrote: > > > >> On Jul 22, 2015, at 9:37 AM, Graham Bloice > wrote: > >> > >>> Most, if not all, will be running Wireshark unelevated, as this

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Jim Young
Hello Yang, From: Yang Luo , Date: Wednesday, July 22, 2015 11:12 PM >I tested it against Win10 10240 x64 (French and Chinese), try installer >at: >https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.02-r2.exe I've continued to test the various Npcap versions in WinPcap API mode on Wind

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Yang Luo
Hi Guy, If I am understanding right, what you asked is exactly what Npcap has implemented for "Admin-only Mode". If you install Npcap in "Admin-only Mode", the driver npf.sys will be protected with Admin rights. Softwares (like Wireshark) loading Npcap's packet.dll will start a daemon named "NPcap

Re: [Wireshark-dev] Qt related menu issues on Mac OS X (bug 10890, etc)

2015-07-22 Thread Luke Mewburn
On Tue, Jul 21, 2015 at 09:26:42PM -0700, Guy Harris wrote: | | On Jul 21, 2015, at 7:53 PM, Luke Mewburn wrote: | | > I've been experiencing weird issues running my Mac OS X builds of | > wireshark compiled with Qt 5.2 from Homebrew. Correcting myself: the Homebrew version is Qt 5.4.

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Yang Luo
On Thu, Jul 23, 2015 at 3:39 AM, Pascal Quantin wrote: > > > Indeed the command output is localized. Before installing Npcap, I have: > État adminÉtat TypeNom de l'interface > - > Activé Conne

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Guy Harris
On Jul 22, 2015, at 1:49 PM, Graham Bloice wrote: > > > On 22 July 2015 at 18:37, Guy Harris wrote: > >> On Jul 22, 2015, at 9:37 AM, Graham Bloice >> wrote: >> >>> Most, if not all, will be running Wireshark unelevated, as this is a basic >>> tenet of Wireshark use. There are millions o

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Graham Bloice
On 22 July 2015 at 21:49, Graham Bloice wrote: > > > On 22 July 2015 at 18:37, Guy Harris wrote: > >> >> On Jul 22, 2015, at 9:37 AM, Graham Bloice >> wrote: >> >> > Most, if not all, will be running Wireshark unelevated, as this is a >> basic tenet of Wireshark use. There are millions of lines

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Graham Bloice
On 22 July 2015 at 18:37, Guy Harris wrote: > > On Jul 22, 2015, at 9:37 AM, Graham Bloice > wrote: > > > Most, if not all, will be running Wireshark unelevated, as this is a > basic tenet of Wireshark use. There are millions of lines of code in > Wireshark dissectors and they really shouldn't b

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Pascal Quantin
2015-07-22 18:25 GMT+02:00 Yang Luo : > Hi Pascal, > > On Wed, Jul 22, 2015 at 11:33 PM, Pascal Quantin > wrote: > >> >> I just gave a try to this new installer: >> - still my rename issue of the loop back installer (as expected ;)). Is >> there some debug log / test I could do on my side? I will

Re: [Wireshark-dev] mailing list test

2015-07-22 Thread Guy Harris
On Jul 22, 2015, at 5:44 AM, Hadriel Kaplan wrote: > I send via SMTP through their servers (i.e., I don't use their web > mail interface - I use IMAP and SMTP from a Mac mail client). > > OK fine , I'll use gmail for the mailing lists. But you really should > try Yahoo mail sometime - you get a

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Guy Harris
On Jul 22, 2015, at 9:37 AM, Graham Bloice wrote: > Most, if not all, will be running Wireshark unelevated, as this is a basic > tenet of Wireshark use. There are millions of lines of code in Wireshark > dissectors and they really shouldn't be given admin privs. Does anybody know whether the

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Graham Bloice
On 22 July 2015 at 17:25, Yang Luo wrote: > - for those having User Account Control activated, you need to start >> Wireshark as administrator (even without restricting Npcap to admin during >> installation) to have the driver started. Unfortunate... If this is the >> loopback adapter that trig

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Yang Luo
Hi Pascal, On Wed, Jul 22, 2015 at 11:33 PM, Pascal Quantin wrote: > > I just gave a try to this new installer: > - still my rename issue of the loop back installer (as expected ;)). Is > there some debug log / test I could do on my side? I will double check if > the rename works fine on a Frenc

Re: [Wireshark-dev] Npcap 0.01 call for test (2nd)

2015-07-22 Thread Pascal Quantin
2015-07-22 6:45 GMT+02:00 Yang Luo : > > Hi all, > > I think I have completely solved the "System error 2" thing, this error is because current Npcap uses WFP technique for handling loopback traffic and WFP will cause the "System error 2" if it is started by OS from boot, so I removed the "Automati

Re: [Wireshark-dev] mailing list test

2015-07-22 Thread Hadriel Kaplan
I send via SMTP through their servers (i.e., I don't use their web mail interface - I use IMAP and SMTP from a Mac mail client). OK fine , I'll use gmail for the mailing lists. But you really should try Yahoo mail sometime - you get all kinds of amazing offers from people you've never met before,

Re: [Wireshark-dev] mailing list test

2015-07-22 Thread Evan Huus
> On Jul 22, 2015, at 02:38, Martin Mathieson > wrote: > > Got this, and didn't need to fish it out of spam this time (where is > where your yahoo mails live for me). Ya, something about the way you send from your yahoo account ruins the DKIM header so most mail clients auto-spam them and ref

Re: [Wireshark-dev] Windows driver signing certificate purchase decision for WinPcap and Npcap

2015-07-22 Thread Graham Bloice
On 22 July 2015 at 07:59, Yang Luo wrote: > Hi, > > I have found this link: > https://www.osr.com/blog/2015/03/18/microsoft-signatures-required-km-drivers-windows-10/, > in which it says: "*These requirements only apply to Windows 10 and > later. In fact, Microsoft plans to offer a bit of a grac

Re: [Wireshark-dev] Windows driver signing certificate purchase decision for WinPcap and Npcap

2015-07-22 Thread Yang Luo
Hi, I have found this link: https://www.osr.com/blog/2015/03/18/microsoft-signatures-required-km-drivers-windows-10/, in which it says: "*These requirements only apply to Windows 10 and later. In fact, Microsoft plans to offer a bit of a grace period: Drivers signed before Windows 10 RTM will be a