Tags: sanyaade-teachings/UsbDk
Tags
build: fix build of Debug_NoSign Signed-off-by: Yuri Benditovich <[email protected]>
Hider API: add ability to delete all persistent rules The application that uses Hider API does not have an ability to query which persistent rules exist. So in order to use UsbDk_DeletePersistentHideRule the application shall guess which rule it needs to delete. Current commit adds ability to delete all existing the persistent rules. This API requires administrative privileges as all APIs related to persistent hide rules. Signed-off-by: Yuri Benditovich <[email protected]>
Use lower device for queries during initialization It is more correct to use lower device in stack for queries during filter initialization. Lower device is in initialized state and can process all kinds of requests, when current one is not ready yet. Signed-off-by: Yuri Benditovich <[email protected]>
Use lower device for queries during initialization It is more correct to use lower device in stack for queries during filter initialization. Lower device is in initialized state and can process all kinds of requests, when current one is not ready yet. Signed-off-by: Yuri Benditovich <[email protected]>
Build: Introduce debug configurations without test signing Signed-off-by: Dmitry Fleytman <[email protected]>
Build: Introduce debug configurations without test signing Signed-off-by: Dmitry Fleytman <[email protected]>
HiderStrategy: Re-use serial numbers of UsbDk devices See log message of previous commit for rationale. Signed-off-by: Dmitry Fleytman <[email protected]>
FilterDevice: Fix recognition of HUB devices Sometimes UsbDk cannot query device descriptors for USB hubs, in such cases it does not attach to theirs stack during parent bus relations processing. However, since UsbDk is registered as USB hub class filter, WDF will call its AddDevice callback anyway. In this case UsbDk should assume that it is dealing with a hub and assign its usual hub strategy. Signed-off-by: Dmitry Fleytman <[email protected]>
ControlDevice: Fix removal of redirection on hub unplug On unplug of USB hub that contains a redirected device, removal of redirection is started when redirected device PDO is still present in UsbDk device lists. In this case UsbDk will try to send reset IOCTL to this device and system will return STATUS_NO_SUCH_DEVICE error code. This commit changes behavior of redirection removal logic in a way that it will not interrupt removal process when such an error is returned by reset. Signed-off-by: Dmitry Fleytman <[email protected]>
RedirectorStrategy: Override device description for redirected devices. There are two reasons for that: 1. There are devices that do not provide device description: In this case, for normal devices, Windows gets description from INF file. Since there is no INF file for UsbDk devices, Windows may fail to initialize the device (depending on implementation of bus driver). 2. With this patch redirected devices show up in device manager as "UsbDk device" which is better then "Unknown Device" or "Mass Storage Device" etc. Signed-off-by: Dmitry Fleytman <[email protected]>
PreviousNext