|
Posted by hq4000@hotmail.com on April 3, 2007, 8:41 am
If you were Registered and logged in, you could reply and use other advanced thread options
I requested an Enterprise internal Authenticode code signing
certificate through my IT. I am able to use the certificate to sign
my kernel driver. Then I proceeded to test the installation of the
kernel driver in the lab. Following are summary of my testing
results:
1. some machines failed to upgrade an older version of same driver
(test signed with self-signed certificate created with makecert).
32-
bit Windows XP SP2.
2. some machines installed the driver ok but without Digital Signer
in
device driver in device manager view. 32-bit Windows XP SP2.
3. one machine installed OK with proper Digital Signer presented in
device manager view. Initially, it also failed as case 1 above. Then
I played it with certmgr.exe with my certificate and .p7b file that
contains the company CA chain. I am not sure exact sequence of
events
happened. This is AMD64 Windows XP. And it seems like I am not able
to reproduce the situation in the other 32-bit Windows XP SP2
machines.
Please note that all machines verified the certificate path OK.
That's they saw the certificate's my company Root CA OK. Please also
note that I had ensured that my company Root CA is installed properly
in Trusted Root Certificatopm Authorities store in localmachine.
What is going on?
| 
XML site map