It would be nice if your code signing improved to use named certificates installed on the machine (instead of given pfx files) and gave more control over the code signing parameters (for example /a /n /td /fd /d /du parameters).
For example, we currently sign our binaries as follows:
"C:\Program Files (x86)\Windows Kits\10\bin\x64\signtool.exe" sign /a /n "Our EV Cert Name" /tr http://timestamp.digicert.com /td sha256 /fd sha256 /d "App Signing Description" /du "App Signing Detail" "TargetFile.exe"
It would be great if IA Authenticode page allowed all of those parameters to be configured and passed them through. Or let us specify the signing command line to be executed and substituted "TargetFile.exe" with a variable.
Got a problem you cannot solve? Try here.
1 post • Page 1 of 1
Who is online
Users browsing this forum: Google [Bot] and 20 guests