-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CORE-8654] Add flag to re-enable TLS client renegotiation #24772
base: dev
Are you sure you want to change the base?
[CORE-8654] Add flag to re-enable TLS client renegotiation #24772
Conversation
Updated to version of Seastar that disables TLS renegotiation by default. Signed-off-by: Michael Boquard <michael@redpanda.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Retry command for Build#60590please wait until all jobs are finished before running the slash command
|
CI test resultstest results on build#60590
test results on build#60611
|
src/v/config/configuration.cc
Outdated
"TLS client renegotiation was removed in TLSv1.3 due to vulnerabilities " | ||
"found in the protocol. By default, this is disabled for TLSv1.2 and " | ||
"below. It can be re-enabled by setting this property to true and " | ||
"restarting Redpanda. This is considered unsafe.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if this is unsafe/bad practice, in which scenarios would the users need to enable this flag? We should add this possibility here.
backwards compatibility with legacy systems?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct - in case their TLS client for some reason just will not work if it can't perform a client initiated TLS renegotiation. I can't think of any that exist and this is more of an escape hatch just in case.
src/v/config/configuration.cc
Outdated
"TLS client renegotiation was removed in TLSv1.3 due to vulnerabilities " | ||
"found in the protocol. By default, this is disabled for TLSv1.2 and " | ||
"below. It can be re-enabled by setting this property to true and " | ||
"restarting Redpanda. This is considered unsafe.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"TLS client renegotiation was removed in TLSv1.3 due to vulnerabilities " | |
"found in the protocol. By default, this is disabled for TLSv1.2 and " | |
"below. It can be re-enabled by setting this property to true and " | |
"restarting Redpanda. This is considered unsafe.", | |
"TLS client renegotiation, removed in TLSv1.3 due to vulnerabilities " | |
"in the protocol, is disabled for TLSv1.2 and earlier. " | |
"It can be re-enabled by setting this property to true and " | |
"restarting Redpanda. This is considered unsafe.", |
acc9670
to
d008988
Compare
Force push d008988:
|
src/v/config/configuration.cc
Outdated
, tls_enable_renegotiation( | ||
*this, | ||
"tls_enable_renegotiation", | ||
"TLS client initiated renegotiation is considered unsafe and is by " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"TLS client initiated renegotiation is considered unsafe and is by " | |
"TLS client-initiated renegotiation is considered unsafe and is by " |
src/v/config/configuration.cc
Outdated
"tls_enable_renegotiation", | ||
"TLS client initiated renegotiation is considered unsafe and is by " | ||
"default disabled. Only re-enable it if you are experiencing issues " | ||
"with your TLS enabled client. This option has no effect on TLSv1.3 " |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"with your TLS enabled client. This option has no effect on TLSv1.3 " | |
"with your TLS-enabled client. This option has no effect on TLSv1.3 " |
src/v/config/configuration.cc
Outdated
"TLS client initiated renegotiation is considered unsafe and is by " | ||
"default disabled. Only re-enable it if you are experiencing issues " | ||
"with your TLS enabled client. This option has no effect on TLSv1.3 " | ||
"connections as client initiated renegotiation was removed.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"connections as client initiated renegotiation was removed.", | |
"connections as client-initiated renegotiation was removed.", |
New config that can be used to re-enable TLS renegotiation if a client absolutely needs that enabled. Has no effect on TLSv1.3 connections. Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
d008988
to
6667f45
Compare
Force push 6667f45:
|
Retry command for Build#60611please wait until all jobs are finished before running the slash command
|
This PR adds a new tunable flag
tls_enable_renegotiation
. This flag is used to re-enable TLS client initiated renegotiation which, by default is disabled.Customers should avoid enabling this flag unless absolutely necessary.
Other than this PR, there will be no further public documentation about this flag.
Backports Required
Release Notes