Certificate Creation tool requests a password when accessing file-based private keys.
The Certificate Creation tool supports many arguments, and Table 1.3 lists some of the more useful ones. You should consult the .NET Framework SDK documentation for full coverage of the Certificate Creation tool.
Switch | Description |
---|---|
-e | Specifies the date when the certificate becomes invalid |
-m | Specifies the duration—in months—that the certificate remains valid |
-n | Specifies an X.500 name to associate with the certificate. This is the name of the software publisher that people will see when they view details of the SPC you create |
-sk | Specifies the name of the CSP key store in which to store the private key |
-ss | Specifies the name of the certificate store where the Certificate Creation tool should store the generated X.509 certificate |
-sv | Specifies the name of the file in which to store the private key |
Once you have created your X.509 certificate with the Certificate Creation tool, you need to convert it to an SPC with the Software Publisher Certificate Test tool (cert2spc.exe). To convert the certificate TestCertificate.cer to an SPC, use the command cert2spc TestCertificate.cer TestCertificate.spc. The Software Publisher Certificate Test tool doesn't offer any optional switches.
The final step before you can use your test SPC is to trust the root test CA, which is the default issuer of the test certificate. The Set Registry tool (setreg.exe) makes this a simple task with the command setreg 1 true. When you have finished using your test SPC, you must remove trust of the root test CA using the command setreg 1 false.
No comments:
Post a Comment