Let's suppose you would like to sign a windows file but for some obscure reason you cannot use MS signtool or signcode utilities. For instance, you would like to do this on Linux. This requires the following software:
- OpenSSL
- osslsigncode
- pvktool
References:
- OpenSSL PKCS#12 FAQ
- Converting a PFX file to SPC and PVK files
- Work around to moving Microsoft® Authenticode® (Multi-Purpose) Certificate to different machines running different Windows platforms
- CAcert Wiki: Authenticode
Activation Record Blog
Subscribe to:
Post Comments (Atom)
1 comments:
I tried osslsigncode and signcode (from Mono) with equivalent certificates and keys (except for converting pvk ino der for osslsigncode) on the same exe. And then I looked properties of the files in Windows XP. And it turned out that Ossl-signed file didn't contain valid signature yet it did have certificate info and even signature info, but the summary in the properties said that the file doesn't have a signature. The product of signcode was ok though. However I tried to find the solution, there was no even a hint of my problem in search results. So, I cannot figure out what is the problem of such a difference? Both tools use Authenticode format and I used the latest versions of them, etc. Please light my search path :)
Post a Comment