Skip to content

kuma v45.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 15:50
· 71 commits to main since this release
  • kuma run no-home|airlock — the sandbox a build tool's scripts deserve. npm install runs lifecycle scripts on every package it touches, and pip's own documentation answers "running arbitrary code from distributions" for what an install does. The verb runs the command under bubblewrap — unprivileged, no setuid bit, already in every image — with the system read-only, a fresh /dev and /proc, a /tmp that vanishes when it exits, and the point: an empty home, a tmpfs mounted where yours is and gone when the command finishes, so the caches and tokens a postinstall reaches for are not in the sandbox to find. The working directory binds read-write after the home tmpfs (later mounts win), so the project is the one real, writable thing the child sees; the agent sockets are unset; the child cannot TIOCSTI keystrokes back into your terminal (--new-session); nothing is left orphaned (--die-with-parent). The child's output is yours and its exit code is the command's. airlock adds the network removal — loopback only — for scripts that should not phone home while they run. The verb refuses the two spellings that would defeat it: running from the home directory or any directory containing it.
  • External monitors get brightness. ddcutil rides the image — tagged uaccess, so the sitting user's session can reach the i2c bus with no group story, with i2c-dev loaded through the module loader the package already ships — and the shell's brightness control speaks DDC/CI through it. This is the machine half of the kumaUI v0.8.0 ride (pin e333d6e: DDC/CI brightness, avif through the video path's libav decode, the wallpaper-derived theme's flavor picker in Settings). The smoke asserts the plumbing rides the image.
  • A new SUID binary fails the compose. The image bakes a golden list of the seventeen setuid paths the base should have (/usr/lib/kuma/suid.golden), and the compose's check runs it — a package update that quietly adds a privileged binary fails the build instead of shipping. One-directional by design: an added SUID bit is the risk class (privilege surface arriving unseen); a removed one is visible at first boot where it matters.
  • The convergence units run sandboxed. The four units that touch the machine on a schedule — backup, restore, snapshot, and the daily converge with its gate — run under NoNewPrivileges and ProtectSystem=strict with their write surfaces settled against what the scripts actually write: restic's cache in /var/cache/restic, and NetworkManager's system-connections for the restore path.
  • The daemon's residue is tightened. The reviews' MINOR list came forward rather than waiting for 45.2: the vault's lock now retires the key with secp256k1's own non_secure_erase — the promise the doc made is the code it runs, no new dependency, the crate had the pass built in — and the same pass runs when the vault drops. The inbound relay channel is bounded: a reconnecting relay's backlog replay sheds at the cap instead of growing the daemon's RSS, and a shed is the requester's own timeout — the same end a jammed queue would have given it. The prompts queue caps at 100 and sheds its oldest, by the activity log's own eviction rule. The socket reads a request line under a 1 MiB cap, answers an over-long line with an error before closing, and no longer keeps one connection's secret-carrying buffer alive into the next. Revocation and deletion forget the relay URLs nobody serves anymore, a teardown clears the road-state map outright, and expired remembered grants are pruned where they are consulted. Two stay deliberate: the blob's wrapped secrets are ciphertext whose unwrap secret lives in memory by design — zeroizing the dead copies buys nothing — and clean's per-tag rmi loop is per-tag tolerance, not an N+1 to fix.
  • The release road keeps its composure. Every cosign invocation retries three times a minute apart (Rekor's transient failures took two road runs on release day — the conflict, the refused connection, and the maintenance window the status page named); the tag watcher checks the registry before dispatching, so re-firing it after a finished promote dispatches no leg; and the save/load digest experiment is run and recorded — the re-serialization is podman save's, so the two-digests-one-content comparison stays retired in favor of trusting bootc's verdict (#68).

Static x86_64 binary, no runtime dependencies.

$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.1.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/kuma

The 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/v45.1.0/kuma-nostrd-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.1.0/kuma-nostr-x86_64-unknown-linux-musl
$ curl -LO https://github.com/Letdown2491/kumaOS/releases/download/v45.1.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-relay

Verify 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-musl

The 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/v45.1.0/cosign.pub
$ cosign verify --key cosign.pub ghcr.io/letdown2491/kuma:niri-45.1.0

The 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 d0b0a000409fcad6adfbc9cf790824042fc34e9c.

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