Results 1 to 9 of 9

Thread: SHA-2 code-signing on old Windows 7 SP1 machines

  1. #1

    Default SHA-2 code-signing on old Windows 7 SP1 machines

    All,

    if you still have to support SHA-2 code-signing on older Windows 7 machines,
    the following might help.

    To handle SHA-2 code-signing (including SHA-2 time-stamping) on Windows 7
    SP1 you need:

    1. SetupBuilder 10.

    2. Windows 7 SP1.

    3. SignTool.exe version 6.1.7000.0.

    4. Microsoft Capicom installed and registered.

    You can use the following tool to install Capicom:
    http://www.lindersoft.com/forums/sho...3010#post53010

    Note 1: you can't use SIGNTOOL.EXE Version 6.1.7000 to handle dual
    SHA-1/SHA-2 code-signing. Only SHA-2 signing works.

    Note 2: it all depends on the Windows OS patch level. Some more information
    here:
    http://www.lindersoft.com/forums/sho...6115#post86115

    Hope this helps.

    --
    Friedrich Linder
    Lindersoft | SetupBuilder | www.lindersoft.com
    954.252.3910 (within US) | +1.954.252.3910 (outside US)

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

  2. #2

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Friedrich,

    > Note 1: you can't use SIGNTOOL.EXE Version 6.1.7000 to handle dual
    > SHA-1/SHA-2 code-signing. Only SHA-2 signing works.

    But if you have 6.3.9600 you can.

    --
    Lee White

    RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
    Report Faxing.....: http://www.cwaddons.com/products/afe/
    ---Enroll Today---: http://CWaddons.com

    Creative Reporting: http://www.CreativeReporting.com

    Product Release & Update Notices
    http://twitter.com/DeveloperPLUS

    Windows 8 brings us "The Oval, Bumper Car, Roller Coaster of Wait!"
    And, now, Windows 10 brings us "The Inch Worm, Bumper Car of Wait!"

  3. #3

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Lee,

    >> Note 1: you can't use SIGNTOOL.EXE Version 6.1.7000 to handle dual
    >> SHA-1/SHA-2 code-signing. Only SHA-2 signing works.
    >
    > But if you have 6.3.9600 you can.

    Yes and no <g>. The main problem with 6.3.9600 and Windows 7 is that you
    need a very *very* specific patch level to get it to work with SHA-2
    (timestamping). On most machines SIGNTOOL 6.3.9600 crashes or does not
    create a valid SHA-2 timestamp.

    Friedrich
    Attached Images Attached Images  

  4. #4

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Hi Friedrich,

    My findings on Win7 with SIGNTOOL 6.3.9600 are that SHA256 is corrected
    generated but kills the previously created SHA1. What is the asset of having
    both SHA1 as well as SHA256 anyway?

    Sim

  5. #5

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Hi Sim,

    > My findings on Win7 with SIGNTOOL 6.3.9600 are that SHA256 is corrected
    > generated but kills the previously created SHA1. What is the asset of
    > having both SHA1 as well as SHA256 anyway?

    Only SetupBuilder 10 can handle "dual" code-signing. Previous SB versions
    do not know nothing about dual code signatures.

    Friedrich

  6. #6

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    >> My findings on Win7 with SIGNTOOL 6.3.9600 are that SHA256 is corrected
    >> generated but kills the previously created SHA1. What is the asset of
    >> having both SHA1 as well as SHA256 anyway?
    >
    > Only SetupBuilder 10 can handle "dual" code-signing. Previous SB versions
    > do not know nothing about dual code signatures.

    BTW, my previous screenshot taken on a Windows 7 machine shows a GPF when
    code-signing a file with SHA-2 and adding a required SHA-2 timestamp. It
    works fine with SIGNTOOL 6.3.9600 using a non-SHA-2 timestamp or no
    timestamp at all.

    http://www.lindersoft.com/forums/sho...6115#post86115

    You need at least a SHA-2 signature with a SHA-2 timestamp. Or better, a
    SHA-1 signature with SHA-1 timestamp *and* SHA-2 signature with SHA-2
    timestamp (aka "dual" code-signed).

    Friedrich

  7. #7

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Friedrich,

    > > But if you have 6.3.9600 you can.
    >
    > Yes and no <g>. The main problem with 6.3.9600 and Windows 7 is that you
    > need a very *very* specific patch level to get it to work with SHA-2
    > (timestamping). On most machines SIGNTOOL 6.3.9600 crashes or does not
    > create a valid SHA-2 timestamp.

    See? I always KNEW I was special.... or is that spatial?

    All I can report is that the current, and static (no updates), Win7 I
    use handles it... as to exactly WHY, beats me!<g>

    If memory serves I did have to jump through some hoops and install a
    few things to make it work but I have no idea what they were.

    --
    Lee White

    RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
    Report Faxing.....: http://www.cwaddons.com/products/afe/
    ---Enroll Today---: http://CWaddons.com

    Creative Reporting: http://www.CreativeReporting.com

    Product Release & Update Notices
    http://twitter.com/DeveloperPLUS

    Windows 8 brings us "The Oval, Bumper Car, Roller Coaster of Wait!"
    And, now, Windows 10 brings us "The Inch Worm, Bumper Car of Wait!"

  8. #8

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Were there any bears chasing you? <g>

    >
    >If memory serves I did have to jump through some hoops and install a
    >few things to make it work but I have no idea what they were.

    Jeff Slarve
    www.jssoftware.com

    Untie that A-String

  9. #9

    Default Re: SHA-2 code-signing on old Windows 7 SP1 machines

    Jeff,

    > Were there any bears chasing you? <g>

    Now that you mention it...

    Lee White

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •