Closed Bug 550521 Opened 12 years ago Closed 12 years ago
Add "ACEDICOM Root" root certificate to NSS
This bug requests inclusion in the NSS root certificate store of the following certificate, owned by ACEDICOM. Friendly name: ACEDICOM Root Certificate location: http://acedicom.edicomgroup.com/archivos/certificados/ACEDICOM%20Root.crt SHA1 Fingerprint: E0:B4:32:2E:B2:F6:A5:68:B6:54:53:84:48:18:4A:50:36:87:43:84 Trust flags: Websites, Email, Code Signing Test URL: https://cartero.edicom.es/RootCertificatePrograms/test.htm This CA has been assessed in accordance with the Mozilla project guidelines, and the certificate approved for inclusion in bug #471045. 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(s) have been attached. They must also specify what OS they would like to use to perform the verification below. 2) A Mozilla representative creates a test build of NSS with the new certificate(s), and attaches nssckbi.dll to this bug. A representative of the CA must download this, drop it into a copy of Firefox and/or Thunderbird on the OS in question and confirm (by adding a comment here) that the certificate(s) have been correctly imported and that websites work correctly. 3) The Mozilla representative checks the certificate(s) into the NSS store, and marks the bug RESOLVED FIXED. 4) 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.
Raúl, Please see step #1 above.
I confirm that all the data in this bug is correct. Also, for the verification process the OS can be either Linux(32 or 64 bit) or MS Windows XP 32 bits, or both if possible.
Thanks, Raúl, for confirming that the data in this bug is correct. This request is now in the "Inclusion in NSS" phase as per: https://wiki.mozilla.org/CA:How_to_apply#Timeline Root inclusions/updates in NSS are grouped and done as a batch when there is either a large enough set of changes or about every 3 months. When this request gets included in a batch of root inclusions/updates, 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.
test build for your verification: https://email@example.com/
As ACEDICOM representative, I confirm that Windows, Linux and Mac OS versions of this firefox pre release works fine with ACEDICOM certificates. Thanks.
Attachment #434572 - Flags: review?(rrelyea) → review+
Comment on attachment 434572 [details] [diff] [review] incremental Patch v2 - update version This is fine, but should not be committed until at least one one change to the builtins files is committed.
Comment on attachment 434570 [details] [diff] [review] Patch v1 - adding r=nelson (this is that one other checkin :).
Attachment #434570 - Flags: review?(rrelyea) → review+
Comment on attachment 434572 [details] [diff] [review] incremental Patch v2 - update version no longer necessary to update version, same change was already done 3 days ago as part of bug 555261.
Attachment #434572 - Attachment is obsolete: true
Checking in certdata.c; /cvsroot/mozilla/security/nss/lib/ckfw/builtins/certdata.c,v <-- certdata.c new revision: 1.65; previous revision: 1.64 done Checking in certdata.txt; /cvsroot/mozilla/security/nss/lib/ckfw/builtins/certdata.txt,v <-- certdata.txt new revision: 1.62; previous revision: 1.61 done
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Hello all, I'm not sure if this is the right place to inform but I've downloaded Mozilla Firefox 3.6.4 beta from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/3.6.4-candidates/build1/ I've checked that ACEDICOM Root certificate IS NOT included. Is it right? Have we missed any step or so? Thanks,
Raúl, Firefox has not yet elected to pick up this latest version of NSS. Please follow Bug 558140 to observe the progress of that request.
You need to log in before you can comment on or make changes to this bug.