OpenSSL is a tool and library that can be used to create certificate requests (CSRs), self-signed certificates, and issue certificates from a CA (if it is a CA that you manage, of course).
Most browsers have several trusted certification authorities. They issue certificates by signing the certificate they give (based on your certificate request). In turn, the certificates they issue can be verified by your users ’browsers against their (issuing) CA ​​certificate, since it comes with them by default.
You can create your own CA certificates and issue certificates yourself, but the problem is that your default CA certificate will not be used by default in most browsers, so it is useless if you do not make your users explicitly imported (which is great for corporate CA, for example, but in principle impractical). A self-signed certificate is a special case: it generates a CA root certificate or a one-time certificate for this machine; In any case, you will have to import it explicitly.
Some pre-trusted CAs will allow you to use OpenSSL to generate a certificate request as part of their procedure, but they may also offer other procedures based on other tools. Which tool you or they use does not really matter. What you want is a certificate issued by a CA that your remote side trusts.
Bruno
source share