I saw that distrust of an eMudhra ECC root has put a lot of university certificates on a tight replacement deadline. How did InCommon users end up affected, and what does this mean for their systems?
Why are universities suddenly replacing so many certificates?
Answers
InCommon offers a subscription certificate service used by many universities. Institutions could pay an annual fee and issue as many certificates as they needed, which made it a practical option for large environments.
The affected certificates chain to an eMudhra ECC root that's being distrusted. The reported scale is roughly 30,000 certificates, with replacement needed by Tuesday. That does not mean every certificate a university has is necessarily affected. The chain is what matters.
Reply to this answer
The immediate headache is finding every affected deployment, not just ordering replacements. Check the certificate chains in use across public services, then replace and test the affected certificates before the deadline. A certificate sitting in an inventory doesn't tell you whether every server is actually presenting the new chain.
Reply to this answer
There is another wrinkle. eMudhra announced an exit from the global SSL and TLS certificate business. Its announcement also said it would continue offering enterprise PKI products, so that should not be read as the company shutting down every certificate-related product.
Reply to this answer
Add your answer
Answers are reviewed before publication.
3x!ferryspindle_246:
And the deadline can turn this into a weekend job for some teams, though others may be dealing with it on Monday.