Thawte Certs
...from ww.thawte.com ...
The Basics of Code Signing\Development
Microsoft’s makecert.exe creates a
digital certificate. This is necessary in order to create an in-house
certificate authority to sign in-house software, but most users don’t need to
touch this tool. cert2spc.exe converts a digital certificate into the Software
Publisher Certificate, which is a certificate in code signing format.
pvk2pfx.exe imports the private key and software publisher certificate into a .pfx file. signtool.exe, the actual code signing tool, takes the .pfx
file as input.
Alternatively,
signatures may be stored in a separate .CAT file which is created with
Microsoft’s
Visual Studio also integrates code signing into the development environment.
Using the Solution Explorer, the programmer can select a certificate from the
Windows® Certificate Store,
from a file, or have Visual Studio gener- ate a test certificate. Thenceforth,
code builds will auto- matically sign the software.7
Many other
integrated development environments are ca- pable of running the command line
tools in an automated fashion as part of the build process. Once set up, code
signing is easy.
makecert (http://msdn.microsoft.com/en-us/library/bfsktky3%28VS.100%29.aspx).
cert2spc (http://msdn.microsoft.com/en-us/library/ f657tk8f%28VS.100%29.aspx).
pvk2pfx -. (http://msdn.microsoft.com/en-us/library/dd434714.aspx).
signtool - (http://msdn.microsoft.com/en-us/ library/8s9b9yaz%28VS.100%29.aspx).
makecat (http://msdn.microsoft.com/en-us/library/aa386967(VS.85).aspx)
%20t133819%20Microsoft_Visual_Studio.png)
Comments
Post a Comment