title: Code Signing Timestamp still expires using Timestamp server
body: <p>Not sure why, but when using Code Signing using symantec's timestamp server it sets the expiration for the year 2020. This defeats the purpose of using a timestamp server if my program is still going to expire.</p>
  
  <p>Following is the output when using signtool.exe to verify the timestamp application:</p>
  
  <pre><code>Signature Index: 0 (Primary Signature)
  Hash of file (sha1): A6F0CEC09F02900D7977C60A87567031D0D96C7A
  
      Signing Certificate Chain:
          Issued to: thawte Primary Root CA
          Issued by: thawte Primary Root CA
          Expires:   Wed Jul 16 19:59:59 2036
          SHA1 hash: 91C6D6EE3E8AC86384E548C299295C756C817B81
  
              Issued to: Thawte Code Signing CA - G2
              Issued by: thawte Primary Root CA
              Expires:   Fri Feb 07 19:59:59 2020
              SHA1 hash: 808D62642B7D1C4A9A83FD667F7A2A9D243FB1C7
  
                  Issued to: My Company
                  Issued by: Thawte Code Signing CA - G2
                  Expires:   Tue Aug 11 19:59:59 2015
                  SHA1 hash: E45B4CBFBA095DB9465F2371C161EF500201561B
  
      The signature is timestamped: Wed Oct 22 12:15:44 2014
      Timestamp Verified by:
          Issued to: Thawte Timestamping CA
          Issued by: Thawte Timestamping CA
          Expires:   Thu Dec 31 19:59:59 2020
          SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656
  
              Issued to: Symantec Time Stamping Services CA - G2
              Issued by: Thawte Timestamping CA
              Expires:   Wed Dec 30 19:59:59 2020
              SHA1 hash: 6C07453FFDDA08B83707C09B82FB3D15F35336B1
  
                  Issued to: Symantec Time Stamping Services Signer - G4
                  Issued by: Symantec Time Stamping Services CA - G2
                  Expires:   Tue Dec 29 19:59:59 2020
                  SHA1 hash: 65439929B67973EB192D6FF243E6767ADF0834E4
  
  
      Successfully verified: SetupGoVivoConsole.exe
  
      Number of files successfully Verified: 1
      Number of warnings: 0
      Number of errors: 0
  </code></pre>
  
  <p>Please note that this certificate is set for 1 year expiry, so it is using a timestamp from the server that Symantec provides. According to the (limited) documentation on this subject, using a timestamp server when signing an application should eliminate the application from expiring after the certificate has expired. According to the information I see above, this is not the case as my application will stop functioning on <code>Tue Dec 29 19:59:59 2020</code>.</p>
  
  <p>The command I am using for signtool is as follows :</p>
  
  <p><code>signtool.exe sign /f "certificate.pfx" /ac "thawte.crt" /p "mypassword" /t http://timestamp.verisign.com/scripts/timstamp.dll "ExecutableToSign.exe"</code></p>