M
M.AbrarAhmad
Guest
We have developed an Indirect Display Driver which works perfectly with TESTSIGNING ON. Though we have signed the driver with Godaddy code Signing Certificate but driver is getting failed to load. It gives C00000BB error at function iddCxAdapterInitAsync.
Perhaps we have acquired wrong certificate to sign this driver. So just want to make sure if this is really because of certificate problem. Does IDD require EV code signing certificates?
Following are is output of signtool verify:
Signature Index: 0 (Primary Signature)
Hash of file (sha1): CA6A6245C38DB7FD4763EDBF51692932FF17DB53
Signing Certificate Chain:
Issued to: Go Daddy Root Certificate Authority - G2
Issued by: Go Daddy Root Certificate Authority - G2
Expires: Fri Jan 01 04:59:59 2038
SHA1 hash: 47BEABC922EAE80E78783462A79F45C254FDE68B
Issued to: Go Daddy Secure Certificate Authority - G2
Issued by: Go Daddy Root Certificate Authority - G2
Expires: Sat May 03 12:00:00 2031
SHA1 hash: 27AC9369FAF25207BB2627CEFACCBE4EF9C319B8
Issued to: XXXXXXXX CORPORATION
Issued by: Go Daddy Secure Certificate Authority - G2
Expires: Thu Feb 20 07:57:07 2020
SHA1 hash: 3B981C333F08769A53763E20D3D13609D30F8AAC
The signature is timestamped: Sat Feb 23 20:12:57 2019
Timestamp Verified by:
Issued to: Thawte Timestamping CA
Issued by: Thawte Timestamping CA
Expires: Fri Jan 01 04:59:59 2021
SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656
Issued to: Symantec Time Stamping Services CA - G2
Issued by: Thawte Timestamping CA
Expires: Thu Dec 31 04: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 04:59:59 2020
SHA1 hash: 65439929B67973EB192D6FF243E6767ADF0834E4
SignTool Error: A certificate chain processed, but terminated in a root
certificate which is not trusted by the trust provider.
Number of files successfully Verified: 0
Number of warnings: 0
Number of errors: 1
abrar
Continue reading...
Perhaps we have acquired wrong certificate to sign this driver. So just want to make sure if this is really because of certificate problem. Does IDD require EV code signing certificates?
Following are is output of signtool verify:
Signature Index: 0 (Primary Signature)
Hash of file (sha1): CA6A6245C38DB7FD4763EDBF51692932FF17DB53
Signing Certificate Chain:
Issued to: Go Daddy Root Certificate Authority - G2
Issued by: Go Daddy Root Certificate Authority - G2
Expires: Fri Jan 01 04:59:59 2038
SHA1 hash: 47BEABC922EAE80E78783462A79F45C254FDE68B
Issued to: Go Daddy Secure Certificate Authority - G2
Issued by: Go Daddy Root Certificate Authority - G2
Expires: Sat May 03 12:00:00 2031
SHA1 hash: 27AC9369FAF25207BB2627CEFACCBE4EF9C319B8
Issued to: XXXXXXXX CORPORATION
Issued by: Go Daddy Secure Certificate Authority - G2
Expires: Thu Feb 20 07:57:07 2020
SHA1 hash: 3B981C333F08769A53763E20D3D13609D30F8AAC
The signature is timestamped: Sat Feb 23 20:12:57 2019
Timestamp Verified by:
Issued to: Thawte Timestamping CA
Issued by: Thawte Timestamping CA
Expires: Fri Jan 01 04:59:59 2021
SHA1 hash: BE36A4562FB2EE05DBB3D32323ADF445084ED656
Issued to: Symantec Time Stamping Services CA - G2
Issued by: Thawte Timestamping CA
Expires: Thu Dec 31 04: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 04:59:59 2020
SHA1 hash: 65439929B67973EB192D6FF243E6767ADF0834E4
SignTool Error: A certificate chain processed, but terminated in a root
certificate which is not trusted by the trust provider.
Number of files successfully Verified: 0
Number of warnings: 0
Number of errors: 1
abrar
Continue reading...