Creating Test Certificates
This topic describes how to use the MakeCert tool to create test certificates. In most development environments, test certificates generated through MakeCert should be sufficient to test the installation and loading of test-signed drivers or driver packages. For more information about this type of test certificate, see MakeCert Test Certificate.
The following command-line example uses MakeCert to complete the following tasks:
Create a self-signed test certificate named Contoso.com(Test). This certificate uses the same name for the subject name and the certificate authority (CA).
Put a copy of the certificate in an output file that is named ContosoTest.cer.
Put a copy of the certificate in a certificate store that is named PrivateCertStore. Putting the test certificate in PrivateCertStore keeps it separate from other certificates that may be on the system.
Use the following MakeCert command to create the Contoso.com(Test) certificate:
makecert -r -pe -ss PrivateCertStore -n CN=Contoso.com(Test) -eku 126.96.36.199.188.8.131.52.3 ContosoTest.cer
The -r option creates a self-signed certificate with the same issuer and subject name.
The -pe option specifies that the private key that is associated with the certificate can be exported.
The -ss option specifies the name of the certificate store that contains the test certificate (PrivateCertStore).
The -n CN= option specifies the name of the certificate, Contoso.com(Test). This name is used with the SignTool tool to identify the certificate.
The EKU option inserts a list of one or more comma-separated, enhanced key usage object identifiers (OIDs) into the certificate. For example,
-eku 184.108.40.206.220.127.116.11.2inserts the client authentication OID. For definitions of allowable OIDs, see the Wincrypt.h file in CryptoAPI 2.0.
ContosoTest.cer is the file name that contains a copy of the test certificate, Contoso.com(Test). The certificate file is used to add the certificate to the Trusted Root Certification Authorities certificate store and the Trusted Publishers certificate store.
The certificate store that contains the test certificate is added to the list of certificate stores that Windows manages for the user account on the development computer on which the certificate store was created.
A developer has to create only one MakeCert test certificate to sign all driver packages on a development computer.
For more information about the MakeCert tool and its command-line arguments, see MakeCert.
After creating a test certificate, use the CertMgr tool to add it to the Trusted Root Certification Authorities certificate store. For more info, see Installing Test Certificates.
Also refer to the readme file
Selfsign_readme.htm in the
bin\selfsign directory of the Windows Driver Kit (WDK).