SetupBuilder 2015 Version 8.5 Build 4654 Pre-Release

[NewsArchive]

SetupBuilder 2015 Version 8.5 Build 4654 Pre-Release available:

http://www.lindersoft.com/downloads_licensed.htm

The new timestamp with a 3161 server is an optional feature now. I'll post
more compatibility information soon (required signtool.exe version,
compliant timestamp servers, etc.).

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

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 10 ready installations in minutes
--Official COMODO Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich!

4654 seems to have done the trick for us:

------------------------------------------------------
Processing Uninstall Code-Signing...
Adding Digital Certificate to Uninstall...
SIGNTOOL
SHA1: 0
Successfully code signed Uninstall Object
Process File Overhead Extraction
OK
Generating Uninstall Delta [8000]...
34 byte-mods applied
Signature source added: (6861;4835)
Signature patch added
OK
Finalizing application...
Adding Digital Certificate...
SIGNTOOL: \PDFX-Gold\PDFT41_CW.exe
SVER: 6.0.4002.0
SHA1: 0
Code signed successfully
Code Signing Certificate Expiration Date: 09/08/2017 - 977 day(s)
Extended Information: Tracker Software Products (Canada) Ltd - 0b 6d
e0 a1 b9 10 52 9e d0 17 9b eb 38 dc 38 4c
Terminating CSigning Process...[0]
OK
------------------------------------------------------

As you can see, no errors.

Thanks very much!

Craig E. Ransom
Tracker Software Products, Ltd.
http://tracker-software.com/

[NewsArchive]

Thanks for the update, Craig !!! The compiler is back to non-3161 timestamp
as the default.

#pragma CODESIGN_TSTYPE = "1" enables the optional timestamp with a 3161
server.

Friedrich

[NewsArchive]

Hi Friedrich!

Thanks for restoring that.

Perhaps you and Jane could collaborate on a "Code-Signing Cookbook"
webpage for your site that would have links to tools and websites that
handle RFC-3161 code-signing.


Craig E. Ransom
Tracker Software Products, Ltd.
http://tracker-software.com/

[NewsArchive]

Hi Craig,

Yes, we'll do.

As far as I can see, the latest SDK 8.1 signtool.exe (6.3.9600.16384) fixes
the RFC-3161 code-signing issue on Windows 7. The old SDK 8.0
(6.2.9200.16384) does not work as expected on Windows 7 (bug?!).

And with regard to the new SHA2 and double SHA1/SHA2 code-signing, it seems
to require Windows 8.0 and later at build-time.

More information soon...

Friedrich

[NewsArchive]

BTW, SHA-2 signing works on Windows 7, but this is still kind of useless for
the next two years because older Windows operating systems do not support
it. Within the next few months, quite a few users with SHA-2 compliant
certificates are going to switch to dual SHA-1/SHA-2 signing. Windows will
cease accepting SHA-1 certificates on January 1, 2017.

Friedrich

[NewsArchive]

Friedrich,

I had to search back for this message to find the options for this pragma.
Don't think it's made it into the current documentation.

Jane

[NewsArchive]

Jane,

> I had to search back for this message to find the options for this
> pragma. Don't think it's made it into the current documentation.

Ouch! You are right. I'll fix this, thank you !!!

Friedrich