You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, where tls_minimum_protocol_version / tls_maximum_protocol_version explicitly mention the difference in client and server configs, cipher_suites does not.
If you agree, I'd be happy to make this change / update the docs to be more clear that the new default client cipher suite is as follows.
These changes clarify that as of v1.16 the default cipher suite is different for client and servers.
Risk Level: Low
Testing: N/A
Docs Changes: Yes
Release Notes: N/A
Platform Specific Features: N/A
Fixes#16469
Signed-off-by: Bobby DeSimone <[email protected]>
These changes clarify that as of v1.16 the default cipher suite is different for client and servers.
Risk Level: Low
Testing: N/A
Docs Changes: Yes
Release Notes: N/A
Platform Specific Features: N/A
Fixesenvoyproxy#16469
Signed-off-by: Bobby DeSimone <[email protected]>
Title: default cipher suite docs are misleading for server and client context
Description:
The default tls client config has changed since v1.16 to be distinct from the default server config.
From
envoy/source/extensions/transport_sockets/tls/context_config_impl.cc
Lines 332 to 356 in bf5d0eb
To
envoy/source/extensions/transport_sockets/tls/context_config_impl.cc
Lines 315 to 331 in ce071f6
This is not clear in the docs.
For example, where
tls_minimum_protocol_version
/tls_maximum_protocol_version
explicitly mention the difference in client and server configs,cipher_suites
does not.If you agree, I'd be happy to make this change / update the docs to be more clear that the new default client cipher suite is as follows.
Related context
The text was updated successfully, but these errors were encountered: