Platform dossiers
- Status
- Draft
- Version
- 0.1.0
- Authority
- UASK standard
- Applies to
- operating-system
Version: 0.1 · facts checked 2026-11-21
This document is informative. It holds the facts about named platforms that the
Platform families part leaves out of its rules, so that a rule never has
to change when a platform does. No sentence here creates an obligation (SCF-CHG-002): what a
product has to satisfy is in the Construction Constitution, and what an
adapter or a construction service has to satisfy is in Platform families. Terms are defined in the
glossary.
1. How to read the facts
Every statement about a platform is a row of a table with five columns: an id, the statement, the version it holds for, the source, and the date on which the source was read. This is the source policy of the knowledge base, section 3, applied to the claim classes Platform and Measured. Sections 2, 8 and 9 are patterns: they reason from the facts, cite them by id and are marked as patterns. Section 3 is a table of facts: each of its cells cites the rows that support it.
- Version. The product and release the statement was read for. Where a source gives no release, the column gives the date of the page or of the data.
- Source. One or two pages that were opened on the date in the last column: the project’s own documentation, manual pages, source files, release notes or specifications. A statement that something does not exist is marked “absence: not stated by the project” and names the pages that were searched.
- Ids. Three letters name the subject (DEB, FBS, PRV and so on), two digits the claim and a letter or a number a part of it, as in DEB-01a. Rows with MAP in the id were written for the mapping table in section 3; other rows support its cells too, and every cell names its rows. A published row id keeps its fact through a refresh and is not reused for another fact; a withdrawn row leaves its id unused.
- Measured rows. A row that reports a count, a share or a duration is a Measured claim (section 4 of the knowledge base): DEB-08a to DEB-08c, DEB-10a, DEB-10b, PIN-01.3, APK-06a, IMP-02.7 to IMP-02.9 and IMP-03.3 to IMP-03.5. The method is the counting rule written in the statement, the environment is the data set named in the Version column, the raw result is the data at the cited source on the date in the last column, and the figures are those read on that date.
- Refresh. A row is refreshed by reading its source again. A changed fact is a PATCH change of
this document (
SCF-CHG-006), and the document is reviewed every six months.
2. Structural differences
Two differences matter more than vocabulary. Both are patterns: they are read from the facts of section 4 and are not platform facts themselves.
Binary-first and source-first
In the deb, rpm and apk families a system is composed by resolving pre-built packages into a root (MAP-DEB-6, MAP-RPM-4, APK-MAP-b). In the BSD families a release is built in order from one source tree as a single unit (FBS-01a, OBS-01a, NBS-01a), and packages are a way of slicing the result. For the stages of the construction pipeline this means that bootstrap and population (S4 and S5) are dependency-resolution problems in the first case and build problems in the second, and that materialisation (S9) is dependency resolution in the first case and staging in the second. The families move towards each other: FreeBSD offers its base system as packages (FBS-07a to FBS-07d), and the packaging systems of illumos and Haiku were package-shaped from the start (OTH-03b, OTH-04b).
Installer-first and image-first
Some families ship an installer that reads an answer file: preseed and autoinstall (MAP-DEB-4,
MAP-DEB-5), kickstart (RPM-07a), setup-alpine (APK-MAP-a), bsdinstall (FBS-04) and OpenBSD
autoinstall (OBS-03a). NetBSD ships an installer, sysinst, with a definition file for defaults, and
documents no unattended mode (NBS-03a to NBS-03c, IMP-05.1, IMP-05.2). Yocto and Buildroot build
images (SBL-04a, SBL-04c) and document no installer and no answer file (SBL-04e, SBL-04f). The row
“Installer contract” of section 3 gives the position of each family.
3. Entity mapping
The twelve portable entities of Platform families (SCF-PLT-007) as each family names them, and a
last row for the signing capability of SCF-PLT-010, which is not an entity. Each cell names, in
brackets, the rows of sections 4 to 7 that support it; “none documented here” means that this
dossier holds no row for the cell and says nothing about the platform. The last three rows give the
version, the source and the date for the whole column.
| Portable entity | deb | rpm | apk | FreeBSD | OpenBSD | NetBSD | illumos | Nix / Guix | Yocto / Buildroot |
|---|---|---|---|---|---|---|---|---|---|
| Origin | sources.list / deb822 .sources (MAP-DEB-1) |
.repo file (baseurl, metalink) (MAP-RPM-1) |
/etc/apk/repositories (APK-08d) |
pkg repository configuration (FBS-11a, FBS-MAP-a) | mirror and release directory (OBS-01c) | release tree and pkgsrc binary packages (NBS-MAP-b, CHO-06.4) | IPS publisher (MAP-ILL-01, MAP-ILL-05) | Nix: flake input, substituter; Guix: channel, substitute server (SBL-02a, SIG-08.1, SBL-02d, SIG-08.2) | Yocto: recipe sources (SBL-04a); Buildroot: <PKG>_SITE (MAP-BRT-02) |
| Pin | snapshot service (Debian, Ubuntu) (DEB-09a to DEB-09c, MAP-DEB-1) | Fedora archive and vault trees (RPM-09a, RPM-09e, RPM-09f); Red Hat content-template snapshot (RPM-09d, PIN-05.1); no snapshot or date-addressed tree in the Fedora download tree (RPM-09c) | release branch; no upstream snapshot (APK-06b, APK-06c) | release branch and pkg branch (PIN-08.1, PIN-08.2, FBS-MAP-a) | release (OPENBSD_x_y_BASE tag) (OBS-MAP-a, PIN-08.3) |
release directory (PIN-08.4, NBS-MAP-b) | FMRI version and timestamp; pkg freeze (MAP-ILL-01, MAP-ILL-02) |
flake.lock revision; channel commit (guix time-machine) (SBL-02a, PIN-04.1, SBL-02d, PIN-04.2) |
Yocto: SRCREV (MAP-YOC-05); Buildroot: .hash files (MAP-BRT-02) |
| Component | .deb (DEB-08c, DEB-14a) |
.rpm (RPM-06a) |
.apk (APK-08c) |
pkg package; with pkgbase also the base system (FBS-02a, FBS-07b, FBS-07d) | set tarball (OBS-01c, OBS-02a) | set tarball (NBS-MAP-b) | IPS package (FMRI) (MAP-ILL-01, OTH-03b) | Nix: derivation and store path (MAP-NIX-01); Guix: substitute (MAP-GUX-03) | Yocto: recipe (SBL-04a); Buildroot: package directory (MAP-BRT-02) |
| Selection | task, metapackage, package list; Ubuntu: germinate seeds (MAP-DEB-2, DEB-07a, DEB-07c, DEB-07d) | comps group, blueprint packages, KIWI packages (MAP-RPM-2, RPM-02b, RPM-03c) | profile apks= (APK-01b, APK-MAP-b) |
package list, src.conf options (FBS-02b, FBS-05a) |
set list (OBS-01c, OBS-02a) | set list (NBS-MAP-b) | package list in the constructor manifest (OTH-02a, MAP-ILL-05) | module options / operating-system (SBL-02c, SBL-02e, MAP-GUX-02) |
Yocto: IMAGE_INSTALL (MAP-YOC-01); Buildroot: BR2_PACKAGE_* options (MAP-BRT-03) |
| Closure | apt solver output (MAP-DEB-6) | libsolv output (MAP-RPM-4) | solver output (apk fetch --simulate --recursive) (APK-MAP-b) |
pkg install -n change list (FBS-MAP-c) |
fixed set (OBS-01c) | fixed set (NBS-MAP-b) | IPS solver (MAP-ILL-04, OTH-03b) | store-path closure (MAP-NIX-01) | Yocto: per-task input checksums (SBL-05a); Buildroot: none documented here |
| Overlay | includes.chroot (live-build) (MAP-DEB-3) |
blueprint customisations, KIWI overlay (MAP-RPM-5, RPM-03c) | apkovl (APK-01b, APK-04a) |
poudriere image overlay directory (FBS-02c) |
siteNN.tgz (OBS-02a) |
mkimage -c custom files, METALOG staging (NBS-MAP-a, NBS-01b) |
extra publisher, package actions (MAP-ILL-05, OTH-03b) | module files, service extensions (SBL-02c, MAP-GUX-04) | Yocto: ROOTFS_POSTPROCESS_COMMAND (MAP-YOC-02); Buildroot: BR2_ROOTFS_OVERLAY (MAP-BRT-01) |
| Hook | chroot hooks (*.hook.chroot) (MAP-DEB-3) |
%post, KIWI hooks, postprocess (MAP-RPM-3, RPM-03c, MAP-RPM-6) |
package scripts (APK-MAP-c) | image pre- and post-scripts (FBS-02c) | install.site (OBS-02b) |
customize() of the embedded mkimage (NBS-MAP-a) |
actuators; no install scripts (OTH-03a, OTH-03b) | activation scripts (MAP-NIX-04, MAP-GUX-04) | postprocess commands; post-build and post-image scripts (MAP-YOC-02, MAP-BRT-01) |
| Layout | image build stage (live-build, debos, mkosi) (DEB-04a, DEB-06a) | blueprint filesystem, osbuild partition stages (MAP-RPM-5, MAP-RPM-9) | mkimage profile (APK-01a) | poudriere image -t (FBS-02b) |
disklabel template (OBS-03b) | build.sh image targets (NBS-01c) |
distribution constructor (OpenIndiana), kayak (OmniOS) (OTH-02a, OTH-02b) | image.repart; guix system image (MAP-NIX-06, MAP-GUX-01) |
wic (MAP-YOC-03); genimage (PRV-02.8) |
| Boot set | signed shim, grub, kernel packages (DEB-11a) |
shim, grub2, kernel packages (MAP-RPM-8) |
kernel flavours (APK-01b, APK-MAP-b) | loader.efi and kernel (FBS-MAP-b) |
bsd, bsd.mp, bsd.rd (OBS-01c) |
kernel sets (NBS-MAP-b) | boot archive (MAP-ILL-03) | kernel, initrd, optional UKI (Nix); kernel, initrd, bootloader (Guix) (MAP-NIX-05, MAP-GUX-02) | Yocto: EFI_PROVIDER (MAP-YOC-04); Buildroot: bootloader (SBL-04c) |
| Installer contract | preseed / autoinstall answer file (MAP-DEB-4, MAP-DEB-5) | kickstart (RPM-07a) | setup-alpine -f (APK-MAP-a) |
installerconfig (FBS-04) |
install.conf (autoinstall) (OBS-03a) |
sysinst (menu), a definition file for defaults; no answer file documented (NBS-03a, NBS-03c) |
none documented here; the constructor and kayak build installation media (OTH-02a, OTH-02b) | declarative configuration file (SBL-02c, SBL-02e) | none documented; image-first (SBL-04e, SBL-04f) |
| Manifest | none documented here | none documented here | SPDX SBOM written by apko build (APK-02d) |
METALOG (ownership and permissions of installed items) (FBS-05c) | checksum list SHA256 of the release directory (OBS-05a) | METALOG (NBS-01b); digest files and hash list (NBS-05a, NBS-05b) | IPS package manifest (OTH-02c, OTH-03b) | none documented here | none documented here |
| Attestation | none documented here | none documented here | none documented here | none documented here | none documented here | none documented here | none documented here | none documented here | none documented here |
Signing (the capability of SCF-PLT-010, not an entity) |
signed Release (repository-level) (SIG-01.1, SIG-01.2) |
package signature; optional metadata signature (SIG-02.1, SIG-02.2, RPM-10a) | signed index, package signature, key files (SIG-03.1 to SIG-03.3) | repository signature or fingerprint directory; default none (FBS-11a, FBS-11b) | signed digest file per release directory (SIG-04.1, OBS-05a) | digest files; PGP-signed hash list (SIG-05.1, NBS-05a, NBS-05b) | per-manifest X.509 signature (SIG-07.1, OTH-02c, OTH-02d) | signed store paths / substitutes (SIG-08.1, SIG-08.2, MAP-NIX-02) | Yocto: signed RPM packages and package feeds (SIG-09.1); Buildroot: none documented (SIG-09.2) |
| Version | Debian 13.7; live-build 1:20250505+deb13u1 and 1:20250814; apt 3.3.8 (unstable man pages; stable has 3.0.3) | Fedora 45; RHEL 8 and 9 (Pin cell only); osbuild v195; KIWI NG 11.1.19; pykickstart 3.78 | Alpine 3.24.4; apk-tools 3.0.10 | FreeBSD 15.1; pkg 2.9.3 | OpenBSD 8.0 | NetBSD 11.1 | OpenIndiana 2026.10; OmniOS r151060 | Nix 2.36.0; Guix 1.5.0 | Yocto 6.1; Buildroot 2026.08 |
| Source | sources.list(5); Live Manual | Image Builder; kickstart | apk-repositories(5); aports mkimage | release(7); poudriere-image(8) | release(8); autoinstall(8) | BUILDING; mkimage | pkg(7); distribution constructor | Nix manual; Guix manual | Yocto variables; Buildroot manual |
| Checked | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 | 2026-11-21 |
4. Family dossiers
Each dossier lists what the documentation of the family states about composition, packaging, signing, pinning and privilege, one fact to a row. A row says what its source states and no more.
4.1 deb
Versions checked: Debian 13 “trixie” 13.7 (stable, released 2026-09-12; 13.0 released 2025-08-09); live-build 1:20250505+deb13u1 (stable) and 1:20250814 (testing/unstable); debootstrap 1.0.141 (stable) and 1.0.145 (unstable); mmdebstrap 1.5.7-1+deb13u1 (stable) and 1.7.0-5 (unstable); bdebstrap v0.8.1 (2026-04-08); debos v1.1.8 (2026-11-03); FAI 6.6 (ISO announcement 2026-06-23); mkosi v27.1 (2026-09-28); sbuild 0.89.3+deb13u4 (stable); apt 3.0.3 (stable) and 3.3.8 (unstable); Ubuntu 26.10 “stonking” (archive Release dated 2026-10-15) and 26.04 LTS “resolute” (2026-04-23); Ubuntu live-build 3.0~a57-1ubuntu56; livecd-rootfs 27.04.1 (changelog head); Kali kali-rolling (InRelease dated 2026-11-20).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| DEB-01a | live-build is described by its own manual page as “a set of scripts to build live system images” that uses a configuration directory to automate and customize the build. | live-build 1:20250814 (unstable); stable 1:20250505+deb13u1 | live-build(7) | 2026-11-21 |
| DEB-01b | The Debian Live Manual states that live system images can be integrated with Debian Installer and calls images that hold a live system plus an otherwise independent installer “combined images”. | Live Manual (trixie-era text); live-build 1:20250505+deb13u1 | Live Manual, chapter 12 Customizing Debian Installer | 2026-11-21 |
| DEB-01c | live-build does not include Debian Installer images by default; the installer has to be enabled with lb config, for example lb config --debian-installer live. |
Live Manual (trixie-era text); live-build 1:20250505+deb13u1 | Live Manual, chapter 12 Customizing Debian Installer | 2026-11-21 |
| DEB-02a | In debian/control the installer udeb bootstrap-base (“Install the base system”) depends on debootstrap-udeb; the base-installer README says “The bootstrap-installer udeb is responsible for calling debootstrap to install the base system”, and debian/control defines no package of the name bootstrap-installer (its two packages are base-installer and bootstrap-base). |
base-installer 1.226 (Debian 13) | README · debian/control | 2026-11-21 |
| DEB-02b | The debootstrap manual page describes the tool as bootstrapping “a basic Debian system of SUITE into TARGET from MIRROR by running SCRIPT”. | debootstrap 1.0.145 (unstable); stable 1.0.141 | debootstrap(8) | 2026-11-21 |
| DEB-02c | sbuild’s default chroot mode is unshare, it is “also used on Debian buildd machines”, and it builds without superuser privileges. | sbuild 0.89.3+deb13u4 (stable) | sbuild(1), CHROOT MODES | 2026-11-21 |
| DEB-02d | The sbuild-createchroot manual, which describes the debootstrap-based chroot creation, says it “is only useful for the schroot backend” and that “Debian buildds have switched to the unshare backend in 2024”. | sbuild 0.89.3+deb13u4 (stable) | sbuild-createchroot(8) | 2026-11-21 |
| DEB-02e | In sbuild’s unshare mode the chroot tarball is created by running mmdebstrap (settings unshare_mmdebstrap_auto_create, unshare_mmdebstrap_extra_args, $mmdebstrap = 'mmdebstrap'). |
sbuild 0.89.3+deb13u4 (stable) | sbuild.conf(5) | 2026-11-21 |
| DEB-03a | The mmdebstrap manual says it “is meant as an alternative to the debootstrap tool” and that it uses apt to resolve dependencies, so it can use more than one mirror. | mmdebstrap 1.5.7-1+deb13u1 (stable); 1.7.0-5 (unstable) | mmdebstrap(1), trixie | 2026-11-21 |
| DEB-03b | The bdebstrap README describes it as “an alternative to debootstrap and a wrapper around mmdebstrap to support YAML based configuration files” that can layer multiple customizations on top of each other. | bdebstrap v0.8.1 (2026-04-08) | bdebstrap README | 2026-11-21 |
| DEB-04a | debos expects a YAML recipe file and runs the actions listed in it sequentially; the README names actions such as debootstrap, apt, image-partition, filesystem-deploy, overlay, run and ostree-commit. |
debos v1.1.8 (2026-11-03) | debos README | 2026-11-21 |
| DEB-04b | Unless --disable-fakemachine is given, debos creates a virtual machine with fakemachine and executes the recipe actions inside it, and it falls back to running the recipe on the host when no backend is supported. |
debos v1.1.8 (2026-11-03) | debos README, Fakemachine Backend | 2026-11-21 |
| DEB-04c | fakemachine creates a virtual machine derived from the current root filesystem, which “allows unprivileged users to perform operations that would normally require root on the host, such as mounting filesystem images”. | fakemachine (main branch, read 2026-11-21) | fakemachine README | 2026-11-21 |
| DEB-05a | The FAI.me web service creates “custom installation or live media or ready-to-boot disk images” without installing FAI locally. | FAI 6.6 | fai-project.org | 2026-11-21 |
| DEB-05b | The FAI feature list includes “Supports creation of custom live ISOs”, and the news item of 2026-06-23 announces ISO images built with FAI 6.6. | FAI 6.6 (2026-06-23) | fai-project.org | 2026-11-21 |
| DEB-06a | mkosi’s Format= setting accepts disk (a GPT image generated with systemd-repart), uki (a unified kernel image), esp, oci (a directory compatible with the OCI image specification), directory, tar, cpio, sysext, confext, portable, addon and none. |
mkosi v27.1 (2026-09-28) | mkosi(1) at tag v27.1, Format= | 2026-11-21 |
| DEB-06b | mkosi’s Distribution= setting accepts debian, kali and ubuntu (and fedora, arch, opensuse, centos, rhel, rocky, alma and others). |
mkosi v27.1 (2026-09-28) | mkosi(1) at tag v27.1, Distribution= | 2026-11-21 |
| DEB-07a | Ubuntu’s livecd-rootfs package, described as “the script used to create the root filesystem on the livecd”, depends on live-build (>= 3.0~a57-1ubuntu31~) and germinate (>= 1.25.1). |
livecd-rootfs 27.04.1 (changelog head) | livecd-rootfs debian/control | 2026-11-21 |
| DEB-07b | The live-build package in Ubuntu is at 3.0~a57-1ubuntu56 (published 2026-10-15 in the 27.04 development series), while Debian’s live-build in unstable is 1:20250814. | Ubuntu live-build 3.0~a57-1ubuntu56; Debian live-build 1:20250814 | live-build package in Ubuntu (Launchpad) · live-build on tracker.debian.org | 2026-11-21 |
| DEB-07c | germinate is documented as a tool that expands dependencies in a list of seed packages. | germinate 2.50 (unstable); 2.46 in trixie | germinate(1) | 2026-11-21 |
| DEB-07d | The livecd-rootfs changelog for 27.04.1 records that seeds are fetched from the git seed repositories on git.launchpad.net via germinate --vcs=git for the image builds. |
livecd-rootfs 27.04.1 | livecd-rootfs debian/changelog | 2026-11-21 |
| DEB-07e | The Launchpad developer documentation states that “only members of the launchpad-livefs-builders team can create new LiveFS or LiveFSBuild objects” because live filesystem builds consume a lot of build-farm time. | Launchpad manual, page last updated 2026-04-22 | Building live filesystems in Launchpad | 2026-11-21 |
| DEB-07f | The launchpad-livefs-builders team has the membership policy “Restricted Team”, 615 active members, and a description saying live filesystem build requests “are restricted to trusted users to prevent abuse of shared resources”. | Launchpad team page, read 2026-11-21 | ~launchpad-livefs-builders | 2026-11-21 |
| DEB-08a | The Debian 13 release announcement of 2025-08-09 states “a total count of 69,830 packages”, of which over 14,100 are new. | Debian 13.0 (2025-08-09) | Debian 13 “trixie” released | 2026-11-21 |
| DEB-08b | The trixie archive (Release: Suite stable, Version 13.7, Date Sat, 12 Sep 2026) lists 37,643 source packages in the component main (count of Package: stanzas in Sources). |
Debian 13.7 | dists/trixie/Release · main/source/Sources.xz | 2026-11-21 |
| DEB-08c | The trixie archive (Version 13.7) lists 68,825 binary packages in the component main for amd64, including Architecture: all packages (count of Package: stanzas in Packages). |
Debian 13.7 | dists/trixie/Release · main/binary-amd64/Packages.xz | 2026-11-21 |
| DEB-09a | snapshot.debian.org describes itself as a “wayback machine” that “consists of all past and current packages the Debian archive provides”, with imports of the main archive “from 2005 until the present”, and it offers the archives debian, debian-archive, debian-backports, debian-debug, debian-ports, debian-security, debian-security-debug and debian-volatile. | snapshot.debian.org, page built 2026-11-21 | snapshot.debian.org | 2026-11-21 |
| DEB-09b | On snapshot.debian.org a snapshot is addressed by a timestamp such as /archive/debian/20091004T111800Z/ (formats yyyymmddThhmmssZ or yyyymmdd), and a request between imports returns the latest import before the requested time. |
snapshot.debian.org, page built 2026-11-21 | snapshot.debian.org | 2026-11-21 |
| DEB-09c | The Ubuntu snapshot service at snapshot.ubuntu.com provides snapshots of the Ubuntu archive “for any date and time after 1 March 2023”, addressed as YYYYMMDDTHHMMSSZ, and is supported in Ubuntu 23.10 onwards plus updated 20.04 (apt 2.0.10) and 22.04 (apt 2.4.11). |
snapshot.ubuntu.com, page read 2026-11-21 | Ubuntu Snapshot Service | 2026-11-21 |
| DEB-10a | The Debian test site reports 36,419 packages (96.9%) built reproducibly in trixie/amd64, 831 (2.2%) failed to build reproducibly and 258 (0.7%) failed to build from source (page updated 2026-11-21 00:06 UTC; IMP-03.3 gives 257 failed to build from source in the later file reproducible.json). | Debian 13.7 (trixie), amd64 | Overview of reproducible builds for packages in trixie for amd64 | 2026-11-21 |
| DEB-10b | The Debian test site reports 38,434 packages (96.1%) built reproducibly in forky/amd64, the current testing suite (page updated 2026-11-21). | Debian testing “forky”, amd64 | Overview of reproducible builds for packages in forky for amd64 | 2026-11-21 |
| DEB-10c | The same test site states that “Testing of Fedora has sadly been suspended for now” (page updated 2026-11-21 01:02 UTC). | tests.reproducible-builds.org overview, 2026-11-21 | Reproducible builds overview | 2026-11-21 |
| DEB-11a | The Debian Secure Boot page lists shim-signed as signed by Microsoft and grub-efi-amd64-signed, the linux-image-*-amd64 kernel packages, shim-helpers-amd64-signed and systemd-boot-efi-amd64-signed as signed by Debian, and says shim embeds Debian’s signing keys. |
Debian 13 (wiki page current 2026-11-21) | Debian wiki: SecureBoot | 2026-11-21 |
| DEB-11b | The same page says that a self-built kernel produces “binaries that are not signed with the Debian key”, so the builder has to sign them and enrol the key with MOK or disable Secure Boot. | Debian 13 (wiki page current 2026-11-21) | Debian wiki: SecureBoot, Secure Boot limitations | 2026-11-21 |
| DEB-11c | Debian 13 stable carries source packages shim 16.1-2 |
Debian 13.7 | shim on tracker.debian.org · shim-signed on tracker.debian.org | 2026-11-21 |
| DEB-11d | Debian 13 stable carries source packages grub2 2.12-9+deb13u2 and linux-signed-amd64 6.12.94+1. | Debian 13.7 | grub2 on tracker.debian.org · linux-signed-amd64 on tracker.debian.org | 2026-11-21 |
| DEB-11e | The Debian wiki lists “Microsoft Corporation UEFI CA 2011” with “Not After: Jun 27 21:32:45 2026 GMT” as expired and “Microsoft UEFI CA 2023” as valid from 2023-06-13 to 2038-06-13, and says Microsoft did not start signing shim with the 2023 CA until October 2025. | Debian wiki page current 2026-11-21 | Debian wiki: SecureBoot/CAChanges | 2026-11-21 |
| DEB-11f | The Debian wiki says a new shim-signed version 16.1-2 in unstable and testing is “dual-signed, signed using both the old and new Microsoft CAs”, and that similar dual-signed shim binaries for Debian 12 and 13 are included in the point releases 12.15 and 13.6. |
Debian wiki page current 2026-11-21 | Debian wiki: SecureBoot/CAChanges | 2026-11-21 |
| DEB-11g | The Debian 13.6 announcement of 2026-07-11 lists shim 16.1-2~deb13u1 and, for shim-signed, “Ensure Secure Boot compatibility with 2023 Microsoft UEFI CA; check for likely boot issues before installation; combine and verify multiple shim signatures; update signed shim binaries”. | Debian 13.6 (2026-07-11) | Updated Debian 13: 13.6 released | 2026-11-21 |
| DEB-11h | Microsoft states that from 2025-10-20 each approved submission returns two signed binaries (2011 CA and 2023 CA), that Microsoft “will not issue dual signed packages”, that expiry “does not invalidate binaries already signed with the 2011 cert”, and, in an update of 2026-06-26, that approved signing submissions return only binaries signed with the 2023 UEFI CA. | Microsoft HDC post, version 4.0 (updated 2026-06-26) | Signing with the new 2023 Microsoft UEFI certificates | 2026-11-21 |
| DEB-12a | The Live Manual lists “Superuser (root) access” first among the requirements for the host that builds a live system image. | Live Manual (trixie-era text); live-build 1:20250505+deb13u1 | Live Manual, 3.1 Requirements | 2026-11-21 |
| DEB-12b | In live-build 1:20250505+deb13u1 the lb front end exits with “Root privileges needed!” when the user id is not 0 for every command except config. |
live-build 1:20250505+deb13u1 | frontend/lb in 1:20250505+deb13u1 | 2026-11-21 |
| DEB-12c | The same check (“Root privileges needed!”, skipped only for config) is present in the live-build git master at commit 531cdb98 of 2026-09-13. |
live-build git master 531cdb98 (2026-09-13) | frontend/lb on salsa.debian.org | 2026-11-21 |
| DEB-13a | The sources.list manual describes the By-Hash option as acquiring indexes “via a URI constructed from a hashsum of the expected file instead of using the well-known stable filename”, which “can avoid hashsum mismatches, but requires a supporting mirror”, with the default coming from Acquire::By-Hash (yes). |
apt 3.0.3 (stable); 3.3.8 (unstable) | sources.list(5) | 2026-11-21 |
| DEB-13b | The apt.conf manual says Acquire::By-Hash is true by default but “automatically disabled if the source indicates no support for it”, and can be forced with the value “force”. |
apt 3.0.3 (stable); 3.3.8 (unstable) | apt.conf(5) | 2026-11-21 |
| DEB-13c | The Debian repository format page defines Acquire-By-Hash as an optional boolean Release field with default “no” where “yes” indicates that the server supports the by-hash locations, and says the current version of an index must be available there. |
Debian wiki page current 2026-11-21 | Debian wiki: DebianRepository/Format | 2026-11-21 |
| DEB-13d | Debian bug 820660 against reprepro, “Generate by-hash indices and add Acquire-By-Hash: yes to InRelease”, severity wishlist, was filed on 2016-04-11 by Raphaël Hertzog (user tag origin-kali), shows its last message on 2021-02-10 and carries no done marker. | reprepro 5.4.6+really5.3.2-3 (unstable) | Debian bug #820660 | 2026-11-21 |
| DEB-13e | The reprepro manual page contains no by-hash setting (absence: not stated by the project; checked the reprepro(1) manual page on 2026-11-21, a search for “by-hash” returns nothing). | reprepro 5.4.6+really5.3.2-3 (unstable, changelog entry 2026-10-16) | reprepro(1) | 2026-11-21 |
| DEB-13f | The aptly publish API documents an AcquireByHash parameter (“provide index files by hash”) for publishing snapshots and local repositories; the page states no default and shows false in its example responses. |
aptly API documentation (page undated, read 2026-11-21) | aptly: Publish API | 2026-11-21 |
| DEB-13g | The kali-rolling InRelease file dated Fri, 20 Nov 2026 12:09:12 UTC has no Acquire-By-Hash field (its header lists Origin, Suite, Codename, Date, Architectures, Components and Description before the MD5Sum, SHA1 and SHA256 lists). |
Kali kali-rolling, 2026-11-20 | kali-rolling InRelease | 2026-11-21 |
| DEB-13h | The Debian trixie Release (13.7) and the Ubuntu noble-updates InRelease (dated 21 Nov 2026) both carry Acquire-By-Hash: yes. |
Debian 13.7; Ubuntu 24.04 noble-updates | trixie Release · noble-updates InRelease | 2026-11-21 |
| DEB-14a | apt-secure(8) says that after an upload is verified and included in the archive “the maintainer signature is stripped off, and checksums of the package are computed and put in the Packages file”, the checksums of the Packages files go into the Release file, and the Release file is signed with the archive key. | apt 3.3.8 (unstable); 3.0.3 (stable) | apt-secure(8) | 2026-11-21 |
| DEB-14b | apt-secure(8) states “apt-secure does not review signatures at a package level” and names debsig-verify and debsign for per-package signatures. | apt 3.3.8 (unstable); 3.0.3 (stable) | apt-secure(8) | 2026-11-21 |
| DEB-14c | The sources.list manual describes Check-Valid-Until (default yes) as the way APT detects replay attacks: a repository declares a time until which its data is valid, and when that time passes without new data the data is treated as expired and an error is raised. |
apt 3.0.3 (stable); 3.3.8 (unstable) | sources.list(5) | 2026-11-21 |
| DEB-14d | The InRelease files of Debian unstable, testing (forky) and trixie-updates dated 2026-11-20 20:13:47 UTC carry Valid-Until: Fri, 27 Nov 2026 20:13:47 UTC (seven days), while the stable trixie Release (13.7, dated 12 Sep 2026) has no Valid-Until field. |
Debian 13.7 | trixie Release · unstable InRelease | 2026-11-21 |
| DEB-14e | The Debian repository format page says the Valid-Until field “may specify at which time the Release file should be considered expired by the client” and that client behaviour on expired Release files is unspecified. |
Debian wiki page current 2026-11-21 | Debian wiki: DebianRepository/Format | 2026-11-21 |
| MAP-DEB-1 | The sources.list manual documents both the one-line format and the deb822-style format (.sources) and, in deb822 entries, a Snapshot option that selects an earlier archive version from a snapshot service. |
apt 3.3.8 (unstable) | sources.list(5) | 2026-11-21 |
| MAP-DEB-2 | The Live Manual selects packages through package lists such as config/package-lists/*.list.chroot, which may name individual packages or task metapackages such as task-gnome-desktop. |
Live Manual (trixie-era text) | Live Manual, 8.2 Choosing packages to install | 2026-11-21 |
| MAP-DEB-3 | The Live Manual adds files to the live system from config/includes.chroot (mirroring the live system’s /) and runs commands in the chroot stage from scripts with the suffix .hook.chroot in config/hooks/live or config/hooks/normal. |
Live Manual (trixie-era text) | Live Manual, chapter 9 Customizing contents | 2026-11-21 |
| MAP-DEB-4 | Ubuntu’s autoinstall format automates Ubuntu Server 20.04 and later and Ubuntu Desktop 23.04 and later, and the same page says preseed is the way to automate installers based on debian-installer. | Ubuntu installation documentation (read 2026-11-21) | Introduction to autoinstall | 2026-11-21 |
| MAP-DEB-5 | The live-build installer stage can place a preseed.cfg file for Debian Installer in config/includes.installer/. |
Live Manual (trixie-era text) | Live Manual, 12.2 Customizing Debian Installer by preseeding | 2026-11-21 |
| MAP-DEB-6 | The why and why-not commands of apt print the reasoning path from APT’s solver. |
apt 3.3.8 (unstable) | apt(8) | 2026-11-21 |
4.2 rpm
Versions checked: Fedora Linux 45 (released 2026-11-03; fedora-repos 45-1, Pungi 4.14.0-2.fc45, dnf5 5.4.6.0-3.fc45, shim-x64 16.1-7, grub2-efi-x64 2.12-81.fc45, kernel-core 7.2.11-300.fc45); RHEL 10.3 and 9.9 (general availability 2026-11-10); AlmaLinux 10.3 and 9.9 (directories dated 2026-11-16); osbuild v195 (2026-11-04), osbuild-composer v184 (2026-11-11), image-builder v91.0.0 (2026-11-16); KIWI NG 11.1.19 (2026-11-18); rpm-ostree v2026.3 (2026-09-10); bootc v1.17.5 (2026-11-20); RPM 6.1.0 (2026-08-20); pykickstart 3.78; ComplianceAsCode content v0.1.82 (2026-09-01).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| RPM-01a | A Fedora compose “is a single run of Pungi that produces a complete set of repositories, installation trees, and images”, and Pungi is the compose tool Fedora uses to assemble distribution trees, with Fedora configuration in pungi-fedora. | Fedora Linux 45; docs page as archived 2026-07-12 | Fedora Docs: Compose generation · Wayback copy of 2026-07-12 | 2026-11-21 |
| RPM-01b | Pungi’s own overview says “Pungi is a distribution compose tool” and that composes are release snapshots holding installation trees, RPMs, repodata, comps, bootable ISOs, kickstart trees, anaconda images and PXE images. | Pungi 4.14.0 (Fedora 45 package); project page is a read-only archive since pagure.io was sunset in 2026 | Pungi overview on pagure.io | 2026-11-21 |
| RPM-01c | Fedora Rawhide composes run automatically every day at 05:15 UTC on compose-rawhide01.rdu3.fedoraproject.org, driven by pungi-koji. |
Fedora docs page as archived 2026-07-12 | Wayback copy of 2026-07-12 | 2026-11-21 |
| RPM-02a | OSBuild is described as “a pipeline-based build system for operating system artifacts” with a universal pipeline description, and its principles state that “manifests are expected to be machine-generated”. | osbuild v195 (2026-11-04) | osbuild README | 2026-11-21 |
| RPM-02b | In the Image Builder documentation a blueprint (TOML) describes the final image and its customizations, and an image is defined by its blueprint and an image type such as qcow2 or AMI. | Image Builder docs (osbuild.org, copyright 2026) | Basic concepts | 2026-11-21 |
| RPM-02c | The on-premises overview calls osbuild-composer “a service for building customized operating system images (currently only Fedora and RHEL)” and says Image Builder is available in Fedora, CentOS Stream and RHEL; the page is undated, and “only” is its wording, which RPM-11b (CentOS hosts offering centos-9 and centos-10 images, osbuild-composer v184 test, read the same day) and RPM-11c (further repository definitions in osbuild/images v91.0.0) do not bear out for the image library. | osbuild-composer v184 (2026-11-11) | On-premises overview | 2026-11-21 |
| RPM-02d | The image-builder CLI is described as stateless: blueprints are passed directly as local .toml files instead of being uploaded to a service. |
image-builder v91.0.0 (2026-11-16) | On-premises overview | 2026-11-21 |
| RPM-03a | KIWI NG is described as “a command-line image builder for Linux distributions” that builds from an image description and package repositories in a prepare step (new root tree) and a create step (disk, ISO or container artifacts). | KIWI NG 11.1.19 (2026-11-18) | KIWI NG documentation | 2026-11-21 |
| RPM-03b | The KIWI NG documentation lists how-tos to build an ISO hybrid live image, a virtual disk image and an expandable disk image, and to boot live and install ISO images from Grub2. | KIWI NG 11.1.19 (2026-11-18) | KIWI NG documentation | 2026-11-21 |
| RPM-03c | A KIWI image description directory holds config.xml or a *.kiwi file, repository definitions, and optional overlays, archives and shell hooks. |
KIWI NG 11.1.19 (2026-11-18) | KIWI NG documentation | 2026-11-21 |
| RPM-03d | Fedora’s compose process submits live and cloud image builds to Koji using Kiwi, and installer trees using Lorax. | Fedora docs page as archived 2026-07-12 | Wayback copy of 2026-07-12 | 2026-11-21 |
| RPM-04a | rpm-ostree is described as a hybrid image/package system that combines libostree as the base image format with RPM, and builds custom base images with rpm-ostree compose image or rpm-ostree compose tree. |
rpm-ostree v2026.3 (2026-09-10) | rpm-ostree documentation | 2026-11-21 |
| RPM-04b | rpm-ostree’s lockfile module describes lockfiles as “a model to pin specific package versions via JSON files (usually stored in git)”. | rpm-ostree v2026.3 (2026-09-10) | rust/src/lockfile.rs | 2026-11-21 |
| RPM-04c | A compose can write a lockfile with --ex-write-lockfile-to (a versions.lock recording the evra of each package) and read it back with --ex-lockfile; the ex- prefix marks these options as experimental. |
rpm-ostree v2026.3 (2026-09-10) | tests/compose/test-lockfile.sh | 2026-11-21 |
| RPM-04d | The treefile key lockfile-repos names repositories “only used to fetch packages locked via lockfiles”. |
rpm-ostree v2026.3 (2026-09-10) | Treefile reference | 2026-11-21 |
| RPM-04e | The rpm-ostree documentation notes that development focus has shifted to bootc, dnf and the ecosystem around them, while rpm-ostree “continues to be supported”. | rpm-ostree v2026.3 (2026-09-10) | rpm-ostree documentation | 2026-11-21 |
| RPM-05a | bootc is described as “transactional, in-place operating system updates using OCI/Docker container images”, where the container image includes a Linux kernel (in /usr/lib/modules) that is used to boot. |
bootc v1.17.5 (2026-11-20) | bootc documentation | 2026-11-21 |
| RPM-05b | The bootc documentation says its CLI and API “are now considered stable”, that the default storage backend uses ostree, and that a composefs backend exists and is needed for sealed images. | bootc v1.17.5 (2026-11-20) | bootc documentation | 2026-11-21 |
| RPM-06a | rpmkeys --checksig verifies “the digests and signatures contained in PACKAGE_FILE to ensure the integrity and origin of the package”, and signatures cannot be verified without the corresponding public key. |
RPM 6.1.0 (2026-08-20); man page dated 2026-10-19 | rpmkeys(8) | 2026-11-21 |
| RPM-06b | The RPM documentation lists the signature and digest tags stored with a package: RSAHEADER and DSAHEADER since RPM 4.0, SHA256HEADER since 4.14, and SHA3_256HEADER and OPENPGPHEADER since 6.0. | RPM 6.1.0 (2026-08-20) | Signatures and Digests | 2026-11-21 |
| RPM-07a | The kickstart documentation says “Using kickstart, a system administrator can create a single file containing the answers to all the questions that would normally be asked during a typical installation” of Fedora or Red Hat Enterprise Linux, and that Red Hat created the kickstart installation method. | pykickstart 3.78 | Kickstart documentation, Chapter 1 | 2026-11-21 |
| RPM-07b | The kickstart documentation marks the %packages and %post sections as “Added in version Fedora4”. |
pykickstart 3.78 | Kickstart documentation, chapters 6 and 9 | 2026-11-21 |
| RPM-07c | The kickstart documentation lists separate command sets for Fedora and for Red Hat Enterprise Linux, including %pre, %pre-install, %post, %onerror and %traceback sections. |
pykickstart 3.78 | Kickstart documentation | 2026-11-21 |
| RPM-08a | The ComplianceAsCode content project states that its purpose is to create security policy content for platforms such as RHEL, Fedora, Ubuntu, Debian and SLES and for products such as Firefox, in SCAP, Ansible, Bash and CEL formats. | ComplianceAsCode content v0.1.82 (2026-09-01) | ComplianceAsCode/content README | 2026-11-21 |
| RPM-08b | The RHEL 10 product holds the profiles anssi_bp28 (four levels), bsi, cis (several), cui, cui_enhanced, e8, hipaa, ism_o (three levels), ospp, pci-dss, stig and stig_gui. | ComplianceAsCode content, master branch read 2026-11-21 | products/rhel10/profiles | 2026-11-21 |
| RPM-08c | The RHEL 10 stig profile is titled “DISA STIG for Red Hat Enterprise Linux 10” and contains configuration checks that “align to the DISA STIG for Red Hat Enterprise Linux 10 V1R3”. |
ComplianceAsCode content, master branch read 2026-11-21 | stig.profile | 2026-11-21 |
| RPM-08d | The RHEL 10 ospp profile is titled “Protection Profile for General Purpose Operating Systems”, is “based on the Red Hat Enterprise Linux 10 Common Criteria Guidance”, and references a NIAP profile page. |
ComplianceAsCode content, master branch | ospp.profile | 2026-11-21 |
| RPM-08e | The RHEL 10 cis profile is titled “CIS Red Hat Enterprise Linux 10 Benchmark for Level 2 - Server” and aligns to benchmark v1.0.1 released 2025-09-30. |
ComplianceAsCode content, master branch | cis.profile | 2026-11-21 |
| RPM-08f | The RHEL 10 pci-dss profile is titled “PCI-DSS v4.0.1 Control Baseline for Red Hat Enterprise Linux 10”. |
ComplianceAsCode content, master branch | pci-dss.profile | 2026-11-21 |
| RPM-08g | The same repository’s products directory also contains debian11, debian12, debian13, ubuntu2204, ubuntu2404 and ubuntu2604 next to the RHEL, Fedora, SUSE and Oracle Linux products. | ComplianceAsCode content, master branch read 2026-11-21 | products directory | 2026-11-21 |
| RPM-09a | The Fedora archive tree at archives.fedoraproject.org holds releases/ and updates/ directories for Fedora 7 through 42 and states that the releases there are “no longer supported or maintained”. |
Fedora archive, listing read 2026-11-21 | Fedora archive: releases · Fedora archive: updates | 2026-11-21 |
| RPM-09b | The Fedora updates archive repository contains “all the old update packages from the Fedora updates yum repository” (packages that reached stable), is served at fedoraproject-updates-archive.fedoraproject.org, and is aimed at OSTree systems that layer packages onto an older base. | Fedora updates archive; tool README read 2026-11-21 (archived repository on pagure.io) | archive-repo-manager README | 2026-11-21 |
| RPM-09c | The Fedora download tree lists the directories core, development, extras, releases and updates, and none is addressed by calendar date (absence: not stated by the project; checked the index at https://dl.fedoraproject.org/pub/fedora/linux/ on 2026-11-21 and found no snapshot or date-addressed tree). | Fedora Linux 45 | dl.fedoraproject.org/pub/fedora/linux/ | 2026-11-21 |
| RPM-09d | Red Hat Lightspeed (Insights) snapshots the core Red Hat repositories “automatically every 24 hours”, lets a content template use the latest snapshots or a specific date, can also snapshot custom and EPEL repositories, and keeps snapshots for 12 months while always keeping the newest. | Red Hat article of 2025-04-23, updated 2025-11-07 (RHEL 8 and 9 covered) | How to use content templates in Red Hat Lightspeed | 2026-11-21 |
| RPM-09e | AlmaLinux announced on 2024-05-02 that older versions are kept in “vault repositories”, with https://vault.almalinux.org as the official endpoint and repo.almalinux.org/vault redirecting to it, and the vault listing holds one directory per minor release (8.3 to 8.10, 9.0 to 9.9, 10.0 to 10.3). | AlmaLinux 10.3 and 9.9 current; vault listing read 2026-11-21 | AlmaLinux mirror-announce, 2024-05-02 · repo.almalinux.org/vault | 2026-11-21 |
| RPM-09f | The Rocky Linux documentation says that when a new minor release arrives “the previous version becomes unsupported and the team moves this version to the vault”, and the vault listing at dl.rockylinux.org holds minor directories 8.3 to 8.9, 9.0 to 9.8 and 10.0 to 10.2. | Rocky Linux docs page read 2026-11-21; vault listing read 2026-11-21 | Rocky Releases · dl.rockylinux.org/vault/rocky | 2026-11-21 |
| RPM-10a | The dnf5 configuration reference defines repo_gpgcheck as an OpenPGP signature check on a repository’s metadata with “Default: False”, and gpgcheck_policy defaults to “legacy”, where gpgcheck=1 sets only pkg_gpgcheck=1. |
dnf5 documentation (latest; Fedora 45 ships dnf5 5.4.6.0-3.fc45) | DNF5 Configuration Reference | 2026-11-21 |
| RPM-10b | The DNF (version 4) configuration reference says for repo_gpgcheck: “The default is False”. |
DNF documentation (latest) | DNF Configuration Reference | 2026-11-21 |
| RPM-10c | The Fedora 45 repository files fedora.repo and fedora-updates.repo in the package fedora-repos 45-1 set gpgcheck=1 and repo_gpgcheck=0 (path /usr/share/dnf5/repos.d/ in the RPM). |
fedora-repos 45-1 (Fedora Linux 45) | fedora-repos-45-1.noarch.rpm | 2026-11-21 |
| RPM-11a | The osbuild.org command-line documentation says an image built with image-builder “will use the same distribution and version (e.g. Fedora 43) as the host system” unless specified otherwise, and that the architecture is always the host’s. | image-builder v91.0.0 (2026-11-16) | On-premises: Using the commandline | 2026-11-21 |
| RPM-11b | The osbuild-composer test cross-distro.sh (“Only allow releases for the current distro”) expects a Fedora host to offer fedora-* images, RHEL 8 to offer rhel-8, RHEL 9 to offer rhel-8 and rhel-9, RHEL 10 and later all rhel releases, CentOS 9 to offer centos-9, and CentOS 10 and later all centos releases. |
osbuild-composer v184 (2026-11-11) | test/cases/cross-distro.sh at v184 | 2026-11-21 |
| RPM-11c | The osbuild images library ships repository definitions for fedora-43 to fedora-46, centos-9 and centos-10, rhel-8 to rhel-10 minors, AlmaLinux, Rocky Linux and Oracle Linux (ol-9, ol-10), and none for a non-RPM family (absence: not stated by the project; checked the directory listing on 2026-11-21). | osbuild/images v91.0.0 (2026-11-16), data/repositories read 2026-11-21 | osbuild/images data/repositories | 2026-11-21 |
| MAP-RPM-1 | Fedora’s .repo files set metalink= (with baseurl= as a commented example), gpgcheck=1, repo_gpgcheck=0 and gpgkey=file:///usr/share/pki/rpm-gpg/.... |
fedora-repos 45-1 (Fedora Linux 45) | fedora-repos-45-1.noarch.rpm | 2026-11-21 |
| MAP-RPM-2 | In a kickstart %packages section packages are chosen “by group or by individual package name”, groups come from the comps file of the installation repository, and @ introduces a group (or a module stream). |
pykickstart 3.78 | Kickstart documentation, Chapter 9 Package Selection | 2026-11-21 |
| MAP-RPM-3 | A kickstart %post section holds commands run once the installation is complete, for example to install additional software or configure a nameserver. |
pykickstart 3.78 | Kickstart documentation, Chapter 6 Post-installation Script | 2026-11-21 |
| MAP-RPM-4 | The rpm-ostree documentation shows libdnf tying together libsolv (SAT solver), librepo and librpm. | rpm-ostree v2026.3 (2026-09-10) | rpm-ostree documentation | 2026-11-21 |
| MAP-RPM-5 | The image-builder blueprint reference lists customizations for files (customizations.files), directories, services, users and filesystems (customizations.filesystem, with a partitioning_mode setting). |
Image Builder docs (osbuild.org, copyright 2026) | Blueprint reference | 2026-11-21 |
| MAP-RPM-6 | The rpm-ostree treefile has postprocess (inline script) and postprocess-script keys. |
rpm-ostree v2026.3 (2026-09-10) | Treefile reference | 2026-11-21 |
| MAP-RPM-7 | The Fedora wiki Secureboot page says a Fedora remix or Fedora-based distribution “can ship the Fedora shim, grub2 and kernel unchanged” and that customising these packages may require signing them with pesign (page undated and written in the Windows 8 era). | Fedora wiki page, read 2026-11-21 | Fedora wiki: Secureboot | 2026-11-21 |
| MAP-RPM-8 | The Fedora 45 Everything tree contains the packages shim-x64 16.1-7, grub2-efi-x64 2.12-81.fc45 and kernel-core 7.2.11-300.fc45. | Fedora Linux 45 | Packages/s/ · Packages/g/ | 2026-11-21 |
| MAP-RPM-9 | OSBuild’s stage directory includes partition and filesystem stages such as org.osbuild.sfdisk, org.osbuild.sgdisk, org.osbuild.systemd-repart.create, org.osbuild.mkfs.ext4 and org.osbuild.mkfs.xfs, plus org.osbuild.kickstart and org.osbuild.grub2. |
osbuild v195 (2026-11-04) | osbuild/stages | 2026-11-21 |
4.3 apk
Versions checked: Alpine Linux 3.24.4 (stable branch v3.24 created 2026-06-09; 3.24.4 mini root filesystem file dated 2026-11-05; the releases page lists no later stable branch); apk-tools 3.0.10 (tag commit 2026-11-19; Alpine 3.24 main ships 3.0.9-r0) and 2.14.13 (tag commit 2026-11-02); alpine-conf 3.22.0 (tag 2026-06-09); apko v1.5.2 (2026-11-20); melange v0.65.0 (2026-11-16). The Alpine wiki (wiki.alpinelinux.org) answered HTTP 403 to every automated fetch, so mkimage, lbu and apkovl behaviour was read in the upstream source repositories (aports, alpine-conf, mkinitfs) instead.
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| APK-01a | The Alpine image builder scripts/mkimage.sh builds images from named profiles: the option –profile selects one, and each profile is a shell function profile_ |
aports master (Alpine 3.24), file read 2026-11-21 | aports scripts/mkimage.sh | 2026-11-21 |
| APK-01b | When a mkimage profile sets apkovl and hostname, mkimage runs the named generator script under fakeroot in the image directory and logs “Generating |
aports master (Alpine 3.24), file read 2026-11-21 | aports scripts/mkimg.base.sh | 2026-11-21 |
| APK-01c | On each boot, the initramfs init loads the apkovl found on the boot medium (or the one named by the apkovl= kernel option) and unpacks it into the new root, printing “Loading user settings from” that file; it is not limited to the first boot. | mkinitfs master (Alpine 3.24), file read 2026-11-21 | mkinitfs initramfs-init.in | 2026-11-21 |
| APK-02a | apko builds an OCI image from a declarative apko.yaml that does not allow executing arbitrary commands; all content comes from installing apk packages. | apko v1.5.2 | apko docs/build-process.md | 2026-11-21 |
| APK-02b | The apko file format has no equivalent of Dockerfile RUN statements, and the apko project states that this lets apko guarantee the contents and reproducibility of the image and produce metadata such as SBOMs. | apko v1.5.2 | apko docs/apko_file.md | 2026-11-21 |
| APK-02c | The apko README states that apko images are fully bitwise reproducible and that running apko twice gives exactly the same binary. | apko v1.5.2 | apko README | 2026-11-21 |
| APK-02d | apko build writes SBOMs by default: the –sbom flag defaults to true and –sbom-formats defaults to spdx. | apko v1.5.2 | apko internal/cli/build.go | 2026-11-21 |
| APK-02e | melange describes its package builds as declarative pipelines, and its minimal example build file runs a shell script in a pipeline step (the runs: key), so melange pipelines can contain imperative shell steps. | melange v0.65.0 | melange README, melange examples/minimal.yaml | 2026-11-21 |
| APK-03 | The Alpine 3.24.4 mini root filesystem tarball for x86_64 (alpine-minirootfs-3.24.4-x86_64.tar.gz) is 3,704,088 bytes; the release listing dates the file 2026-11-05. | Alpine 3.24.4 | latest-releases.yaml, x86_64 | 2026-11-21 |
| APK-04a | lbu commit stores the configuration as one archive named |
alpine-conf 3.22.0 | alpine-conf lbu.in | 2026-11-21 |
| APK-04b | At boot the initramfs restores the apkovl by extracting the tar.gz archive into the new root and then installs the packages named in the restored /etc/apk/world. | mkinitfs master, Alpine 3.24 | mkinitfs initramfs-init.in | 2026-11-21 |
| APK-05a | When apko does not run as root, or the file system cannot do it, it ignores chown, chmod and character-device creation errors and records the intended ownership, permissions and device files in the final layer tar stream. | apko v1.5.2 | apko docs/build-process.md | 2026-11-21 |
| APK-05b | apko derives the image creation time from the newest build date embedded in the installed apks unless SOURCE_DATE_EPOCH is set, so the output depends on the selected package set. | apko v1.5.2 | apko internal/cli/build.go | 2026-11-21 |
| APK-06a | In the v3.24 main repository for x86_64 the APKINDEX lists 5,961 package names with no name repeated, apk-tools-3.0.9-r0.apk is served, and apk-tools-3.0.8-r0.apk and apk-tools-3.0.7-r0.apk answer HTTP 404. | Alpine 3.24, checked 2026-11-21 | dl-cdn v3.24/main/x86_64 | 2026-11-21 |
| APK-06b | The Alpine user handbook says each stable release and edge has its own main and community repositories, and that downgrading packages or versions is currently not supported. | handbook 0.1a, read 2026-11-21 | Alpine Linux user handbook, apk | 2026-11-21 |
| APK-06c | The mirror root dl-cdn.alpinelinux.org/alpine/ lists one directory per release branch (v3.0 to v3.25), plus edge and latest-stable, and no dated snapshot directory. | mirror listing, 2026-11-21 | absence: not stated by the project; checked mirror root and user handbook on 2026-11-21 | 2026-11-21 |
| APK-07a | apk trusts the public keys placed in /etc/apk/keys to verify the cryptographic signatures of packages. | apk-tools 3.0.x | apk-keys(5) | 2026-11-21 |
| APK-07b | For apk v2 packages a single signature from a trusted key is sufficient and the signature entry name carries the key file name (.SIGN.RSA. |
apk-tools 3.0.x | apk-v2(5), apk-keys(5) | 2026-11-21 |
| APK-07c | None of the 36 apk-tools manual pages in the doc directory (including apk-keys(5), apk-v2(5), apk-v3(5), apk-repositories(5), apk-verify(8)) describes key revocation or key expiry; the only match for “expire” concerns the index cache. | apk-tools master (3.0.10 line) | absence: not stated by the project; checked the apk-tools doc directory on 2026-11-21 | 2026-11-21 |
| APK-08a | Alpine 3.23.0 (2025-12-03) ships apk-tools v3 while keeping the v2 index and package format for now. | Alpine 3.23.0 | Alpine 3.23.0 release notes | 2026-11-21 |
| APK-08b | The apk-tools tag v3.0.0 points to a commit of 2025-12-01, the newest 3.0 tag, v3.0.10, to a commit of 2026-11-19, and the 2.14 line continues (v2.14.13, commit of 2026-11-02). | apk-tools 3.0.10, 2.14.13 | apk-tools tags (GitLab API) | 2026-11-21 |
| APK-08c | The Alpine 3.24 main repository for x86_64 serves apk-tools-3.0.9-r0, packages as .apk files and the index as APKINDEX.tar.gz, and contains no .adb file. | Alpine 3.24, apk-tools 3.0.9-r0 | dl-cdn v3.24/main/x86_64 | 2026-11-21 |
| APK-08d | A repository line in apk-repositories(5) defaults to the v2 type, can be declared v3, and a v3 repository requires a v3 format index file; apk-v3(5) describes the v3 package format as “adb”. | apk-tools 3.0.x | apk-repositories(5), apk-v3(5) | 2026-11-21 |
| APK-MAP-a | setup-alpine reads an answer file with -f (a local path or an HTTP(S) or FTP URL) and writes an example answer file with -c. | alpine-conf 3.22.0 | alpine-conf setup-alpine.in | 2026-11-21 |
| APK-MAP-b | mkimg.base.sh computes the package closure of the profile variable apks with apk fetch –simulate –recursive, and the base profile sets kernel_flavors=“lts”. | aports master, Alpine 3.24 | aports scripts/mkimg.base.sh | 2026-11-21 |
| APK-MAP-c | apk-package(5) lists the package script types trigger, pre-install, post-install, pre-deinstall, post-deinstall, pre-upgrade and post-upgrade. | apk-tools 3.0.x | apk-package(5) | 2026-11-21 |
| APK-MAP-d | The v3.24 main APKINDEX.tar.gz begins with a signature entry named .SIGN.RSA.alpine-devel@lists.alpinelinux.org-6165ee59.rsa.pub, and a v2 package carries its signature as the first .SIGN. |
Alpine 3.24; apk-tools 3.0.x | v3.24 main APKINDEX.tar.gz, apk-v2(5) | 2026-11-21 |
4.4 FreeBSD
Versions checked: FreeBSD 15.1-RELEASE (2026-06-16, production release per freebsd.org/releases; EOL 2027-03-31); 14.5-RELEASE (2026-09-08) and 14.4-RELEASE (2026-03-10); releng/15.2 exists in the source tree but 15.2 is listed as upcoming; pkg 2.9.3 (2026-11-17). Manual pages are the 15.1-RELEASE or Ports versions of man.freebsd.org (release(7) dated 2025-10-13, bsdinstall(8) 2026-05-12, freebsd-base(7) 2026-04-23, bectl(8) 2026-02-04, poudriere-image(8) 2025-12-12).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| FBS-01a | release.sh, the documented wrapper for clean release builds, reads an optional release.conf (release.sh -c release.conf), runs make buildworld and make installworld to create a chroot, and runs make release inside it with the result in $CHROOTDIR/R. | FreeBSD 15.1 | release(7) | 2026-11-21 |
| FBS-01b | The release makefile targets produce installation media (cdrom: disc1.iso and bootonly.iso; memstick: memstick.img), virtual machine disk images (vm-image: vhdf, vmdk, qcow2 and raw, enabled by WITH_VMIMAGES) and cloud images (vm-cloudware, enabled by WITH_CLOUDWARE). | FreeBSD 15.1 | release(7) | 2026-11-21 |
| FBS-02a | poudriere bulk builds binary packages from a list of ports in poudriere-managed jails and produces a ready-to-export package tree, i.e. a private package repository. | poudriere (FreeBSD 15.1 man pages, 2025-11/12) | poudriere-bulk(8), poudriere(8) | 2026-11-21 |
| FBS-02b | poudriere image builds OS filesystem images from a jail and a package list (-f), with image types such as iso, usb, rawdisk, zfs, tar and firmware, and its manual page marks the feature ALPHA. | poudriere-image(8) of 2025-12-12 | poudriere-image(8) | 2026-11-21 |
| FBS-02c | poudriere image takes an overlay directory copied into the image (-c), a pre-script (-B) and a post-script (-A), and poudriere bulk takes extra ports trees as overlays (-O). | poudriere man pages 2025-11/12 | poudriere-image(8), poudriere-bulk(8) | 2026-11-21 |
| FBS-03a | nanobsd.sh creates embedded FreeBSD system images that run read-only, laid out with two image partitions (code#1 and code#2) and a configuration partition mounted under /cfg. | FreeBSD 15.1 | nanobsd(8) | 2026-11-21 |
| FBS-03b | The NanoBSD tree ships the scripts updatep1 and updatep2, which write a new image into partition 1 or 2 and mark it active with gpart, and refuse to overwrite the partition that is running. | releng/15.1 | src tools/tools/nanobsd/Files/root/updatep1 | 2026-11-21 |
| FBS-04 | bsdinstall(8) runs a script (a preamble of installer variables such as PARTITIONS, ZFSBOOT_DISKS or COMPONENTS followed by a sh(1) setup script) placed at /etc/installerconfig on release media at boot time, and reboots automatically when the installation has completed. | FreeBSD 15.1 | bsdinstall(8) | 2026-11-21 |
| FBS-05a | The src.conf(5) pages of FreeBSD 14.1, 14.2, 14.3, 14.4, 14.5, 15.0 and 15.1 list the option WITHOUT_REPRODUCIBLE_BUILD (“Include build metadata (such as the build time, user, and host) in the kernel, boot loaders, and uname output”), so that this metadata is excluded by default. | FreeBSD 14.1 to 15.1 | src.conf(5), 15.1 | 2026-11-21 |
| FBS-05b | The src.conf(5) page of FreeBSD 14.0 lists the opposite form WITH_REPRODUCIBLE_BUILD (“Exclude build metadata … so that builds produce bit-for-bit identical output”), i.e. the option is off by default in 14.0. | FreeBSD 14.0 | src.conf(5), 14.0 | 2026-11-21 |
| FBS-05c | Makefile.inc1 documents -DNO_ROOT as “install without using root privilege” and METALOG as the file that records permissions and ownership when NO_ROOT is set (default ${DESTDIR}/${DISTDIR}/METALOG); it forces NO_ROOT mode for the distributeworld, packageworld, distributekernel and packagekernel targets. | releng/15.1 | src Makefile.inc1 | 2026-11-21 |
| FBS-05d | release.sh exits with “Needs to be run as root.” when it is not started as uid 0, and passes NO_ROOT=1 to make release inside the build chroot. | releng/15.1 | src release/release.sh | 2026-11-21 |
| FBS-06 | bectl(8) manages bootable ZFS clones called boot environments, which are selectable directly from the boot loader so that system changes can be tested and abandoned; its subcommands include create, activate (also temporary, -t), list, mount and destroy. | FreeBSD 15.1 | bectl(8) | 2026-11-21 |
| FBS-07a | The FreeBSD 15.0 announcement presents installing and managing the base system with pkg(8) as new in 15.0 and states that pkgbase is offered as a technology preview. | FreeBSD 15.0 (2025-12) | FreeBSD 15.0-RELEASE announcement | 2026-11-21 |
| FBS-07b | The FreeBSD 15.1 release notes call systems installed with base system packages (pkgbase) “supported in FreeBSD 15.0 and later” and state that the bsdinstall script target now installs pkgbase by default (components chosen with COMPONENTS), while distribution-set installation remains when DISTRIBUTIONS is defined. | FreeBSD 15.1 | FreeBSD 15.1-RELEASE release notes | 2026-11-21 |
| FBS-07c | The FreeBSD wiki page PkgBase, last edited 2026-09-10, says official packages have been published since October 2023 and that use of pkgbase remains somewhat experimental. The three statuses differ by source and date: FBS-07a is the 15.0 announcement (December 2025), FBS-07b the 15.1 release notes (2026-06-16, the statement of the release itself) and this edit of 2026-09-10 the newest of the three; the dossier does not reconcile them. | wiki edit of 2026-09-10 | FreeBSD wiki, PkgBase | 2026-11-21 |
| FBS-07d | freebsd-base(7) states that support for installing the base system as packages was introduced in FreeBSD 15.0, with packages for all supported releases hosted at pkg.freebsd.org and updated for errata and security updates. | FreeBSD 15.1 | freebsd-base(7) | 2026-11-21 |
| FBS-08a | The task list on the FreeBSD wiki page SecureBoot (last edited 2025-05-21, category Stale) shows “Acquire FreeBSD signing key” as “Not started”. | wiki edit of 2025-05-21 | FreeBSD wiki, SecureBoot | 2026-11-21 |
| FBS-08b | uefisign(8) in FreeBSD 15.1 signs PE binaries with the Authenticode scheme required by UEFI Secure Boot, and its example signs a binary with a self-generated certificate and key. | FreeBSD 15.1 | uefisign(8) | 2026-11-21 |
| FBS-08c | The FreeBSD Foundation guide to UEFI Secure Boot says the loader cannot yet verify the kernel (“Currently there is no support for these verifications”) and describes combining loader and kernel into one self-signed EFI object; the page carries no date. | page undated, read 2026-11-21 | FreeBSD Foundation, FreeBSD UEFI Secure Boot | 2026-11-21 |
| FBS-08d | The FreeBSD 15.1 release notes and the loader.efi(8) and uefi(8) manual pages of 15.1 do not mention UEFI Secure Boot support or a Microsoft-signed shim. | FreeBSD 15.1 | absence: not stated by the project; checked the 15.1 release notes and loader.efi(8) on 2026-11-21 | 2026-11-21 |
| FBS-09a | The freebsd-update script exits with “freebsd-update is incompatible with the use of packaged base” when pkg reports that /usr/bin/uname comes from a package. | releng/15.1 | src usr.sbin/freebsd-update/freebsd-update.sh | 2026-11-21 |
| FBS-09b | Per the 15.0 announcement, systems installed from distribution sets continue to use freebsd-update(8), while systems installed with the packaged base are managed entirely with pkg(8). | FreeBSD 15.0 | FreeBSD 15.0-RELEASE announcement | 2026-11-21 |
| FBS-10a | freebsd-update creates a boot environment with bectl before installing updates by default (config option CreateBootEnv, default yes, when bectl check reports boot environment support). | releng/15.1 | src freebsd-update.sh | 2026-11-21 |
| FBS-10b | freebsd-base(7) gives pkg upgrade -r FreeBSD-base as the update of the running system and describes no boot environment step. | FreeBSD 15.1 | absence: not stated by the project; checked freebsd-base(7) on 2026-11-21 | 2026-11-21 |
| FBS-10c | The Handbook upgrade section for base packages on ZFS has the administrator create the boot environment by hand (“Create a boot environment using bectl(8)”) before a major upgrade, and notes the pkgbasify conversion tool creates a backup boot environment. | Handbook, read 2026-11-21 | FreeBSD Handbook, Updating and Upgrading | 2026-11-21 |
| FBS-10d | The source of pkg 2.9.3 and the pkg(8) and pkg.conf(5) manual pages contain no reference to boot environments, bectl or libbe. | pkg 2.9.3 | absence: not stated by the project; checked the pkg 2.9.3 source archive and pkg.conf(5) on 2026-11-21 | 2026-11-21 |
| FBS-11a | pkg.conf(5) sets the signature type of a repository with signature_type, which takes NONE (default), PUBKEY (a public key file, for the built-in signing support) or FINGERPRINTS (a directory with trusted and revoked fingerprint files, for an external signing command). | pkg 2.9.3 | pkg.conf(5) | 2026-11-21 |
| FBS-11b | The FreeBSD-base repository example in pkg.conf(5) uses signature_type “fingerprints” with fingerprints “/usr/share/keys/pkg”. | pkg 2.9.3 | pkg.conf(5) | 2026-11-21 |
| FBS-MAP-a | pkg.freebsd.org serves, per ABI such as FreeBSD:15:amd64, the repository branches latest, quarterly, release_0 and release_1, and for the base system base_latest, base_weekly, base_release_0 and base_release_1. | listing of 2026-11-21 | pkg.freebsd.org FreeBSD:15:amd64 | 2026-11-21 |
| FBS-MAP-b | On UEFI systems loader.efi loads the kernel, and bsdinstall installs it on the EFI System Partition. | FreeBSD 15.1 | loader.efi(8) | 2026-11-21 |
| FBS-MAP-c | pkg install examines the dependencies of the packages named, adds missing packages to the work list and sorts it into dependency order, and with -n (dry-run mode) prints the list of changes without making any; pkg fetch with -d fetches a package and its dependencies. | pkg 2.9.3 (man pages of FreeBSD 15.1 and Ports.quarterly) | pkg-install(8); pkg-fetch(8) | 2026-11-21 |
4.5 OpenBSD
Versions checked: OpenBSD 8.0 (released 2026-10-20, the 61st release, per openbsd.org). Manual pages are the OpenBSD-8.0 collection of man.openbsd.org; release(8) is dated 2026-08-25.
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| OBS-01a | release(8) lists the build steps in order: update sources, build and install a new kernel, build a new base system, make and validate the base system release, build and install Xenocara, make and validate the Xenocara release, create boot and installation disk images, make the third-party packages; it says to build and install a new kernel and reboot before building the programs that use it. | OpenBSD 8.0 | release(8) | 2026-11-21 |
| OBS-01b | release(8) describes the base system release as at least one generic kernel, installation media, the release tarballs, installation instructions and checksum files, and the disk images install${VERSION}.img and install${VERSION}.iso as containing the built tarballs. | OpenBSD 8.0 | release(8) | 2026-11-21 |
| OBS-01c | The amd64 directory of the 8.0 release holds the tarballs base80, comp80, game80, man80, xbase80, xfont80, xserv80 and xshare80 (.tgz), the images install80.img, install80.iso, miniroot80.img, cd80.iso and floppy80.img, the kernels bsd, bsd.mp and bsd.rd, and SHA256 and SHA256.sig. | OpenBSD 8.0 | pub/OpenBSD/8.0/amd64 | 2026-11-21 |
| OBS-02a | The install and upgrade scripts accept a user-created set site80.tgz (and hostname-specific site80-$(hostname -s).tgz), a tar archive rooted in / and untarred with -xzphf that “is installed last”, so it can complement and modify the files of a default install. | OpenBSD 8.0 | OpenBSD FAQ 4, Customizing the Install Process | 2026-11-21 |
| OBS-02b | If they exist and are executable, /install.site and /upgrade.site are run at the end of the install and upgrade respectively, with chroot(8) based at the system’s root. | OpenBSD 8.0 | install.site(5) | 2026-11-21 |
| OBS-03a | autoinstall(8) performs unattended installation or upgrade by answering installer questions from a line-oriented response file (install.conf, MAC_address-install.conf or hostname-install.conf), fetched over HTTP from the location given by DHCP. | OpenBSD 8.0 | autoinstall(8) | 2026-11-21 |
| OBS-03b | autoinstall(8) uses /auto_install.conf or /auto_upgrade.conf from the RAM disk of bsd.rd when present, and the response file can carry a URL of a disklabel(8) autopartitioning template. | OpenBSD 8.0 | autoinstall(8) | 2026-11-21 |
| OBS-04a | The stack protector is enabled systemwide by default since OpenBSD 3.3, and each shared object gets its own stack protector cookie since 5.3. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04b | W^X is strictly enforced by default since OpenBSD 6.0 (first used on sparc, sparc64, alpha and hppa in 3.3): a program violates it only if its executable is marked PT_OPENBSD_WXNEEDED and sits on a filesystem mounted wxallowed. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04c | ASLR is provided by default since OpenBSD 3.4; position-independent executables are enabled globally by default since 5.3; position-independent static binaries for /bin, /sbin and ramdisks were implemented for 5.7. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04d | The malloc(3) implementation of OpenBSD 4.4 randomizes allocations and adds guard pages and randomized (delayed) free. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04e | The sigreturn-oriented programming (SROP) mitigation is enabled by default since OpenBSD 6.0, and the start-up relinking of libc.so, libcrypto and ld.so in random order is enabled by default since 6.0 and 6.2. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04f | RETGUARD, a per-function return-address cookie that replaces the stack protector, is implemented for amd64 and arm64 in OpenBSD 6.4, for mips64 in 6.7 and for powerpc and powerpc64 in 6.9, and amd64 system call stubs are protected in 7.3. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04g | The kernel is relinked from its object files in random order before every reboot (kernel relinking, June 2017); the page names the date, not a release number. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04h | Permissions of address-space regions can be made immutable (mimmutable(2)), most of a program’s static address space is immutable automatically (Dec 4, 2022), and the linker option –execute-only is enabled by default (Dec 2022 to Feb 2023, on several architectures); the page names dates, not release numbers. | OpenBSD 8.0 documentation | OpenBSD innovations | 2026-11-21 |
| OBS-04i | OpenBSD 7.5 replaces pinsyscall(2) with pinsyscalls(2): the kernel matches each system call number to the specific address it must come from. | OpenBSD 7.5 | OpenBSD 7.5 changes | 2026-11-21 |
| OBS-04j | OpenBSD 7.4 enables Indirect Branch Tracking for amd64 userland at exec time unless the PS_NOBTCFI flag is set. | OpenBSD 7.4 | OpenBSD 7.4 changes | 2026-11-21 |
| OBS-05a | A release directory carries SHA256 and SHA256.sig; signify -C -p /etc/signify/openbsd-80-base.pub -x SHA256.sig verifies the signature of the checksum list and then the checksum of each file. | OpenBSD 8.0 | OpenBSD FAQ 4, Downloading, signify(1) | 2026-11-21 |
| OBS-05b | OpenBSD releases ship the current signify key, the next key and a collection of older keys in /etc/signify, so sysupgrade(8) finds the keys of the next release already installed. | OpenBSD 8.0 | sysupgrade(8) | 2026-11-21 |
| OBS-05c | The source tree directory etc/signify holds per-release public keys named openbsd-NN-base.pub, openbsd-NN-fw.pub, openbsd-NN-pkg.pub and openbsd-NN-syspatch.pub, including openbsd-80-* and openbsd-81-*. |
OpenBSD master (-current), 2026-11-21 | openbsd/src etc/signify | 2026-11-21 |
| OBS-05d | syspatch(8) fetches, verifies, installs and reverts binary patches and refers to signify(1); the signify paper states that pkg_add verifies every package with signify and describes a key rotation that generates keys for the release after next. | syspatch(8) 8.0; paper of 2015 | syspatch(8), signify paper (BSDCan 2015) | 2026-11-21 |
| OBS-06a | The files listed in OBS-01c (the sets, the installer images, the kernels bsd, bsd.mp and bsd.rd, and the checksum file SHA256 with its signature SHA256.sig) are the release artefacts of OpenBSD 8.0/amd64. | OpenBSD 8.0 | pub/OpenBSD/8.0/amd64 | 2026-11-21 |
| OBS-06b | The signature file SHA256.sig of OpenBSD 8.0/amd64 starts with the comment “untrusted comment: verify with openbsd-80-base.pub” and is the signature over the SHA256 checksum list of the directory. | OpenBSD 8.0 | 8.0/amd64/SHA256.sig | 2026-11-21 |
| OBS-06c | install80.iso and install80.img contain no SHA256.sig, so the installer asks whether to continue without verification, and the image itself is verified beforehand with the signed SHA256.sig of the mirror. | OpenBSD 8.0 | OpenBSD FAQ 4, Downloading | 2026-11-21 |
| OBS-07 | No OpenBSD FAQ page (14 pages checked: current, 1, 4, 5, 6, 7, 10, 11, 13, 14, 15, 16, 17 and upgrade80) and no text of release(8) for 8.0 contains the word “reproducible”, and the project documents no reproducible-build procedure. | OpenBSD 8.0 | absence: not stated by the project; checked the OpenBSD FAQ index pages and release(8) on 2026-11-21 | 2026-11-21 |
| OBS-08a | syspatch(8) is “designed to work solely on official OpenBSD releases”. | OpenBSD 8.0 | syspatch(8) | 2026-11-21 |
| OBS-08b | The syspatch script runs only on a release (it stops with “Unsupported release” on -current or -stable version strings) and switches between the GENERIC and GENERIC.MP relink data according to kern.osversion. | OpenBSD master (-current) syspatch.sh, file read 2026-11-21 | openbsd/src usr.sbin/syspatch/syspatch.sh | 2026-11-21 |
| OBS-08c | FAQ 10 states that syspatch(8) upgrades files in need of security or reliability fixes on a supported release and that binary patches are available on amd64, arm64 and i386. | OpenBSD 8.0 | OpenBSD FAQ 10, Security Updates | 2026-11-21 |
| OBS-09 | “Only the GENERIC and GENERIC.MP kernels are supported by the OpenBSD team.” | OpenBSD 8.0 | OpenBSD FAQ 5, Building a Custom Kernel | 2026-11-21 |
| OBS-10a | In release(8) commands that must be run as the superuser are marked with a hash (steps include make config and make install of the kernel, make build and make release), and privileges are de-escalated to the user build whenever possible. | OpenBSD 8.0 | release(8) | 2026-11-21 |
| OBS-10b | FAQ 5 says a release needs a filesystem mounted with the noperm option so that the build infrastructure can use the unprivileged build user for much of the process. | OpenBSD 8.0 | OpenBSD FAQ 5, Building a release | 2026-11-21 |
| OBS-MAP-a | release(8) names two families of CVS tags: OPENBSD_x_y_BASE for the sources of the x.y release and OPENBSD_x_y for the x.y stable branch. | OpenBSD 8.0 | release(8) | 2026-11-21 |
4.6 NetBSD
Versions checked: NetBSD 11.1 (announced 2026-11-02; first point release of the 11 stable branch; NetBSD 10.2 is the other supported series). Manual pages are the NetBSD-11.1 collection of man.netbsd.org; BUILDING is the file of the netbsd-11 branch (man page date 2023-07-21).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| NBS-01a | NetBSD is designed to be buildable on most POSIX-compliant host systems, and the build.sh script in the source tree supports both native and cross builds. | netbsd-11 branch (NetBSD 11.1) | src BUILDING | 2026-11-21 |
| NBS-01b | build.sh -U sets MKUNPRIVED=yes, under which user, group, permissions and file flags are not set on installed items but appended to a file METALOG in DESTDIR, which the set tarball generation uses so that the right ownership is stored; this allows a non-root make install. | NetBSD 11.1 | mk.conf(5), src BUILDING | 2026-11-21 |
| NBS-01c | BUILDING describes the build.sh targets release, iso-image (installation CD-ROM image), install-image (bootable installation disk image for USB sticks) and live-image (bootable disk image for virtual machines or USB), and says install-image and live-image need a build with MKUNPRIVED=yes because they use DESTDIR/METALOG. | netbsd-11 branch (NetBSD 11.1) | src BUILDING | 2026-11-21 |
| NBS-02a | mk.conf(5) documents MKREPRO (default no): with yes, two builds from the same source tree produce the same build results, and MKREPRO_TIMESTAMP sets the timestamp of all files in the sets. | NetBSD 11.1 | mk.conf(5) | 2026-11-21 |
| NBS-02b | build.sh -P sets MKREPRO and MKREPRO_TIMESTAMP to the latest source CVS timestamp for reproducible builds, and -V var=[value] passes an environment variable such as MKREPRO=yes to the build. | netbsd-11 branch (NetBSD 11.1) | src BUILDING | 2026-11-21 |
| NBS-03a | sysinst(8) is a menu-based program to install or upgrade NetBSD, and its -f definition_file option sets defaults such as fetch locations (ftp host and dir, nfs host and dir), devices (cd dev, local dev) and the disktab diskname. | NetBSD 11.1 | sysinst(8) | 2026-11-21 |
| NBS-03b | BUILDING states that the iso-image and install-image media automatically run the sysinst(8) menu-based installation program, and describes live-image as a disk image that boots to multi-user mode without installation. | netbsd-11 branch (NetBSD 11.1) | src BUILDING | 2026-11-21 |
| NBS-03c | The strings “unattended”, “autoinstall” and “automated install” do not occur in the NetBSD 11.0 and 11.1 CHANGES files, in sysinst(8) or in BUILDING. | NetBSD 11.0 and 11.1 | absence: not stated by the project; checked CHANGES-11.0, sysinst(8) on 2026-11-21 | 2026-11-21 |
| NBS-04a | pkg_install.conf(5) sets VERIFIED_INSTALLATION to one of never, always, trusted or interactive with the default never (“Install package unconditionally”), and always requires a valid X.509 or OpenPGP signature. | NetBSD 11.1 | pkg_install.conf(5) | 2026-11-21 |
| NBS-04b | pkg_admin(1) has the subcommand gpg-sign-package, which signs a binary package with GPG. | NetBSD 11.1 | pkg_admin(1) | 2026-11-21 |
| NBS-05a | The release directories of NetBSD 11.1 carry digest files MD5 and SHA512 (for example amd64/binary/sets), and the release announcement links one list of hashes for the whole distribution that is signed with the NetBSD Security Officer’s PGP key. | NetBSD 11.1 | NetBSD 11.1 announcement, amd64/binary/sets listing | 2026-11-21 |
| NBS-05b | The file NetBSD-11.1_hashes.asc is a PGP clear-signed message (“BEGIN PGP SIGNED MESSAGE”, hash SHA512) listing all distribution files of NetBSD-11.1; the MD5 and SHA512 files inside the release directories have no .asc file next to them in the listings checked. | NetBSD 11.1 | NetBSD-11.1_hashes.asc | 2026-11-21 |
| NBS-MAP-a | The embedded image script distrib/utils/embedded/mkimage calls host-specific functions make_fstab, customize (after unpacking the sets), populate and make_label, takes a custom files directory with -c, and builds the image with the tools makefs and mtree from the unpacked sets. | netbsd-11 branch | src distrib/utils/embedded/mkimage | 2026-11-21 |
| NBS-MAP-b | The release directory NetBSD-11.1/amd64/binary holds the subdirectories kernel (netbsd-GENERIC.gz, netbsd-INSTALL.gz and others) and sets (base.tar.xz, comp.tar.xz and others), each with its own MD5 and SHA512 files. | NetBSD 11.1 | amd64/binary/sets listing, amd64/binary/kernel listing | 2026-11-21 |
4.7 Other Unix
DragonFly BSD, illumos distributions, Haiku and Darwin.
Versions checked:
- DragonFly BSD 6.4.2, released 2025-05-09 (release page; download page still serves 6.4.2; master is 6.5-DEVELOPMENT, no 6.5 or 6.6 release found on the project site or the users list through 2026-11-17).
- OpenIndiana Hipster snapshot 2026.10, announced 2026-11-07 (openindiana.org announcements); OmniOS r151060, released 2026-11-02 (omnios.org news); illumos-gate has no numbered releases,
beadm(8)page dated 2023-03-10; IPS = OpenIndianapkg5branchoi(last push 2026-11-16), IPS developer guide PDF built 2019-05-22. - Haiku R1/beta6, released 2026-08-26.
- Apple: macOS Tahoe 26 Software License Agreement (document EA1955, PDF last modified 2025-09-09); Apple Public Source License 2.0 (dated August 6, 2003); latest open-source drop
macos-265(macOS 26.5, tagged 2026-06-17, kernel tagxnu-12377.121.6).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| OTH-01a | DragonFly BSD builds its live release (ISO image) with make release run from src/nrelease, a directory of the main git source tree documented in nrelease(7); the target builds world and kernel, installs them, adds packages and prepares the ISO image. |
DragonFly 6.4.2 (man page on master, 6.5-DEVELOPMENT) | nrelease(7), DragonFly On-Line Manual Pages | 2026-11-21 |
| OTH-01b | HAMMER2 provides snapshots: hammer2 snapshot path [label] creates a snapshot of a directory (a PFS), and the project describes snapshots as instant and mounted snapshots as writable. |
DragonFly 6.4.2; hammer2(8) footer 6.5-DEVELOPMENT | hammer2(8), DragonFly On-Line Manual Pages and HAMMER page, dragonflybsd.org | 2026-11-21 |
| OTH-01c | The DPorts overlay for the sysutils/beadm port (the ZFS boot-environment tool) sets IGNORE with the reason “DragonFly has no ZFS support”. |
DPorts master (DragonFly 6.4.2 and 6.5 package sets, 2026Q4) | DeltaPorts ports/sysutils/beadm/overlay.dops | 2026-11-21 |
| OTH-01d | A boot-environment tool for DragonFly, dfbeadm(8), was announced on the users list on 2019-08-21 as a separate project in “v0.1.0-BETA” form that snapshots every mounted HAMMER2 filesystem; the user still edits vfs.root.mountfrom in loader.conf(5) by hand. |
dfbeadm v0.1.0-BETA (2019-08-21); not part of DragonFly 6.4.2 | Introducing dfbeadm(8), Ready for Testing (users list, 2019-08-21) | 2026-11-21 |
| OTH-02a | OpenIndiana builds its installation images (ISO and USB) with the distribution constructor: distro_const build <manifest>.xml, where the XML manifest lists packages and publishers, for example /usr/share/distro_const/slim_cd/slim_cd_x86.xml (desktop) and text_install/text_mode_x86.xml (server). |
OpenIndiana Hipster 2026.10 (documentation page last updated 2023-09-03) | Using distribution constructor, OpenIndiana Docs | 2026-11-21 |
| OTH-02b | OmniOS builds its install media with the separate kayak project: gmake ... install-iso builds the ISO and install-usb builds a .usb-dd image from it. |
OmniOS r151060 (kayak master) | omniosorg/kayak README | 2026-11-21 |
| OTH-02c | An IPS manifest carries signature actions: a signature value over the manifest plus a chain of X.509 certificates (PEM files) that leads to a trust anchor set in the publisher configuration. |
IPS (pkg5 oi; guide built 2019-05-22) |
Packaging and Delivering Software with IPS, chapter 11 Signing Packages (PDF) | 2026-11-21 |
| OTH-02d | pkgsign(1) adds a signature action to the manifests of the given FMRIs in a repository using a private key and certificate (-k, -c, intermediate certificates -i); the default algorithm is rsa-sha256. |
pkg5 oi (man page dated 21 May 2013) |
pkgsign(1), OpenIndiana/pkg5 | 2026-11-21 |
| OTH-02e | pkg install and update commands take --require-new-be, --deny-new-be and --be-name, and the image property be-policy (values default, always-new, create-backup) sets when a boot environment is created during packaging operations. |
pkg5 oi (pkg(1) dated 24 Jun 2019) |
pkg(1), OpenIndiana/pkg5 | 2026-11-21 |
| OTH-02f | beadm(8) in illumos manages ZFS boot environments: create, activate (also one-time with -t), list, mount, unmount, rename, destroy and rollback. |
illumos-gate man page dated March 10, 2023 | beadm(8), illumos manual pages | 2026-11-21 |
| OTH-03a | The IPS design removes scripting from packaging operations: the developer guide states that scripting is inherently unverifiable and that software self-assembly eliminates the need for install-time scripting, with actions replacing the former SVR4 class-action scripts. | IPS (pkg5 oi; guide built 2019-05-22) |
Packaging and Delivering Software with IPS, chapter 1 and Software Self-Assembly (PDF) | 2026-11-21 |
| OTH-03b | pkg(7) documents the action types file, dir, link, hardlink, driver, depend, license, legacy, set, group and user, and the actuators reboot-needed, disable_fmri, refresh_fmri, restart_fmri and suspend_fmri; the service actuators disable, refresh, restart or suspend an SMF service instance around the install of the tagged action. |
pkg5 oi (pkg(7)) |
pkg(7), OpenIndiana/pkg5 | 2026-11-21 |
| OTH-04a | Haiku builds with its own fork of Jam (“Jam 2.5-haiku-20111222”); jam -q @nightly-anyboot produces an anyboot ISO, jam -q @nightly-raw a raw image haiku.image, and the haiku-image Jam target is what @nightly-raw stands for. |
Haiku master, checked 2026-11-21 (release R1/beta6) | ReadMe.Compiling.md and UserBuildConfig.ReadMe | 2026-11-21 |
| OTH-04b | Haiku packages are compressed filesystem images that packagefs, a kernel component, mounts at install and on each boot; the /system hierarchy is read-only because it is an amalgamation of the installed packages. |
Haiku R1/beta1 text; packagefs is still named in R1/beta6 | R1/beta1 Release Notes, Package Manager and R1/beta6 Release Notes | 2026-11-21 |
| OTH-04c | Haiku’s package manager presents installed packages as a read-only filesystem, so a packaged file cannot be deleted or renamed in place; entries are hidden through BlockedEntries in a packages settings file. |
Haiku site guide, current at 2026-11-21 (R1/beta6) | Disabling components of packages, Haiku guides | 2026-11-21 |
| OTH-05a | Apple publishes the source of the open-source Darwin components, including the XNU kernel, under the Apple Public Source License (APSL) Version 2.0, dated August 6, 2003. | APSL 2.0; xnu-12377.121.6 (macOS 26.5 drop macos-265, 2026-06-17) |
Apple Public Source License 2.0, opensource.apple.com and xnu APPLE_LICENSE at tag xnu-12377.121.6 | 2026-11-21 |
| OTH-05b | APSL 2.0 section 2.2 grants the right to modify Covered Code and to use, reproduce, display, perform, distribute internally and Externally Deploy the modifications, for commercial or non-commercial purposes, on condition that source of externally deployed modifications is made available under the same licence (2.2(c)). | APSL 2.0 | xnu APPLE_LICENSE, section 2 | 2026-11-21 |
| OTH-05c | The xnu README documents building the kernel with make SDKROOT=<path to macOS SDK> ARCH_CONFIGS=<arch> KERNEL_CONFIGS=<variant> and states that the build also creates a bootable kernel image. |
xnu-12377.121.6 | xnu README.md | 2026-11-21 |
| OTH-05d | Section 2.M of the macOS Tahoe 26 licence allows the licensee to modify or replace only the Open-Sourced Components, provided the resulting modified Apple Software is used in place of the unmodified software on Apple-branded computers the licensee owns or controls. | macOS Tahoe 26 SLA, EA1955 | Software License Agreement for macOS Tahoe 26, section 2.M (PDF) | 2026-11-21 |
| OTH-05e | Section 2.J of the same licence excludes installing or running the Apple Software on non-Apple-branded computers and, except as expressly permitted in section 3, excludes renting, leasing, lending, selling, redistributing or sublicensing it. | macOS Tahoe 26 SLA, EA1955 | Software License Agreement for macOS Tahoe 26, section 2.J (PDF) | 2026-11-21 |
| OTH-05f | Section 4.B of the same licence states that Apple Software modified or replaced under section 2.M may not be transferred, and that its components are provided as a bundle that may not be separated and distributed as standalone applications. | macOS Tahoe 26 SLA, EA1955 | Software License Agreement for macOS Tahoe 26, section 4.B (PDF) | 2026-11-21 |
| OTH-05g | Section 2.N of the same licence excludes reverse engineering, decompiling and creating derivative works of the Apple Software, except to the extent prohibited by law or by the licensing terms of the Open-Sourced Components. | macOS Tahoe 26 SLA, EA1955 | Software License Agreement for macOS Tahoe 26, section 2.N (PDF) | 2026-11-21 |
| OTH-05h | The apple-oss-distributions/distribution-macOS repository carries tag macos-265 (annotated tag dated 2026-06-17) whose release.json lists project xnu at tag xnu-12377.121.6. |
macOS 26.5 source drop | apple-oss-distributions/distribution-macOS, tag macos-265 | 2026-11-21 |
| MAP-ILL-01 | A full IPS FMRI is pkg://<publisher>/<name>@<version>:<timestamp>, and the timestamp is the time the package was published. |
pkg5 oi (pkg(7)) |
pkg(7), PACKAGE FMRIS AND VERSIONS | 2026-11-21 |
| MAP-ILL-02 | pkg freeze records a version constraint chosen by the administrator, and incorporations deliver incorporate dependencies that bound package versions. |
pkg5 oi (pkg(1), pkg(7)) |
pkg(7), CONSTRAINTS AND FREEZING | 2026-11-21 |
| MAP-ILL-03 | IPS updates boot blocks and prepares the boot archive (ramdisk) itself when a package operation needs it. | IPS (guide built 2019-05-22) | Packaging and Delivering Software with IPS, Software Self-Assembly (PDF) | 2026-11-21 |
| MAP-ILL-04 | The client side of pkg5 contains a solver module (pkg_solver.py) that the planner uses to compute the end state of a package operation. |
pkg5 oi branch, 2026-11-16 |
src/modules/client/pkg_solver.py, OpenIndiana/pkg5 | 2026-11-21 |
| MAP-ILL-05 | The constructor manifest accepts an additional publisher for image construction (pkg_repo_addl_authority) and another for the installed system (post_install_repo_addl_authority), and controls installer behaviour. |
OpenIndiana Hipster 2026.10 | Using distribution constructor, OpenIndiana Docs | 2026-11-21 |
4.8 Source-based and image-first Linux
Gentoo, Nix, Guix, Yocto, Buildroot and Arch Linux.
Versions checked:
- Gentoo catalyst 4.2.0 (
catalyst/version.pyon gitweb.gentoo.org, last commit 2026-11-01; dev-util/catalyst 4.2.0 is keyworded~archin the Gentoo package database); RelEng amd64 23.0-profile specs. - Nix 2.36.0 (release notes dated 2026-11-16, tag 2026-11-18); NixOS 26.05 (manual and download page at 2026-11-21).
- GNU Guix 1.5.0, released 2026-01-23.
- Yocto Project 6.1 “blacksail”, released September 2026 (6.1.0; stable until April 2027); 6.0 “wrynose” is the long-term-support series (6.0.4, September 2026, support until April 2030).
- Buildroot 2026.08.2 (news 2026-11-16; manual of the 2026.08 series generated 2026-09-04); 2026.11-rc1 on 2026-11-14; long-term series 2025.02.20.
- Arch Linux: rolling; current ISO 2026.11.01 (kernel 7.2.11).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| SBL-01a | catalyst --snapshot <git-treeish> builds a squashfs snapshot of the Gentoo ebuild repository from the given git treeish (the value is passed to git archive), and spec files select that snapshot with snapshot_treeish. |
catalyst 4.2.0 | catalyst/main.py and catalyst/targets/snapshot.py | 2026-11-21 |
| SBL-01b | The Gentoo wiki’s catalyst example sets snapshot_treeish to a 40-character commit hash (e7b9afdd137f25a545a1f56ce1ca4c1d7be16160) in a stage1 spec. |
catalyst 4.2.0 page, Gentoo Wiki | Catalyst, Gentoo Wiki | 2026-11-21 |
| SBL-01c | In the RelEng amd64 23.0 specs the stage1 spec uses the previous stage3 as seed (source_subpath: 23.0-default/stage3-amd64-openrc-latest, update_seed: yes), and the stage3 spec takes the new stage1 as source (source_subpath: 23.0-default/stage1-amd64-openrc-@TIMESTAMP@). |
RelEng 23.0 specs, catalyst 4.2.0 | stage1-openrc-23.spec and stage3-openrc-23.spec | 2026-11-21 |
| SBL-01d | catalyst 4.2.0 keeps a stage2 target (“builds upon previous stage1 tarball”); the RelEng amd64 spec directory lists stage1, stage3, stage3d and stage4w specs for the 23.0 profile and no plain stage2 spec. |
catalyst 4.2.0; RelEng amd64 specs at 2026-11-21 | catalyst/targets/stage2.py and releases/specs/amd64 | 2026-11-21 |
| SBL-02a | Nix writes a lock file flake.lock (UTF-8 JSON) next to flake.nix; it holds a graph of the flake inputs with exact revisions (rev, narHash) so that the inputs are reproducible. |
Nix 2.36.0 | nix flake, Lock files, Nix 2.36.0 Reference Manual | 2026-11-21 |
| SBL-02b | The Nix 2.36.0 manual marks the nix flake command as experimental (“This program is experimental and its interface is subject to change”). |
Nix 2.36.0 | nix flake, Nix 2.36.0 Reference Manual | 2026-11-21 |
| SBL-02c | NixOS has a declarative configuration model: the administrator edits a description of the desired system (configuration.nix) and NixOS makes it happen. |
NixOS 26.05 | NixOS Manual, Changing the Configuration | 2026-11-21 |
| SBL-02d | guix time-machine runs a chosen revision of Guix, defined by a commit or by a channel description file produced by guix describe. |
Guix 1.5.0 manual | Invoking guix time-machine, GNU Guix Reference Manual | 2026-11-21 |
| SBL-02e | Guix System declares all aspects of the global system configuration (services, time zone, locale, user accounts) in one place, and the configuration can be instantiated and rolled back. | Guix 1.5.0 manual | System Configuration, GNU Guix Reference Manual | 2026-11-21 |
| SBL-03a | The Guix full-source bootstrap starts from a 357-byte hex0-seed binary (i686-linux and x86_64-linux), which builds hex0, hex1, M0, hex2, M1, mescc-tools, M2-Planet and then GNU Mes. |
Guix 1.5.0 manual | The Full-Source Bootstrap, GNU Guix Reference Manual | 2026-11-21 |
| SBL-03b | The Guix blog announced on 2023-04-26 that the full-source bootstrap had been merged into the Guix main branch the day before, and that the bootstrap graph was then rooted in a 357-byte program. | Guix main branch, April 2023 | The Full-Source Bootstrap: Building from source all the way down, Guix blog | 2026-11-21 |
| SBL-03c | Guix 1.4.0 was released on 2022-12-19 and Guix 1.5.0 on 2026-01-23, with no release between them, so 1.5.0 is the first numbered release published after the 2023-04-25 merge of the full-source bootstrap; the 1.5.0 announcement lists full-source bootstraps of the Zig and Mono compilers. | Guix 1.4.0 and 1.5.0 | Blog, Releases, GNU Guix | 2026-11-21 |
| SBL-03d | The same blog post says the earlier reduced seed was “just GNU Mes and MesCC-Tools (and the driver to build Guix packages: a static build of GNU Guile 2.0.9)”, and its package graph lists a bootstrap-guile-2.0.9 driver of about 25 MiB next to the 357-byte seed. |
Guix main branch, April 2023 | The Full-Source Bootstrap: Building from source all the way down, Guix blog | 2026-11-21 |
| SBL-03e | The Guix 1.5.0 manual gives about 250 MB as the combined size of the traditional bootstrap binaries (Bourne shell, Coreutils, Awk, Findutils, sed, grep, Guile, GCC, Binutils, GNU C Library). | Guix 1.5.0 manual | The Full-Source Bootstrap, GNU Guix Reference Manual | 2026-11-21 |
| SBL-04a | The Yocto Project builds images and applications with cross-development toolchains that the OpenEmbedded build system generates for the target hardware, and recipes obtain sources from upstream releases, local projects or an SCM. | Yocto Project 6.1 | Overview and Concepts Manual, Yocto Project Concepts | 2026-11-21 |
| SBL-04b | In Yocto, the package-management image feature “installs package management tools and preserves the package manager database”, and “runtime package management” (installing packages on a running device from a package feed) is a documented, optional setup. |
Yocto Project 6.1 | Reference Manual, Features, image features and Development Tasks Manual, Using Runtime Package Management | 2026-11-21 |
| SBL-04c | Buildroot automates building a complete Linux system for an embedded target using cross-compilation: it can generate a cross-compilation toolchain, a root filesystem, a kernel image and a bootloader. | Buildroot 2026.08 manual | The Buildroot user manual, About Buildroot | 2026-11-21 |
| SBL-04d | The Buildroot FAQ explains why Buildroot does not generate binary packages (.deb, .ipkg): it does not track which package installed which file, and changes made in menuconfig are not applied to the output directory without a rebuild. | Buildroot 2026.08 manual | The Buildroot user manual, FAQ: why Buildroot does not generate binary packages | 2026-11-21 |
| SBL-04e | The Yocto Project 6.1 Overview and Concepts Manual, Variables Glossary, Images reference and Features reference describe no installer and no answer file for installing an image onto a target; the only installer they name is the SDK installer, a self-extracting script that installs the SDK on a development host. | Yocto Project 6.1 | absence: not stated by the project; checked Overview and Concepts Manual, Variables Glossary, Images and Features on 2026-11-21 | 2026-11-21 |
| SBL-04f | The Buildroot user manual describes no installer and no answer file for the generated system; its occurrences of “installer” name the preferred installation method of Perl and Python package build systems. | Buildroot 2026.08 manual | absence: not stated by the project; checked the Buildroot user manual on 2026-11-21 | 2026-11-21 |
| SBL-05a | BitBake works per task: the shared state (sstate) code computes a checksum of a task’s inputs, and a task whose checksum has a stored result is not run again; the result can be fetched from a shared state cache. | Yocto Project 6.1 | Overview and Concepts Manual, Shared State Cache | 2026-11-21 |
| SBL-05b | Yocto Hash Equivalence tracks a task hash, an output hash and a unihash per task; a Hash Equivalence server stores the mapping from task hash to output hash, so an unchanged output lets dependent tasks keep their earlier hashes. | Yocto Project 6.1 | Overview and Concepts Manual, Hash Equivalence | 2026-11-21 |
| SBL-05c | Buildroot integrates ccache, a compiler cache that stores the object files of each compilation (enabled with “Enable compiler cache”, directory BR2_CCACHE_DIR, default $HOME/.buildroot-ccache). |
Buildroot 2026.08 manual | The Buildroot user manual, Using ccache in Buildroot | 2026-11-21 |
| SBL-05d | The Buildroot manual states that Buildroot does not attempt to detect which parts of the system must be rebuilt when the configuration changes, and that the user decides when a full rebuild is necessary. | Buildroot 2026.08 manual | The Buildroot user manual, Understanding when a full rebuild is necessary | 2026-11-21 |
| SBL-06a | The Arch Linux Archive stores daily snapshots of the official repositories under /repos/YYYY/MM/DD/ on archive.archlinux.org. |
Arch Linux (rolling), ISO 2026.11.01 | Arch Linux Archive, ArchWiki, /repos | 2026-11-21 |
| SBL-06b | The live index of archive.archlinux.org/repos/2026/11/ lists one directory per day, 15 to 20 November 2026 among them, and the special links last, week and month. |
Arch Linux Archive at 2026-11-21 | archive.archlinux.org/repos/2026/11/ | 2026-11-21 |
| SBL-06c | The Archive keeps packages “for a few years”; older packages move to the Arch Linux Historical Archive on the Internet Archive, which does not offer point-in-time snapshots of the repositories. | Arch Linux Archive wiki page, 2026-11-21 | Arch Linux Archive, ArchWiki, Historical Archive | 2026-11-21 |
| MAP-NIX-01 | A Nix closure is the set of store paths reachable from a store path through references; the closure of a derivation corresponds to build-time dependencies and the closure of its output to runtime dependencies. | Nix 2.36.0 | Glossary, closure, Nix 2.36.0 Reference Manual | 2026-11-21 |
| MAP-NIX-02 | nix store sign signs store paths with a local secret key (--key-file), and the require-sigs setting accepts paths signed by a key listed in trusted-public-keys. |
Nix 2.36.0 | nix store sign, Nix 2.36.0 Reference Manual | 2026-11-21 |
| MAP-NIX-03 | The NixOS 26.05 manual has chapters “Building Images with nixos-rebuild build-image” and “Building Images via systemd-repart”. | NixOS 26.05 | NixOS Manual, Building Images via systemd-repart | 2026-11-21 |
| MAP-NIX-04 | The NixOS module option system.activationScripts is a set of shell script fragments executed when a system configuration is activated (updating /etc, creating accounts), at every boot and every nixos-rebuild. |
nixpkgs release-26.05 | nixos/modules/system/activation/activation-script.nix | 2026-11-21 |
| MAP-NIX-05 | nixpkgs release-26.05 has a module boot.uki (options name, version, settings, configFile) that builds a unified kernel image with ukify. |
nixpkgs release-26.05 | nixos/modules/system/boot/uki.nix | 2026-11-21 |
| MAP-NIX-06 | nixpkgs release-26.05 defines image.repart options (image version, compression, size, partitions with contents from store paths) in nixos/modules/image/repart.nix. |
nixpkgs release-26.05 | nixos/modules/image/repart.nix | 2026-11-21 |
| MAP-GUX-01 | guix system image produces disk images; --image-type selects the type and defaults to mbr-hybrid-raw, and iso9660 is another value. |
Guix 1.5.0 manual | Invoking guix system, GNU Guix Reference Manual | 2026-11-21 |
| MAP-GUX-02 | The Guix operating-system record has the fields kernel (default linux-libre), initrd (default base-initrd) and bootloader. |
Guix 1.5.0 manual | operating-system Reference, GNU Guix Reference Manual | 2026-11-21 |
| MAP-GUX-03 | Guix ignores substitutes that are not signed or are not signed by a key in the access control list, and raises an error for a tampered substitute. | Guix 1.5.0 manual | Substitute Authentication, GNU Guix Reference Manual | 2026-11-21 |
| MAP-GUX-04 | Guix service types extend other service types, for example activation-service-type receives the activation code of a service, and etc-service-type is a documented service type in the Service Reference. |
Guix 1.5.0 manual | Service Types and Services, GNU Guix Reference Manual and Service Reference | 2026-11-21 |
| MAP-YOC-01 | IMAGE_INSTALL is used by recipes to specify the packages to install into an image through the image class. |
Yocto Project 6.1 | Variables Glossary, IMAGE_INSTALL | 2026-11-21 |
| MAP-YOC-02 | ROOTFS_POSTPROCESS_COMMAND specifies a list of functions called once the build system has created the root filesystem, and ${IMAGE_ROOTFS} points to the directory that becomes the root filesystem image. |
Yocto Project 6.1 | Variables Glossary, ROOTFS_POSTPROCESS_COMMAND | 2026-11-21 |
| MAP-YOC-03 | WKS_FILE specifies the location of the Wic kickstart file used to create a partitioned image (image.wic). |
Yocto Project 6.1 | Variables Glossary, WKS_FILE | 2026-11-21 |
| MAP-YOC-04 | EFI_PROVIDER selects the EFI bootloader for bootable images (hddimg, iso, wic.vmdk); the default is grub-efi and systemd-boot can be used instead. |
Yocto Project 6.1 | Variables Glossary, EFI_PROVIDER | 2026-11-21 |
| MAP-YOC-05 | SRCREV is the revision of the source code used to build a package (Subversion, Git and Mercurial only), and for a fixed revision the manual advises a full revision identifier, such as the full SHA of Git, and not a tag, so that BitBake does not query the remote repository on every parse. |
Yocto Project 6.1 | Variables Glossary, SRCREV | 2026-11-21 |
| MAP-BRT-01 | Buildroot customises the target through BR2_ROOTFS_OVERLAY (adds or overwrites files), BR2_ROOTFS_POST_BUILD_SCRIPT (commands before the filesystem image is generated) and BR2_ROOTFS_POST_IMAGE_SCRIPT (commands after it). |
Buildroot 2026.08 manual | The Buildroot user manual, Customizing the generated target filesystem | 2026-11-21 |
| MAP-BRT-02 | Buildroot package .hash files carry hashes that Buildroot checks for downloaded files; a package consists of Config.in, a .mk file with <PKG>_SITE, and a .hash file. |
Buildroot 2026.08 manual | The Buildroot user manual, Adding new packages to Buildroot | 2026-11-21 |
| MAP-BRT-03 | The manual’s example package declares its configuration option in Config.in as config BR2_PACKAGE_PKG_1 with bool "pkg-1" and a help text, next to the .mk and .hash files of the package directory. |
Buildroot 2026.08 manual | The Buildroot user manual, Adding new packages to Buildroot | 2026-11-21 |
5. Privilege
Which construction steps need privilege, on Linux and in the build tools of the families. Whether a
build is unprivileged says nothing about its isolation: the isolation boundary is a separate matter
(SCF-BLD-001, SCF-BLD-002).
Versions checked: Debian 13.7 (2026-09-12); mmdebstrap 1.7.0-5 (Debian unstable, man page source updated 2026-11-19); apko v1.5.2 (2026-11-20); Nix 2.36.0 (2026-11-19); systemd 262.2 (2026-11-05); mkosi v27.1 (2026-09-28); e2fsprogs 1.47.4; erofs-utils 1.9.4; dosfstools 4.2; mtools 4.0.50; genimage v20 (2026-06-05); squashfs-tools 4.7.5 (2026-03-01); xorriso 1.5.8.pl02 (Debian man page; GNU manual 2026); live-build 1:20250814 (Debian unstable man page); Linux man-pages 6.19 (2026-02); util-linux 2.43 (losetup page); Linux 7.3 (2026-10-18), stable 7.3.5 (2026-11-17), mainline 7.4-rc3 (2026-11-15); NetBSD 11.1 (2026-11-02); FreeBSD 15.1 (2026-06-16); OpenBSD 8.0 (2026-10-20).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| PRV-01.1 | In unshare mode, mmdebstrap run by a normal (non-root) user uses Linux user namespaces to allow unprivileged use of chroot and creation of files that appear owned by the superuser; a tarball made in this mode is bit-by-bit identical to one made in root mode, and only newuidmap(1) and newgidmap(1) run as root, through their setuid bit. | mmdebstrap 1.7.0-5 | mmdebstrap(1), section MODES | 2026-11-21 |
| PRV-01.2 | mmdebstrap in auto mode chooses unshare mode when /etc/subuid and /etc/subgid are set up and otherwise fakechroot mode when the fakechroot binary exists; its root (sudo) mode needs to mount and therefore needs CAP_SYS_ADMIN. | mmdebstrap 1.7.0-5 | mmdebstrap(1), section MODES | 2026-11-21 |
| PRV-01.3 | What apko does without root (ignores ownership and device errors and records the intended values in the layer) is stated once, in APK-05a; in addition apko lays out apk package files directly with its own implementation. | apko v1.5.2 | apko docs/build-process.md | 2026-11-21 |
| PRV-01.4 | The Nix manual states that the sandbox setting requires Nix to run as root, with the build-users feature running builds under other users; build-users-group defaults to nixbld when running as root and to empty otherwise, and with an empty group builds run under the uid of the Nix process. | Nix 2.36.0 | Nix manual, conf-file: sandbox, build-users-group | 2026-11-21 |
| PRV-01.5 | A Nix local store with a root other than / (a local chroot store) supports building and running on Linux when mount namespaces and user namespaces are enabled. | Nix 2.36.0 | Nix manual, Local Store | 2026-11-21 |
| PRV-02.1 | mke2fs -d copies the contents of a directory, or of a tarball, into the root directory of the new file system; tarball input needs libarchive support and the value - reads a tarball from standard input. | e2fsprogs 1.47.4 | mke2fs(8) | 2026-11-21 |
| PRV-02.2 | The option mke2fs -d to pre-populate a file system from a directory hierarchy first appears in the E2fsprogs 1.43 release notes (17 May 2016), and tarball input (when libarchive is available) in the 1.47.1 notes (20 May 2024); release 1.47.4 is dated 6 March 2026. | e2fsprogs 1.43; 1.47.1; 1.47.4 | E2fsprogs release notes | 2026-11-21 |
| PRV-02.3 | mkfs.erofs creates an EROFS image file from a local directory, a compressed tarball, an S3 bucket or prefix, an OCI image reference, or other EROFS images. | erofs-utils 1.9.4 | mkfs.erofs(1) | 2026-11-21 |
| PRV-02.4 | mkfs.fat creates a FAT file system on a device or in an image file, and the image file does not need to exist when the option -C is given. | dosfstools 4.2 | mkfs.fat(8) | 2026-11-21 |
| PRV-02.5 | mtools is a collection of utilities to access MS-DOS disks from Unix without mounting them, and mcopy with the option -s copies directories and their contents recursively. | mtools 4.0.50 | GNU mtools; mcopy(1) | 2026-11-21 |
| PRV-02.6 | The repart.d setting CopyFiles= copies files or directories from the host into the file system created for a partition, and systemd-repart –offline builds the image without loop devices, which the manual describes as useful to build images unprivileged. | systemd 262.2 | repart.d(5); systemd-repart(8) | 2026-11-21 |
| PRV-02.7 | In mkosi, RepartOffline= is enabled by default so that systemd-repart builds disk images without loopback devices, and with RepartOffline=no mkosi cannot run unprivileged. | mkosi v27.1 | mkosi(1) at tag v27.1, RepartOffline= | 2026-11-21 |
| PRV-02.8 | genimage generates file-system and flash or disk images (types include erofs, ext2 to ext4, iso, squashfs, vfat, hdimage) from a root file-system tree, and its README says it is intended to be run in a fakeroot environment. | genimage v20 | genimage README | 2026-11-21 |
| PRV-02.9 | mmdebstrap writes ext4 (through mke2fs), squashfs (through tar2sqfs), erofs (through mkfs.erofs) and ext2 (through genext2fs) images from a tarball of the chroot to a regular file, and its examples build a chroot tarball without superuser privileges. | mmdebstrap 1.7.0-5 | mmdebstrap(1), sections FORMATS and EXAMPLES | 2026-11-21 |
| PRV-03.1 | mksquashfs builds a squashfs image from source directories or from an uncompressed tar read on standard input (-tar), can make all files owned by root (-all-root) or by a given uid and gid (-force-uid, -force-gid), accepts pseudo-file definitions (-p), and builds reproducible images with -repro or -repro-time. | squashfs-tools 4.7.5 | mksquashfs(1) | 2026-11-21 |
| PRV-03.2 | xorriso copies file objects from POSIX file systems into a Rock Ridge ISO 9660 image, writes the result to optical media or to file-system objects (a stdio: path can name a regular file), needs neither an external ISO formatter nor a burn program, and sets one uid and gid for all files of the new image with -uid and -gid. | xorriso 1.5.8.pl02 | xorriso(1), GNU manual | 2026-11-21 |
| PRV-04.1 | mount(2) states that appropriate privilege, on Linux the CAP_SYS_ADMIN capability, is required to mount file systems. | man-pages 6.19 (2026-02-11) | mount(2) | 2026-11-21 |
| PRV-04.2 | With CAP_SYS_ADMIN in the user namespace that owns the mount namespace, a process can create bind mounts and mount /proc and /sys (since Linux 3.8), devpts, tmpfs, ramfs and mqueue (3.9), bpf (4.4) and overlayfs (5.11), and cgroup2 with the cgroup namespace (4.6); mounting block-based file systems needs CAP_SYS_ADMIN in the initial user namespace. | man-pages 6.19 (2026-02-08) | user_namespaces(7) | 2026-11-21 |
| PRV-04.3 | mknod(2) fails with EPERM when the node is anything other than a regular file, FIFO or UNIX domain socket and the caller lacks CAP_MKNOD; user_namespaces(7) lists creating a device among the operations that only a process privileged in the initial user namespace can perform. | man-pages 6.19 | mknod(2); user_namespaces(7) | 2026-11-21 |
| PRV-04.4 | mmdebstrap documents that a directory chroot made in any mode other than sudo lacks special device files, that mknod does not function in unshared user namespaces (option –skip=output/mknod), and that a tarball can have ./dev removed for extraction by a non-root user who cannot create device nodes. | mmdebstrap 1.7.0-5 | mmdebstrap(1), sections FORMATS, output cleanup and EXAMPLES | 2026-11-21 |
| PRV-04.5 | loop(4) describes /dev/loop-control, available since Linux 3.1, whose ioctl operations LOOP_CTL_GET_FREE, LOOP_CTL_ADD and LOOP_CTL_REMOVE find, add and remove loop devices; the page names no capability for these operations. | man-pages 6.19 (2026-02-08) | absence: not stated by the project (the capability for the loop-control operations); checked loop(4) on 2026-11-21 | 2026-11-21 |
| PRV-04.6 | In the Linux 7.3 loop driver, LOOP_SET_STATUS, LOOP_SET_STATUS64, LOOP_SET_BLOCK_SIZE, LOOP_SET_CAPACITY and LOOP_SET_DIRECT_IO return EPERM unless the device was opened for writing or the caller has CAP_SYS_ADMIN; these are the only capable() checks in the file, so attaching a backing file depends on write access to the device node. | Linux 7.3 | drivers/block/loop.c at v7.3 | 2026-11-21 |
| PRV-04.7 | The default udev rules of systemd assign GROUP=“disk” to block devices and to loop-control, so access to the loop device nodes follows the node permissions of the initial namespace. | systemd main (release 262.2) | rules.d/50-udev-default.rules.in | 2026-11-21 |
| PRV-05.1 | Linux 6.7 (released 2024-01-07) contains the commit “binfmt_misc: enable sandboxed mounts”, which makes binfmt_misc mountable in non-initial user namespaces with one superblock per user namespace, so that an unprivileged sandbox registers its own binary types (for example qemu-user handlers) without changing the host. | Linux 6.7 | commit 21ca59b365c0 in torvalds/linux | 2026-11-21 |
| PRV-05.2 | Before that commit binfmt_misc could be mounted only in the initial user namespace, and binary types registered there were available to all sandboxes. | Linux 6.6 and earlier | commit 21ca59b365c0 in torvalds/linux | 2026-11-21 |
| PRV-05.3 | The binfmt_misc file-system type in Linux 7.3 sets FS_USERNS_MOUNT, so the position of 6.7 holds in the current stable series. | Linux 7.3 | fs/binfmt_misc.c at v7.3 | 2026-11-21 |
| PRV-05.4 | A binary type is registered by mounting binfmt_misc and writing a string of the form :name:type:offset:magic:mask:interpreter:flags to /proc/sys/fs/binfmt_misc/register. | Linux 7.4-rc3 documentation | Kernel documentation: binfmt_misc | 2026-11-21 |
| PRV-06.1 | The superuser requirement of the host that builds live system images with live-build is stated once, in DEB-12a; the Live Manual lists it first among the requirements. | live-build 1:20250505+deb13u1 (Live Manual, trixie-era text) | Debian Live Manual, 3.1 Requirements | 2026-11-21 |
| PRV-06.2 | That live-build includes no Debian Installer images by default, and the combined image, are stated once, in DEB-01c and DEB-01b; lb_config(1) lists the installer types (live and others) that lb config –debian-installer accepts. | live-build 1:20250814 (unstable man page); the Live Manual as in DEB-01b | Debian Live Manual, Customizing the Debian Installer; lb_config(1) | 2026-11-21 |
| PRV-07.1 | The NetBSD Guide builds a complete release as a non-root user with ./build.sh -U -u -j2 -O ~/obj -m evbarm -a aarch64 release, and describes -U as an unprivileged build. | NetBSD 11.1 | NetBSD Guide, chapter 33 Crosscompiling NetBSD | 2026-11-21 |
| PRV-07.2 | The unprivileged build of NetBSD (build.sh -U, MKUNPRIVED=yes, the file METALOG in DESTDIR) is stated once, in NBS-01b. | NetBSD 11.1 | NetBSD Guide, build.sh options and variables | 2026-11-21 |
| PRV-07.3 | The unprivileged install of the FreeBSD base system (-DNO_ROOT, METALOG, the targets that force it) is stated once, in FBS-05c. | FreeBSD 15.1 (releng/15.1) | Makefile.inc1 on releng/15.1 | 2026-11-21 |
| PRV-07.4 | The FreeBSD 15.1 release/Makefile runs its sub-makes with -DNO_ROOT -DWITHOUT_QEMU -DDB_FROM_SRC, while release(7) describes the release.sh wrapper as checking out the trees into a chroot(8), installing buildworld there, and running make release inside it. | FreeBSD 15.1 | release/Makefile on releng/15.1; release(7) | 2026-11-21 |
| PRV-07.5 | src.conf(5) of FreeBSD 15.1 lists WITHOUT_REPRODUCIBLE_BUILD, the non-default form (FBS-05a), which includes build time, user and host in the kernel, boot loaders and uname output so that successive builds are not bit-for-bit identical, and WITH_INSTALL_AS_USER, which makes install targets succeed for non-root users. | FreeBSD 15.1 | src.conf(5) | 2026-11-21 |
| PRV-07.6 | The release(8) page of OpenBSD 8.0 marks the kernel build, make build of the base system and cd /usr/src/etc && make release as commands run as the superuser, needs a file system mounted with the noperm option and owned by user build, and uses the vnd(4) device vnd0. | OpenBSD 8.0 | release(8), OpenBSD 8.0 | 2026-11-21 |
6. Archive pinning
What each platform provides for binding a build to a past state of its archive, and where it provides
nothing. The producer-held snapshot of SCF-SRC-004 is the remedy where nothing is provided.
Versions checked: Debian 13.7 (2026-09-12); Ubuntu snapshot service as documented 2026-11-21 (service introduced 2023-11-02); Arch Linux Archive (rolling, daily); Gentoo catalyst 4.x; Nix 2.36.0 (2026-11-19); Guix 1.5.0 (tag 2026-01-21); RHEL 8 and 9 content templates (article 2025-04-23, updated 2025-11-07); Fedora archive tree (page capture 2026-03-15); Rocky vault README; Alpine v3.24 (branch 2026-06-09, 3.24.4); Kali 2026.3; FreeBSD 15.1; OpenBSD 8.0; NetBSD 11.1.
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| PIN-01.1 | snapshot.debian.org lists imports of the main Debian archive with states roughly six hours apart for the debian archive (updated every six hours); the span of the imports and the archives offered are stated in DEB-09a. | snapshot.debian.org, news of 2024-10-08 | snapshot.debian.org | 2026-11-21 |
| PIN-01.2 | The form of a snapshot URL and the answer to a request for a time without an import are stated once, in DEB-09b. | snapshot.debian.org, page read 2026-11-21 | snapshot.debian.org, Usage | 2026-11-21 |
| PIN-01.3 | snapshot.debian.org held 172 TB of data on 2024-10-08, and its /mr/timestamp/ endpoint listing all timestamps per archive was added in August 2024. | snapshot.debian.org, news of 2024-10-08 | snapshot.debian.org, News | 2026-11-21 |
| PIN-01.4 | snapshot.ubuntu.com states an intention to keep dates up to at least two years in the past; the dates served and the supported releases are stated in DEB-09c. | Ubuntu snapshot service, page of 2026-11-21 | Ubuntu Snapshot Service | 2026-11-21 |
| PIN-01.5 | Canonical introduced the Ubuntu snapshot service, available at snapshot.ubuntu.com, on 2 November 2023 in its announcement of the Azure integration. | Ubuntu snapshot service | Canonical blog, 2 November 2023 | 2026-11-21 |
| PIN-02.1 | The Arch Linux Archive stores official ISO images and bootstrap tarballs, all versions of each package, and daily snapshots of the official repositories, and its /repos directory is organised by date as repos/YYYY/MM/DD. | Arch Linux Archive, wiki page and listing read 2026-11-21 | ArchWiki: Arch Linux Archive | 2026-11-21 |
| PIN-02.2 | archive.archlinux.org/repos lists year directories 2013 to 2026 plus last, month and week, and the ArchWiki states that packages are kept for a few years before they move to the Arch Linux Historical Archive on the Internet Archive. | Arch Linux Archive, wiki page and listing read 2026-11-21 | archive.archlinux.org/repos; ArchWiki: Arch Linux Archive | 2026-11-21 |
| PIN-03.1 | The Gentoo ebuild repository (::gentoo) is maintained on the gitweb.gentoo.org server, and Portage synchronises it by rsync (the default) or by git. | Gentoo wiki, page of 2026-11-21 | Gentoo wiki: Gentoo ebuild repository | 2026-11-21 |
| PIN-03.2 | From version 4, catalyst clones the ::gentoo repository with git and compresses it into a squashfs snapshot named gentoo- |
catalyst 4.x | Gentoo wiki: Catalyst | 2026-11-21 |
| PIN-04.1 | Nix generates a UTF-8 JSON lock file flake.lock in the flake directory that maps unlocked inputs in flake.nix to locked input specifications, and flake references can name a Git revision (rev) as a commit hash. | Nix 2.36.0 | Nix manual: nix flake, Lock files | 2026-11-21 |
| PIN-04.2 | guix time-machine runs Guix at a revision given by a commit or by a channel description file created by guix describe, the Guix history is immutable, and the command refuses commits older than v0.16.0 (December 2018). | Guix 1.5.0 | GNU Guix manual: Invoking guix time-machine | 2026-11-21 |
| PIN-05.1 | Red Hat Lightspeed (formerly Insights) content templates use repository snapshots, and the core Red Hat repositories (for example RHEL 9 BaseOS and AppStream for x86_64) are snapshotted automatically every 24 hours; a template can follow the latest snapshot or be frozen at a chosen date. | RHEL 8 and 9 | Red Hat Developer: How to use content templates | 2026-11-21 |
| PIN-05.2 | Red Hat Enterprise Linux Extended Update Support keeps a system on one minor release for 24 months through separate repositories per minor release, with backports of Critical and Important security fixes; it is an add-on offering for subscribers. | RHEL 8 and 9 EUS | Red Hat: RHEL Extended Update Support overview | 2026-11-21 |
| PIN-05.3 | Fedora infrastructure documents moving the trees of end-of-life releases from the download area to the archive under /pub/archive/fedora/linux (releases, updates, updates/testing) because the download servers hold terabytes of data. | Fedora docs, capture of 2026-03-15 | Fedora Docs: How to Archive Old Fedora Releases (Wayback capture of docs.fedoraproject.org) | 2026-11-21 |
| PIN-05.4 | The README of the Rocky Linux vault says it is not an updated location for installing Rocky Linux, that no release there is supported, and that use is at the user’s own risk. | Rocky vault, README of 2024-06-05 | dl.rockylinux.org/vault README | 2026-11-21 |
| PIN-06.1 | dl-cdn.alpinelinux.org/alpine/ contains one directory per release branch (v3.0 to v3.25), plus edge and latest-stable, and no date-addressed directories. | Alpine, listing of 2026-11-21 | absence: not stated by the project (date-addressed directories); checked dl-cdn.alpinelinux.org/alpine/ on 2026-11-21, as in APK-06c | 2026-11-21 |
| PIN-06.2 | The release page says “Each May and November we make a release branch from edge” and gives the branch dates as 2026-06-09 for v3.24 and 2025-12-03 for v3.23, so the dates fall after the named months; it states that the main repository is typically supported for 2 years and the community repository until the next stable release (v3.24 end of support 2028-06-01). | Alpine v3.24 and v3.23 | Alpine release branches | 2026-11-21 |
| PIN-07.1 | kali-last-snapshot is a Kali branch into which kali-rolling is merged at each versioned release (for example 2020.3 to 2020.4), so users receive updates between releases only at those points, and packages in it are not updated until the next point release. | Kali 2026.3 | Kali docs: Kali branches | 2026-11-21 |
| PIN-07.2 | packages.linuxmint.com/dists lists one directory per release codename (for example faye, gigi, adrien), changed in place (adrien on 2026-11-20, faye and gigi on 2026-11-17), and no date-addressed directories. | Linux Mint repository, listing of 2026-11-21 | absence: not stated by the project (date-addressed directories); checked packages.linuxmint.com/dists on 2026-11-21 | 2026-11-21 |
| PIN-07.3 | The Linux Mint documentation index lists four guides, for installation, use, translation and fixing faults, and names no repository snapshot service. | Linux Mint documentation page of 2026-11-21 | absence: not stated by the project (a repository snapshot service); checked the Linux Mint documentation index on 2026-11-21 | 2026-11-21 |
| PIN-08.1 | The FreeBSD Handbook describes a Quarterly ports branch cut from HEAD at the start of each quarter (January, April, July, October), named like 2023Q1, that receives security fixes, bug fixes and framework changes, and says pkg tracks the quarterly branch by default and not HEAD. | FreeBSD 15.1 Handbook | FreeBSD Handbook: Quarterly and Latest Ports Branches | 2026-11-21 |
| PIN-08.2 | The freebsd-src repository carries a release branch releng/15.1 for FreeBSD 15.1, released 2026-06-16. | FreeBSD 15.1 | freebsd-src branch releng/15.1; FreeBSD release information | 2026-11-21 |
| PIN-08.3 | The OpenBSD release(8) procedure uses cvs tags: OPENBSD_x_y_BASE for the sources of release x.y and OPENBSD_x_y for its stable branch, and warns that cvs tags are sticky. | OpenBSD 8.0 | release(8), OpenBSD 8.0 | 2026-11-21 |
| PIN-08.4 | The NetBSD Guide states that the source files of a release do not change after the release is made and fetches them with cvs checkout -r TAG, for example netbsd-11-1-RELEASE. | NetBSD 11.1 | NetBSD Guide, chapter 32 Obtaining the sources | 2026-11-21 |
7. Signing models
How the families of section 3 sign what they distribute (deb, rpm, apk, FreeBSD, OpenBSD, NetBSD, illumos, Nix and Guix, Yocto, Buildroot), and the signing of container images. Gentoo, Arch Linux, DragonFly BSD, Haiku and Darwin are described in section 4 and have no signing rows here.
Versions checked: Yocto Project 6.1 and Buildroot 2026.08 manuals (read 2026-11-21); apt 3.3.8 (Debian unstable man page 2026-11-16), trixie apt 3.0.3; rpm 6.1.0 (2026-08-20); dnf5 5.4.8.0 (2026-11-11); apk-tools v3.0.10 (2026-11-19); OpenBSD 8.0; NetBSD 11.1 (2026-11-02), pkg_install 20260227; FreeBSD 15.1, pkg 2.9.3 (2026-11-17); OmniOS pkg(1) page of 2026-08-19; Nix 2.36.0; Guix 1.5.0; cosign v3.1.4 (2026-10-20); Notation v1.3.2 (2025-04-27); Notary Project signature specification (main, read 2026-11-21).
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| SIG-01.1 | APT checks the signature of the Release file for all repositories, which ensures that data like packages in the archive cannot be modified by people without access to the Release file signing key. | apt 3.3.8 | apt-secure(8) | 2026-11-21 |
| SIG-01.2 | The Debian Security FAQ describes package integrity checking as verifying the Release file signature against the archive public key, where the Release file contains the checksums of Packages and Sources files, which contain the checksums of binary and source packages. | Debian 13.7 | Debian Security FAQ | 2026-11-21 |
| SIG-01.3 | debsig-verify verifies the origin signature of an individual deb against policy files found in a directory named after the public key ID of the signer. | debsig-verify, Debian unstable man page read 2026-11-21 | debsig-verify(1) | 2026-11-21 |
| SIG-02.1 | rpmkeys –checksig (-K) verifies the digests and signatures contained in a package file to ensure the integrity and origin of the package. | rpm 6.1.0 (2026-08-20) | rpmkeys(8) | 2026-11-21 |
| SIG-02.2 | dnf5 has the repository options pkg_gpgcheck (OpenPGP check of packages) and repo_gpgcheck (OpenPGP check of repository metadata), both defaulting to False in the configuration reference, and keeps the keys for the two checks separately. | dnf5 5.4.8.0 | DNF5 configuration reference | 2026-11-21 |
| SIG-03.1 | A v2 apk package starts with signature files named .SIGN.algorithm.keyid placed before any other data, where the key id is the name of the key file in /etc/apk/keys, and a single signature from a trusted key is sufficient. | apk-tools v3.0.10 | apk-v2(5) | 2026-11-21 |
| SIG-03.2 | The directory /etc/apk/keys stores the public keys that apk trusts to verify signatures for packages. | apk-tools v3.0.10 | apk-keys(5) | 2026-11-21 |
| SIG-03.3 | The index created by apk index must be cryptographically signed before apk accepts it. | apk-tools v3.0.10 | apk-index(8) | 2026-11-21 |
| SIG-04.1 | signify -C verifies a signed checksum list (the signed output of sha256) and then the checksum of each file; the OpenBSD FAQ verifies a downloaded image with signify -Cp /etc/signify/openbsd-80-base.pub -x SHA256.sig. | OpenBSD 8.0 | signify(1); OpenBSD FAQ 4 | 2026-11-21 |
| SIG-04.2 | The OpenBSD installer asks “Directory does not contain SHA256.sig. Continue without verification?” when the directory holding the sets has no SHA256.sig; install media images carry no SHA256.sig because verifying them from inside the image would be meaningless. | OpenBSD 8.0 | OpenBSD FAQ 4 | 2026-11-21 |
| SIG-04.3 | pkg_add rejects unsigned packages by default unless they come from a trusted source (TRUSTED_PKG_PATH) or -D unsigned is used, checks that a package signature is valid and issued by a key in /etc/signify/*-pkg.pub, and verifies the compressed package data against the signature before it unpacks files. | OpenBSD 8.0 | pkg_add(1) | 2026-11-21 |
| SIG-05.1 | The NetBSD 11.1 announcement offers a list of hashes of all files in the distribution, signed with the NetBSD Security Officer’s PGP key. | NetBSD 11.1 | Announcing NetBSD 11.1 | 2026-11-21 |
| SIG-05.2 | The package signing of NetBSD is stated in NBS-04a (VERIFIED_INSTALLATION defaults to never, install unconditionally; always requires a valid X.509 or OpenPGP signature) and NBS-04b (pkg_admin gpg-sign-package signs a binary package with GPG). | NetBSD 11.1 | pkg_admin(1); pkg_install.conf(5) | 2026-11-21 |
| SIG-06.1 | The signature types of a pkg repository (default NONE) are stated in FBS-11a, and the signature type of the shipped FreeBSD and FreeBSD-base repositories (fingerprints with /usr/share/keys/pkg) in FBS-11b. | FreeBSD 15.1, pkg 2.9.3 | pkg.conf(5) | 2026-11-21 |
| SIG-06.2 | pkg repo can sign the repository catalogue with an rsa, ecdsa or eddsa key or through an external signing command: rsa signs the SHA256 hash of the repository and ecdsa and eddsa sign its BLAKE2 hash. | FreeBSD 15.1, pkg 2.9.3 | pkg-repo(8) | 2026-11-21 |
| SIG-07.1 | The image property signature-policy of IPS has the values ignore, verify (the default; manifests with signatures must be validly signed), require-signatures (every newly installed package has at least one valid signature) and require-names (as require-signatures, plus required common names in the certificate chains). | OmniOS pkg(1), page of 2026-08-19 | pkg(1), OmniOS manual | 2026-11-21 |
| SIG-08.1 | Nix, with require-sigs true (the default), accepts a non-content-addressed path added or copied to the store (for example from a binary cache) only with a signature by a trusted key, meaning a key in trusted-public-keys or the public counterpart of a key in secret-key-files. | Nix 2.36.0 | Nix manual, conf-file: require-sigs | 2026-11-21 |
| SIG-08.2 | Guix raises an error for a tampered substitute and ignores substitutes that are not signed or not signed by a key in the access control list. | Guix 1.5.0 | GNU Guix manual: Substitute Authentication | 2026-11-21 |
| SIG-08.3 | A Notary Project signature has a payload that is the descriptor (media type, digest, size) of the signed OCI artifact, and signatures for OCI artifacts are stored in and retrieved from an OCI registry. | Notary signature specification (main) | Notary Project signature specification | 2026-11-21 |
| SIG-08.4 | cosign sign signs a container image given by its reference, allows several signatures on one image, and in the default keyless mode records the signing event in the Rekor transparency log together with the artifact hash, the public key and the signature. | cosign v3.1.4 | Sigstore: Signing Containers; Sigstore: Overview | 2026-11-21 |
| SIG-09.1 | The Yocto Development Tasks Manual section “Generating and Using Signed Packages” describes signing RPM packages during a build (the rpm recipe is configured for OpenPGP signing) and using signed package feeds, and says that if security fails for a signed package the build system stops the build. | Yocto Project 6.1 | Development Tasks Manual, Generating and Using Signed Packages | 2026-11-21 |
| SIG-09.2 | The Buildroot user manual has no occurrence of “signature”, “GPG” or “gpg”: it describes no signing of packages, images or downloads; package .hash files carry hashes that Buildroot checks for downloaded files (MAP-BRT-02). |
Buildroot 2026.08 manual | absence: not stated by the project; checked the Buildroot user manual on 2026-11-21 | 2026-11-21 |
8. Choosing an approach
Patterns for common requirements. The right column cites the facts each pattern rests on; a pattern is a choice and is not a platform fact.
| Requirement | Approach | Facts |
|---|---|---|
| Support a distribution whose build pipeline is closed or inseparable from its vendor | remaster the official image; the inherited boot chain stays valid while the signed boot components are left unchanged | CHO-01.1 to CHO-01.4, IMP-01.1 to IMP-01.5 |
| Combined live and installer media in the deb family | the Debian live builder, run on a build host with superuser access | CHO-02.1, CHO-02.2, DEB-12a to DEB-12c |
| Disk, root filesystem, container or unified-kernel outputs | an unprivileged package-to-filesystem toolchain | CHO-03.1 to CHO-03.3, PRV-02.6, PRV-02.7 |
| Pinning and reproducibility by construction | a fully declarative source-based system | CHO-04.1 to CHO-04.3, SBL-02a to SBL-02e |
| Appliance with atomic update and rollback | an image-first system with A/B or commit-based deployment | CHO-05.1 to CHO-05.3, FBS-03a, FBS-03b |
| BSD appliance | the family’s own release tooling and a package repository held by the producer | CHO-06.1 to CHO-06.3 |
Versions checked: Cubic (README of main, 2026-11-21); xorriso 1.5.8.pl02; live-build 1:20250814; Debian 13.7; Kali 2026.3; mkosi v27.1 (2026-09-28); systemd 262.2; Nix 2.36.0; Guix 1.5.0; RAUC v1.15.2 (2026-03-27); libostree v2026.7 (2026-11-13); bootc v1.17.5 (2026-11-20); FreeBSD 15.1 with pkg 2.9.3; OpenBSD 8.0; NetBSD 11.1.
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| CHO-01.1 | Cubic is a GUI wizard to create a customized Live ISO image for Ubuntu and Debian based distributions; it runs on Ubuntu 18.04.5 and later and Debian 11 and later and customizes the Live ISOs of Ubuntu 14.04 and later and many Debian-based distributions. | Cubic, README of main | Cubic README | 2026-11-21 |
| CHO-01.2 | xorriso can load an existing ISO image and write a completely new image from it plus modifications (“modifying”), and -boot_image any keep keeps or copies El Torito boot images unaltered while replay re-creates the boot equipment of the loaded image. | xorriso 1.5.8.pl02 | xorriso(1), GNU manual | 2026-11-21 |
| CHO-01.3 | Kali documents that its live image is created with live-build from the build scripts in kali-live and that the installer image is built from kali-installer, so Kali builds its images rather than remastering an upstream image. | Kali 2026.3 | Kali docs: Live build a custom Kali ISO | 2026-11-21 |
| CHO-01.4 | In Ubuntu’s boot chain shim validates GRUB and the kernel against its embedded trust database when they are signed with Canonical’s UEFI key, and Ubuntu’s MokManager enrolls further keys at the console; an image whose shim, GRUB and kernel packages are those of the base distribution therefore boots under the same validation. | Ubuntu security documentation, page of 2026-11-21 | Ubuntu security documentation: UEFI Secure Boot | 2026-11-21 |
| CHO-02.1 | The Debian Live Manual describes a live system image with a separate kernel and initrd that launches a standard Debian Installer from the bootloader as a combined image, and describes a Live Debian Installer variant; live-build includes neither by default. | live-build 1:20250814 | Debian Live Manual: Customizing the Debian Installer | 2026-11-21 |
| CHO-02.2 | The build host of live-build needs superuser access (see PRV-06.1); running the builder inside a virtual machine is a deployment choice of the producer and is not described by the Debian pages. | live-build 1:20250814 | Debian Live Manual, 3.1 Requirements | 2026-11-21 |
| CHO-03.1 | mkosi Format= produces directory, tar, cpio, disk (GPT block device image built with systemd-repart), uki, esp, oci, oci-archive, sysext, confext, portable and addon outputs. | mkosi v27.1 | mkosi(1) at tag v27.1, Format= | 2026-11-21 |
| CHO-03.2 | When mkosi does not run as root it unshares a user namespace and maps the current user to root in it (using systemd-nsresourced when available), and it needs unrestricted ability to create and act within Linux namespaces. | mkosi v27.1 | mkosi(1) at tag v27.1, execution flow and Unprivileged User Namespaces | 2026-11-21 |
| CHO-03.3 | mkosi is described as a wrapper around dnf –installroot, apt, pacman and zypper that generates customized disk images. | mkosi v27.1 | mkosi README at tag v27.1 | 2026-11-21 |
| CHO-04.1 | The NixOS reproducibility page says that a Nix derivation has deterministic references to all its dependencies and builds in a sandbox, which it calls an excellent starting point, and that builds can still leak timestamps or other nondeterminism, tracked with an issue tag in nixpkgs. | NixOS reproducibility page, 2026-11-21 | reproducible.nixos.org | 2026-11-21 |
| CHO-04.2 | The NixOS report for the minimal ISO runtime closure (nixos-unstable, x86_64-linux, page dated 2025-02-09) shows 579 of 582 paths (99.48%) reproducible, and the build-time closure report shows 2551 of 2641 paths (96.59%). | nixos-unstable, report of 2025-02-09 | Minimal ISO runtime report; Minimal ISO build-time report | 2026-11-21 |
| CHO-04.3 | guix challenge compares build outputs of independent builds of a store item from several substitute servers and reports the share of items that were identical, differed or were inconclusive. | Guix 1.5.0 | GNU Guix manual: Invoking guix challenge | 2026-11-21 |
| CHO-05.1 | RAUC is an update client for embedded devices that also creates update bundles on the host; it models redundant slots of one class, notes that classic A+B redundancy is a common setup, and its scenarios page describes symmetric root file system slots. | RAUC v1.15.2 | RAUC: Basic Concepts; RAUC: Scenarios | 2026-11-21 |
| CHO-05.2 | libostree (OSTree) combines a git-like model for committing and downloading bootable file system trees with a deployment layer, and lists transactional upgrades and rollback among its features. | libostree v2026.7 (2026-11-13) | libostree documentation | 2026-11-21 |
| CHO-05.3 | bootc provides transactional, in-place operating system updates using OCI/Docker container images, with the kernel in the image used to boot, and its documentation calls the CLI and API stable. | bootc v1.17.5 (2026-11-20) | bootc documentation | 2026-11-21 |
| CHO-06.1 | On FreeBSD, pkg repo creates the catalogue of a package repository and can sign it, and the release machinery (release(7)) builds installation media from the base system. | FreeBSD 15.1, pkg 2.9.3 | pkg-repo(8); release(7) | 2026-11-21 |
| CHO-06.2 | On OpenBSD the package manager rejects unsigned packages by default (SIG-04.3). | OpenBSD 8.0 | pkg_add(1) | 2026-11-21 |
| CHO-06.3 | On OpenBSD, release(8) describes building the base system release and the Xenocara release from sources checked out with one cvs tag. | OpenBSD 8.0 | release(8) | 2026-11-21 |
| CHO-06.4 | On NetBSD, build.sh builds a complete release from source (see PRV-07.1), and pkgsrc creates a binary package with make package into PACKAGES (default /usr/pkgsrc/packages) that pkg_admin gpg-sign-package can sign. | NetBSD 11.1 | pkgsrc guide, chapter 7 Creating binary packages; pkg_admin(1) | 2026-11-21 |
9. Known limits
What a conformance statement is asked to state rather than discover late (SCF-PLT-025,
SCF-PLT-024). This section is a pattern, like sections 2 and 8: each row is a reading of the
facts cited in its last column, with the version, source and date of those rows, and is not a
platform fact itself. Where the sources are silent the limit is narrowed to what they do state,
and a limit that rests on an absence is worded as “no documented …”.
| Limit | What the facts show | Facts |
|---|---|---|
| A combined live and installer image without privilege in the deb family | every command of the live builder except config exits unless run as the superuser, and the manual lists superuser access as a requirement; no unprivileged path is documented |
DEB-12a to DEB-12c, PRV-06.1, PRV-06.2 |
| A derivative that rebuilds the kernel or the bootloader and the signed boot chain of its upstream | firmware validates a signature over the binary; binaries a derivative builds itself carry the derivative’s signature and not the upstream’s, and reviewers advise reusing the signed components of another distribution where the kernel is not customised | IMP-01.1 to IMP-01.6, DEB-11a, DEB-11b, MAP-RPM-7 |
| A signed boot component from the mainstream signing authority | review and signing take months (measured data of 2026-11-21), with registration, key-protection and audit prerequisites; the 2011 CA is replaced by the 2023 CA for signing from 27 June 2026; code under GPLv3 is excluded | IMP-02.1 to IMP-02.9, DEB-11e to DEB-11h |
| Bit-for-bit reproducibility in every family | the project lists and tests some families and does not name others; the documentation of some families (Alpine, Fedora tests) records that tests are disabled | IMP-03.1 to IMP-03.6, DEB-10a to DEB-10c, NBS-02a, FBS-05a |
| Enrolling a producer platform key on consumer firmware | in user mode the Platform Key and the key databases change only with data signed by the current key holder; clearing the key needs a signed deletion or a platform-specific method; a console tool of the boot loader can enrol a key after a password step (physical presence, IMP-04.4); keys can be added directly to the firmware of the machines of a small deployment, and vendors in control of their firmware install keys (factory pre-enrolment, IMP-04.5); no row documents remote provisioning on a managed platform, the third case of SCF-PLT-024 |
IMP-04.1 to IMP-04.5 |
| An unattended-installation contract in every family | the NetBSD installer documents a menu and a defaults file, and no unattended mode is documented | IMP-05.1, IMP-05.2, NBS-03a to NBS-03c |
Versions checked: UEFI Specification 2.11 (UEFI Forum source repository, tag UEFI_2.11 read 2026-11-21); shim 16.1 (2025-08-13); Microsoft UEFI Signing Requirements version 9.0 (updated 2025-10-15, effective 2025-10-20); shim-review repository (main, 532 issues at 2026-11-17); Debian trixie reproducibility data (JSON of 2026-11-21); NetBSD 11.1; FreeBSD 15.1; Ubuntu security documentation page of 2026-11-21.
| ID | Statement | Version | Source | Checked |
|---|---|---|---|---|
| IMP-01.1 | The UEFI specification describes a digital signature as a hash of the data encrypted with the private key, embeds the signature of a UEFI executable in the certificate table of the PE/COFF image, and builds the image digest as the Authenticode PE image hash. | UEFI 2.11, chapter 32 | UEFI 2.11 source, 32 Secure Boot and Driver Signing | 2026-11-21 |
| IMP-01.2 | Firmware checks a UEFI image against the authorized signature database and the forbidden signature database before starting it, and an image whose signature is not found in the authorized database, or is found in the forbidden one, is deferred. | UEFI 2.11, chapter 32 | UEFI 2.11 source, 32 Secure Boot and Driver Signing | 2026-11-21 |
| IMP-01.3 | shim first tries the standard LoadImage() and StartImage() calls and, if Secure Boot rejects the binary, validates it against a built-in certificate and runs it when neither the binary nor the signing key is forbidden; a vendor certificate is built into shim at build time with VENDOR_CERT_FILE. | shim 16.1 | rhboot/shim README | 2026-11-21 |
| IMP-01.4 | Ubuntu documents that shim contains an embedded trust database that includes Canonical’s signing certificate and uses it to validate GRUB and the kernel when they are signed with Canonical’s UEFI key. | Ubuntu security documentation, page of 2026-11-21 | Ubuntu security documentation: UEFI Secure Boot | 2026-11-21 |
| IMP-01.5 | The shim-review reviewer guidelines say a vendor that does not need to customise the kernel should reuse shim, grub or systemd-boot, and kernel from another signed distribution. | shim-review main, file read 2026-11-21 | shim-review reviewer guidelines | 2026-11-21 |
| IMP-01.6 | SBAT records component names and generation numbers in a .sbat section of PE images for revocation by generation; the BootHole revocation added 3 certificates and 150 image hashes to the dbx, consuming 10 kB of the roughly 32 kB of revocation storage typically available. | shim main, SBAT.md read 2026-11-21 | rhboot/shim SBAT.md | 2026-11-21 |
| IMP-02.1 | The Microsoft UEFI CA 2011 expired on 27 June 2026 and is replaced by Microsoft UEFI CA 2023 for third-party boot loaders and Microsoft Option ROM UEFI CA 2023 for option ROMs. | Microsoft support page of 2026-11-21 | Microsoft: Windows Secure Boot certificate expiration and CA updates | 2026-11-21 |
| IMP-02.2 | The shim-review README states that as of 27 June 2026 shims sent to Microsoft can only be signed by the Microsoft UEFI CA 2023 and that signing with the 2011 CA is no longer possible. | shim-review main, file read 2026-11-21 | shim-review README | 2026-11-21 |
| IMP-02.3 | Microsoft’s UEFI signing requirements exclude code subject to GPLv3 and name GRUB 2, licensed under GPLv3, as an example that will not be signed; they also exclude internal-only code and sign only products for public availability. | Microsoft UEFI signing requirements 9.0 | Microsoft: Updated UEFI Signing Requirements | 2026-11-21 |
| IMP-02.4 | The requirements ask for private keys protected by a hardware cryptography module at a level at least equal to FIPS 140-2 Level 2, recommend an EV certificate, and ask for an independent security audit every 12 months, with an exemption for shim submissions that went through the shim review board and hand off only to open source boot loaders. | Microsoft UEFI signing requirements 9.0 | Microsoft: Updated UEFI Signing Requirements | 2026-11-21 |
| IMP-02.5 | Registration for the Microsoft hardware program needs an extended validation (EV) code signing certificate, a Microsoft Entra ID global administrator, company information (a D-U-N-S number or manually entered company details) and a legal contact who can sign agreements. | Microsoft Learn, page of 2026-11-21 | Microsoft Learn: Register for the Microsoft Hardware program | 2026-11-21 |
| IMP-02.6 | The shim-review template asks “Why are you unable to reuse shim from another distro that is already signed?”, and the README says a reasonable wait for a review can reach 2-3 months. | shim-review main, file read 2026-11-21 | shim-review README | 2026-11-21 |
| IMP-02.7 | In the shim-review issue tracker 92 issues carry the label new vendor: 86 are closed (39 with the label accepted, 47 without it, 4 of those superseded) and 6 are open (4 of them already labelled accepted); counted through the GitHub REST API on 2026-11-21 over 532 issues excluding pull requests. | shim-review, data of 2026-11-21 | shim-review issues labelled new vendor | 2026-11-21 |
| IMP-02.8 | For the 39 closed new-vendor issues labelled accepted the time from opening to closing has a median of 241 days (quartiles 91, 241 and 343; minimum 17, maximum 998); for the 21 of them opened since 2024-01-01 the median is 163 days; counted through the GitHub REST API on 2026-11-21. | shim-review, data of 2026-11-21 | shim-review issues labelled new vendor and accepted | 2026-11-21 |
| IMP-02.9 | Across all shim-review issues, 283 closed issues carry the label accepted, with a median of 76 days from opening to closing; the 47 closed new-vendor issues without that label have a median of 149 days; counted through the GitHub REST API on 2026-11-21. | shim-review, data of 2026-11-21 | shim-review issues labelled accepted | 2026-11-21 |
| IMP-03.1 | The Reproducible Builds list of involved projects names Alpine Linux, Arch Linux, Debian, Fedora, FreeBSD, GNU Guix, NetBSD, NixOS, openSUSE, OpenWrt and others, and does not name OpenBSD, illumos, Gentoo, Kali, Linux Mint or Rocky and AlmaLinux. | reproducible-builds.org, page of 2026-11-21 | absence: not stated by the project (the platforms named last); checked Reproducible Builds: involved projects on 2026-11-21 | 2026-11-21 |
| IMP-03.2 | The Reproducible Builds CI page lists coreboot, Debian, FreeBSD and NetBSD as tested within its infrastructure, Arch Linux, GNU Guix, NixOS and openSUSE among projects tested outside it, and Alpine Linux, Fedora and OpenWrt as projects whose tests are disabled because they became unmaintained. | reproducible-builds.org, page of 2026-11-21 | Reproducible Builds: CI tests | 2026-11-21 |
| IMP-03.3 | In the Debian test data file reproducible.json (last modified 2026-11-21 04:01 GMT) the suite trixie on amd64 has 36419 packages with status reproducible, 831 FTBR and 257 FTBFS (counted by suite, architecture and status; latest build date in the set 2026-09-14). The HTML overview of DEB-10a, updated 2026-11-21 00:06 UTC, gives the same first two counts and 258 for FTBFS; the two files are different data times. | Debian trixie 13.7 | Debian reproducible.json | 2026-11-21 |
| IMP-03.4 | The weekly FreeBSD test of the main branch reports 529 of 529 files (100.0%) reproducible, last run on 2026-11-19 at commit ef3c76fd2. | FreeBSD main (16-CURRENT) | Reproducible FreeBSD | 2026-11-21 |
| IMP-03.5 | The weekly NetBSD test of the master branch reports 29 of 33 built files reproducible (printed as 87.8%; 29/33 is 87.9% rounded), last run on 2026-11-20 at revision d0963c7c6, and lists the sparc64 ISO images, live image and base.tgz as unreproducible. | NetBSD-current (11.99) | Reproducible NetBSD | 2026-11-21 |
| IMP-03.6 | systemd-repart states that byte-for-byte reproducible images require –offline=yes, because populating a file system through the kernel writes metadata that cannot be corrected from userspace afterwards. | systemd 262.2 | systemd-repart(8) | 2026-11-21 |
| IMP-04.1 | While no Platform Key is enrolled the platform is in setup mode, where firmware does not require authentication to modify the Platform Key, key exchange keys and image security databases; after the Platform Key is enrolled it requires authentication for these changes. | UEFI 2.11, chapter 32 | UEFI 2.11 source, Firmware/OS Key Exchange: Creating Trust Relationships | 2026-11-21 |
| IMP-04.2 | In user mode the authenticated PK variable is written only when the new key is signed with the current platform private key, key exchange keys are written only with data signed with the current PK, and signature databases only with data signed by a key exchange key or the PK. | UEFI 2.11, chapter 32 | UEFI 2.11 source, Enrolling The Platform Key and Signature Database Update | 2026-11-21 |
| IMP-04.3 | The Platform Key can be cleared by a deletion signed with the current PK or by a secure platform-specific method, and leaving Deployed Mode needs a secure platform-specific method or deletion of the authenticated PK. | UEFI 2.11, chapter 32 | UEFI 2.11 source, Clearing The Platform Key | 2026-11-21 |
| IMP-04.4 | MokManager provides a console for enrolling new public keys; most of its operations require user authentication through a password that the user sets during the previous boot phase and that is valid for a single run of shim and MokManager. | Ubuntu security documentation, page of 2026-11-21 | Ubuntu security documentation: UEFI Secure Boot | 2026-11-21 |
| IMP-04.5 | The shim-review submission guide says that for small deployments it is often possible to add public keys directly into the firmware of the machines involved, and that hardware vendors in control of their firmware install their keys into the other keyrings. | shim-review main, file read 2026-11-21 | shim-review: submitting | 2026-11-21 |
| IMP-05.1 | sysinst is described as a menu-based program that installs or upgrades a NetBSD system and is usually invoked automatically when booting from installation media; its options are -C, -D, -f definition_file, -m and -p, and the definition file sets defaults such as machine, transfer directory, FTP and NFS sources, local device, target root mount and disk name. | NetBSD 11.1 | sysinst(8), NetBSD 11.1 | 2026-11-21 |
| IMP-05.2 | The NetBSD 11.0 and 11.1 announcements list changes to the installation process only as new split sets (base32, base64, debug32, debug64, manhtml) and describe no unattended-installation facility. | NetBSD 11.0 (2026-07-30), 11.1 (2026-11-02) | absence: not stated by the project (an unattended-installation facility); checked Announcing NetBSD 11.0 and Announcing NetBSD 11.1 on 2026-11-21 | 2026-11-21 |