cc_staff
1,486
edits
(Marked this version for translation) |
(Added docs about certbot) |
||
Line 6: | Line 6: | ||
<!--T:2--> | <!--T:2--> | ||
Transport Layer Security (TLS) and formerly Secure Sockets Layer (SSL) are both often referred to as SSL and allow encrypted communications over computer networks. | Transport Layer Security (TLS) and formerly Secure Sockets Layer (SSL) are both often referred to as SSL and allow encrypted communications over computer networks. | ||
==Signed Certificate== | |||
Having a certificate signed by a [https://en.wikipedia.org/wiki/Certificate_authority Certificate Authority] (CA) allows visitors of the site to verify by a third party (the CA) that the website is the expected website, avoiding [https://en.wikipedia.org/wiki/Man-in-the-middle_attack man-in-the-middle-attacks]. Many CAs require a yearly fee, one CA which does not is the [https://letsencrypt.org/ let's encrypt] CA. [https://certbot.eff.org/ Certbot] is a tool for automatically creating and renewing an SSL certificate signed by the let's encrypt CA and automatically configures your web-server to use the SSL certificate. See the [https://certbot.eff.org/docs/ certbot docs] website for instructions on using certbot. | |||
==Self-Signed Certificate== | |||
This section describes the procedure for creating a self-signed SSL certificate as apposed to one signed by a [https://en.wikipedia.org/wiki/Certificate_authority CA] and configuring Apache to use it to encrypt communications. Self signed certificates should not be used for production sites, though they may be useful for small locally used sites and for testing. | |||
<!--T:3--> | <!--T:3--> |