It’s the “etc.” that makes this a very difficult and time consuming
question to answer. I can’t think of a general answer that’s going to
work for all devices.
In general, though, I can say with some confidence that this is a very
hard problem to solve.
Let’s just use my company’s device, for example: our touchpad driver
provides an API usable by applications. It does this by creating a
uniquely-symbolically-named device object that apps can open. I don’t
see you your proposed driver can effectively control this without
knowing what that device object’s symbolic name is. So now we’re talking
about enumerating those, and how to you know which are devices you can
safely filter and which ones are things where you will wreck the system
if you disallow access?
Also, everyone here has different backgrounds/areas of driver
specialization.
Devices that have file systems may be best filtered using standard
filesystem access mechanisms, for example, but I wouldn’t really be the
best guy to answer that.
USB and serial devices will probably need a device upper filter driver
or a vastly more complicated (and prone to disasterous errors) bus
filter driver… unless someone wants to propose another kind of solution.
I suspect that network cards need yet another kind of solution (maybe an
IM filter?), but I’ve only briefly looked NDIS that so I can’t really
answer the question for that kind of device.
shark marian wrote:
hello burn,
sorry, i have not give out my goal.
my goal is to control the access of the devices,such as the
netcard,usb port,etc.
for example,three persons A,B,C use one computer,A has the admin
priviledge,and he does not allow the B and C to use the netcard or usb
port,so he want to control the access of the device,what the A want to
do is my goal.
i do not know whether i describe in detail?
regards
ding hao
ä¸Žè”æœºçš„æœ‹å‹è¿›è¡Œäº¤æµï¼Œè¯·ä½¿ç”¨ MSN Messenger: http://messenger.msn.com/cn
–
…/ray..
Please remove “.spamblock” from my email address if you need to contact
me outside the newsgroup.