JSchy65

MQTT 5.0 / message-expiry-interval / if exceeded, not all messages are deleted

1

mosquitto broker version 1.6.15. (Oracle Linux 8) The MQTT 5.0 Specification Chapter 3.3.2.3.3 "Message Expiry Interval" requires: "If the **Message Expiry Interval has passed** and the Server has not managed...

MQTT 5.0 / Session Expiry Interval only works within one run of mosquitto

1

mosquitto broker version 1.6.15. (Oracle Linux 8) MQTT 5.0 Specification chapter 3.1.2.11.2 Session Expiry Interval "Non-normative comment: The clock in the Client or Server may not be running for part...

"per_listener_settings true" causes messages for clients to no longer be stored

13

mosquitto broker version 2.0.15 (Oracle Linux 8) Start mosquitto with the following configuration: sys_interval 1 per_listener_settings **true** listener 1883 allow_anonymous true mosquitto_sub -p 1883 -v -t '$SYS/broker/clients/connected' -t '$SYS/broker/clients/total' -t...

MQTT 5 / mosquitto_sub / unexpected Recive Maximum Property

3

mosquitto_sub client version 2.0.14 (Ubuntu 20.04) The CONNECT Properties contain an unexpected Recive Maximum Property value. mosquitto_sub -p 1883 -q 1 -t test/# -c -i abc123 -x 30 -D connect...

Parameter bridge_protocol_version mqttv50 leads to lost messages on remote broker

3

If a bridge connects two brokers and the connection between the bridge and the remote broker is disrupted, using **bridge_protocol_version mqttv50** as bridge parameter **leads to lost messages** if the...

The MQTT 5.0 specification defines in 3.1.2.11.2 the Session Expiry Interval for the CONNECT properties. Actual (2.0.18), the Mosquitto Bridge sends no Session Expiry Interval value within the CONNECT Properties....

TLS / Certificate Hostname Verification against IP fails with "address family must be specified"

1

### Describe the bug Using Forward Output Plugin with TLS. Hostname is an IP address. Server certificate contains it's correct IP in it's SubjectAlternativeNames extention. tls_verify_hostname is switched to on....

TLS security issue: tls.verify is not validating host subject alternative name

5

## Bug Report If **tls.verify** is set to **on** on the client side, **the servers's subject alternative name (SAN) will still not be validated**. fluent-Bit Version **2.1.10** Ubuntu **22.04.2 LTS**...