If the Connect flags indicate that he user name exists but none is present in the payload treat this as a malformed CONNECT packet.

XMLWordPrintable

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: core
    • None
    • Environment:

      MQTT Server

    • Hide

      Remove the following from the description of the UserName field.

      Note that, for compatibility with the original MQTT V3 specification, the Remaining Length field from the fixed header takes precedence over the User Name flag. Server implementations must allow for the possibility that the User Name flag is set, but the User Name string is missing. This is valid, and connections should be allowed to continue.

      Show
      Remove the following from the description of the UserName field. Note that, for compatibility with the original MQTT V3 specification, the Remaining Length field from the fixed header takes precedence over the User Name flag. Server implementations must allow for the possibility that the User Name flag is set, but the User Name string is missing. This is valid, and connections should be allowed to continue.
    • Hide

      If the UserName bit or Password bit is set, then the fields MUST be present in the Connect message.
      see draft 04.

      Show
      If the UserName bit or Password bit is set, then the fields MUST be present in the Connect message. see draft 04.

      If the Connect flags indicate that the user name exists but none is present in the payload treat this as a malformed CONNECT packet and disconnect the client.
      See issue-8 as to whether a connack is flowed.

            Assignee:
            Andrew Banks (Inactive)
            Reporter:
            Andrew Banks (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: