Added support for TLS SNI #66
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
tsaarni
force-pushed
the
tls-sni
branch
2 times, most recently
from
2386bb9 to
007e9cf
Compare
|
@tsaarni please reabase this 🙏 |
Signed-off-by: Tero Saarni <[email protected]>
|
Rebased! |
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 used to connect to the syslog server, this change adds the TLS SNI extension to the TLS handshake, to indicate the wanted server name to the server.
Note that the
hostconfiguration option needs to be set to FQDN (Fully Qualified Domain Name) and not e.g. IP address or hostname without domain part.Part of elastic/logstash#15236