Codesigning failure with new certificate

[NewsArchive]

Hi,

I just received my new certificate from Comodo.
Exported it to PFX.

Tested with Setupbuilder 10.0.5710.

1) On my Window 10 machine it codesigns with both SHA1, SHA2 & Dual Sign
without problems.
Signtool Ver.: 10.0.10586.15

2) On my Windows XP SP3 machine it gives a "Compiler error GEN1053" error
trying to codesign with SHA1.
Signtool Ver.: 5.2.3790.2568
If I put my old PFX certificate back that expires in 3 days (16/07/2018) it
codesigns 100% with SHA1 on my Windows XP SP3 machine.

What could be the problem?
I still need my Windows XP machine to work because I still have some C6.3
projects running on it.
Please help.

Regards

Johan de Klerk

[NewsArchive]

Hi Johan,

> 2) On my Windows XP SP3 machine it gives a "Compiler error GEN1053" error
> trying to codesign with SHA1.
> Signtool Ver.: 5.2.3790.2568

That's the problem. You need the later signtool to be able to do dual
code signing and code signing with SHA2

You can get it by downloading the MS Windows SDK. It can be found
*somewhere* on the MS website<g>

Best regards,

--
Arnor Baldvinsson
Icetips Alta LLC

[NewsArchive]

Hi Arnor,

I know on Win XP it will only Codesign SHA1.
It works with my old certificate with Signtool Ver.: 5.2.3790.2568.
I only do SHA1 on the Win XP machine, not SHA2.
But not with the new certificate.

Regards

Johan de Klerk

[NewsArchive]

Some feedback.

I got it working.

I had to export it as a SHA1 only PFX file for use on Win XP.
With my previous certificate it had both SHA1 & SHA2 exported and I could
use the same PFX file in Win XP and Win 10.

I now have a PXF with only SHA1 in for Win XP and another PFX file with SHA1
& SHA2 for Win 10.

Maybe the new certificates are generated in a different way than the old
cetificates.
Got it working so I am all good.

Regards

Johan de Klerk