I read that self-signed certificates suffer from performance issues (for example, here) but which ones exactly? I can guess this can be related to revocation checks or something but not sure.
I read that self-signed certificates suffer from performance issues (for example, here ) but
Share
I disagree with the article about “performance problems” in using of certificates created by MakeCert.exe.
If no revocation information will be included in the created certificate then no performance loss can be because of revocation. Probably the only thing which is specific for using of self-signed certificate is following: you should include the self-signing certificate in the
Rootcertificates store (Trusted Root Certification Authorities) or more better in theAuthRootcertificates store (Third-Party Root Certificate Authorities) on all computers which will use it. After this your self-signing certificate will be not more worth as VeriSign root certificate in the most scenarios. Of cause this way is possible only inside of one company and can be difficult used in the enterprise scenarios with a lot of independent client computers.By the way it is possible to create a simple PKI with respect of MakeCert.exe utility. For example you can create the self-sign root certificate of your mini CA:
then you can create an additional child certificate
You can choose different enhanced key usage OIDs in the
ekuswitch depends from the scenarios in which you want use the certificate.To add the root certificate of your mini CA in the
AuthRootcertificate store (Third-Party Root Certificate Authorities) we can use for example CertMgr.exe utilityYou can also create and use Certificate Revocation List File if it needed for your scenario.
See How to: Create Temporary Certificates for Use During Development and other How to Articles for more examples.