OpenSSL Certificate Authority: Difference between revisions
imported>Jawadmin (Created page with "This guide demonstrates how to act as your own certificate authority (CA) using the OpenSSL command-line tools. This is useful in a number of situations, such as issuing serve...") |
imported>Jawadmin No edit summary |
||
| Line 5: | Line 5: | ||
In some cases it may make more sense to act as your own CA, rather than paying a CA like DigiCert. Common cases include securing an intranet website, or for issuing certificates to clients to allow them to authenticate to a server (eg, Apache, OpenVPN). | In some cases it may make more sense to act as your own CA, rather than paying a CA like DigiCert. Common cases include securing an intranet website, or for issuing certificates to clients to allow them to authenticate to a server (eg, Apache, OpenVPN). | ||
[[Create the root pair]] | * [[Create the root pair]] | ||
[[Create the intermediate pair]] | * [[Create the intermediate pair]] | ||
[[Sign server and client certificates]] | * [[Sign server and client certificates]] | ||
[[Certificate revocation lists]] | * [[Certificate revocation lists]] | ||
[[Online Certificate Status Protocol]] | * [[Online Certificate Status Protocol]] | ||
[[Appendices]] | * [[Appendices]] | ||
Revision as of 09:55, 23 December 2018
This guide demonstrates how to act as your own certificate authority (CA) using the OpenSSL command-line tools. This is useful in a number of situations, such as issuing server certificates to secure an intranet website, or for issuing certificates to clients to allow them to authenticate to a server. Introduction OpenSSL is a free and open-source cryptographic library that provides several command-line tools for handling digital certificates. Some of these tools can be used to act as a certificate authority. A certificate authority (CA) is an entity that signs digital certificates. Many websites need to let their customers know that the connection is secure, so they pay an internationally trusted CA (eg, VeriSign, DigiCert) to sign a certificate for their domain. In some cases it may make more sense to act as your own CA, rather than paying a CA like DigiCert. Common cases include securing an intranet website, or for issuing certificates to clients to allow them to authenticate to a server (eg, Apache, OpenVPN).