Hmmm... I'll just assume that all the "prior to Effective Date" conditions are satisfied but both the end and root certs are 2048-bit. I can't speak to how actively or widely used the cert is nor how costly it would be to replace other than to say I've seen it on a half dozen different hosts.
Regarding "no known security risks", however, that point is a farce. The mere existence of the cert puts everyone at risk. If I can get my hands on the private key (Heartbleed, compromised admin/root account) I can start setting up bogus sites anywhere (the cloud). Add in a splash of DNS poison and hack some easy, popular targets (compromised admin accounts, SQL injection, MITM) and I'm golden! My malware distribution factory is ready for action and it will take a lot of effort to stop me. Of course first you would have to catch me. So is this cert still allowable since it's 2048-bit? Is there any requirement that might force its discontinued use upon (or prior to) its expiration date next year? Original Message From: Peter Bowen Sent: Wednesday, August 20, 2014 4:03 PM It is allowed by the BRs if (as per section 12): a. The Root CA uses a 1024-bit RSA signing key that was created prior to the Effective Date; b. The Applicant’s application was deployed prior to the Effective Date; c. The Applicant’s application is in active use by the Applicant or the CA uses a documented process to establish that the Certificate’s use is required by a substantial number of Relying Parties; d. The CA follows a documented process to determine that the Applicant’s application poses no known security risks to Relying Parties; and e. The CA documents that the Applicant’s application cannot be patched or replaced without substantial economic outlay. and the Root CA Certificate has a validity period beginning on or before 31 Dec 2010 (Appendix A) _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
