SB7 Code-Signing headaches
Hi all!
I recently had my main development PC go down, but we had all the source
codes, etc. backed up on our FTP site so no major harm done.
Since moving to the new PC however, I can not get SB7 to code-sign my
installs, although it used to on my other PC just fine!
I have Jane Fleming's excellent PDF and gone through it, trying to pick
it up where we screwed up, but not certain.
We opted for the PFX file/password combination instead of the cpc/pvx
files, and I have specified SignTool.exe'sd fully-qualified pathname as
our "code signer" in SB7's Options dialog | Filenames page.
If anyone has been through a "forced port" and has a checklist for
getting Comodo's certificate to work, I'd like to hear it. Note that the
certificate was NOT obtained using a Win Vista/7 PC but and older Win XP
one, and we had been using it for for some time prior to the crash, and
it has not expired.
The end of the compile looks like:
SIGNTOOL
Compiler warning GEN1061: File not found:
Compiler error GEN1053: Code signing process failed. Error Code: 1
--------------------------------------- Done
---------------------------------------
PDF_XchangePro_setup.sb7 - 1 error(s), 2 warning(s)
Compilation Time: 26.91 sec.
Date/Time: 3/21/2013 -- 4:06:58PM
------------------------------- Compilation aborted
-------------------------------
(The two warnings are from checking two subinstalls we include with some
of our packages. They are supposed to come to me presigned and I just
include them. During signing they have the "Skip If Signed" option checked.)
Thanks in advance for any assistance!
--
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/
1 Attachment(s)
Re: SB7 Code-Signing headaches
Craig,
Try running signtool in wizard mode, you might get some clues.
(start it as signtool signwizard)
Also, do you have a capicom.dll file in your windows (or syswow) folder?
Jane
Re: SB7 Code-Signing headaches
Hi Jane!
capicom.dll is in the folder with signtool.exe.
I'll try signwizard and see what it says.
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/
Re: SB7 Code-Signing headaches
Hi Jane!
OK, signtool.exe running signwizard with capicom.dll will not let me
select the certificate PFX file that we have been using.
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/
Re: SB7 Code-Signing headaches
> Hi all!
>
> I recently had my main development PC go down, but we had all the source
> codes, etc. backed up on our FTP site so no major harm done.
Craig,
In addition to what Jane suggested - New computer? - if running Windows 7
or Windows 8, be sure and download the newer Windows 7 signtool.exe at this
location -
http://www.microsoft.com/downloads/d...2-529fa782d63b
Here is the previous SetupBuilder discussion for this:
http://www.lindersoft.com/forums/showthread.php?p=56858
Newer signtool.exe does not require CAPICOM.DLL
Encourager Software Developer Tips
http://www.encouragersoftware.com/so...evelopers.html
My company's Developer Tips also contains some helpful hints as well,
including what installation options for the W7 signtool.exe install.
David
--
From David Troxell - Product Scope 8! - Encourager Software
http://www.encouragersoftware.com/pr...-features.html
Re: SB7 Code-Signing headaches
Hi David!
I'll give that a try!
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/
1 Attachment(s)
Re: SB7 Code-Signing headaches
Hi Craig
I recently changed from using the .spc/.pvk and Signcode.exe to using just the .PFX
with Signtool on Win7Pro O/S.
At first it failed, just as your appears to be failing.
What I found was causing the problem was in the SB7 script, in the Details for the
#code-sign application script details, I had the old references to the Credentials
File and Private Key files as well as the new PFX File (optional). see attached
screenshot. Like this, it would not code-sign with Signtool.
Once I deleted the references to the Credentials File and Private Key files, it
started working. But it ONLY failed the first time after I started using the PFX
file. Now when working on older SB7 scripts, it works if I leave those old files in
there and just add the PFX details.
(Maybe a bug in SB7. Whoa, did I really say that! <G>) Maybe Friedrich needs to know
about this....
This may work for you.
JohnG
1 Attachment(s)
Re: SB7 Code-Signing headaches
Hi John!
This is what we have been using which worked on my old PC but won't sign
on the new PC.
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/
Re: SB7 Code-Signing headaches
Hi Craig,
> This is what we have been using which worked on my old PC but won't sign
> on the new PC.
It's not enough to simply have capicom.dll in the folder with signtool.exe.
It is a self-registration file.
http://www.lindersoft.com/forums/sho...icom#post66432
http://www.lindersoft.com/forums/sho...3010#post53010
Then switch the IDE to SignTool.exe (Tools | Options... | File Locations
tab) and you are done ;-)
Friedrich
Re: SB7 Code-Signing headaches
Hi Friedrich!
Sorry, but no. After installing capicom.dll from your site and changing
to use signtool.exe (had already done that), still getting errors:
SIGNTOOL
Compiler warning GEN1061: File not found:
Compiler error GEN1053: Code signing process failed. Error Code: 1
I used your capicom 2.0.1.2 installer exe as well. I even tried Regsvr32
on capicom.dll 2.0.1.2. It registered but no luck.
I'm holding off until later today and see about getting a replacement
certificate file from my company. Not a new one, just a copy of the one
we've been using.
Craig E. Ransom
Tracker Software Products, Ltd.
http://www.tracker-software.com/