Page 1 of 1

Authenticode Signature Error during build Code signing error

Posted: Thu Jul 25, 2013 12:20 pm
by jtoledano
Recently purchased a code signing certificate from Comodo and downloaded and exported a .pfx file. Then moved this file to the server where I have my instllation files to build. Installaware 16 Studio is installed on another server. The server with Installaware seems to have the correct Comodo root and intermediate certificates installed.

When the build tries to code sign the installation exe or, if I have the option to automatically sign all checked on, I get the error message: Error during build: Code signing failed! I tried with time stamp and without, Password and not.

James

Re: Authenticode Signature Error during build Code signing e

Posted: Fri Jul 26, 2013 7:35 am
by FrancescoT
Dear James,

could you please have a look at the following topic?
http://www.installaware.com/forum/viewt ... f=2&t=4437

Regards

Re: Authenticode Signature Error during build Code signing e

Posted: Fri Jul 26, 2013 1:23 pm
by jtoledano
Francesco,

I did look at this older post. I believe you are referring to creating PVK/SPC certs and running that option. But I was assuming I could just sign using the PFX option in InstallAware 16. Or do I have to go the PVK/SPC route? A confusing issue I know, but any further insight on running it with the PFX option will help.

Thanks,
James

Re: Authenticode Signature Error during build Code signing e

Posted: Mon Jul 29, 2013 11:04 am
by FrancescoT
Dear James,

yes, you are right.

Honestly, I haven't tried but I'm not informed of a similar issue with other users.
Let me see if I'm able to find a certificate to test with.

Regards

Re: Authenticode Signature Error during build Code signing e

Posted: Wed Jul 31, 2013 11:43 am
by jtoledano
Here is where I am so far:

InstallAware 16 is installed on a Server 2003 SP2 machine with the latest MS SDK tools installed. I can successfully run Signtool.exe to code sign an exe but not timestamp. I tried running Signtool on a Windows 7 machine and no issues. The server can communicate out to the Comodo URL for time stamping, but the InstallAware Authenticode option still returns "Error during build: Code signing failed!". Also tried turning off Firewall and AntiVirus.

Any ideas?

Re: Authenticode Signature Error during build Code signing e

Posted: Thu Aug 01, 2013 5:09 am
by FrancescoT
... have you tried with installing IA on WIN 7?

Regards

Re: Authenticode Signature Error during build Code signing e

Posted: Thu Aug 01, 2013 6:47 am
by jtoledano
Just installed the latest IA16 on a W7 machine. It now runs with the Authenticode option, with Time Stamping. No errors during the build. I suspect there are some missing components on my Server 2003 machine and legacy issues, but not sure what at this point. Thanks for the help.

Regards, James

Re: Authenticode Signature Error during build Code signing e

Posted: Thu Aug 01, 2013 11:40 am
by FrancescoT
happy you solved!

Regards

Re: Authenticode Signature Error during build Code signing e

Posted: Tue Aug 06, 2013 1:29 pm
by jtoledano
Hi,

I installed IA 17 on my W7 machine, no problems with the installation and I can build my existing projects without Authenticode. However, if I select to compile with the Uncompressed build settings with Authenticode automatically signing all files being installed (exe, ocx, etc.), it builds OK, but not if I select Compressed build. If I use the Compressed build option, I can only code sign my package installation, but not all files. These are the last few lines of the build progress before it crashes:

Created Windows Installer database
Built installation executable
Injected setup languages
Code signing: C:\temp\Release\Single\test.exe
Injected runtime files
Error during build: Unable to build setup files: An error occured during (de)compression
Compressing install: componentstree.dfm (0%)

James

Re: Authenticode Signature Error during build Code signing e

Posted: Wed Aug 07, 2013 2:47 am
by FrancescoT
Dear James,

an update (IA 17.02) has been made available.
It should be just enough to re-generate your license file.

More info about this specific issue are available at;
http://www.installaware.com/forum/viewt ... 610#p35610

Regards