From b367c369cfe44017e6a18274ea95cc62a64e17c5 Mon Sep 17 00:00:00 2001 From: Christine Dodrill Date: Thu, 11 Apr 2019 14:20:10 -0700 Subject: [PATCH] Update site-to-site-wireguard-part-3-2019-04-11.markdown --- blog/site-to-site-wireguard-part-3-2019-04-11.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/site-to-site-wireguard-part-3-2019-04-11.markdown b/blog/site-to-site-wireguard-part-3-2019-04-11.markdown index 0aa591e..40e9364 100644 --- a/blog/site-to-site-wireguard-part-3-2019-04-11.markdown +++ b/blog/site-to-site-wireguard-part-3-2019-04-11.markdown @@ -26,7 +26,7 @@ A TLS Certificate Authority is a certificate that is allowed to issue other cert ### Why Should I Create One? -Generally, it is useful to create a custom TLS certificate authority when there are custom DNS domains being used. This allows you to create `https://` links for your internal services (which can then act as [Progressive Web Apps](https://christine.website/blog/progressive-webapp-conversion-2019-01-26)); and will fully prevent the ["Not Secure"](https://versprite.com/blog/http-labeled-not-secure/) blurb from showing up in the URL bar. +Generally, it is useful to create a custom TLS certificate authority when there are custom DNS domains being used. This allows you to create `https://` links for your internal services (which can then act as [Progressive Web Apps](https://christine.website/blog/progressive-webapp-conversion-2019-01-26)). This will also fully prevent the ["Not Secure"](https://versprite.com/blog/http-labeled-not-secure/) blurb from showing up in the URL bar. Sometimes your needs may involve needing to see what an application is doing over TLS traffic. Having a custom TLS certificate authority already set up makes this a much faster thing to do.