Code Signing

Code signing still not working automatically in the 1750 release I'm
afraid Friedrich.

Now you've put a delay in, I can see that the password field is only
getting 4 or 5 characters (it varies). My password is 6 characters long.

This always worked on this machine and only stopped working when I
installed IE7.
--
Simon Craythorn
InterVations, Inc
http://www.intervations.com

Hi Simon,

Thanks for the info. I also have IE7 here on three machines, but it always
works fine. But I see some strange things on these IE7 machines when
running other applications (IE7 seems to slow down sings).

Perhaps we have to wait one second longer before sending the first character
to give the dialog a little more time to come to the foreground.

Am I allowed to send you an internal sbuilder.exe build later this week?

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

Of course, no problem. Anything I can do to help.
--
Simon Craythorn
InterVations, Inc
http://www.intervations.com

Could I also suggest a modification to how you do this...

If you import the .pvk and .spc files into your Windows Certificate
store (you can do this with the pvkimprt tool available here...
http://www.microsoft.com/downloads/d...displaylang=EN)
then you can call signcode with -cn <certificate common name> rather
than -spc <filename> -pvk <filename>. Doing it this way doesn't require
a password to be entered. The password is verified when the certificate
is imported, using it to sign after that doesn't require the password.
--
Simon Craythorn
InterVations, Inc
http://www.intervations.com

Friedrich,
I understand your sticking with signcode.exe to be compatible with Win98...
Afraid I'm always going to consider the MS window popping up and (knock on
wood) getting the password filled in as a kludge. <G> It doesn't work
reliably on my machine, and apparently I'm not the only one.

If I don't enable digital signature on the Project | Settings tab, I can
just use #run to run a signing batch file after the script compiles.

The problem is that if I DO tick the Enable Installer Integrity Check box
and then sign the installer using my batch file, the integrity check fails
when I run the installer.

If I tell SB6 to sign the installer, hit cancel when the password window
pops up, then run my batch file... everything is fine.

So... would it be possible to add a check box to the digital signature tab
in Project | Settings... to run my own signing batch file after the script
finishes compiling rather than invoking signcode.exe? That way, those of
use who aren't having great success with the fill-in-the-window trick would
have an alternative.

Jane

It is working fine (multiple exe and installer signing) here with the latest
revision and IE7 installed (bhishing filter off). Perhaps a user defined delay
would be helpful?

Greg Fasolt