HiveMQ 1.4.2 released

We are pleased to announce the release of HiveMQ 1.4.2! This minor feature and bugfix release brings several stability improvements and you can configure the secure transport protocol (like TLS) now by your own.

Configurable secure transport protocol

It’s now possible to configure the secure transport protocol used for secure MQTT communication in the configuration file. Prior HiveMQ version used the standard Java TLS (which is essentially TLS 1.0) for secure communication. If your JVM supports it, you can now configure to use TLS 1.1 or TLS 1.2 (or even fall back to an less secure alternative like SSLv3).

To configure the protocol, a new property called ssl.protocol was introduced in the configuration.properties file. Depending on your VM, you can try SSLv3, TLS, TLSv1, TLSv1.1 or TLSv1.2. The default protocol is TLS. These changes are fully backwards compatible.

Stability improvements & bugfixes

There have been many stability improvements and bugfixes, many of them include more robust QoS 2 edge case handling, especially when using websockets.

We suggest to update to this new minor version. Let us know in the comments what you think and if the new configurable secure protocol option is useful for you!

The HiveMQ Team