When running the Cert-C ME cert sample to read in a DSA certificate, the following error is returned:
>cert -in dsa.cer -inform bin -text
Unable to load the certificate
Error: (10008) NOT_FOUND
A possible cause is a bug in Cert-C ME release 1.5.0.7 and earlier, where it cannot load a DSA certificate that does not have a NULL parameter in the signature algorithm. According to RFC 3279 (http://www.ietf.org/rfc/rfc3279.txt), this is correct -- the DSA signature should not have a NULL parameter specified:
--------------------------------------------------------------------------------------------
id-dsa-with-sha1 OBJECT IDENTIFIER ::= {
iso(1) member-body(2) us(840) x9-57 (10040)
x9cm(4) 3 }
When the id-dsa-with-sha1 algorithm identifier appears as the
algorithm field in an AlgorithmIdentifier, the encoding SHALL omit
the parameters field. That is, the AlgorithmIdentifier SHALL be a
SEQUENCE of one component: the OBJECT IDENTIFIER id-dsa-with-sha1.
--------------------------------------------------------------------------------------------
But somehow, the Cert-C ME toolkit expects a NULL parameter to be there. This bug has been resolved in Cert-C ME 1.5.0.8.
Related Articles
Parsing Old Messages Against A New XML 38Number of Views Emergency Bug Fix 112194 5Number of Views Web Server Will Not Start Up After Applying Service Pack 2 25Number of Views ERROR: (10008) NOT_FOUND when generating ECC parameters 27Number of Views ORA-15001: diskgroup "DG01" does not exist error in RSA Identity Governance & Lifecycle 100Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.1 Quick Setup Fails with "Failed to Attach Replica Instance" User Application Portal How to set up the REST RSA SecurID Authentication API for Authentication Manager 8.2 SP1