Re: Restricting access to USB devices
From: Doron Holan [MS] (doronh_at_nospam.microsoft.com)
Date: 11/04/04
- Next message: Doron Holan [MS]: "Re: ACPI/Power Management Questions"
- Previous message: manu: "Re: event vs volatile bool"
- In reply to: Vasantharaj: "Restricting access to USB devices"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 3 Nov 2004 23:52:24 -0800
why disable usbhub? all it does is allow you to attach devices downstream.
why control audio and HID? what is in those interfaces that are "read only"
d
-- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is provided "AS IS" with no warranties, and confers no rights. "Vasantharaj" <vasantharajg@nestec.net> wrote in message news:beb9bfc1.0411030602.6b20742d@posting.google.com... > Hi All, > > We have two requirements in our project, it is related to USB devices > in WDM. > We don't have much idea regarding the USB devices and USB class > drivers. > So I hope I can get some guidance from this group regarding my > problem. > > Operating System : Windows XP Embedded. > > One requirement is, support only few specific USB devices in the > machine. All other USB devices should be blocked. > The following are the USB device classes to be supported in the > machine. > a. Human Input Devices (HID), > b. Chip/Smart Card Interface Devices (CCID) > c. Various Mass Storage class devices (MSC). E.g.. Smart Card > d. Audio and Modem devices > > Our Current Idea for implementing this > ---------------------------------------------- > Remove the class drivers of the classes of devices to be blocked. > Some of the classes we identified to be removed are listed below. > > a. Printer Class (usbprint.sys) > b. Communications Device Class (mdismp.sys) > c. Imaging Class (usbscan.sys) > d. Hub Device Class (usbhub.sys ) > > This can be done while configuring embedded Windows XP. > > Will be there any problem if we remove these drivers ? > > The second requirement is that the read/write access to the supported > USB devices should be controlled. > i.e.. if it the permission set is READ_ONLY, only read access will be > allowed. > Our current Idea for implementing this > ------------------------------------------- > 1. Write a USB filter driver ( Say, usbmon.sys) > 2. Install it as a 'class upper filter driver' to the required classes > of devices. > a. Human Interface Device (HID) Class. (hidclass.sys) > b. Audio Class (sysaudio.sys) > c. Mass Storage Class (usbstor.sys) > 3. Export a IOCTL from usbmon.sys so that user mode applications can > control the read/write operations to . > > > Is there any better idea for implementing these things. Are we in > right direction? > Please advice. > > Thanks in advance, > vasanth.
- Next message: Doron Holan [MS]: "Re: ACPI/Power Management Questions"
- Previous message: manu: "Re: event vs volatile bool"
- In reply to: Vasantharaj: "Restricting access to USB devices"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|