From 9224ab9b35cbd31dcec7f3c9f223d803d4dbcc80 Mon Sep 17 00:00:00 2001 From: Jared Kirschner <85913323+jkirschner-hashicorp@users.noreply.github.com> Date: Sat, 19 Nov 2022 08:53:27 -0500 Subject: [PATCH] docs: clarify TLS cipher suite config (#15203) --- website/content/docs/agent/config/config-files.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/agent/config/config-files.mdx b/website/content/docs/agent/config/config-files.mdx index 2f807c3a8..734cc3414 100644 --- a/website/content/docs/agent/config/config-files.mdx +++ b/website/content/docs/agent/config/config-files.mdx @@ -1984,8 +1984,8 @@ specially crafted certificate signed by the CA can be used to gain full access t - `tls_cipher_suites` ((#tls_defaults_tls_cipher_suites)) This specifies the list of supported ciphersuites as a comma-separated-list. Applicable - to TLS 1.2 and below only. The list of all supported ciphersuites is - available through [this search](https://github.com/hashicorp/consul/search?q=goTLSCipherSuites+%3D+map). + to TLS 1.2 and below only. The list of all ciphersuites supported by Consul is + available in [the TLS configuration source code](https://github.com/hashicorp/consul/search?q=%22var+goTLSCipherSuites%22). ~> **Note:** The ordering of cipher suites will not be guaranteed from Consul 1.11 onwards. See this [post](https://go.dev/blog/tls-cipher-suites)