Closed
Bug 938814
Opened 12 years ago
Closed 11 years ago
Add Atos TrustedRoot 2011 root certificate to NSS
Categories
(NSS :: CA Certificates Code, task)
NSS
CA Certificates Code
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kathleen.a.wilson, Unassigned)
References
Details
Attachments
(1 file)
891 bytes,
application/pkix-cert
|
Details |
This bug requests inclusion in the NSS root certificate store of the following certificate, owned by Atos.
Friendly name: Atos TrustedRoot 2011
Certificate location: https://pki.atos.net/Download/AtosTrustedRoot2011.cer
SHA1 Fingerprint: 2B:B1:F5:3E:55:0C:1D:C5:F1:D4:E6:B7:6A:46:4B:55:06:02:AC:21
Trust flags: Websites, Email, Code Signing
Test URL: https://pki.atos.net:7081/
This CA has been assessed in accordance with the Mozilla project guidelines, and the certificates approved for inclusion in bug #711366.
The next steps are as follows:
1) A representative of the CA must confirm that all the data in this bug is correct, and that the correct certificate has been attached.
2) A Mozilla representative creates a patch with the new certificate, and provides a special test version of Firefox.
3) A representative of the CA uses the test version of Firefox to confirm (by adding a comment in this bug) that the certificate has been correctly imported and trust bits correctly set.
4) The Mozilla representative requests that another Mozilla representative review the patch.
5) The Mozilla representative adds (commits) the patch to NSS, then closes this bug as RESOLVED FIXED.
6) At some time after that, various Mozilla products will move to using a version of NSS which contains the certificate. This process is mostly under the control of the release drivers for those products.
Reporter | ||
Comment 1•12 years ago
|
||
Martin, Please see step #1 above.
Comment 2•12 years ago
|
||
Given data is correct:
- Name: Atos TrustedRoot 2011 -> checked
- Location: https://pki.atos.net/Download/AtosTrustedRoot2011.cer -> checked
- Fingerprint: 2B:B1:F5:3E:55:0C:1D:C5:F1:D4:E6:B7:6A:46:4B:55:06:02:AC:21 -> checked
- Trust Flags: Websites, Email, Code Signing -> checked
- Test URL: https://pki.atos.net:7081/ -> checked
The attached certificate is also correct.
Reporter | ||
Comment 3•12 years ago
|
||
Thanks for confirming that the data in this bug is correct.
Root inclusions and changes are usually grouped and done as a batch when there is
either a large enough set of changes or about every 3 months.
At some point in the next 3 months a test build will be provided and this bug
will be updated to request that you test it. Since you are cc'd on this bug,
you will get notification via email when that happens.
Reporter | ||
Comment 4•11 years ago
|
||
Please test that your root has been correctly included, that the trust bits are set correctly, and that connections to your test site work with basic domain validation status.
The test build is available at
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/kaie@kuix.de-e9ed86288188/
Download a binary for your preferred operating system, you probably want one of the following files:
try-linux/firefox-....en-US.linux-i686.tar.bz2
try-linux64/firefox-....en-US.linux-x86_64.tar.bz2
try-macosx64/firefox-....en-US.mac.dmg
try-win32/firefox-....en-US.win32.zip
Please follow the test instructions here:
https://wiki.mozilla.org/CA:How_to_apply#Testing_Inclusion
Make sure you use a fresh profile for your testing.
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Comment 5•11 years ago
|
||
Thanks Kathleen,
i checked the test build 29.0a1 (2014-01-07) of Firefox with a new empty profile to confirm the correct Atos CA certificate (Atos TrustedRoot 2011) was added and the trust bits was set correctly.
I also checked our SSL test website.
Reporter | ||
Comment 6•11 years ago
|
||
Thanks for testing.
We are targeting Firefox 29 for this change.
https://wiki.mozilla.org/RapidRelease/Calendar
Comment 7•11 years ago
|
||
done as part of bug 957300
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•