Code signing problem

[Stein Inge]

Hi folks
I'm trying to make a patch that is to be downloaded from our web server. I have a certificate that I would like to use. But when building the patch, I get the following error from VisualPatch:

Code signing patch file...
Error 7274: Execute program error executing code signing tool - 0 (1)

Build failed - 1 Error(s), 0 Warning(s)

I screendump of my Code Settings window is attached. Maybe I have done something obvious wrong that can be spottet from the picture?

I wonder how I should read this error message? What does "0 (1)" mean, and does this give any indication of what could be wrong?

My system is Vista Ultimate and VisualPatch 3.0.2.0

Best regards
Stein Inge Haaland

[jassing]

I haven't used signtool; just signcode
I know that if you enter the wrong password; you get a similar error using signcode.. have you tried signing using the tool itself; rather than integrating into VP?

[Darryl]

Also, in version 3.0.3.0 which is the current version, we are now passing additional information returned from the code signing tool to the output window, which may provide further details as to what is occurring.

Hope that helps.

[jassing]

Also, in version 3.0.3.0 which is the current version, we are now passing additional information returned from the code signing tool to the output window, which may provide further details as to what is occurring.

Hope that helps.

Problem turned out that actual certificate was missing...
I haven't used one certificate vendor that made the process "super simple" to obtain and download all the required files -- comodo was at least pleasant to deal with (not to mention inexpensive)

[Ulrich]

I haven't used one certificate vendor that made the process "super simple" to obtain and download all the required files -- comodo was at least pleasant to deal with (not to mention inexpensive)

My process wasn't that pleasant, as I had difficulties to get them accept my and my own company's documents, but a week and several document scans later I was informed that my certificate was finally ready. But they are surely the less expensive around today.

VeriSign wants US$ 499, Thawte goes for US$ 299, GlobalSign wants US$ 229, and Comodo (InstantSSL) asks US$ 180 for a code-signing certificate, all valid one year, with small discounts for longer periods.

It should be noted, however, that there is some kind of SSL Partner who offers a gateway to the Comodo certificate, and you can purchase the same certificate for only US$ 99 per year. If you are interested, go here (https://secure.ksoftware.net/code_signing.html).

Ulrich

[jassing]

My process wasn't that pleasant, as I had difficulties to get them accept my and my own company's documents, but a week and several document scans later I was informed that my certificate was finally ready. But they are surely the less expensive around today.

VeriSign wants US$ 499, Thawte goes for US$ 299, GlobalSign wants US$ 229, and Comodo (InstantSSL) asks US$ 180 for a code-signing certificate, all valid one year, with small discounts for longer periods.

It should be noted, however, that there is some kind of SSL Partner who offers a gateway to the Comodo certificate, and you can purchase the same certificate for only US$ 99 per year. If you are interested, go here (https://secure.ksoftware.net/code_signing.html).

Ulrich

I actually discovered comodo thru a friend once I had trouble getting a certificate thru Verisign -- despite having a DUNS #; they wouldn't accept me as "me" (I am Josh Assing, dba jAssing Consulting) -- however, they wouldn't accept any of that for the certificate "Josh Assing" "jAssing Consulting" "Josh Assing Consulting" "J.Assing consulting" -- nothing; but had a duns # and have been around for a long time... Commodo had my certificate ready in a few days.

one of the costs of a certificate is the research required to verify your information. So there is typically a 'lag time'.

-josh