Repository navigation
kuma v44.14.0
-
A machine-added account converges through a delta. The delta compiler's contract was that accounts ride the image: the declaration COPY is verbatim, but the
/usr/lib/kuma/users.ddropins were build-time work, so a machine that added[other_users.<name>]and rankuma upgradegot the re-baked declaration, no account, no refusal, no message. The compiler emits the dropin now — plus the build-time shell guard, the key file under/etc/kuma/keys/<name>, and the sshd conf serving it when the base lacks one — exactly what a full build would have baked, and the boot sync loop converges the account the same way it converges its own. A moved account re-emits (the dropin is the live config the sync reads every boot, so shell and groups moves land on the next one); a dropped one — an account the release names that the declaration does not — refuses loudly, because the sync creates accounts and never deletes them, and a removal the machine would never see is not convergence. An autologin move refuses too: the greeter's[initial_session]stanza rides the image, and a delta carrying it would silently not log anyone in. The smoke's delta lane now runs the true scenario: the release no longer bakes the account the machine declares. -
The nostr layer's enablement converges at boot. The baked preset governs preset applications, and the build's
--global presetran once, inside the image — a booted machine's/etckept the enable link its last image merged into it, so a disable delivered by delta was a preset file standing down over a link that never heard of it. A boot-time converger (kuma-nostr-preset.service, oneshot, before any user manager starts) re-applies the baked preset on every boot, reading the unit names from the preset file itself — the preset stays the single source of truth, a delta's rewrite of it is the whole move, and the same lines carry the arm back on.kuma syncstarts it on demand, so convergence need not wait for the next boot;kuma doctorreads its last run beside the other convergers. The smoke's delta lane asserts the flip itself now:systemctl --global is-enabledanswersdisabledon the booted delta deployment. -
The second audit ran with the release. Two full lanes over everything 44.13.0 shipped (#55, the #49 pattern): security re-walked the default-armed layer (arming creates nothing — the locked daemon touches the bus, the state dir, its socket; no relay), the hand-rolled vault client (signature-dispatched parsing, no key material in any error path), the account machinery (name charset, sourced dropins, the autologin singleton), the preset converger, and kumaui's Vault tab and restore path — no findings needing code, four hand-forwards recorded. Performance read the boot graph's delta by construction: one small pre-login oneshot (offline file ops, no D-Bus), zero-to-a-few no-op
usermodspawns per declared account, the daemon a session cost — and named the gate that does not exist yet (per-unit boot timing on green runs), recorded as its hand-forward.
Static x86_64 binary, no runtime dependencies.
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.14.0/kuma-x86_64-unknown-linux-musl
$ chmod +x kuma-x86_64-unknown-linux-musl && sudo mv kuma-x86_64-unknown-linux-musl /usr/local/bin/kumaThe image build stages the layer's three binaries from beside
the running kuma on every compose, nostr or not, so they
install to the same place:
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.14.0/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.14.0/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.14.0/nip46-relay-x86_64-unknown-linux-musl
$ chmod +x kuma-nostrd-x86_64-unknown-linux-musl kuma-nostr-x86_64-unknown-linux-musl nip46-relay-x86_64-unknown-linux-musl
$ sudo mv kuma-nostrd-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostrd
$ sudo mv kuma-nostr-x86_64-unknown-linux-musl /usr/local/bin/kuma-nostr
$ sudo mv nip46-relay-x86_64-unknown-linux-musl /usr/local/bin/nip46-relayVerify it came from this workflow:
$ cosign verify-blob \
--bundle kuma-x86_64-unknown-linux-musl.bundle \
--certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
kuma-x86_64-unknown-linux-muslBuilt from 53744a358a8caab1bcf5f364691f5dd25a6c2a7e.
The installer media on this page verifies the same way:
$ cosign verify-blob \
--bundle kuma-x86_64.iso.bundle \
--certificate-identity-regexp '^https://github.com/Letdown2491/kumaOS/.+@refs/tags/' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
kuma-x86_64.iso