PaulTech
Active Member
- Reaction score
- 36
- Location
- California
With the recent report of the Lenovo Superfish fiasco it had me looking at the "Trusted Root Certificates" (certmgr.msc (run as admin))
I don't like the looks of many of those listed and it seems I should include a check for my clients machines.
In a brief search I found:
http://blogs.msdn.com/b/muaddib/arc...ishing-certificates-for-smart-card-logon.aspx
https://www.myotherpcisacloud.com/p...store-backup-and-cleanup-with-powershell.aspx
Anyone have guidelines on what can or cannot be deleted?
For example how do I minimize the number of Trusted Root Certificates? And if I remove them and they are required will I be prompted to "re-trust" the certificate if and when it is required? Here some as examples;
ADOCA02 - Australian Defence Organisation (ADO) Certificate Authority 02
CFCA GT CA - China Financial CA
Default CA
EBG Elektronik Sertifika Hizmet Saglayicisi
Hongkong Post Root CA
Autoridade Certificadora Raiz Brasileira
Thanks for the insight and help!
I don't like the looks of many of those listed and it seems I should include a check for my clients machines.
In a brief search I found:
http://blogs.msdn.com/b/muaddib/arc...ishing-certificates-for-smart-card-logon.aspx
https://www.myotherpcisacloud.com/p...store-backup-and-cleanup-with-powershell.aspx
Anyone have guidelines on what can or cannot be deleted?
For example how do I minimize the number of Trusted Root Certificates? And if I remove them and they are required will I be prompted to "re-trust" the certificate if and when it is required? Here some as examples;
ADOCA02 - Australian Defence Organisation (ADO) Certificate Authority 02
CFCA GT CA - China Financial CA
Default CA
EBG Elektronik Sertifika Hizmet Saglayicisi
Hongkong Post Root CA
Autoridade Certificadora Raiz Brasileira
Thanks for the insight and help!