Closed
Bug 1920641
Opened 1 year ago
Closed 1 year ago
Remove Security Communication RootCA3 root cert
Categories
(NSS :: CA Certificates Code, task)
NSS
CA Certificates Code
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cainfo, Assigned: bwilson)
References
Details
Attachments
(1 file)
No description provided.
| Reporter | ||
Comment 1•1 year ago
|
||
- Subject/Issuer field values in the root certificate to be changed
Issuer: C=JP, O=SECOM Trust Systems CO.,LTD., CN=Security Communication RootCA3
Subject: C=JP, O=SECOM Trust Systems CO.,LTD., CN=Security Communication RootCA3 - SHA256 Fingerprint of the certificate to be changed
24A55C2AB051442D0617766541239A4AD032D7C55175AA34FFDE2FBC4F5C5294
https://crt.sh/?q=24A55C2AB051442D0617766541239A4AD032D7C55175AA34FFDE2FBC4F5C5294 - Specify the change to be made
Remove the Security Communication RootCA3 from the file certdata.txt. - Reason for requesting this change
We mainly issue document signing and code signing certificates from Security Communication RootCA3.
There are subordinate CA certificates for TLS server use with Name Constraints extension under Security Communication RootCA3, but we have no plans to build TLS server CA or S/MIME CA that require WebTrust audit in the future.
Therefore, we would like to remove the Security Communication RootCA3 from the file certdata.txt. - Impact that the change may have on Mozilla users
There is no impact to Mozilla users.
| Assignee | ||
Updated•1 year ago
|
Assignee: nobody → bwilson
Status: UNCONFIRMED → ASSIGNED
Type: enhancement → task
Ever confirmed: true
Flags: needinfo?(bwilson)
| Assignee | ||
Updated•1 year ago
|
Component: CA Certificate Root Program → CA Certificates Code
Product: CA Program → NSS
Version: 3.0 → unspecified
| Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(bwilson)
Comment 2•1 year ago
|
||
Depends on D229176
Comment 3•1 year ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
| Assignee | ||
Updated•1 year ago
|
Flags: needinfo?(bwilson)
You need to log in
before you can comment on or make changes to this bug.
Description
•