From 3bd9be7151e4f2f98ad50b02b9573749b0f5df83 Mon Sep 17 00:00:00 2001 From: rob dux Date: Tue, 2 Aug 2016 21:24:02 -0500 Subject: [PATCH] update ca tutorial to one more recent and relevant --- website/source/docs/agent/encryption.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/agent/encryption.html.markdown b/website/source/docs/agent/encryption.html.markdown index 2d1b98219..caff772b9 100644 --- a/website/source/docs/agent/encryption.html.markdown +++ b/website/source/docs/agent/encryption.html.markdown @@ -59,7 +59,7 @@ Consul supports using TLS to verify the authenticity of servers and clients. To Consul requires that all clients and servers have key pairs that are generated by a single Certificate Authority. This can be a private CA, used only internally. The CA then signs keys for each of the agents, as in -[this tutorial on generating both a CA and signing keys](https://langui.sh/2009/01/18/openssl-self-signed-ca/) +[this tutorial on generating both a CA and signing keys](http://russellsimpkins.blogspot.com/2015/10/consul-adding-tls-using-self-signed.html) using OpenSSL. Note: client certificates must have [Extended Key Usage](https://www.openssl.org/docs/apps/x509v3_config.html#extended_key_usage_) enabled for client and server authentication.