45d9b2d020
Some checks failed
Build veilor-os OCI (BlueBuild) / Build + sign + push OCI (push) Failing after 1m10s
Initial scaffold for the v0.7 hybrid path. Spike branch only — does
NOT land in main until success criteria pass (see bluebuild/README.md).
## What this commits
- bluebuild/recipe.yml — BlueBuild recipe extending
ghcr.io/secureblue/securecore-kinoite-hardened-userns:latest with:
* veilor branding overlay (overlay/, assets/, scripts/ at /usr/share/veilor-os)
* sudo restored (revert secureblue's run0-only)
* Xwayland restored (some apps still need it)
* mullvad-browser layered alongside Trivalent (default browser kept)
* tailscale + yggdrasil packages (mesh stack layers 1 + 2)
* tailscaled.service pre-disabled (awaits first-boot prompt)
* yggdrasil.service enabled (idle warm-fallback per STRATEGY.md)
* veilor-firstboot.service + veilor-modules-lock.service enabled
* cosign signing module configured
- bluebuild/config/just/60-veilor.just — ujust recipes:
* install-reticulum (RetiNet AGPL fork — mesh layer 3)
* install-reticulum-rnode (LoRa hardware)
* install-thorium (opt-in browser with explicit CVE-lag warning)
* veilor-mesh-join (token paste / QR for tailscale onboarding)
- bluebuild/README.md — spike doc + smoke-test commands + 5-item
success criteria checklist
- kickstart/install-ostreecontainer.ks — install kickstart template
for the v0.7 path. No %packages block; uses
`ostreecontainer --url=ghcr.io/veilor-org/veilor-os:43 --transport=registry`
to populate / from the OCI image directly during anaconda's install
pass. No first-boot rebase, no transition window. Keeps existing
LUKS+btrfs partitioning verbatim.
- .github/workflows/build-bluebuild.yml — GH Actions workflow:
* Triggered on push to v0.7-bluebuild-spike, weekly cron, dispatch
* Uses blue-build/github-action@v1 (TODO: pin to commit SHA per
CI hardening agent 8 follow-up)
* Builds + cosign-signs (keyless via Sigstore) + pushes to GHCR
* Smoke-tests the OCI image (sudo, mullvad-browser, yggdrasil,
tailscale all present)
* Generates SBOM (SPDX) via anchore/sbom-action
* Publishes SLSA build provenance attestation
## What this does NOT change
- main branch is untouched. v0.5.x kickstart path keeps shipping.
- kickstart/veilor-os.ks (the live-ISO ks) is untouched — the v0.7
hybrid uses the existing live-ISO build path; only the install-time
ks (install-ostreecontainer.ks) is new.
- overlay/, scripts/, assets/ are untouched on this branch — the
recipe pulls them in via `type: files` modules at build time.
## Spike success criteria (reproduced from bluebuild/README.md)
- [ ] `bluebuild build recipe.yml` exits 0
- [ ] `bootc container lint` exits 0 on resulting image
- [ ] `podman run` smoke-test passes
- [ ] CI workflow builds + cosign-signs + pushes to GHCR
- [ ] Installer ISO using `ostreecontainer` against this OCI reaches
SDDM with admin login on first boot
If all 5 land, merge v0.7-bluebuild-spike → main as v0.7.0.
## Reference
- docs/STRATEGY.md (full plan)
- docs/ROADMAP.md v0.7 (schedule)
- docs/THREAT-MODEL.md (publish before v0.7 ship)
- secureblue: https://github.com/secureblue/secureblue
- BlueBuild: https://blue-build.org
- ostreecontainer: https://docs.fedoraproject.org/en-US/bootc/anaconda-install/
118 lines
No EOL
4.9 KiB
YAML
118 lines
No EOL
4.9 KiB
YAML
# veilor-os — BlueBuild recipe (v0.7 spike, 1-day target)
|
|
#
|
|
# Extends secureblue's hardened Kinoite OCI image with veilor branding,
|
|
# threat-model-driven UX choices, and the three-layer mesh stack
|
|
# (Tailscale + Yggdrasil + opt-in Reticulum). This is the OCI image
|
|
# that the v0.7+ kickstart's `ostreecontainer` directive pulls into
|
|
# the target root during the install pass.
|
|
#
|
|
# Build: bluebuild build recipe.yml
|
|
# Test: podman run --rm -it ghcr.io/veilor-org/veilor-os:43 /bin/bash
|
|
# CI: .github/workflows/build-bluebuild.yml signs + pushes to GHCR.
|
|
#
|
|
# Reference: https://blue-build.org/reference/recipe/
|
|
---
|
|
name: veilor-os
|
|
description: Hardened security-branded Fedora KDE on top of secureblue.
|
|
|
|
# Base image: secureblue's hardened Kinoite variant with userns sandboxing.
|
|
# That brings in: sysctl + kargs + custom SELinux policy + USBGuard +
|
|
# hardened-malloc + Unbound DoT + chronyd NTS + Trivalent browser.
|
|
base-image: ghcr.io/secureblue/securecore-kinoite-hardened-userns
|
|
image-version: latest
|
|
|
|
modules:
|
|
# ── 1. veilor branding overlay ──────────────────────────────────
|
|
# Stamps our overlay/* tree onto the OCI image. KDE color scheme,
|
|
# Plymouth theme, SDDM theme, fontconfig, os-release.
|
|
- type: files
|
|
files:
|
|
- source: ../overlay
|
|
destination: /
|
|
|
|
- type: files
|
|
files:
|
|
- source: ../assets
|
|
destination: /usr/share/veilor-os/assets
|
|
|
|
- type: files
|
|
files:
|
|
- source: ../scripts
|
|
destination: /usr/share/veilor-os/scripts
|
|
|
|
# ── 2. Branding overrides at build time ─────────────────────────
|
|
- type: script
|
|
snippets:
|
|
- |
|
|
# os-release brand
|
|
sed -i \
|
|
-e 's|^GRUB_DISTRIBUTOR=.*|GRUB_DISTRIBUTOR="veilor-os"|' \
|
|
/etc/default/grub 2>/dev/null || true
|
|
# Apply our kde-theme + plymouth in build
|
|
bash /usr/share/veilor-os/scripts/kde-theme-apply.sh || true
|
|
bash /usr/share/veilor-os/scripts/30-apply-v03-theme.sh 2>/dev/null || true
|
|
plymouth-set-default-theme details 2>/dev/null || true
|
|
|
|
# ── 3. Override secureblue's run0-only — restore sudo ───────────
|
|
# secureblue removes sudo + replaces with run0. Too disruptive for
|
|
# daily-driver workflows. Restore sudo, keep run0 available.
|
|
- type: rpm-ostree
|
|
install:
|
|
- sudo
|
|
|
|
# ── 4. Re-enable Xwayland ───────────────────────────────────────
|
|
# secureblue disables Xwayland for attack-surface reduction. Some
|
|
# apps (Element, Slack-likes, older Qt5 tools) still need it.
|
|
# User who wants it removed back can `rpm-ostree override remove`.
|
|
- type: rpm-ostree
|
|
install:
|
|
- xorg-x11-server-Xwayland
|
|
|
|
# ── 5. Mullvad Browser as anti-fingerprint companion ────────────
|
|
# Layered alongside Trivalent (kept as default per STRATEGY.md).
|
|
# Trivalent for daily browsing, Mullvad for pseudonymous browsing.
|
|
# Thorium remains opt-in only via `ujust install-thorium` — see
|
|
# config/thorium.just for the warning + install logic.
|
|
- type: rpm-ostree
|
|
install:
|
|
- mullvad-browser
|
|
|
|
# ── 6. Mesh stack packages ──────────────────────────────────────
|
|
# Layer 1 (Day 1 daily driver, service pre-disabled): Tailscale
|
|
# Layer 2 (Day 1 idle warm-fallback): Yggdrasil-go
|
|
# Layer 3 (opt-in via ujust): Reticulum / RetiNet — handled in just/
|
|
- type: rpm-ostree
|
|
install:
|
|
- tailscale
|
|
- yggdrasil
|
|
|
|
# ── 7. ujust recipes for opt-in components ──────────────────────
|
|
- type: files
|
|
files:
|
|
- source: config/just
|
|
destination: /usr/share/ublue-os/just
|
|
|
|
# ── 8. Service tuning: tailscale pre-disabled, yggdrasil idle ───
|
|
- type: systemd
|
|
system:
|
|
enabled:
|
|
- yggdrasil.service # idle warm-fallback (config = empty Listen[])
|
|
disabled:
|
|
- tailscaled.service # awaits first-boot prompt for join
|
|
# secureblue parents already enable: sshd, fail2ban, usbguard,
|
|
# auditd, firewalld, chronyd, sddm — no re-enable needed.
|
|
|
|
# ── 9. veilor-os specific systemd units ─────────────────────────
|
|
# veilor-firstboot.service comes in via overlay/etc/systemd/system/
|
|
# — needs explicit enable since it's not part of secureblue's set.
|
|
- type: systemd
|
|
system:
|
|
enabled:
|
|
- veilor-firstboot.service
|
|
- veilor-modules-lock.service
|
|
|
|
# ── 10. signing config ──────────────────────────────────────────
|
|
# bluebuild emits cosign.pub at root; CI uses the pinned key
|
|
# generated for veilor-org. signed-by reference for bootc upgrade
|
|
# signature verification.
|
|
- type: signing |