Comodo Timestamp Server Problem (April 30, 2009)

[NewsArchive]

All,

We noticed that the Comodo timestamp server does not work stable today.
More and more support requests with regard to "Compiler error GEN1053: Code
signing process failed. Error Code: -1" are coming in here.

Please note that this is NOT a SetupBuilder problem. I would suggest to
switch to the VeriSign timestamp server for today.

--
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]

While you're on your Black Sea cruise with nothing to do....

One option in SB configuration could be the URLs for the two main timestamp
servers (and possibly space for a third), from which the user could select
in the CodeSign script elements.

And possibly a bit more explicit error message for 1053 on the code sign
function. You know - "This could mean I can't find your file or your
certificate or that your certificate has expired. But if code-signing has
suddenly stopped working, the time stamp server you're using may be down.
Do you want to switch and try using a different time stamp server?"

JAT...

Jane

[NewsArchive]

Hi Jane,

> One option in SB configuration could be the URLs for the two main
> timestamp servers (and possibly space for a third), from which the user
> could select in the CodeSign script elements.

The #code-sign application..." directive already provides a combo with
pre-defined timestamp servers.

It's not possible to add this to the General Properties in SB6, but is
already available in SB7.

> And possibly a bit more explicit error message for 1053 on the code sign
> function. You know - "This could mean I can't find your file or your
> certificate or that your certificate has expired. But if code-signing has
> suddenly stopped working, the time stamp server you're using may be down.
> Do you want to switch and try using a different time stamp server?"

Good idea. Unfortunately, the Microsoft Authenticode tool does not return
any error code. So if "Compiler error GEN1053: Code signing process failed.
Error Code: -1" is reported, it can be anything. An invalid Win32
application file header, an expired or invalid code-signing certificate, an
invalid or down timestamp server, a firewall issue when connecting to the
server, a virus or spyware tool that blocks the Authenticode signing
process, a wrong password, and more <g>.

But I'll add the above to the documentation, thank you!

Friedrich

[NewsArchive]

> All,
>
> We noticed that the Comodo timestamp server does not work stable today.
> More and more support requests with regard to "Compiler error GEN1053: Code
> signing process failed. Error Code: -1" are coming in here.
>
> Please note that this is NOT a SetupBuilder problem. I would suggest to
> switch to the VeriSign timestamp server for today.

http://timestamp.verisign.com/scripts/timstamp.dll

David

--
From David Troxell - Product Scope 7 - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
Profile Exchanges - www.encouragersoftware.com/profile/
http://www.profileexchanges.com/blog/