-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig #12355
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
when using LoadTLSServerConfig
andrewkroh
reviewed
May 29, 2019
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.
This lines up with my expectations as a user. When requiring TLS client authentication the user should have to specify what CA's are trusted. But what if client_auth: none
is used?
Co-Authored-By: Andrew Kroh <andrew.kroh@elastic.co>
andrewkroh
approved these changes
May 29, 2019
Co-Authored-By: Andrew Kroh <andrew.kroh@elastic.co>
jenkins test this please |
ph
added a commit
to ph/beats
that referenced
this pull request
May 30, 2019
… when using LoadTLSServerConfig (elastic#12355) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit 8589309)
ph
added a commit
to ph/beats
that referenced
this pull request
May 30, 2019
… when using LoadTLSServerConfig (elastic#12355) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit 8589309)
ph
added a commit
to ph/beats
that referenced
this pull request
May 30, 2019
… when using LoadTLSServerConfig (elastic#12355) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit 8589309)
ph
added a commit
to ph/beats
that referenced
this pull request
May 30, 2019
… when using LoadTLSServerConfig (elastic#12355) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit 8589309)
ph
added a commit
to ph/beats
that referenced
this pull request
Jun 3, 2019
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12362)" This reverts commit 1886e8e.
ph
added a commit
to ph/beats
that referenced
this pull request
Jun 3, 2019
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12363)" This reverts commit debc457.
ph
added a commit
to ph/beats
that referenced
this pull request
Jun 3, 2019
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12364)" This reverts commit e9717b6.
ph
added a commit
to ph/beats
that referenced
this pull request
Jun 4, 2019
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12365)" This reverts commit 0a4fa5f.
ph
added a commit
to ph/beats
that referenced
this pull request
Jun 5, 2019
… and Key when using LoadTLSServerConfig (elastic#12355)" This reverts commit 8589309.
andrewvc
pushed a commit
to andrewvc/beats
that referenced
this pull request
Jun 12, 2019
… and Key when using LoadTLSServerConfig (elastic#12355)" (elastic#12441) This reverts commit 8589309.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…horities, Certificate file and Key when using LoadTLSServerConfig (elastic#12365) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit fdd0b75)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12365)" (elastic#12420) This reverts commit 8e3d18d.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…horities, Certificate file and Key when using LoadTLSServerConfig (elastic#12364) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit fdd0b75)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12364)" (elastic#12398) This reverts commit 6d567ae.
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…horities, Certificate file and Key when using LoadTLSServerConfig (elastic#12363) * Enforce presence of Certificate Authorities, Certificate file and Key when using LoadTLSServerConfig (cherry picked from commit fdd0b75)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…cate Authorities, Certificate file and Key when using LoadTLSServerConfig (elastic#12363)" (elastic#12396) This reverts commit ef21ef4.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When TLS is enabled for a Server we enforce CA, Certificate and the private key to make sure that the communication is correctly encrypted.