From 91b158ac17027b2256dfcaad343606a4063e39ed Mon Sep 17 00:00:00 2001 From: Bill Zimmerman Date: Fri, 8 Nov 2019 11:06:26 +0100 Subject: [PATCH] Updated HTTPS support (markdown) --- HTTPS--support.md => SSL-(Manual-steps).md | 2 ++ 1 file changed, 2 insertions(+) rename HTTPS--support.md => SSL-(Manual-steps).md (97%) diff --git a/HTTPS--support.md b/SSL-(Manual-steps).md similarity index 97% rename from HTTPS--support.md rename to SSL-(Manual-steps).md index 986c659..8cbebcd 100644 --- a/HTTPS--support.md +++ b/SSL-(Manual-steps).md @@ -1,5 +1,7 @@ _Cette page est disponible [en français](https://static.cinay.xyz/2019/08/RaspAP-support-HTTPS-pour-un-serveur-local.html)._ +**Update:** this process is now [automated by the Quick Installer](https://github.com/billz/raspap-webgui/wiki/SSL-certificates-(Quick-Installer)). + ### Preamble HTTPS prevents network attackers from observing or injecting page contents. Clearly, this is a _good thing_ for RaspAP — given its function for creating and managing wireless networks. But HTTPS needs TLS certificates, and while deploying public websites is largely a [solved issue thanks to the ACME protocol and Let's Encrypt](https://www.leebutterman.com/2019/08/05/analyzing-hundreds-of-millions-of-ssl-connections.html), local web servers still mostly use HTTP because no one can get a universally valid certificate for localhost.