When I create a SSL self-signed certificate.

  1. If I don't add the .crt on the client side, the browser (Chrome/Firefox) seems to download implicitly the .crt. Is it possible to prevent this ?

  2. If I add the .crt within Chrome Trusted root store, I get the so-called "Your connection is not private" page. Is it normal ? Is there a way to avoid it ?

  • 1
    Adding the certificate to the operating system's certificate store allows indicates to Chrome that you trust the certificate, it is at that point, you shouldn't get an untrusted page. The only reason you would still get an untrusted page is because there is some sort of certificate error with the certificate your trusting. Why do you want to prevent the client's browser from downloading the certificate? – Ramhound Feb 17 '16 at 14:57
  • Related – Ramhound Feb 17 '16 at 14:58
  • Ok, I want to give the .crt only to some computer/people inside the intranet. – Stef Feb 17 '16 at 15:10
  • In order to do that you would need to only allow specific machines to access the server. You can also on those machines specifically not trust the certificate, then configure the browser to explicitly allow trusted websites. – Ramhound Feb 17 '16 at 15:13
  • I think the OP is getting confused between server and client certs. In order to limit access from users it is possible to create a CA and create self-digned client keys+certs which The web server can be configured to recognise and limit traffic on. This allows a single server to serve protected and unprotected content [without worring abou ips or login usernames or passwords]. He should google ”client side certificates” as this is not amenable to a SU question. – davidgo Feb 17 '16 at 18:04

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.