Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Problem with code signing

Hi,
We have started running into a certificate issue with our most recent build (you can download it at https://degoo.com/download). Our code signing certificate has expired but this build was built before the cert expired. I was under the impression that timestamping was supposed to solve this particular issue. When checking the certificate with signtool.exe we get the following output:

Code: Select all

Signing Certificate Chain:
    Issued to: StartCom Certification Authority
    Issued by: StartCom Certification Authority
    Expires:   Wed Sep 17 21:46:36 2036
    SHA1 hash: 3E2BF7F2031B96F38CE6C4D8A85D3E2D58476A0F

        Issued to: StartCom Class 2 Primary Intermediate Object CA
        Issued by: StartCom Certification Authority
        Expires:   Wed Oct 25 00:01:46 2017
        SHA1 hash: D893C4F678F891F2823CD078AA5E1C48FD1DA225

            Issued to: Degoo Backup AB
            Issued by: StartCom Class 2 Primary Intermediate Object CA
            Expires:   Tue Oct 21 19:41:58 2014
            SHA1 hash: D395396C8170E1018029E664D8C5F071BDA07650

The signature is timestamped: Sun Oct 05 21:44:01 2014
Timestamp Verified by:
    Issued to: Thawte Timestamping CA
    Issued by: Thawte Timestamping CA
    Expires:   Fri Jan 01 01:59:59 2021
    SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656

        Issued to: Symantec Time Stamping Services CA - G2
        Issued by: Thawte Timestamping CA
        Expires:   Thu Dec 31 01:59:59 2020
        SHA1 hash: 6C07453FFDDA08B83707C09B82FB3D15F35336B1

            Issued to: Symantec Time Stamping Services Signer - G4
            Issued by: Symantec Time Stamping Services CA - G2
            Expires:   Wed Dec 30 01:59:59 2020
            SHA1 hash: 65439929B67973EB192D6FF243E6767ADF0834E4

SignTool Error: WinVerifyTrust returned error: 0x800B0101
        A required certificate is not within its validity period when verifying
against the current system clock or the timestamp in the signed file.

Number of files successfully Verified: 0
Number of warnings: 0
Number of errors: 1
As you can see the timestamping occurred on Sun Oct 05 2014 and the cert expires on Tue Oct 21 2014. Any idea on why this is happening?
Yrlec
Posts: 30
Joined: Wed Jun 20, 2012 3:49 pm

Re: Problem with code signing

I should also add that we are building using Advanced Installer 9.8.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Problem with code signing

Hello,

I apologize for my delayed reply.

I'm not sure why this happened. Can you please make sure you have correctly set the "Time Stamp URL" field from "Digital Signature" page?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”