How to avoid browser warning when you sign SSL certificate?

I am planning to deploy my own hardware device, possibly as a RaspberryPi running a NodeJs server that should enable HTTPS communication. It is intended to run as an intranet and will always have a name with the same name (or the same IP address). Let's say stephan.box.

What is the best practice for equipping such devices with encryption to ensure a secure wireless HTTP connection?

Is it possible to self-sign an SSL certificate for a static IP or domain name to avoid a browser warning?

+3


source to share


1 answer


You can only avoid browser warnings if the browser for the certificate or the certificate itself trusts the browser. If you are creating a certificate that is self-signed, or if you are using a private CA, you must import this CA in all browsers that need to access the system or accept the warning once across all browsers. The only way to avoid this is with a CA that browsers already trust, which means buying a certificate (some CAs provide simple certificates as well at no cost).



+2


source







All Articles