Phenomenon:
- Now there is a Web site posted on IIS, using the HTTPS protocol, CA's certificate is too expensive, so can't afford it. But to visit the site when the old talk about a warning and too annoying, how to do?
Workaround:
- Create a root certificate makecert-r-pe-n "Cn=my root"-ss ca-sr currentuser-a Sha1-sky signature-cy authority-sv ca.pvk CA.cer
- Create a server certificate
Makecert-pe-n "Cn=*.mysite.com"-a Sha1-sky exchange-eku 1.3.6.1.5.5.7.3.1-ic ca.cer-iv ca.pvk-sp "Microsoft RSA SC Hannel cryptographic Provider "-sy 12-sv server.pvk server.cer
- Convert server certificate pvk2pfx-pvk server.pvk-spc server.cer-pfx server.pfx
Attention:
- Send the root certificate to the customers who need to connect to your site and have them install Ca.cer to trusted Root certification authorities
- The second step of "cn=*.mysite.com" must be matched with your website domain name
- In the third step, get the Server.cer import into your IIS server certificate and configure the HTTPS binding in your website to select the imported certificate
[Solve a problem every day series-0003] how to create and apply a self-signed certificate