Closed Bug 592984 Opened 14 years ago Closed 10 years ago

Nickname of Valicert root is "RSA Root Certificate 1"

Categories

(NSS :: CA Certificates Code, task, P2)

3.12.7

Tracking

(Not tracked)

RESOLVED WORKSFORME
3.12.9

People

(Reporter: stefan.bauer, Assigned: KaiE)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; de; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 (.NET CLR 3.5.30729)
Build Identifier: NSS Revision: 1.58 $ $Date: 2010/02/16

from certdata.txt

# Certificate "RSA Root Certificate 1"
#
CKA_CLASS CK_OBJECT_CLASS CKO_CERTIFICATE
CKA_TOKEN CK_BBOOL CK_TRUE
CKA_PRIVATE CK_BBOOL CK_FALSE
CKA_MODIFIABLE CK_BBOOL CK_FALSE
CKA_LABEL UTF8 "RSA Root Certificate 1"
CKA_CERTIFICATE_TYPE CK_CERTIFICATE_TYPE CKC_X_509
CKA_SUBJECT MULTILINE_OCTAL


I would assume after reading RSA, that this CA belongs to RSA Security Inc but the issuer is 

Issuer: L=ValiCert Validation Network,O=ValiCert\, Inc.,OU=ValiCert

any chance to get this renamed please?

thanks in advance


Reproducible: Always
Yeah, this is Bizarre.  
Anyone know (remember?) how this happened? 
Was this because of CA mergers and acquisitions?

Does the Valicert cert belong there?  
What happened to that RSA cert?
Assignee: nobody → kaie
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Summary: Certification Name is not Subject: - mislieading name of file → Nickname of Valicert root is "RSA Root Certificate 1"
Target Milestone: --- → 3.12.9
Version: unspecified → 3.12.7
This root, "OU = ValiCert Class 3 Policy Validation Authority" is owned by RSA.

It is a legacy, 1024-bit root. 

Email that I have from RSA says: "The Valicert Class 3 root is the signatory of the intermediate RSA Public Root V1 which we use to sign our end customers.

According to email I have from RSA, RSA is in the process of retiring this root. They have not done new signings with this root in over a year.
This root was removed in Bug 1021967.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
See Also: → 1021967
You need to log in before you can comment on or make changes to this bug.