Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech QA/Testing 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I've a development environment with a test public key infrastructure. This infrastructure has one root CA, one intermediate CA and multiple end-entities (clients and servers). On the dev. machines, the root CA is installed into the "Trusted Root Certification Authorities", simulating a "commercial trusted CA"
I've successfully used this environment several times in the past, however I'm currently observing the following behavior: the root CA is automatically removed from the "Trusted Root Certification Authorities" the first time a chain using it is built (e.g. SSL connection establishment).
I know that windows automatically adds certificates to the "Trusted Root Certification Authorities". However, I didn't knew that they could be automatically removed. What are the circumstances on which this removal can happen?
The root certificate doesn't point to a CRL nor to a OCSP endpoint.
Thanks
Pedro