Timothy Buchanan <[email protected]> writes:

> I copied the example mosquitto.conf to /etc/mosquitto then added these 
> lines:
>
> listener 1883
> allow_anonymous true
>
> and now the broker is worhking again. Thanks very much for the help.

Glad it works.

Do note that your config, the broker will allow unauthenticated clients
to subscribe and get updates, and either 1) the login information for
the writer will be exposed in plaintext or 2) writes can happen without
any kind of authorization

This means that guest devices, proprietary software in IOT devices,
software you don't expect on other devices, and any devices that connect
to your network can listen to and forge MQTT updates.  You may think
this is ok, especially if it's just weather, but if you do more with it,
like Home Assistant with the ability to control devices, then you will
likely want real security.  I realize that's non-trivial, but most of
the pain is getting the machine set up with a working domain name so
that the letsencrytp validator can answer a challenge.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/rmiv8z9hhgo.fsf%40s1.lexort.com.

Attachment: signature.asc
Description: PGP signature

Reply via email to