logoalt Hacker News

6thbit • yesterday at 1:33 PM • 2 replies • view on HN

Yeah, why may that be hard? That’s the question

I don’t think it’s gross incompetence, since they documented the steps to remove. They may have some unexpected dependency on the file? Looks mysterious from the outside.


Replies

lukasgelbmann • yesterday at 3:33 PM

I think the main problem is that the weak eMudhra intermediates were cross-signed by Sectigo. Certificate revokations are needed to handle this correctly.

Dropping the Sectigo root along with the eMudhra root is the easy and safe solution, and maybe this is what Apple should have done (it’s the workaround they recommend!). But it means that some small percentage of certificates that are fine won’t be accepted.

giancarlostoro • yesterday at 2:02 PM

People would have to use it in some drastic catastrophic way for them to force it out in an update, which they might push it out in the next macOS update, which don't come nearly as frequently as Windows bloatware updates do.

➕ show 3 replies