Tell me more ×  I'm currently using a self signed certificate
for in-house development purposes and want to make sure I am
aware of any real security risks.  Here's how I set things up.
Root Certificate    1. Created a Root CA .pvk and .cert   2.
Installed the CA root .cert on my local machine under "Trusted
Root Certification Authorities"   3. Installed the CA root .cert
on my development hosting server under "Trusted Root
Certification Authorities"  Certificate for My Site    1.
Generated another certificate from the root .cert and .pvk   2.
Imported the new certificate as a .pfx file on the hosting
server   3. Setup the hosting server to use the new cert for my
site in IIS  Other than the private key for the root
certificate, are there any other pieces of data that pose a
security risk if someone were to get a hold of them?
share|improve this question This is not really about "self-
signed certificate risks", but rather about the risks associated
with creating your own CA. –  Bruno Jan 12 '12 at 18:28 Tha