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.
Problem
When a MQTT 5.0 CONNECT packet has the reserved bit (bit 0 of Connect Flags) set to 1, Mosquitto silently closes the connection without sending a CONNACK packet.
Per the MQTT 5.0 OASIS specification §3.1.2.3, bit 0 of the Connect Flags byte is reserved and must be set to 0.
Current Behavior
Expected Behavior
Per [MQTT-3.1.2-3] and §4.13, the server should send a CONNACK with Reason Code
0x81(Malformed Packet) before closing the connection.Fix
Test Case
Verified with an automated MQTT 5.0 conformance test (T-70) that sends CONNECT with reserved bit=1 and expects a CONNACK with Reason Code 0x81.
References