7 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
jschoubben	159ed53103	Rebased onto main: ADR 0188 renumbered to 0201, and minio takes the sdk at 0.1.7 ... The bundles refactor took ADR 0188 on main, so minio's comments cite 0201. The sdk is 0.1.7 after the same rebase, and minio needs the `derived` field it carries.	2026-10-04 02:45:13 +02:00
jschoubben	661114370f	minio declares the bucket it derives; its consumers stop transcribing it (hq ADR 0188) ... serves.s3-bucket.bucket is ${consumer:as:dns}; the provisioner uses what it is given. nextcloud, invoicing and photos ask for ${bound:s3-bucket:bucket} instead of naming mesh-novox-* literals, which also named this node. bucketFor and the long-dead accessKeyFor are gone.	2026-10-04 02:34:06 +02:00
jochen	0cb0f814b4	Every credential provider says whether it still holds a consumer ... holds() for postgres, mssql, mongodb, minio, lavinmq, mosquitto, mailu and gitea, so the harness makes again a login the backend lost (hq issue 120). Each checks the mesh's password as the consumer presents it, or compares it read-only, and returns false only when the backend says the credential is absent or wrong; an unreachable backend throws.	2026-09-26 01:09:52 +02:00
jschoubben	6e8c18afff	Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation	2026-09-05 12:49:16 +02:00
jschoubben	3b03fcd8f7	Providers create the credential the mesh minted, sealing nothing (ADR 0053) ... redis, postgres and minio adapters drop generatePassword + the returned credential: each creates the resource under the login the mesh derived (`as`) with the password the mesh minted (`p.password`). minio's client gains a secret-key argument so it sets the mesh's secret rather than generating one. umami (analytics) is re-pointed at the new contract too; its siteId return is a data-provision concern ADR 0053 scopes out. Proven: mesh-lab provider-uses-mesh-credential green — redis creates the consumer's login with the mesh's password, the consumer authenticates (PONG), no seal key set. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF	2026-09-05 00:27:37 +02:00
jschoubben	f689b7dfa6	minio: full nox module — client, tools, provisioner and events (ADR 0044/0045/0046) ... Object store, an s3-bucket provider. Client ported with no npm deps: S3 data plane over fetch + SigV4 (node:crypto), scoped access keys via the mc CLI (the admin API needs an Argon2 payload node built-ins can't make — the honest port hal also used). Tools: list buckets/objects, bucket info, presigned url. The provisioner makes a bucket + scoped key per grant and emits module.minio.bucket.created/removed (the secret stays off the bus). Typechecks; manifest parses. (Trimmed the generated self-consuming ledger: a provider need not subscribe to its own emits.)	2026-09-04 02:35:51 +02:00