-
Notifications
You must be signed in to change notification settings - Fork 591
Added note tls version below 1.2 should set compatible cipher suites #2502
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
Conversation
ceb0c9f to
4a917fd
Compare
|
/test release-notes |
networking/v1alpha3/gateway.proto
Outdated
| // Optional: Minimum TLS protocol version. | ||
| // Optional: Minimum TLS protocol version. By default, it is `TLSV1_2`. | ||
| // TLS protocol versions below TLSV1_2 require setting compatible ciphers with the | ||
| // `cipherSuites` setting as the default ciphers no longer include compatible ciphers. |
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.
Reading this the default is 1.2. Versions below 1.2 require setting compatible ciphers. Then the last part says that 1.2, the default, no longer includes compatible ciphers. I think we either need to say 1.2 and below don't include compatible ciphers or more likely its change
| // `cipherSuites` setting as the default ciphers no longer include compatible ciphers. | |
| // `cipherSuites` setting as they no longer include compatible ciphers. |
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.
done
|
Can we add a warning to the validation webhook for this as well? Or alterntively, just automatically set the ciphers? |
SG, this will bring better UX |
586e254 to
e679e52
Compare
|
/cherry-pick release-1.16 |
|
@hzxuzhonghu: new pull request created: #2513 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/api#release-1.16 from head istio-testing:cherry-pick-2502-to-release-1.16: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-2502-to-release-1.16."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"} |
| } | ||
|
|
||
| // Optional: Minimum TLS protocol version. | ||
| // Optional: Minimum TLS protocol version. By default, it is `TLSV1_2`. |
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.
@lei-tang please review
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.
@hzxuzhonghu
Nit: Consider replacing "Using TLS protocol versions below TLSV1_2 has serious security considerations and risks." with "Using TLS protocol versions below TLSV1_2 has serious security risks."
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.
SG, i will update
lei-tang
left a comment
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.
Nit: Consider replacing "Using TLS protocol versions below TLSV1_2 has serious security considerations and risks." with "Using TLS protocol versions below TLSV1_2 has serious security risks."
For istio/istio#41305