Hi !

I want to allow user ( without admin rights ) access to device object of
the NDIS miniport driver ( use PCI card ).

I changed permissions of the driver to full for users and that work. I
read that the same possible to do by INF :

1)
http://www.microsoft.com/whdc/driver/security/drvsecure.mspx?pf=true#secmod2
show the example line:

HKR,,Security,,"D:P(A;;GA;;;SY)"

So I wrote next in the INF

[mydevice.Security]

HKR,,Security,,"D:P(A;;GA;;;WD)"

In the registry I see Key "security " with a string - "D:P(A ( 6
characters )

Before I tried AU instead of WD with the same effect

2)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/se
tup/specifying_a_security_descriptor_from_an_inf_file.asp

show line :

"D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"

I wrote next

[mydevice.Security]

"D:P(A;;GA;;;WD)"

Cannot correctly install driver at all

Any comments ?

TIA

Arkady

Re: Work with driver by User without admin rights by Eliyas

Eliyas
Mon May 03 19:42:26 CDT 2004

Show us the INF. Look at the setupapi.log for any error messages.

--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx


"Arkady Frenkel" <arkadyf@hotmailxdotxcom> wrote in message
news:urKE$6UMEHA.628@TK2MSFTNGP11.phx.gbl...
> Hi !
>
> I want to allow user ( without admin rights ) access to device object of
> the NDIS miniport driver ( use PCI card ).
>
> I changed permissions of the driver to full for users and that work. I
> read that the same possible to do by INF :
>
> 1)
> http://www.microsoft.com/whdc/driver/security/drvsecure.mspx?pf=true#secmod2
> show the example line:
>
> HKR,,Security,,"D:P(A;;GA;;;SY)"
>
> So I wrote next in the INF
>
> [mydevice.Security]
>
> HKR,,Security,,"D:P(A;;GA;;;WD)"
>
> In the registry I see Key "security " with a string - "D:P(A ( 6
> characters )
>
> Before I tried AU instead of WD with the same effect
>
> 2)
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/se
> tup/specifying_a_security_descriptor_from_an_inf_file.asp
>
> show line :
>
> "D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"
>
> I wrote next
>
> [mydevice.Security]
>
> "D:P(A;;GA;;;WD)"
>
> Cannot correctly install driver at all
>
> Any comments ?
>
> TIA
>
> Arkady
>
>



Re: Work with driver by User without admin rights by Arkady

Arkady
Wed May 05 02:46:55 CDT 2004

Hi , Eliyas !
That working INF where to to [MyDevice] to key AddReg section I added
MyDevice.Security and add
[MyDevice.Security]
HKR,,Security,,"D:P(A;;GA;;;WD)"
I can't attached the log ( sent attached but don't see it , so I put it
after message ) , which show nothing about security but the line is
corrupted and shown as before.
I put some comments inside it too. The most interesting effect that after
adding the security lines to INF even
with signed cat "Found New Hardware wizard" dialog appear which not happen
with INF without that ( with my programming installation )


Here the setupapi :

[SetupAPI Log]
OS Version = 5.1.2600 Service Pack 1
Platform ID = 2 (NT)
Service Pack = 1.0
Suite = 0x0100
Product Type = 1
Architecture = x86
[2004/05/04 10:08:18 444.25 Driver Install]
.... Here started im third party driver...
#I306 DICS_START: Device has been started.


A.F. - After installshield do main job ( put our and third party IM driver
into directory and call install of third party IM ),
A.F. - installshield call dll with SetupCopyOEMInf() inside for silent
installation of Miniport driver.
A.F. - That work if no mention security section in INF , but With it no
silent install and
A.F. - "Found New Hardware wizard" dialog is jumping up :( as possible to
see in the next lines )
A.F. - with obviously correct cat file ( as I mention absolutely silent
installation if no security section in INF present )
A.F. - Any comments about that too ?
A.F. - At the end security key with partly string appear in registry as I
mentioned before.


[2004/05/04 10:08:22 344.1]
#-198 Command line processed:
C:\PROGRA~1\COMMON~1\INSTAL~1\Engine\6\INTEL3~1\IKernel.exe -Embedding
#E361 An unsigned or incorrectly signed file
"C:\TIWLAN\Drivers\tnet1130.inf" will be installed (Policy=Ignore). Error
0x800b0100: No signature was present in the subject.

A.F. - Here I insert network card into slot :

[2004/05/04 10:10:28 544.3 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_104c&dev_9066&subsys_9067104c&rev_00,pci\ven_104c&dev_9066&subsys_90
67104c,pci\ven_104c&dev_9066&cc_028000,pci\ven_104c&dev_9066&cc_0280
#-018 Searching for compatible ID(s):
pci\ven_104c&dev_9066&rev_00,pci\ven_104c&dev_9066,pci\ven_104c&cc_028000,pc
i\ven_104c&cc_0280,pci\ven_104c,pci\cc_028000,pci\cc_0280
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "PCI\VEN_104C&DEV_9066&SUBSYS_9067104C" in
C:\WINDOWS\inf\oem5.inf; Device: "TNET1130 WLAN Adapter"; Driver: "TNET1130
WLAN Adapter"; Provider: "Texas Instruments"; Mfg: "Texas Instruments";
Section name: "TIACXXP".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [TIACXXP]. Rank: 0x00008001. Effective driver
date: 03/10/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [TIACXXP] in
"c:\windows\inf\oem5.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"PCI\VEN_104C&DEV_9066&SUBSYS_9067104C&REV_00\5&3995D710&14&0008F0".
#-011 Installing section [TIACXXP] from "c:\windows\inf\oem5.inf".
#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem5.inf" for
driver "TNET1130 WLAN Adapter" blocked (server install). Error 1168: Element
not found.
#E122 Device install failed. Error 1168: Element not found.
#E157 Default installer failed. Error 1168: Element not found.
[2004/05/04 10:10:32 864.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{151E5349-857F-4E45-B8EE-EDD7B2DA1714}
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
pci\ven_104c&dev_9066&subsys_9067104c&rev_00,pci\ven_104c&dev_9066&subsys_90
67104c,pci\ven_104c&dev_9066&cc_028000,pci\ven_104c&dev_9066&cc_0280
#-018 Searching for compatible ID(s):
pci\ven_104c&dev_9066&rev_00,pci\ven_104c&dev_9066,pci\ven_104c&cc_028000,pc
i\ven_104c&cc_0280,pci\ven_104c,pci\cc_028000,pci\cc_0280
#I022 Found "PCI\VEN_104C&DEV_9066&SUBSYS_9067104C" in
C:\WINDOWS\inf\oem5.inf; Device: "TNET1130 WLAN Adapter"; Driver: "TNET1130
WLAN Adapter"; Provider: "Texas Instruments"; Mfg: "Texas Instruments";
Section name: "TIACXXP".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [TIACXXP]. Rank: 0x00008001. Effective driver
date: 03/10/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [TIACXXP] in
"c:\windows\inf\oem5.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#I060 Set selected driver.
#-019 Searching for hardware ID(s):
pci\ven_104c&dev_9066&subsys_9067104c&rev_00,pci\ven_104c&dev_9066&subsys_90
67104c,pci\ven_104c&dev_9066&cc_028000,pci\ven_104c&dev_9066&cc_0280
#-018 Searching for compatible ID(s):
pci\ven_104c&dev_9066&rev_00,pci\ven_104c&dev_9066,pci\ven_104c&cc_028000,pc
i\ven_104c&cc_0280,pci\ven_104c,pci\cc_028000,pci\cc_0280
#I022 Found "PCI\VEN_104C&DEV_9066&SUBSYS_9067104C" in
C:\WINDOWS\inf\oem5.inf; Device: "TNET1130 WLAN Adapter"; Driver: "TNET1130
WLAN Adapter"; Provider: "Texas Instruments"; Mfg: "Texas Instruments";
Section name: "TIACXXP".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [TIACXXP]. Rank: 0x00008001. Effective driver
date: 03/10/2004.
#-019 Searching for hardware ID(s):
pci\ven_104c&dev_9066&subsys_9067104c&rev_00,pci\ven_104c&dev_9066&subsys_90
67104c,pci\ven_104c&dev_9066&cc_028000,pci\ven_104c&dev_9066&cc_0280
#-018 Searching for compatible ID(s):
pci\ven_104c&dev_9066&rev_00,pci\ven_104c&dev_9066,pci\ven_104c&cc_028000,pc
i\ven_104c&cc_0280,pci\ven_104c,pci\cc_028000,pci\cc_0280
#I022 Found "PCI\VEN_104C&DEV_9066&SUBSYS_9067104C" in
c:\tiwlan\drivers\TNET1130.INF; Device: "TNET1130 WLAN Adapter"; Driver:
"TNET1130 WLAN Adapter"; Provider: "Texas Instruments"; Mfg: "Texas
Instruments"; Section name: "TIACXXP".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x00008001.
#I023 Actual install section: [TIACXXP]. Rank: 0x00008001. Effective driver
date: 03/10/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [TIACXXP] in
"c:\windows\inf\oem5.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of
"PCI\VEN_104C&DEV_9066&SUBSYS_9067104C&REV_00\5&3995D710&14&0008F0".
#W334 Failed to verify catalog when scanning file queue. Error 1168: Element
not found.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem5.inf" for
driver "TNET1130 WLAN Adapter" will be installed (Policy=Ignore). Error
1168: Element not found.
#W187 Install failed, attempting to restore original files.
#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem5.inf" for
driver "TNET1130 WLAN Adapter" will be installed (Policy=Ignore). Error
1168: Element not found.
#-024 Copying file "C:\TIWLAN\Drivers\FwRad16.bin" to
"C:\WINDOWS\System32\DRIVERS\FwRad16.bin".
#E360 An unsigned or incorrectly signed file "C:\TIWLAN\Drivers\FwRad16.bin"
for driver "TNET1130 WLAN Adapter" will be installed (Policy=Ignore). Error
1168: Element not found.
#-336 Copying file "C:\TIWLAN\Drivers\FwRad17.bin" to
"C:\WINDOWS\System32\DRIVERS\FwRad17.bin" via temporary file
"C:\WINDOWS\System32\DRIVERS\SET15.tmp".
#E360 An unsigned or incorrectly signed file "C:\TIWLAN\Drivers\FwRad17.bin"
for driver "TNET1130 WLAN Adapter" will be installed (Policy=Ignore). Error
1168: Element not found.
#-336 Copying file "C:\TIWLAN\Drivers\TNET1130.sys" to
"C:\WINDOWS\System32\DRIVERS\TNET1130.sys" via temporary file
"C:\WINDOWS\System32\DRIVERS\SET16.tmp".
#E360 An unsigned or incorrectly signed file
"C:\TIWLAN\Drivers\TNET1130.sys" for driver "TNET1130 WLAN Adapter" will be
installed (Policy=Ignore). Error 1168: Element not found.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [TIACXXP.Interfaces] from
"c:\windows\inf\oem5.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of
"PCI\VEN_104C&DEV_9066&SUBSYS_9067104C&REV_00\5&3995D710&14&0008F0".
#I121 Device install of
"PCI\VEN_104C&DEV_9066&SUBSYS_9067104C&REV_00\5&3995D710&14&0008F0" finished
successfully.
[2004/05/04 10:10:48 864.40 Driver Install]
A.F. - Here 3 part driver installed and started
#I306 DICS_START: Device has been started.
[2004/05/04 10:10:49 864.42 Driver Install]
#-019 Searching for hardware ID(s): ms_pschedmp
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{151E5349-857F-4E45-B8EE-EDD7B2DA1714}
#I022 Found "ms_pschedmp" in C:\WINDOWS\INF\netpsa.inf; Device: "Packet
Scheduler Miniport"; Driver: "Packet Scheduler Miniport"; Provider:
"Microsoft"; Mfg: "Microsoft"; Section name: "PSchedMP.ndi".
#I023 Actual install section: [PSchedMP.ndi]. Rank: 0x00000000. Effective
driver date: 07/01/2001.
#I063 Selected driver installs from section [PSchedMP.ndi] in
"c:\windows\inf\netpsa.inf".
#I320 Class GUID of device remains: {4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [PSchedMP.ndi.Interfaces] from
"c:\windows\inf\netpsa.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "ROOT\MS_PSCHEDMP\0002".
#I121 Device install of "ROOT\MS_PSCHEDMP\0002" finished successfully.
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0002".
#I306 DICS_START: Device has been started.
[2004/05/04 10:10:48 864.34]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{151E5349-857F-4E45-B8EE-EDD7B2DA1714}
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0000".
#I306 DICS_START: Device has been started.
[2004/05/04 10:10:48 864.35]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{151E5349-857F-4E45-B8EE-EDD7B2DA1714}
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of "ROOT\MS_PSCHEDMP\0001".
#I306 DICS_START: Device has been started.
[2004/05/04 10:10:51 864.50]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line:
rundll32.exe newdev.dll,ClientSideInstall
\\.\pipe\PNP_Device_Install_Pipe_0.{151E5349-857F-4E45-B8EE-EDD7B2DA1714}
#-166 Device install function: DIF_PROPERTYCHANGE.
#I292 Changing device properties of
"PCI\VEN_104C&DEV_9066&SUBSYS_9067104C&REV_00\5&3995D710&14&0008F0".
#I306 DICS_START: Device has been started.

TIA

Arkady

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:OTp5sCXMEHA.1156@TK2MSFTNGP09.phx.gbl...
> Show us the INF. Look at the setupapi.log for any error messages.
>
> --
> -Eliyas
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> http://www.microsoft.com/whdc/hwdev/driver/kb-drv.mspx
>
>
> "Arkady Frenkel" <arkadyf@hotmailxdotxcom> wrote in message
> news:urKE$6UMEHA.628@TK2MSFTNGP11.phx.gbl...
> > Hi !
> >
> > I want to allow user ( without admin rights ) access to device object of
> > the NDIS miniport driver ( use PCI card ).
> >
> > I changed permissions of the driver to full for users and that work.
I
> > read that the same possible to do by INF :
> >
> > 1)
> >
http://www.microsoft.com/whdc/driver/security/drvsecure.mspx?pf=true#secmod2
> > show the example line:
> >
> > HKR,,Security,,"D:P(A;;GA;;;SY)"
> >
> > So I wrote next in the INF
> >
> > [mydevice.Security]
> >
> > HKR,,Security,,"D:P(A;;GA;;;WD)"
> >
> > In the registry I see Key "security " with a string - "D:P(A ( 6
> > characters )
> >
> > Before I tried AU instead of WD with the same effect
> >
> > 2)
> >
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/setupapi/se
> > tup/specifying_a_security_descriptor_from_an_inf_file.asp
> >
> > show line :
> >
> > "D:P(A;CI;GA;;;BA)(A;CI;GA;;;SY)"
> >
> > I wrote next
> >
> > [mydevice.Security]
> >
> > "D:P(A;;GA;;;WD)"
> >
> > Cannot correctly install driver at all
> >
> > Any comments ?
> >
> > TIA
> >
> > Arkady
> >
> >
>
>