Add Athens Exchange root certificate

This case is a request to add the “Athens Exchange S.A. (Athex)” CA root certificate to the Mozilla CA Root Certification Program. The CA program staff asked the CA to provide initial CA information and later requested additional information to become compliant with the CA/Browser Forum Baseline Requirements, including obtaining a Baseline Requirements audit and attaching the audit statement to the bug. The CA submitted the requested information documents and assurance/attestation reports. Mozilla staff later noted that there had been no update from the CA for more than 1.5 years and closed the bug as “Won’t fix,” with an indication that it could be reopened if the CA provided further information. A later commenter noted that certificates available at a referenced URL used 1024-bit RSA and SHA-1 signatures, but the bug remained closed as WONTFIX. No further action is recorded in the thread beyond the closure and the possibility of reopening if new information is provided.

1. 2014-02-04 Bug created to apply for registration to add the Athens Exchange (Athex) root certificate to the Mozilla CA Root Certification Program.
2. 2014-02-12 Mozilla requested the initial CA information document and the CA was asked to provide highlighted items.
3. 2014-02-24 The CA submitted initial CA information answers and assurance/attestation reports.
4. 2014-03-04 Mozilla updated the status, indicating further information was needed for Baseline Requirements compliance and a BR audit statement.
5. 2016-09-19 Mozilla closed the request as Won’t fix due to no CA updates for more than 1.5 years.

1. 2014-02-04 Helex representative — Created the application materials attachment for registration to participate in the Mozilla CA Root Certification Program.
2. 2014-02-05 Mozilla representative — Accepted the bug, noted a backlog, and said she would update when beginning the Information Verification phase (with wiki links).
3. 2014-02-12 Mozilla representative — Requested the initial CA information document and asked the CA to provide the highlighted requested information (with a checklist link).
4. 2014-02-24 Helex representative — Responded that the requested information was sent in the attachment files.
5. 2014-02-24 Helex representative — Created attachments including CA information answers and independent assurance/attestation reports.
6. 2014-03-04 Mozilla representative — Updated the CA information document status, stating the CA needed to become compliant with Baseline Requirements, get a BR audit, and attach the BR audit statement to the bug.
7. 2016-09-19 Mozilla representative — Closed the bug for now as Won’t fix due to no CA update for more than 1.5 years, stating it would be reopened if further information is provided.
8. 2016-09-20 Hboeck representative — Noted that certificates at a provided URL include 1024-bit RSA and SHA-1 signatures, in case the bug is reconsidered.