Closed Bug 260259 Opened 17 years ago Closed 16 years ago

SECOM CA certificate request


(NSS :: CA Certificate Root Program, task)

Not set


(Not tracked)



(Reporter: hecker, Assigned: hecker)




SECOM is a Japan-based CA. For links to relevant information see

They are WebTrust for CA audited, so approval should be relatively
straightforward. The main task will be to sort out exactly which CAs are at
issue here and which CA certificates should be included. (It appears at first
glance that SECOM operates at least two CAs, but I have not yet looked
at them in detail to determine their relationship to each other, whether they
are true root CAs, etc.)
Accepting this bug, and adding a few more comments:

First, the URL for my CA certificate list is

The URL in the previous comment is wrong.

Second, upon investigation it appears that SECOM is operating two CAs.
The first CA, marked as SECOM Root1 CA in the list above and in the
SECOM documentation, appears to simply be the existing ValiCert Class 1 Policy
Validation Authority, which SECOM apparently has taken over; the CA cert appears
to be already included in NSS/Mozilla/Firefox/etc. The second CA, Security
Communication Root CA1, is apparently a new root CA.
Depends on: 261379
Per my comments above, I'm approving inclusion of the Security Communication RootCA1
certificate in Mozilla, etc., and have filed bug 261379 against NSS to get the
cert actually added to NSS. As noted in my previous comments in this bug, SECOM actually
has two root CA certs; however one of them, SECOM Root1 CA (or SECOM Root CA1) is actually a Valicert root cert that is already in
NSS/Mozilla. The new cert we want to add is the Security Communication Root1CA
certificate, at

Please submit technical comments about adding the cert to NSS to bug 261379; all
other comments should be made in this bug or in the n.p.m.crypto newsgroup.

Nelson has added this root CA cert to NSS.  So
you can mark the bug fixed now.
Certificates are in Firefox 1.0.2 and Thunderbird 1.0.2; resolving as fixed and
removing dependency on bug 261379.
Closed: 16 years ago
No longer depends on: 261379
Resolution: --- → FIXED
Product: → NSS
You need to log in before you can comment on or make changes to this bug.