With great power comes great responsibility. It's not because there were no misuse of the certificates this time that it didn't happen or would have not happen.
I personally have removed their certificates from my system. This is the responsible move to do if you care about your security or don't want your computers to be used as part of the DDoS like we've seen against GitHub.
It prevents your computer from loading undesired piece of JavaScript in case of a MITM attack.
It doesn't prevent things if the server itself serve you malware, but that's another story.
> It prevents your computer from loading undesired piece of JavaScript in case of a MITM attack.
Only if the site you were visiting was over HTTPS, which it was not in the Github attack. Saying that you should remove this certificate if you don't want to participate in the Github attack or similar attacks is simply not true.
security: SecTrustSettingsRemoveTrustSettings (user): No Trust Settings were found.
security: SecTrustSettingsRemoveTrustSettings (admin): No Trust Settings were found.
Or edit /etc/ca-certificates.conf directly and run update-ca-certificates afterwards (as the file advises).
I'm normally a fan of dpkg-reconfigure, but in this case, paging through 25 screens of 6 certs at a time, without search, is a far worse case than firing up your preferred browser, finding the root you want to revoke, and planting a bang '!' in front of it.
Otherwise, the processes vilda and I describe are identical.
I personally have removed their certificates from my system. This is the responsible move to do if you care about your security or don't want your computers to be used as part of the DDoS like we've seen against GitHub.