From d52a0b2909dc1228e317a811293a941a6a2b1c0d Mon Sep 17 00:00:00 2001 From: Kyle Havlovitz Date: Fri, 16 Jun 2017 12:54:25 -0700 Subject: [PATCH] Update encryption.html.md --- website/source/docs/agent/encryption.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/agent/encryption.html.md b/website/source/docs/agent/encryption.html.md index 0fcf48de3..a100c98be 100644 --- a/website/source/docs/agent/encryption.html.md +++ b/website/source/docs/agent/encryption.html.md @@ -64,10 +64,10 @@ through the following process. rolling update of the cluster with these new values. After this step, the agents will be able to decrypt gossip but will not yet be sending encrypted traffic. 3. Remove the [`encrypt_verify_outgoing`](/docs/agent/options.html#encrypt_verify_outgoing) setting -to change it back to false (the default) and perform another rolling update of the cluster. The +to change it back to `true` (the default) and perform another rolling update of the cluster. The agents will now be sending encrypted gossip but will still allow incoming unencrypted traffic. 4. Remove the [`encrypt_verify_incoming`](/docs/agent/options.html#encrypt_verify_incoming) setting -to change it back to false (the default) and perform a final rolling update of the cluster. All the +to change it back to `true` (the default) and perform a final rolling update of the cluster. All the agents will now be strictly enforcing encrypted gossip. ## RPC Encryption with TLS