[Winpcap-users] Feature request: restricting use of winpcap
loris.degioanni at gmail.com
Mon Aug 1 19:18:07 GMT 2005
Sorry for my previuos email in Italian, wrongly sent to the list. I was
commenting with Gianluca that a "default" BPF filter, that the
administrator can set to restrict the view of normal users, could be a
quite cool feature to add.
Gianluca Varenni wrote:
> Hi Phil.
> As Loris explained some days ago on the mailing list
> we are definitely planning to add such feature, but it won't be
> available in the upcoming WinPcap 3.1. The idea is putting some ACLs on
> the npf devices to selectively allow/deny tx and rx through a control
> panel applet (or something similar).
> Have a nice day
> ----- Original Message ----- From: "Ph. Marek" <philipp.marek at bmlv.gv.at>
> To: <winpcap-users at winpcap.org>
> Sent: Monday, August 01, 2005 1:14 AM
> Subject: [Winpcap-users] Feature request: restricting use of winpcap
>> Hello everybody!
>> I'd like to do some packet reading/analysing in a script, giving
>> about the network status (sing cdp). That works beautifully parsing the
>> tethereal output.
>> What I don't want is giving users on the PC full sniffing capabilities.
>> Is there a way to restrict communication between the npf driver and other
>> applications, either by applying an acl to the npf device file, or
>> some registry values to define a filter string and deny packet injection?
>> I guess the easiest solution would be to set an acl - so the script
>> runs in another security context) could do as it likes.
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
More information about the Winpcap-users