Repository navigation
feat(mqtt): optional TLS for broker connections - #555
Merged
Merged
Conversation
This file contains hidden or 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
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.
MQTT can now connect over TLS, from the local settings page and from a plan sent by NetPulse.
MQTT_TLSandMQTT_TLS_INSECUREare stored in the MQTT env file under/etc/netgrip. When TLS is on and no port is set, the default is 8883.tls://and the client verifies against the system roots. The insecure option skips verification for self-signed brokers.mqtt.configureaccepts 7 arguments (old layout) or 9 (withtlsandtlsInsecure). NetPulse sends the long form only when TLS is enabled, so older servers keep working.Part of gnacho/netpulse#1764. NetPulse will only propagate TLS to agents running v0.78.0 or newer.