Driver Signing Problem

Hallo,

For VISTA I have build a signed driver package with a "VeriSign Class 3 Code Signing 2000 CA"
ID. Our Rule is using the same package for Windows XP.

In Vista the installation is OK but in Windows XP I can see some errors in setupapi.log

#E360 An unsigned or incorrectly signed file "c:\windows\inf\oem9.inf" for driver "XXX" will be installed (Policy=Ignore). Error 1168:

What is not correct with my signing ? The result: class installer entrys (ICON, name) are not
installed in registry and CoInstaller DLL is not running by the installation.

When I break this signed package (insert a space into INF file) all is fine.

elli

Ivco
Thu Apr 19 12:13:42 CDT 2007

If you use signability to sign the driver make sure that the OS is set
correctly. For example:
/os:264 - means Windows XP, 32-bit version and Windows Vista, 32-bit version

Take a look at this:
http://msdn2.microsoft.com/en-us/library/aa906345.aspx

Have fun

Mathias Ellinger wrote:
> Hallo,
>
> For VISTA I have build a signed driver package with a "VeriSign Class 3 Code Signing 2000 CA"
> ID. Our Rule is using the same package for Windows XP.
>
> In Vista the installation is OK but in Windows XP I can see some errors in setupapi.log
>
> #E360 An unsigned or incorrectly signed file "c:\windows\inf\oem9.inf" for driver "XXX" will be installed (Policy=Ignore). Error 1168:
>
> What is not correct with my signing ? The result: class installer entrys (ICON, name) are not
> installed in registry and CoInstaller DLL is not running by the installation.
>
> When I break this signed package (insert a space into INF file) all is fine.
>
> elli

Mathias
Fri Apr 20 02:49:57 CDT 2007

Ivco wrote:

> If you use signability to sign the driver make sure that the OS is set correctly. For example:
> /os:264 - means Windows XP, 32-bit version and Windows Vista, 32-bit version


signability sucks ... I must always close a notepad window ... in automatic MSBuild
process with some packages that is not so funny.
I use the the Winqual submission and inf2Cat.exe for CAT generation and signtool for
binary signing.

When the package is signed the class installer entrys are ignored and I cannot find no
entrys for given class GUID in registry. Class installer DLL is not installed in windows
direcory. The result, no ICON in device manager ...

My fix for Windows XP: my CoInstaller DLL make the entries in class key and the INF File
have a extra part to copy the class installer DLL. That is only a fix than I have the
security dialogs too. Gr...

elli


>
> Take a look at this:
> http://msdn2.microsoft.com/en-us/library/aa906345.aspx
>
> Have fun
>
> Mathias Ellinger wrote:
> > Hallo,
> >
> > For VISTA I have build a signed driver package with a "VeriSign Class 3 Code Signing 2000 CA"
> > ID. Our Rule is using the same package for Windows XP.
> >
> > In Vista the installation is OK but in Windows XP I can see some errors in setupapi.log
> >
> > #E360 An unsigned or incorrectly signed file "c:\windows\inf\oem9.inf" for driver "XXX" will be installed (Policy=Ignore). Error 1168: What is not correct with my signing ? The result: class installer entrys (ICON, name) are not
> > installed in registry and CoInstaller DLL is not running by the installation.
> >
> > When I break this signed package (insert a space into INF file) all is fine.
> >
> > elli



--

Owen
Fri Apr 20 10:58:03 CDT 2007


try adding the command line 'taskkill /FI "WINDOWTITLE eq signability*"'=
=

after calling signability


On Fri, 20 Apr 2007 08:49:57 +0100, Mathias Ellinger <me@nospam.de> wrot=
e:

> Ivco wrote:
>
>> If you use signability to sign the driver make sure that the OS is se=
t =

>> correctly. For example:
>> /os:264 - means Windows XP, 32-bit version and Windows Vista, 32-bit =
=

>> version
>
>
> signability sucks ... I must always close a notepad window ... in =

> automatic MSBuild
> process with some packages that is not so funny.
> I use the the Winqual submission and inf2Cat.exe for CAT generation an=
d =

> signtool for
> binary signing.
>
> When the package is signed the class installer entrys are ignored and =
I =

> cannot find no
> entrys for given class GUID in registry. Class installer DLL is not =

> installed in windows
> direcory. The result, no ICON in device manager ...
>
> My fix for Windows XP: my CoInstaller DLL make the entries in class ke=
y =

> and the INF File
> have a extra part to copy the class installer DLL. That is only a fix =
=

> than I have the
> security dialogs too. Gr...
>
> elli
>
>
>>
>> Take a look at this:
>> http://msdn2.microsoft.com/en-us/library/aa906345.aspx
>>
>> Have fun
>>
>> Mathias Ellinger wrote:
>> > Hallo,
>> >
>> > For VISTA I have build a signed driver package with a "VeriSign Cla=
ss =

>> 3 Code Signing 2000 CA"
>> > ID. Our Rule is using the same package for Windows XP.
>> >
>> > In Vista the installation is OK but in Windows XP I can see some =

>> errors in setupapi.log
>> >
>> > #E360 An unsigned or incorrectly signed file =

>> "c:\windows\inf\oem9.inf" for driver "XXX" will be installed =

>> (Policy=3DIgnore). Error 1168: What is not correct with my signing =
? =

>> The result: class installer entrys (ICON, name) are not
>> > installed in registry and CoInstaller DLL is not running by the =

>> installation.
>> >
>> > When I break this signed package (insert a space into INF file) all=
=

>> is fine.
>> >
>> > elli
>
>
>



-- =

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/