View Full Version : Trouble with signcode
NewsArchive
12-03-2008, 03:08 AM
See attached.
I was using signcode without problems so far, but lately I have the
compilation fail when it try to sign the uninstaller. It succeeds however in
sign an exe in the install. How is this possible?
Using SB 6.9 #2415. By the way, it worked before... any chance of a bug in
latest version?
--
Jorge Alejandro Lavera - Huenuleufu Development SRL
www.ClarionDevelopment.com - Custom development.
www.ClarionTemplates.com - Templates for Clarion.
www.IP-Tree.com - Analize and document your network.
www.InBack.com - Protect your data.
NewsArchive
12-03-2008, 03:09 AM
> See attached.
> I was using signcode without problems so far, but lately I have the
> compilation fail when it try to sign the uninstaller. It succeeds however
> in sign an exe in the install. How is this possible?
> Using SB 6.9 #2415. By the way, it worked before... any chance of a bug in
> latest version?
No, there is not a bug in the latest SetupBuilder version.
If one code-signing process succeeds (#code-sign application) then you have
that one filled correctly. Check the code-sign information in your "Digital
Signature".
Hope this helps.
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
NewsArchive
12-03-2008, 03:09 AM
Yes!!! As always. Thank you! I had wrong the timestamp string in the
project settings. Couldn't spot it before.
I wish Microsoft retuns more helpful error messages in signtool <g>.
--
Jorge Alejandro Lavera - Huenuleufu Development SRL
www.ClarionDevelopment.com - Custom development.
www.ClarionTemplates.com - Templates for Clarion.
www.IP-Tree.com - Analize and document your network.
www.InBack.com - Protect your data.
NewsArchive
12-03-2008, 03:09 AM
>> Hope this helps.
>
> Yes!!! As always. Thank you! I had wrong the timestamp string in the
> project settings. Couldn't spot it before.
> I wish Microsoft retuns more helpful error messages in signtool <g>.
<G>
Yes, I found it by trial and error. I played with it and "2" is returned if
the timestamp server is not accessible (server down, URL incorrect,
connection blocked, etc.). It returns "1" if the certificate password is
incorrect.
If the path to the certificate is incorrect, the compiler will report an
additional "File not found" error.
Friedrich
NewsArchive
12-03-2008, 03:10 AM
> See attached.
> I was using signcode without problems so far, but lately I have
> the compilation fail when it try to sign the uninstaller. It succeeds
> however in sign an exe in the install. How is this possible?
> Using SB 6.9 #2415. By the way, it worked before... any chance of a bug
> in latest version?
By the way, make sure that the timestamp server is accessible. SignTool.exe
returns "2" if the timestamp server cannot be accessed.
HTH,
--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910
SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes
-- Official Comodo Code Signing and SSL Certificate Partner
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.