From 0b9ad9e88253f07806d75b0157ac8ea15827c8a7 Mon Sep 17 00:00:00 2001 From: Nelson Elhage Date: Wed, 7 May 2014 15:04:50 -0700 Subject: [PATCH] docs: The config key is "encrypt", not "encrypt_key" --- 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 94710b6dd7..eef505f424 100644 --- a/website/source/docs/agent/encryption.html.markdown +++ b/website/source/docs/agent/encryption.html.markdown @@ -15,7 +15,7 @@ seperate systems, one for gossip traffic and one for RPC. Enabling gossip encryption only requires that you set an encryption key when starting the Consul agent. The key can be set using the `-encrypt` flag -on `consul agent` or by setting the `encrypt_key` in a configuration file. +on `consul agent` or by setting the `encrypt` parameter in a configuration file. It is advisable to put the key in a configuration file to avoid other users from being able to discover it by inspecting running processes. The key must be 16-bytes that are base64 encoded. The easiest method to