SB6 installer signing

[NewsArchive]

Merry Christmas, Friedrich :)

In the spirit of jollity (is that a word?) I decided to download and play
with SB6 developer today.
Signing doesn't work for me if I specify a password in the project.
The MS password window pops open, waits the 2 seconds that you've mentioned
in a prior thread, I sometimes see a quick flash of black dots as the
password gets put into it, sometimes don't see them. Either way, the
compiler reports that signing failed.
If I don't put a password in the IDE and just enter it manually when that
window pops open, signing and time stamping work fine.

Jane

[NewsArchive]

Jane,

Merry X'mas to you too from France :)

hdere it works flawlessly with my comoddo digital signature ....
I also see the popu window and nothing else but the compiler reports
signature ok and when I right click on the exe signed all is well there

maybe a pb with the url given or something else ?

JP

--

Thank you

Jean-Pierre GUTSATZ

Best Regards

[NewsArchive]

crois pas, J-P...
All the URL information is present in SB6.
When I input the password manually, it works.
When I also put the password into the information page in SB6, I get
"Compiler warning GEN1053: Code signing process failed"

Joyeux Noël des États-Unis

Jane

[NewsArchive]

Jane,

Crois savoir ... :)

I think you should remove all from tha main windows - did the same at
first - and add it in source like FL showed us a couple of posts back

[ Initialize Setup ]
! --- Define commonly used constants ---
#include script "Common Definitions.sbi"
/* #embed Vista manifest "J:\cgf.exe" */
#code-sign application "J:\cgf.exe"
#code-sign application "J:\upg.exe"
#code-sign application "J:\upg3.exe"

I commented the manfest thing as I have a pb with 3rdParty templates but the
code signin from source works perfectly here...

JP

--

Thank you

Jean-Pierre GUTSATZ

Best Regards

[NewsArchive]

ah... non... Merçi, mais c'est pas ça...
My problem is with signing the installer package itself, as set in the
Project | Settings | Digital Signature screen, not with individual items
within it.
At the moment, I'm still signing my components manually.

But you aroused my curiosity. I tried the #code-sign to sign a component in
the installer and that also doesn't work for me unless I type in the
password manually when the password window pops open.

On that subject... the Release Notes warn that the uninstaller .EXE isn't
signed. Do you know if it's possible to use #code-sign to sign it somehow?


Jane

[NewsArchive]

Jane,

I really think there is a pb with your pwd or cerificate or something !

Here I tried your way of signing the installer AND my 3 exe's and all is
perfect ! désolé ... <G>

If you want to test it with my cerificate etc please contact me by email
.....

JP
--

Thank you

Jean-Pierre GUTSATZ

Best Regards

[NewsArchive]

Thank you, Jean-Pierre

But my certificate works fine when I input the password manually. Something
must just hate me :(

Jane

[NewsArchive]

Jane,

In case ... is your certificate from commodo also ?
Want me to try it here ?

JP

--

Thank you

Jean-Pierre GUTSATZ

Best Regards

[NewsArchive]

Yes, it's from Comodo.
But it's not important to me at this point. I use a batch file to sign my
stuff before building an installer anyway.
I just thought I'd report to Friedrich what seems (at least on my machine)
not to be working.

Merçi encore,

Jane

[NewsArchive]

Hi Jane,

Thank you :) We had great Christmas and I hope the same for you!

I fear "something" on your machine does not allow the compiler to give focus
to the code-signing tool. As I understand it, the "improvement" in SB6
makes it even worse on your machine (compared to SB5).

Do you have Tweak UI / Power Toys for Windows XP or something like that and
"Prevent applications from stealing focus" is enabled?

Thanks,
Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

[NewsArchive]

Hi Friedrich,
No, no Power Toys-type stuff.
I just tried a sample script with NOTHING else open on my computer - one
..exe to sign and the installer itself.
For both signings the window popped up, I saw the two second pause, then saw
the password dots get filled in (so it did have focus) then the window
immediately closed (less than a half second after the password is entered)
and both signings fail.
It's not a big deal. I'll just sign my stuff manually. Just wanted to let
you know.

On a related topic, your release notes mention that the uninstaller will not
get signed. Is there some point where I could inject a #msgbox to pause the
script, then find the uninstaller in some temporary directory and manually
sign it?

Jane

[NewsArchive]

Hi Jane,

> Hi Friedrich,
> No, no Power Toys-type stuff.
> I just tried a sample script with NOTHING else open on my computer - one
> ..exe to sign and the installer itself.
> For both signings the window popped up, I saw the two second pause, then
> saw the password dots get filled in (so it did have focus) then the window
> immediately closed (less than a half second after the password is entered)
> and both signings fail.
> It's not a big deal. I'll just sign my stuff manually. Just wanted to
> let you know.

Very, very strange. I did not receive any similar report so it seems to be
machine specific. And I cannot reproduce this problem on any of our 12 test
machines :-(

The next SB6 build will be available within the next 7-10 days. I'll try to
display the error code returned from the code-signing tool. Perhaps this
will give us more information.

> On a related topic, your release notes mention that the uninstaller will
> not get signed. Is there some point where I could inject a #msgbox to
> pause the script, then find the uninstaller in some temporary directory
> and manually sign it?

The problem is that the uninstall is compiled (on-the-fly) at runtime. We
use our "zero-byte overhead" technology here. The uninstall executable is
not included in the install package (0 byte overhead). That means there is
nothing to sign when you build your installer <g>.

I already have an idea on how to solve this problem (in theory). I'll keep
you posted.

Thanks,
Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6
Create Windows Vista ready installations in minutes

[NewsArchive]

A more specific errorcode would be interesting, Friedrich.
All I get is SB's "Compiler warning GEN1053"

Jane