Problems Sign my (32Bit) driver on Windows Vista OS

NTDEV
1

Hi,

I have few problems when trying to Sign my (32Bit)
driver and loading it on Vista OS.
Here is a little description that correspond my
driver:

  1. I am using WDK 5384 with the latest “signtool” that
    I have downloaded from Microsoft website
    (http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx).

  2. My driver is not a part of the logo program.

  3. The driver is registered itself during App runtime.

  4. My certificate for signing method is Verisign Class

  6. The signature method I am using is an “embedded
    signature” using cross-certificate.

  7. The signing method is finished successfully
    (verification is successful using the “signtool” app
    both on signing and testing machines).

I have encountered few problems which I Hope you can
help.

  1. If I run “MSInfo32.exe”, then go to “Software
    environments” -> “Signed Drivers”, my driver appear as
    not digitally Signed.

  2. “Event Viewer” recognizes the driver as not
    digitally signed.

  3. “Windows Defender” App is launching a Popup Balloon
    which asks the user to allow the operation, Even
    though the driver appear as digitally signed.

If further information is needed - please let me know

Thanks in advance

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

2

I already downloaded this file…

I also downloaded the latest CAPICOM.DLL…

There are few more application there…

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Alon
Sent: Sunday, July 30, 2006 2:52 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Problems Sign my (32Bit) driver on Windows Vista OS

Hi,

I have few problems when trying to Sign my (32Bit)
driver and loading it on Vista OS.
Here is a little description that correspond my
driver:

  1. I am using WDK 5384 with the latest “signtool” that
    I have downloaded from Microsoft website
    (http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx).

  2. My driver is not a part of the logo program.

  3. The driver is registered itself during App runtime.

  4. My certificate for signing method is Verisign Class

  6. The signature method I am using is an “embedded
    signature” using cross-certificate.

  7. The signing method is finished successfully
    (verification is successful using the “signtool” app
    both on signing and testing machines).

I have encountered few problems which I Hope you can
help.

  1. If I run “MSInfo32.exe”, then go to “Software
    environments” -> “Signed Drivers”, my driver appear as
    not digitally Signed.

  2. “Event Viewer” recognizes the driver as not
    digitally signed.

  3. “Windows Defender” App is launching a Popup Balloon
    which asks the user to allow the operation, Even
    though the driver appear as digitally signed.

If further information is needed - please let me know

Thanks in advance

Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Hi,

I really didn’t understand the reply

“Elad Raz” wrote in message
news:xxxxx@ntdev…
>I already downloaded this file…
>
> I also downloaded the latest CAPICOM.DLL…
>
> There are few more application there…
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf
Of Alon
> Sent: Sunday, July 30, 2006 2:52 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Problems Sign my (32Bit) driver on
Windows Vista OS
>
> Hi,
>
> I have few problems when trying to Sign my (32Bit)
> driver and loading it on Vista OS.
> Here is a little description that correspond my
> driver:
>
> 1. I am using WDK 5384 with the latest “signtool”
that
> I have downloaded from Microsoft website
>
(http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx).
>
> 2. My driver is not a part of the logo program.
>
> 3. The driver is registered itself during App
runtime.
>
> 4. My certificate for signing method is Verisign
Class
> 3.
>
> 5. The signature method I am using is an “embedded
> signature” using cross-certificate.
>
> 6. The signing method is finished successfully
> (verification is successful using the “signtool” app
> both on signing and testing machines).
>
> I have encountered few problems which I Hope you can
> help.
>
> 1. If I run “MSInfo32.exe”, then go to “Software
> environments” -> “Signed Drivers”, my driver appear
as
> not digitally Signed.
>
> 2. “Event Viewer” recognizes the driver as not
> digitally signed.
>
> 3. “Windows Defender” App is launching a Popup
Balloon
> which asks the user to allow the operation, Even
> though the driver appear as digitally signed.
>
> If further information is needed - please let me
know
>
> Thanks in advance
>
>
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam
protection around
> http://mail.yahoo.com
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR
Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com