chore(deps): update helm chart mosquitto to v2 #403
Merged
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.
This PR contains the following updates:
1.3.1
->2.1.1
Release Notes
eclipse/mosquitto
v2.0.1
Compare Source
==================
Security:
malformed CONNACK message to the broker a NULL pointer dereference occurred,
most likely resulting in a segfault. This will be updated with the CVE
number when it is assigned.
Affects versions 2.0.0 to 2.0.9 inclusive.
Broker:
an old session. Closes #2134.
Clients:
receive-maximum
to not exceed the-C
message count in mosquitto_suband mosquitto_rr, to avoid potentially lost messages. Closes #2134.
Client library:
mosquitto_loop_start()
, then if the connection failed due to the remoteserver being inaccessible they called
mosquitto_loop_stop(, true)
andrecreated the mosquitto object.
Build:
declarations.
v2.0.0
==================
Breaking changes:
When the Mosquitto broker is run without configuring any listeners it will
now bind to the loopback interfaces 127.0.0.1 and/or ::1. This means that
only connections from the local host will be possible.
Running the broker as
mosquitto
ormosquitto -p 1883
will bind to theloopback interface.
Running the broker with a configuration file with no listeners configured
will bind to the loopback interface with port 1883.
Running the broker with a listener defined will bind by default to
0.0.0.0
/
::
and so will be accessible from any interface. It is still possible tobind to a specific address/interface.
If the broker is run as
mosquitto -c mosquitto.conf -p 1884
, and alistener is defined in the configuration file, then the port defined on the
command line will be IGNORED, and no listener configured for it.
All listeners now default to
allow_anonymous false
unless explicitly setto true in the configuration file. This means that when configuring a
listener the user must either configure an authentication and access control
method, or set
allow_anonymous true
. When the broker is run without aconfigured listener, and so binds to the loopback interface, anonymous
connections are allowed.
If Mosquitto is run on as root on a unix like system, it will attempt to
drop privileges as soon as the configuration file has been read. This is in
contrast to the previous behaviour where elevated privileges were only
dropped after listeners had been started (and hence TLS certificates loaded)
and logging had been started. The change means that clients will never be
able to connect to the broker when it is running as root, unless the user
explicitly sets it to run as root, which is not advised. It also means that
all locations that the broker needs to access must be available to the
unprivileged user. In particular those people using TLS certificates from
Lets Encrypt will need to do something to allow Mosquitto to access
those certificates. An example deploy renewal hook script to help with this
is at
misc/letsencrypt/mosquitto-copy.sh
.The user that Mosquitto will change to are the one provided in the
configuration,
mosquitto
, ornobody
, in order of availability.The
pid_file
option will now always attempt to write a pid file,regardless of whether the
-d
argument is used when running the broker.The
tls_version
option now defines the minimum TLS protocol version tobe used, rather than the exact version. Closes #1258.
The
max_queued_messages
option has been increased from 100 to 1000 bydefault, and now also applies to QoS 0 messages, when a client is connected.
The mosquitto_sub, mosquitto_pub, and mosquitto_rr clients will now load
OS provided CA certificates by default if
-L mqtts://...
is used, or ifthe port is set to 8883 and no other CA certificates are loaded.
Minimum support libwebsockets version is now 2.4.0
The license has changed from "EPL-1.0 OR EDL-1.0" to "EPL-2.0 OR EDL-1.0".
Broker features:
easier to extend.
defined and updated as the broker is running.
then try "nobody" instead. This reduces the burden on users installing
Mosquitto themselves.
bridge_outgoing_retain
option, to allow outgoing messages from abridge to have the retain bit completely disabled, which is useful when
bridging to e.g. Amazon or Google.
being false.
to a v3.x only broker.
log_dest dlt
.Closes #1735.
mosquitto_broker_publish()
andmosquitto_broker_publish_copy()
functions, which can be used by plugins to publish messages.
mosquitto_client_protocol_version()
function which can be used byplugins to determine which version of MQTT a client has connected with.
mosquitto_kick_client_by_clientid()
andmosquitto_kick_client_by_username()
functions, which can be used by plugins to disconnect clients.
keyfile, not capath or cafile.
bridge_max_packet_size
option. Closes #265.bridge_bind_address
option. Closes #1311.ciphers_tls1.3
option, to allow setting TLS v1.3 ciphersuites.Closes #1825.
Broker fixes:
malformed-packet
reason code on invalid PUBLISH,SUBSCRIBE, and UNSUBSCRIBE packets.
mosquitto_client_certificate(). Closes #1842.
file and
per_listener_settings true
is set and the client did not set ausername. Closes #1891.
log_timestamp_format
not applying tolog_dest topic
. Closes #1862.notifications_local_only
was set true. Closes #1902.Client library features:
now expected to be generated on the broker. This matches the behaviour for
v5 clients. Closes #291.
mosquitto_property_identifier()
, for retrieving the identifier integerfor a property.
mosquitto_property_identifier_to_string()
for converting a propertyidentifier integer to the corresponding property name string.
mosquitto_property_next()
to retrieve the next property in a list, foriterating over property lists.
setting the retain bit.
sockets. Closes #1526.
mosquitto_ssl_get()
to allow clients to access their SSL structure andperform additional verification.
of the
mosquitto_connect*()
call.MOSQ_OPT_TLS_USE_OS_CERTS
option, to instruct the client to load andtrust OS provided CA certificates for use with TLS connections.
Client library fixes:
reconnects. Closes #1846.
Client features:
mosquitto_sub -W <secs>
andmosquitto_rr -W <secs>
. Closes #275.--unix
argument.JSON output. Closes #1416.
--pretty
option to mosquitto_sub/rr for formatted/unformatted JSONoutput.
Closes #1416.
--nodelay
to all clients to allow them to use the MOSQ_OPT_TCP_NODELAYoption.
-x
to all clients to all the session-expiry-interval property to beeasily set for MQTT v5 clients.
--random-filter
to mosquitto_sub, to allow only a certain proportionof received messages to be printed.
precision for some parameters.
--version
for all clients.-L mqtts://...
, or if port is set to 8883 and no other CA certificates areused. Closes #1824.
--tls-use-os-certs
option to all clients.Client fixes:
-f
.-e
and-t
arguments in mosquitto_rr. Closes #1881.Windows, rather than just quitting. Closes #1908.
Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.