Bugfix release. There was a bug where connecting using an already registered client id before the old client timed out, resulted in deletion of the old and new session, resulting in not having subscriptions. Downloads available as usual.

Includes one change: the logger erroneously reopened the file on each log line. The flag to only do it on config reload (SIGHUP) or log reload (SIGUSR1) was not cleared. Under heavy load conditions, this can also cause a run-away of open file handles, so it’s advised to update.

No functional change, only cosmetic ones:

A fix in QoS packet handling: always re-transmit QoS packets on reconnect, not only on the first reconnect. This may fix lost packets on very bad connections.

FlashMQ version 1.7.7 contains a minor fix on websocket close. A recent change was introduced that caused any websocket close to produce an error in the log about an invalid close frame. Version 1.7.7 fixes that. Not much functionally changed.

Version 1.7.6 contains a security fix relating to “last will and testament” messages. Wills placed by clients were published even when that client’s authentication failed. Update available as usual. Setting wills_enabled false in the config file is a mitigation.

Minor change: The plugin loading priority has changed to favor FlashMQ’s plugin first. This allows a plugin to be both Mosquitto v2 and FlashMQ native. This allows writing transitional code.

This mostly contains internal code maintenance, but there is one small extra feature: Builds available as usual.

Fixes from 1.7.1 and 17.2 are:

One small fix: clients that only opened a TCP connection and did nothing else were not disconnected by the keep-alive mechanism.