GEN1053 - Code signing failed error code: 1 (SB8)

[NewsArchive]

I tried everything, it's just one of more code signing line, I even tried copy
&paste from line which one pass.
What else can be done here? That's not even recently added, compiled fine before
Thanks for any suggestion
Darko

[NewsArchive]

Darko,

> I tried everything, it's just one of more code signing line, I even tried
> copy &paste from line which one pass.
> What else can be done here? That's not even recently added, compiled fine
> before

If it worked fine before and nothing else changed, it's caused by one or
more of the following:

1. Certificate expired
2. Firewall blocks access to the timestamp server
3. Timestamp server down

Friedrich

[NewsArchive]

BTW, make sure the external .exe to be signed has a valid PE Header. And
enable the "Skip if file is already code signed". Microsoft Authenticode
does not work on files with an invalid/corrupt PE Header.

Friedrich

[NewsArchive]

Thanks, but as I said, it's just happen to be the last one of many #code sign lines,
and I copy & paste one to be sure

And exe itself run just fine so I believe it's PE header is ok?
Darko

[NewsArchive]

> Thanks, but as I said, it's just happen to be the last one of many #code
> sign
> lines, and I copy & paste one to be sure

Quite a few developers are using different code-signing certificates. You
would be surprised how often I have seen this issue and the developer was
using a valid and an exired certificate in different lines <g>

> And exe itself run just fine so I believe it's PE header is ok?

No. It's very well possible that the .exe works fine but has an invalid PE
Header structure. Authenticode (which itself modifies the PE Header) checks
the structure before code-signing it and if it is invalid, it terminates the
signing process.

But if it is always the last line (even if you change the code-signing
sequence) then a buggy virus/spyware update causes it in your case. Perhaps
an "over-protective" bug in the system because it noticed that Microsoft
Authenticode "manipulated" too many files and then it simply locks the
process.

Friedrich

[NewsArchive]

Thanks Friedrich for pointing to right direction, I linked that one exe with
"lib" option instead of "dll" as was before,
and now SB (ok, signtool.exe) compiles happily. So there must be something with
exe seems so.
Thanks again
Darko

[NewsArchive]

Hi Darko,

> Thanks Friedrich for pointing to right direction, I linked that one exe
> with "lib" option instead of "dll" as was before, and now SB (ok,
> signtool.exe) compiles happily. So there must be something with exe seems
> so.

Perfect. Thanks for the update.

Friedrich

[NewsArchive]

> I tried everything, it's just one of more code signing line

In most cases, this is caused by a buggy virus definition update or firewall
update. Try to add the Microsoft Authenticode tool to the "exclusion list"
(to skip real-time monitoring) to see if this can work around it. Or switch
to another timestamp server.

It's not caused by your SetupBuilder compiler so you can't do anything else
(in your project).

Friedrich