Repository navigation
kuma v44.15.0
-
One keyboard layout, every layer, with the boot layer made honest.
[system].keymap("de", "us", "de-latin1" — the console's vocabulary, because one value has to work for the console and the session both) composes a niri input stanza into/etc/kuma/keymap.kdl, included ahead of thelocal.kdlinclude so the machine's layout beats the defaults and a person's own override still beats the machine; writes/etc/vconsole.confahead of the build's one initramfs regeneration, so the LUKS passphrase prompt speaks it too; and the greeter's session wrapper appends the same stanza to a runtime copy of its pinned config.kuma keymap apply <layout>moves the three runtime layers on a booted machine and says plainly which layer it cannot move: the initramfs is image content, moved by declaring the keymap and rebuilding, never by the verb.kuma keymap status --jsonreads every layer back, the image's baked one included, andkuma doctorwarns when the layers disagree — the common drift being exactly the quiet one, the prompt that kept speaking the old layout. COSMIC machines get the vconsole and boot layers; there is no session stanza to include. A keymap move refuses the delta compiler, because the runtime layers are three of the four and carrying them alone would half-converge (#58). -
The account bridge's gap has a heal. The delta is compiled by the machine's own binary — the release the machine is leaving — and a binary predating the account emission stages a deployment whose
/usr/lib/kuma/users.dis empty while the re-baked declaration still names the accounts: the ride carries the names, nothing carries the dropins, and/usris read-only at runtime, so nothing at boot could write them where the converger looks.kuma-user-sync.service's ExecStartPre (kuma accounts-heal) fills the hole from the ride into/var/lib/kuma/users.d— 0600, the emission's own shape — the sync's loop converges the account the same boot, a dropin takes it back, and the heal retires its own file.kuma doctorcross-checks the declaration's additional accounts against what actually carries them, so the silent shape a stale compiler leaves is a finding (#60). The smoke's delta lane runs the true scenario on the N-1 compiler that needs it: 44.14.0 emits the dropin, 44.13.0 predates the emission, and the proof waits for the road whose N-1 can carry it. -
boot-titles guarantees /boot is writable itself. No unit in the boot graph owns the rw half — ostree-remount does not touch it, and the guest's boot.mount comes from the initramfs — so a machine with stale titles to fix could only fail the write. With titles to write, the caller remounts rw on a bounded retry (ten rounds × 200 ms, the mountinfo read the authority) and refuses loudly if the filesystem stays read-only; a machine with nothing to fix touches no mounts (#59).
-
The release page teaches image verification, not just artifact verification. The body's verify section now names the thing most kuma machines actually run:
cosign verify --key cosign.pubagainst the pinnedniri-<version>tag — the key form, because a podman policy.json can name a key and not a keyless identity, which is why publish.yml signs with one — the key fetched from the release tag that names the code which shipped, and the digest-pinned form beside it, the verify response being where the digest comes from. A test holds release.yml and publish.yml to one registry path and one tag scheme, the same standard the asset names were already held to (#57). -
doctor states its check conventions. Two species, written where the checks live: floor checks grade the image's baked posture and are permanent by design — the boot smoke's hardening lap pins the same floor — and drift reconcilers grade stateful drift, retiring once every supported install path has run them. The 44.15.0 audit's ledger: none retire; every reconciler's drift is still produced by a supported upgrade chain or by ordinary use, and the smoke's doctor lap reads by check name and asserts no count, so a retirement, when one eventually comes, is a silent no-op there (#56).
-
The third audit ran before the release. Two lanes over everything 44.15.0 ships (#63, the #55 pattern). Performance read the compose question by construction — the keymap's boot layer feeds the build's existing initramfs regeneration, zero added dracut minutes on keyed builds — and the boot graph's delta: the heal a no-op read on gapless machines, boot-titles' remount retry bounded at ~2 s and only when titles need writing, the include one stat per niri load, check_keymap four file reads against the ~6.6 s doctor baseline. Security walked the keymap value's road (one validator, three sinks — a KDL string, a single-quoted echo, an argv), the trust directions (a root-written stanza user-read; the heal steered solely by the ride), the heal's writes, boot-titles' remount, and the release page's interpolations. One finding:
kuma keymap applywas the one writer in the tree off the house shape — now temp and rename with an explicit 0644, so a hardened umask cannot lock the greeter out of its own layout and a crash cannot leave a half stanza behind. Hand-forward: per-unit boot timing on green runs, carried from #55. -
The prose names its shortcuts as commands. The README answers "why this exists" before "what do I type", and the everyday-use section names
kuma add,kuma remove,kuma cleanandkuma completionsas commands — the verb-documentation gate reads pages for command mentions, and bare words in a list are not one. -
doctor's /etc drift check stops watching
/etc/vconsole.conf. The file's sanctioned writer islocalectl set-keymap— whatkuma keymap applyruns — and localectl rewrites the file in its own format (a header, FONT, the XKB lines), so re-applying even the declared layout re-shadowed the compose's one-liner and the byte compare warned again on every legitimate apply. The TTY layer's semantics stay watched by the keymap check, which reads the KEYMAP= line off every layer and already narrates the dangerous case — a local copy holding back a moved declaration — as layer-versus-initramfs drift with the right fix attached.
Static x86_64 binary, no runtime dependencies.
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.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.15.0/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.0/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v44.15.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-muslThe image this release publishes verifies with the committed
public key — the same key every kuma machine's own policy
enforces on update:
$ curl -sSLO https://github.com/Letdown2491/kumaOS/raw/v44.15.0/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-44.15.0The moving tag is the convenience and the digest is the proof;
the verify response prints the digest it checked, and the same
command against that digest pins the bytes:
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma@sha256:<digest the verify above printed>Built from 125936e7c76c2f6c86ab94a271569e78e66f4068.
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