Add option -ti/--tls_insecure to not check certificate hostname #244
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
|
Thanks! |
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.
Description:
New command line option
-ti/--tls_insecureis added. When enabled, causes the TLS engine not to check the server hostname against the hostname contained in the certificate provided by the server. This may be needed in scenarios where we are accessing an MQTT server having a valid, CA signed, certificate from an internal network, where such server is accessed via a local name or even a local IP address (192.168.x.y, or even 127.0.0.1).This option is ignored if TLS is not enabled.
Checklist: