[Winpcap-users] Feature request: restricting use of winpcap

[Loris Degioanni]

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.

Loris


Gianluca Varenni wrote:
> Hi Phil.
> 
> As Loris explained some days ago on the mailing list 
> (http://www.winpcap.org/pipermail/winpcap-users/2005-July/000202.html) 
> 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
> GV
> 
> ----- 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 
>> information
>> 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 
>> setting
>> 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 
>> (which
>> runs in another security context) could do as it likes.
>>
>>
>>
>> Regards,
>>
>> Phil
>> _______________________________________________
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>>
> 
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>