Announcement

Collapse
No announcement yet.

New Version Available 9.5.1.0

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • New Version Available 9.5.1.0

    Today (March 2, 2016) we have released a new version of Setup Factory (v9.5.1.0). Commercial users can download the new full installer from your customer portal.

    This release contains the following features and bug fixes:
    • Feature: Added SHA-256 code signing support.
    • Feature: Added the ability to dual-sign setups (SHA-256 and SHA-1).
    • Feature: Added a password field for the code signing certificate(s).
    • Feature: Added a few items to the System.GetOSProductInfo action's constants.
    • Change: Removed support for signing with signcode.exe, instead use signtool.exe.
    • Fix: Made several changes in order to prevent errors that may occur due to anti-virus scanning when launching the setup and installing files.
    • Fix: Fixed a bug where registering/unregistering fonts could hang the setup on some systems.
    • Fix: Fixed a bug where temporary font files were not be deleted from the setup's temp folder after the setup completes.
    • Fix: Fixed a bug where session variables set via an uninstall INI file on the command line weren't being set in the uninstall.
    • Fix: Fixed a bug where if a custom screen contained a GroupBox control, tabbing through the controls failed to work properly.
    • Fix: Fixed a bug where using the UninstallData.RemoveItem action with the UNINDATA_SUPPORTFILES item type wasn't removing the item from the uninstall's configuration file.
    • Fix: Recompiled the distributed copies of lua5.1.dll to pass the binary analyzer tests DBCheck and NXCheck.
    • Fix: Changed references in Setup Factory from Windows Server 10 to Windows Server 2016.

  • #2
    have a problem with the new codesigning... getting an error.

    SignTool Error: Invalid option: /fd

    Code signing setup runtime
    > Signing with SHA-1...
    > Signing command: "C:\Signcode\signtool.exe" sign /f "C:\Software\Art Dept\Thawte\DevCert_2015-2018\OS201505303591.pfx" /p "****" /t "http://timestamp.globalsign.com/scripts/timstamp.dll" /d "ArtistScope Web Browser" /du "www.artistscope.com" "C:\Users\ARTIST~1\AppData\Local\Temp\_ir_sf_build _0\ir_tmp_rtm.tmp"
    Done Adding Additional Store
    Successfully signed and timestamped: C:\Users\ARTIST~1\AppData\Local\Temp\_ir_sf_build_ 0\ir_tmp_rtm.tmp


    > Signing with SHA-256...
    > Signing command: "C:\Signcode\signtool.exe" sign /f "C:\Software\Art Dept\Thawte\DevCert_2015-2018\OS201505303591.pfx" /p "****" /fd sha256 /tr "http://timestamp.globalsign.com/scripts/timstamp.dll" /td sha256 /d "ArtistScope Web Browser" /du "www.artistscope.com" /as "C:\Users\ARTIST~1\AppData\Local\Temp\_ir_sf_build _0\ir_tmp_rtm.tmp"

    SignTool Error: Invalid option: /fd


    Error 4304: Execute program error executing code signing tool - 0 (1)
    ArtistScope - Copy Protection & DRM Software

    Comment


    • #3
      That problem was solved by updating signtool.exe from Windows SDK 7.1.

      But now a new problem...

      > Signing with SHA-256...
      > Signing command: "C:\Signcode\signtool.exe" sign /f "C:\Software\Art Dept\Thawte\DevCert_2015-2018\OS201505303591.pfx" /p "****" /fd sha256 /tr "http://timestamp.globalsign.com/scripts/timstamp.dll" /td sha256 /d "ArtistScope Web Browser" /du "www.artistscope.com" /as "C:\Users\ARTIST~1\AppData\Local\Temp\_ir_sf_b uild _0\ir_tmp_rtm.tmp"
      SignTool Error: Invalid option: /as


      Error 4304: Execute program error executing code signing tool - 0 (1)

      Running SUF using "Run as Adninistrator" did not help.

      Click image for larger version

Name:	signtool.jpg
Views:	164
Size:	84.0 KB
ID:	297444
      ArtistScope - Copy Protection & DRM Software

      Comment


      • #4
        You need the signtool from Windows 8.1 SDK. Also, the timestamp URLs for SHA-256 and SHA-1 should not be the same.

        Ulrich

        Comment


        • #5
          Ok, thanks. Have updated to signtool SDK/8.1 and this time pointed to the resource in the SDK rather than copy signtool.exe to a work folder. That is now signing.

          So, different URLs for timestamps? Can you recommend which to use?
          ArtistScope - Copy Protection & DRM Software

          Comment

          Working...
          X