Comodo expire date

[NewsArchive]

Some of my exe's show 2017 and some show 2020 like it should be.
Same build multiple exe's

Dan Scott

[NewsArchive]

Dan,

> Some of my exe's show 2017 and some show 2020 like it should be.
> Same build multiple exe's

Were ALL EXE's actually recompiled by Clarion so the cert was
overwritten and do you have the compiler directive set to skip files
that are already signed?

--
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!"

[NewsArchive]

Dan,

> Some of my exe's show 2017 and some show 2020 like it should be.
> Same build multiple exe's

what Lee said.

Two possible reasons for this:

1. the exe's were already code-signed with your "old" certificate.
Recompile the exe's and use your "new" code-signing certificate to
code-sign.

-or-

2. your "old" certificate is still valid and you are using the "old"
certificate in your project to code-sign. Make sure you are using the "new"
(valid until 2020) certificate.

BTW, you can check the timestamp on the exe's to find out what the problem
is (see attached screenshot).

Friedrich