¿Por qué mi verificación de firma de código (autenticación de MS) falla?

Question

He publicado this question y tengo un certificado de firma de código recién acuñado de Thawte.

Seguí las instrucciones (o eso creía) y la firma del código afirma tener éxito, sin embargo, cuando intento verificar que la herramienta muestre un error.

Los resultados del paso de verificación parecen mostrar que es correcto, sin embargo, hay un error y ninguna explicación sobre por qué existe el error.

Cualquier comentario o sugerencia es muy apreciada.

línea de comandos para firmar exe:

signtool sign /f mdt.pfx /p password /t http://timestamp.verisign.com/scripts/timstamp.dll test.exe 

Resultados:

The following certificate was selected: 
    Issued to: [my company] 

    Issued by: Thawte Code Signing CA 

    Expires: 4/23/2011 7:59:59 PM 

    SHA1 hash: 7D1A42364765F8969E83BC00AB77F901118F3601 


Done Adding Additional Store 


Attempting to sign: test.exe 

Successfully signed and timestamped: test.exe 


Number of files successfully Signed: 1 

Number of warnings: 0 

Number of errors: 0 

Tenga en cuenta que no hay errores o advertencias.

Ahora, cuando intento para verificar imaginar mi sorpresa:

signtool verify /v test.exe 

resultados en:

Verifying: test.exe 

SHA1 hash of file: 490BA0656517D3A322D19F432F1C6D40695CAD22 
Signing Certificate Chain: 
    Issued to: Thawte Premium Server CA 

    Issued by: Thawte Premium Server CA 

    Expires: 12/31/2020 7:59:59 PM 

    SHA1 hash: 627F8D7827656399D27D7F9044C9FEB3F33EFA9A 


     Issued to: Thawte Code Signing CA 

     Issued by: Thawte Premium Server CA 

     Expires: 8/5/2013 7:59:59 PM 

     SHA1 hash: A706BA1ECAB6A2AB18699FC0D7DD8C7DE36F290F 


      Issued to: [my company] 

      Issued by: Thawte Code Signing CA 

      Expires: 4/23/2011 7:59:59 PM 

      SHA1 hash: 7D1A42364765F8969E83BC00AB77F901118F3601 


The signature is timestamped: 4/27/2010 10:19:19 AM 

Timestamp Verified by: 
    Issued to: Thawte Timestamping CA 

    Issued by: Thawte Timestamping CA 

    Expires: 12/31/2020 7:59:59 PM 

    SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656 


     Issued to: VeriSign Time Stamping Services CA 

     Issued by: Thawte Timestamping CA 

     Expires: 12/3/2013 7:59:59 PM 

     SHA1 hash: F46AC0C6EFBB8C6A14F55F09E2D37DF4C0DE012D 


      Issued to: VeriSign Time Stamping Services Signer - G2 

      Issued by: VeriSign Time Stamping Services CA 

      Expires: 6/14/2012 7:59:59 PM 

      SHA1 hash: ADA8AAA643FF7DC38DD40FA4C97AD559FF4846DE 



Number of files successfully Verified: 0 

Number of warnings: 0 

Number of errors: 1 

Answer 1

Trate Signtool verify /v /pa foo.exe

De Using SignTool to Verify a File Signature (el subrayado es mío)

SignTool verify MyControl.exe

Si el ejemplo anterior falla, que podría ser que la firma utiliza un certificado de firma de código . SignTool se predetermina a la política del controlador de Windows para la verificación.

El siguiente comando verifica la firma , utilizando la política de verificación autenticación por defecto:

SignTool verify /pa MyControl.exe