-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
enabling TLS 1.3 support for TCP listeners #8305
Changes from all commits
ce66fdf
df62488
3932aab
d1dc2f7
9240fe1
f1da4c6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -134,21 +134,21 @@ Default: cn`, | |
"tls_min_version": { | ||
Type: framework.TypeString, | ||
Default: "tls12", | ||
Description: "Minimum TLS version to use. Accepted values are 'tls10', 'tls11' or 'tls12'. Defaults to 'tls12'", | ||
Description: "Minimum TLS version to use. Accepted values are 'tls10', 'tls11', 'tls12' or 'tls13'. Defaults to 'tls12'", | ||
DisplayAttrs: &framework.DisplayAttributes{ | ||
Name: "Minimum TLS Version", | ||
}, | ||
AllowedValues: []interface{}{"tls10", "tls11", "tls12"}, | ||
AllowedValues: []interface{}{"tls10", "tls11", "tls12", "tls13"}, | ||
}, | ||
|
||
"tls_max_version": { | ||
Type: framework.TypeString, | ||
Default: "tls12", | ||
Description: "Maximum TLS version to use. Accepted values are 'tls10', 'tls11' or 'tls12'. Defaults to 'tls12'", | ||
Description: "Maximum TLS version to use. Accepted values are 'tls10', 'tls11', 'tls12' or 'tls13'. Defaults to 'tls12'", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I also wonder if, for My other question is whether we're aware of Active Directory or OpenLDAP presently supporting TLS 1.3. |
||
DisplayAttrs: &framework.DisplayAttributes{ | ||
Name: "Maximum TLS Version", | ||
}, | ||
AllowedValues: []interface{}{"tls10", "tls11", "tls12"}, | ||
AllowedValues: []interface{}{"tls10", "tls11", "tls12", "tls13"}, | ||
}, | ||
|
||
"deny_null_bind": { | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,6 +21,7 @@ var TLSLookup = map[string]uint16{ | |
"tls10": tls.VersionTLS10, | ||
"tls11": tls.VersionTLS11, | ||
"tls12": tls.VersionTLS12, | ||
"tls13": tls.VersionTLS13, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This looks great. If we ended up defaulting to TLS 1.3, we'd want to update lines 103 and 144 as well. |
||
} | ||
|
||
// cipherMap maps the cipher suite names to the internal cipher suite code. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -109,9 +109,9 @@ This endpoint configures LDAP in the Kerberos auth method. | |
- `starttls` `(bool: false)` – If true, issues a `StartTLS` command after | ||
establishing an unencrypted connection. | ||
- `tls_min_version` `(string: tls12)` – Minimum TLS version to use. Accepted | ||
values are `tls10`, `tls11` or `tls12`. | ||
values are `tls10`, `tls11`, `tls12` or `tls13`. | ||
- `tls_max_version` `(string: tls12)` – Maximum TLS version to use. Accepted | ||
values are `tls10`, `tls11` or `tls12`. | ||
values are `tls10`, `tls11`, `tls12` or `tls13`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does Kerberos support TLS 1.3? Same question for Consul and Zookeeper. |
||
- `insecure_tls` `(bool: false)` – If true, skips LDAP server SSL certificate | ||
verification - insecure, use with caution! | ||
- `certificate` `(string: "")` – CA certificate to use when verifying LDAP server | ||
|
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.
Does Cassandra support TLS 1.3? I see an issue here from a while ago, but it's still open. I haven't found it explicitly mentioned in their docs. The current test coverage of this code doesn't exercise TLS. Might be a good idea to add test coverage in
cassandra_test.go
to verify that it does work.