3 Commits

Include renames

Author	SHA1	Message	Date
jochen	13b7562c47	Keep secrets off command lines the runtime records (hq issue 282) ... mosquitto passed the broker's admin password to mosquitto_ctrl as -P on every docker exec, and the container runtime keeps every exec's command line in its event stream, where docker_events returned it. The admin credentials now reach mosquitto_ctrl as a 0600 options file fed on stdin, client passwords at its own prompt, and an argv carrying a secret is refused before it runs. The admin secret says it is taken at start: the bootstrap re-runs when the mesh replaces it and re-keys the broker online from the value it last applied, so it can be rotated. docker_events redacts what an exec's command line carried, and docker_secrets_in_events names such secrets by name. keycloak's repair hands kcadm its passwords through KC_CLI_PASSWORD; minio gives mc its root alias through MC_HOST_mesh.	2026-10-07 01:37:21 +02:00
jochen	69f2efb591	mosquitto: run mosquitto_ctrl inside the broker's container ... The module's code moved out of its container and took mosquitto_ctrl from a host package. A machine whose package index is stale cannot install it (hq issue 205), so the tools failed. The broker's own image carries the tool at the broker's version: the tools exec into the running broker, and the bootstrap seeds from a throwaway container of the same image.	2026-10-04 01:00:51 +02:00
jschoubben	1080f45012	mosquitto: a consumer's grant is the topics it asks for, and its binding says the port ... mqtt-topic served nothing: with two listens the mesh could not say which port a consumer dials, so a consumer had to type 1883 into its config. It now serves the MQTT listener's port (the machine's, once assigned) and the scheme, so `${bound:mqtt-topic:port}` fills. The provisioner confined every consumer to `<as>/#`, which leaves nothing for the consumers the broker exists for: Home Assistant discovers under homeassistant/# and tasmota/discovery/#, and Node-RED's flows follow the devices' own topics. A consumer now contributes `topics` (MQTT topic filters) to its mqtt-topic requirement and is granted exactly those; with none, its own subtree as before. Settings merge into contributions, so an operator narrows a grant per assignment. The role is brought to exactly the wanted ACLs (stale ones removed), `holds` checks the ACLs too, and an invalid list is refused, never quietly narrowed. Only the role named for the consumer is touched: a client carried from the predecessor's password file keeps its own.	2026-09-30 13:01:14 +02:00