I haven’t run the signed code yet, but the certificate chain sure looks
right.
Jan
C:\Temp\VS>\WinDDK\7600.16385.1\bin\amd64\signtool verify -v -kp SOS.dll
Verifying: SOS.dll
Hash of file (sha1): 664B9BD846DE41CBB6B057A3CF8CA9ED8E738C27
Signing Certificate Chain:
Issued to: Class 3 Public Primary Certification Authority
Issued by: Class 3 Public Primary Certification Authority
Expires: Tue Aug 01 16:59:59 2028
SHA1 hash: 742C3192E607E424EB4549542BE1BBC53E6174E2
Issued to: VeriSign Class 3 Code Signing 2009-2 CA
Issued by: Class 3 Public Primary Certification Authority
Expires: Mon May 20 16:59:59 2019
SHA1 hash: 12D4872BC3EF019E7E0B6F132480AE29DB5B1CA3
Issued to: Paradigm Matrix, Inc.
Issued by: VeriSign Class 3 Code Signing 2009-2 CA
Expires: Thu Sep 15 16:59:59 2011
SHA1 hash: F1A3A58A3FA13F316F27BB6BFFC35E784D90CE1D
The signature is timestamped: Wed Sep 15 18:43:00 2010
Timestamp Verified by:
Issued to: Thawte Timestamping CA
Issued by: Thawte Timestamping CA
Expires: Thu Dec 31 16:59:59 2020
SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656
Issued to: VeriSign Time Stamping Services CA
Issued by: Thawte Timestamping CA
Expires: Tue Dec 03 16:59:59 2013
SHA1 hash: F46AC0C6EFBB8C6A14F55F09E2D37DF4C0DE012D
Issued to: VeriSign Time Stamping Services Signer - G2
Issued by: VeriSign Time Stamping Services CA
Expires: Thu Jun 14 16:59:59 2012
SHA1 hash: ADA8AAA643FF7DC38DD40FA4C97AD559FF4846DE
Cross Certificate Chain:
Issued to: Microsoft Code Verification Root
Issued by: Microsoft Code Verification Root
Expires: Sat Nov 01 06:54:03 2025
SHA1 hash: 8FBE4D070EF8AB1BCCAF2A9D5CCAE7282A2C66B3
Issued to: Class 3 Public Primary Certification Authority
Issued by: Microsoft Code Verification Root
Expires: Mon May 23 10:11:29 2016
SHA1 hash: 58455389CF1D0CD6A08E3CE216F65ADFF7A86408
Issued to: VeriSign Class 3 Code Signing 2009-2 CA
Issued by: Class 3 Public Primary Certification Authority
Expires: Mon May 20 16:59:59 2019
SHA1 hash: 12D4872BC3EF019E7E0B6F132480AE29DB5B1CA3
Issued to: Paradigm Matrix, Inc.
Issued by: VeriSign Class 3 Code Signing 2009-2 CA
Expires: Thu Sep 15 16:59:59 2011
SHA1 hash: F1A3A58A3FA13F316F27BB6BFFC35E784D90CE1D
Successfully verified: SOS.dll
Number of files successfully Verified: 1
Number of warnings: 0
Number of errors: 0
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-425040-
xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Wednesday, September 15, 2010 5:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] FYI - VeriSign has code signing certificates on sale
Yes, but does it work? Remember, Verisign was just devoured by Symantec.
Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
Sent: Wednesday, September 15, 2010 7:34 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] FYI - VeriSign has code signing certificates on sale
I JUST today received a brand new code signing certificate, it’s a CURRENT
deal.
Jan
>
> > noticed an offer from VeriSign for a code signing certificate for
> > $99
>
> Didn’t that expire many years ago?
>
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer