Have to live with it but a real pain. Following all the threads, but
still not there yet. Not sure of the cause, using a Win 7 machine,
wrong setting somewhere, the newer 8.1 codesign.exe I downloaded.
Don Harvey
Printable View
Have to live with it but a real pain. Following all the threads, but
still not there yet. Not sure of the cause, using a Win 7 machine,
wrong setting somewhere, the newer 8.1 codesign.exe I downloaded.
Don Harvey
Don,
> Have to live with it but a real pain. Following all the threads,
> but still not there yet. Not sure of the cause, using a Win 7
> machine, wrong setting somewhere, the newer 8.1 codesign.exe I
> downloaded.
See the million posts below <g>.
For example:
http://www.lindersoft.com/forums/sho...51-Again-SHA-1
Most Windows 7 machines do NOT support dual code-signing. You need Windows
8.1 or better to have a rock solid code-signing environment.
So you did NOT follow all the threads <g> ;-) It's not a code-signing
issue. It's a Windows 7 issue!
Friedrich
Lee mentioned an SDK that satisfies the code signing ability's
requirements on Windows 7.
Jeff Slarve
www.jssoftware.com
Twitter free since Jan 11, 2016
I'll search help files & Google for you.
Grammar troll's, are the worse.
I know, have printed out or read 76 items, it must be on item 77 :)
Guess probably the easiest approach is to update this machine.
Don Harvey
Printing out doesn't count unless you actually read them <G>
Jane Fleming
Hi Friedrich,
> Most Windows 7 machines do NOT support dual code-signing. You need Windows
> 8.1 or better to have a rock solid code-signing environment.
My 32bit Development Win7 VM hasn't been updated since early 2015 and it
can still happily dual code sign;) I will upgrade it to W10 soon, but
until then it's saying in early 2015 mode<g>
Best regards,
--
Arnor Baldvinsson
Icetips Alta LLC
Of course I did, it was exciting reading :)
Upgrading to Win10 solved the problem here. Was reluctant for fear some
of the older programs would no longer work but thankfully the upgrade
was pretty smooth.
Don Harvey
Hi Jeff,
> Lee mentioned an SDK that satisfies the code signing ability's
> requirements on Windows 7.
IMO, it depends on the specific patch level of the Windows 7 machine.
Unfortunately, Microsoft changed something code-signing wise in one of the
2015 patches.
See attached screenshots. This is a Windows 7 SP1 machine and dual
SHA-1/SHA-2 code-signing always fails. Tested with signtool.exe versions
6.1.7000, 6.1.7600, 6.2.9200, 6.3.9600 and 10.0.20140. SHA-1 in the dual
code-signing process always succeeds, but SHA-2 fails. But it's not caused
by the SHA-2 signature per-se. SHA-2 only signing even works with 6.1.7000
(according to Microsoft, it was version 6.1.7600 that introduced SHA-2).
Friedrich
Hi Arnor,
>> Most Windows 7 machines do NOT support dual code-signing. You need
>> Windows 8.1 or better to have a rock solid code-signing environment.
>
> My 32bit Development Win7 VM hasn't been updated since early 2015 and it
> can still happily dual code sign;) I will upgrade it to W10 soon, but
> until then it's saying in early 2015 mode<g>
I also had a perfectly working dual code-signing environment under Windows 7
SP1 (64-bit). But on September 25, 2015 I updated the machine and one of
the security updates killed "dual" mode <g>.
Friedrich
Friedrich,
> This is a multi-part message in MIME format.
> -----------------2950704976
> Content-Type: text/plain; charset=us-ascii
>
> Hi Jeff,
>
> > Lee mentioned an SDK that satisfies the code signing ability's
> > requirements on Windows 7.
>
> IMO, it depends on the specific patch level of the Windows 7 machine.
> Unfortunately, Microsoft changed something code-signing wise in one of the
> 2015 patches.
Did you change something in your reader?
Many of your messages today are kinda messed up and look like the
above, at least in my reader.<g>
Lee White