Driver Signing Status

[Ranga]

Hi all,

I opened the Device Manager, and looked for the Driver details of devices installed.


But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me in this regard.

With Regards,
Ranga.

 

[KM]

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in your build?

Btw, why do you really need the driver to be signed?

 

[Ranga]

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

 

[KM]

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

 

[Slobodan Brcin \(eMVP\)]

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as a key to unlock some options (DRM like).
One way would be to test if all USB drivers are signed (including filter drivers). This would prevent in some measure easy hacking
by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

 

[KM]

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as a key

to unlock some options (DRM like).

One way would be to test if all USB drivers are signed (including filter

drivers). This would prevent in some measure easy hacking

by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in

your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver details of devices installed.


But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me in this regard.

With Regards,
Ranga.

 

[Ranga]

No, KM.

We want this to be present in XPE OS. That is the specific objective.

I had added driver signing user Interface, But this did not help me
out.

I installed the drivers during FBA and also during runtime. Still the
problem existed.

Can anyone help me out.

Regards,
Ranga.

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as a key

to unlock some options (DRM like).

One way would be to test if all USB drivers are signed (including filter

drivers). This would prevent in some measure easy hacking

by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in

your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver details of devices installed.


But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me in this regard.

With Regards,
Ranga.

 

[KM]

Ranga,

The only thing I can think of here is the driver's .cat file. However, you mentioned that you were able to install the driver on XP
Pro without signature problem, right? This is confusing...
Try to figure out what .cat file is used for the driver you are playing with on XP Pro. Make sure the same files are used on XPe.

Sorry, can't help you here much.

--
Regards,
KM, BSquare Corp.

No, KM.

We want this to be present in XPE OS. That is the specific objective.

I had added driver signing user Interface, But this did not help me
out.

I installed the drivers during FBA and also during runtime. Still the
problem existed.

Can anyone help me out.

Regards,
Ranga.

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as a key

to unlock some options (DRM like).

One way would be to test if all USB drivers are signed (including filter

drivers). This would prevent in some measure easy hacking

by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver details of devices installed.


But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me in this regard.

With Regards,
Ranga.

 

[Ranga]

Thanks KM.

I am adding required drivers from Windows Embedded Studio. Now I run
the FBA. After the FBA process is complete and the Explorer shell is
launched, i went to the Device Manager.

I found that the Driver Signer to be "" Not Digitallay Signed"".

This happened to be there for all the Microsoft components. I also
added, FBA driver signing component as well.

Still I get the same error. What could be the reason for this?

Please help me regarding this.

Regards,
Ranga.

Ranga,

The only thing I can think of here is the driver's .cat file. However, you mentioned that you were able to install the driver on XP
Pro without signature problem, right? This is confusing...
Try to figure out what .cat file is used for the driver you are playing with on XP Pro. Make sure the same files are used on XPe.

Sorry, can't help you here much.

--
Regards,
KM, BSquare Corp.

No, KM.

We want this to be present in XPE OS. That is the specific objective.

I had added driver signing user Interface, But this did not help me
out.

I installed the drivers during FBA and also during runtime. Still the
problem existed.

Can anyone help me out.

Regards,
Ranga.

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as a key to unlock some options (DRM like).
One way would be to test if all USB drivers are signed (including filter drivers). This would prevent in some measure easy hacking
by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for signing to work
but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in
your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver details of devices installed.


But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me in this regard.

With Regards,
Ranga.

 

[KM]

Ranga,

It does sound like you are missing some components.
Check if the following components are in your image (I am pretty sure they
are but just in case):
Primitive: Setupapi, [Visibility=200]
PnP (User-mode), [Visibility=1000]
PnP (Kernel-mode), [Visibility=200]
Session Manager (Windows subsystem), [Visibility=1000]
Primitive: Crypt32, [Visibility=200]
Primitive: Wintrust, [Visibility=200]
(these are beside the components you have already mentioned earlier).

Another suggestion I have is you can try XPProEmulation.slx image from
www.xpefiles.com (Development Utilities/Main folder) to see if your driver
gets signed properly there. It does not help you with the issue but will
bring in more info.

KM

Thanks KM.

I am adding required drivers from Windows Embedded Studio. Now I run
the FBA. After the FBA process is complete and the Explorer shell is
launched, i went to the Device Manager.

I found that the Driver Signer to be "" Not Digitallay Signed"".

This happened to be there for all the Microsoft components. I also
added, FBA driver signing component as well.

Still I get the same error. What could be the reason for this?

Please help me regarding this.

Regards,
Ranga.


"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

The only thing I can think of here is the driver's .cat file. However, you mentioned that you were able to install the driver on XP
Pro without signature problem, right? This is confusing...
Try to figure out what .cat file is used for the driver you are playing with on XP Pro. Make sure the same files are used on XPe.

Sorry, can't help you here much.

--
Regards,
KM, BSquare Corp.

No, KM.

We want this to be present in XPE OS. That is the specific objective.

I had added driver signing user Interface, But this did not help me
out.

I installed the drivers during FBA and also during runtime. Still the
problem existed.

Can anyone help me out.

Regards,
Ranga.






"KM" <konstmor@nospam_yahoo.com> wrote in message

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as

a key
to unlock some options (DRM like).

One way would be to test if all USB drivers are signed (including

filter
drivers). This would prevent in some measure easy hacking

by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for

signing to
work

but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just

installed
it

at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00.

But
this,

probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in
your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver

details of
devices installed.

But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver

signing
status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me

in this
regard.

With Regards,
Ranga.

 

[Ranga]

Dear KM,

Thanks for your response. But, even then, I have added all the
abovesaid components, eventhen, I get the same error. What could be
the reason behind this.

Please help me.

With Regards,
Ranga.

Ranga,

It does sound like you are missing some components.
Check if the following components are in your image (I am pretty sure they
are but just in case):
Primitive: Setupapi, [Visibility=200]
PnP (User-mode), [Visibility=1000]
PnP (Kernel-mode), [Visibility=200]
Session Manager (Windows subsystem), [Visibility=1000]
Primitive: Crypt32, [Visibility=200]
Primitive: Wintrust, [Visibility=200]
(these are beside the components you have already mentioned earlier).

Another suggestion I have is you can try XPProEmulation.slx image from
www.xpefiles.com (Development Utilities/Main folder) to see if your driver
gets signed properly there. It does not help you with the issue but will
bring in more info.

KM

Thanks KM.

I am adding required drivers from Windows Embedded Studio. Now I run
the FBA. After the FBA process is complete and the Explorer shell is
launched, i went to the Device Manager.

I found that the Driver Signer to be "" Not Digitallay Signed"".

This happened to be there for all the Microsoft components. I also
added, FBA driver signing component as well.

Still I get the same error. What could be the reason for this?

Please help me regarding this.

Regards,
Ranga.


"KM" <konstmor@nospam_yahoo.com> wrote in message

a key
to unlock some options (DRM like).filter
drivers). This would prevent in some measure easy hackingsigning to
work

but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just

installed
it

at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00.

But
this,

probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in
your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver

details of
devices installed.

signing
status.

in this
regard.

 

[KM]

Ranga,

I have no more ideas.
Can you try XPProEmulation on your hardware and see if drivers get signed properly?

--
Regards,
KM, BSquare Corp.

Dear KM,

Thanks for your response. But, even then, I have added all the
abovesaid components, eventhen, I get the same error. What could be
the reason behind this.

Please help me.

With Regards,
Ranga.

Ranga,

It does sound like you are missing some components.
Check if the following components are in your image (I am pretty sure they
are but just in case):
Primitive: Setupapi, [Visibility=200]
PnP (User-mode), [Visibility=1000]
PnP (Kernel-mode), [Visibility=200]
Session Manager (Windows subsystem), [Visibility=1000]
Primitive: Crypt32, [Visibility=200]
Primitive: Wintrust, [Visibility=200]
(these are beside the components you have already mentioned earlier).

Another suggestion I have is you can try XPProEmulation.slx image from
www.xpefiles.com (Development Utilities/Main folder) to see if your driver
gets signed properly there. It does not help you with the issue but will
bring in more info.

KM

Thanks KM.

I am adding required drivers from Windows Embedded Studio. Now I run
the FBA. After the FBA process is complete and the Explorer shell is
launched, i went to the Device Manager.

I found that the Driver Signer to be "" Not Digitallay Signed"".

This happened to be there for all the Microsoft components. I also
added, FBA driver signing component as well.

Still I get the same error. What could be the reason for this?

Please help me regarding this.

Regards,
Ranga.


"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

The only thing I can think of here is the driver's .cat file. However,

you mentioned that you were able to install the driver on XP

Pro without signature problem, right? This is confusing...
Try to figure out what .cat file is used for the driver you are playing

with on XP Pro. Make sure the same files are used on XPe.

Sorry, can't help you here much.

--
Regards,
KM, BSquare Corp.


No, KM.

We want this to be present in XPE OS. That is the specific objective.

I had added driver signing user Interface, But this did not help me
out.

I installed the drivers during FBA and also during runtime. Still the
problem existed.

Can anyone help me out.

Regards,
Ranga.






"KM" <konstmor@nospam_yahoo.com> wrote in message

Slobodan,

I agree, in cases where driver is included in a protection scheme it is
better be signed and verified.

Thanks for the good point

Konstantin

Hi Konstantin,

There is one possible use of signed drivers.
Consider that you want to use USB dongle for copy protection or as

a key
to unlock some options (DRM like).

One way would be to test if all USB drivers are signed (including

filter
drivers). This would prevent in some measure easy hacking

by replacing or putting some filter driver along the USB stack.

Best regard,
Slobodan

Ranga,

Verification of what? You still need to test if the driver is working
properly wheher it is signed or not.

I don't know which components you really need to include for

signing to
work

but my guess would be that including "Driver Signing User Interface" and
resolving its dependencies should be enough.

Did you install the driver during FBA? Did you try installing it manually at
runtime? (resolving its dependencies first)
Basically, have you componentized "the kit" yourself, or just installed
it
at run time?

Check your FBAlog.txt and SetupApi.log for possible related errors.

You can also try disabling driver signing policy by setting this registry
value [HKLM\SOFTWARE\Microsoft\Driver Signing],"Policy"=hex:00. But
this,
probalby, doesn't help you with the issue.

KM

Thanks KM for your support.

This problem is with all the drivers present in the kit.

This Digital is needed for verification purposes.

What are the components that are required for this purpose?

With Regards,
Ranga.

"KM" <konstmor@nospam_yahoo.com> wrote in message

Ranga,

Which driver? You custom one? Do you have a .cat file for driver in
your
build?

Btw, why do you really need the driver to be signed?

--
Regards,
KM, BSquare Corp.


Hi all,

I opened the Device Manager, and looked for the Driver

details of
devices installed.

But in Windows XP Professional, this is displayed as

Digital Signer: Microsoft Windows Xp Publisher


In XP Embedded, this is displayed as

Digital Signer: Not Signed.

I added the following components to enable the Driver signing
status.

Driver Signing User Interface
FBA: Driver Signing
Signature Verifier

But I could not get it correct.

What is the component responsible for this? Please help me

in this
regard.

With Regards,
Ranga.