Accessing driver needs Administrator priviledges

NTDEV
1

Hello,

I have been working past few months changing a WDM driver to a WDF driver.
But I noticed now that the application which is using this driver to
communicate with the device (which is a scanner) needs to be run as
‘Administrator’ in order to communicate with the device. Previous driver
does not need that.

I noticed this during the development also. But I thought may be it is due
to the fact that driver is not signed, etc. But I have not read about
anything like this behavior in MSDN.

Is this normal behavior? or is there something that I need to do?

-Pradeepa

2

See “INF AddReg” WDK topic, “Security” value.

3

Yes and you can look to the device object security with the SysInternals WinObj utility. The device object path can be found in the Device Manager details tab for the device.

Look at the WdfDeviceInitAssignSDDLString API documentation.

4

Hello,

Thank you very much for the help. The issue I had was in the
“WdfDeviceInitAssignSDDLString”
API.

I have passed SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_R_RES_R previously which is
actually wrong. I need RW permission for RES.

So I changed it to SDDL_DEVOBJ_SYS_ALL_ADM_RWX_WORLD_RWX_RES_RWX and
everything works well now.

Thanks for pointing the WinObj utility. It is also really good.

Cheers.

-Pradeepa

On Tue, Sep 23, 2014 at 7:08 AM, wrote:

> Yes and you can look to the device object security with the SysInternals
> WinObj utility. The device object path can be found in the Device Manager
> details tab for the device.
>
> Look at the WdfDeviceInitAssignSDDLString API documentation.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>