Bug in Certificates viewer on Win 2K
From: Sam Wilson (sam.wilson_at_bentley.com)
Date: 10/23/03
- Next message: Sergio Dutra [MS]: "Re: CryptAcquireContext"
- Previous message: Musa: "Urgent: Problem with CAPICOM using in VC++ ActiveX Dll getting unhandle exception error"
- Next in thread: Rhett Gong: "RE: Bug in Certificates viewer on Win 2K"
- Reply: Rhett Gong: "RE: Bug in Certificates viewer on Win 2K"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 23 Oct 2003 15:22:26 -0400
We have a class 3 code-signing certificate issued by Verisign. Somebody incorrectly installed the certificate on a Windows 2000 machine, which brought to light the following bug in the Windows Certificates viewer:
All certificates involved in this are installed in the machine store.
The intermediate CA's certificate was incorrectly installed by someone here in the Personal store, rather than in the Intermediate Ceritificate Authorities store where it should have been.
Here's the bug:
The Certificates viewer presented our class 3 certificate as trusted and showed a Certification Path that included the intermediate CA and tracing back to the root CA.
The signcode.exe program, however, refused to use our class 3 certificate, reporting:
Error: Failed to build the certificate chain as requested
Error: Signing Failed. Result = 800b010a, (-2146762486)
One of the two is incorrect. I believe that signcode is correct and the Certificates viewer is incorrect.
-------------------------------------------------
Samuel W. Wilson Bentley Systems, Inc.
sam.wilson@bentley.com www.bentley.com
- Next message: Sergio Dutra [MS]: "Re: CryptAcquireContext"
- Previous message: Musa: "Urgent: Problem with CAPICOM using in VC++ ActiveX Dll getting unhandle exception error"
- Next in thread: Rhett Gong: "RE: Bug in Certificates viewer on Win 2K"
- Reply: Rhett Gong: "RE: Bug in Certificates viewer on Win 2K"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|