github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Correct heading level in encryption documentation 

The ‘RPC Encryption’ heading is semantically at the same level as ‘Gossip Encryption’.
pull/2611/head
Amir Yalon 8 years ago committed by GitHub
parent
dc2a54a77b
commit
2932648c05
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      website/source/docs/agent/encryption.html.markdown

2
website/source/docs/agent/encryption.html.markdown
Unescape View File

@ -53,7 +53,7 @@ $ consul agent -data-dir=/tmp/consul -config-file=encrypt.json
All nodes within a Consul cluster must share the same encryption key in
order to send and receive cluster information.
# RPC Encryption with TLS
## RPC Encryption with TLS
Consul supports using TLS to verify the authenticity of servers and clients. To enable this,
Consul requires that all clients and servers have key pairs that are generated by a single

Write Preview
Loading…
Cancel
Save