Downloads and verification
Tato stránka zatím není přeložená, zobrazuje se anglická verze.
UFLinux images are published as GitHub Releases of
UFlinux-project/uflinux3. Every
artifact is built by GitHub Actions from a version tag, and the workflow attaches build
attestations to what it publishes.
What a release contains
Section titled “What a release contains”| Artifact | Naming | Notes |
|---|---|---|
| Live ISO | uflinux-VERSION-ARCH.iso |
Six architectures |
| Checksums | SHA256SUMS |
Covers the ISOs |
| Device images | uflinux-VERSION-DEVICE-ARCH.img.zst |
Zstandard level 12 |
| Device checksums | …img.zst.sha256 |
One sidecar per image |
| Package repository | apk/v3.24/uflinux |
Signed APKs plus APKINDEX |
The repository URL for the current baseline is:
https://repo.uflinux.org/apk/v3.24/uflinuxThat is a custom Pages domain — a CNAME record pointing at the repository’s
github.io site. The separate apps repository carrying uflinux-files lives at
https://apps-repo.uflinux.org/ and is signed by its own uflinux3.ec384.pub key.
Verifying a download
Section titled “Verifying a download”Checksums first:
sha256sum -c SHA256SUMSFor device images, the sidecar sits next to the file:
sha256sum -c uflinux-0.1.0-rpi-aarch64.img.zst.sha256Then verify the build attestation with the gh CLI:
gh attestation verify uflinux-0.1.0-x86_64.iso --repo UFlinux-project/uflinux3An attestation ties the artifact to the workflow run that produced it, which a checksum alone cannot.
Which artifact to trust most
Section titled “Which artifact to trust most”Publication requires green build reports for all six architectures and green boot reports for both x86_64 firmware modes. That means:
- x86_64 is the only architecture whose ISO has actually been booted — in CI, on BIOS and UEFI, including installation onto XFS and reboot from the installed disk.
- The other five architectures are built and their packages and ISOs published, but no virtual machine is started with them. Expect rough edges.
- Device images are supplementary. They are attached to the release but cannot block it, and none has an automated boot test.
A configured test is not evidence of a successful run. For anything beyond x86_64, check the workflow results and the attached build records rather than assuming a row passed. See Architectures and boot.
Signing
Section titled “Signing”Packages are signed with an EC P-256 or P-384 key published as uflinux.ec.pub. apk v2 has
no ECDSA signature stream, so the signature is carried in the SHA-256 stream and the stream
name RSA256 describes the digest rather than the algorithm. The apps repository uses a
separate key, uflinux3.ec384.pub, which uflinux-release installs and which is also
published next to the apps index.
Development and pre-release images are signed with an ephemeral development key, not the release key. Do not treat a development image as a persistent-key release or use it to validate public updates.
Derived from README.md inUFlinux-project/uflinux3(b4f4817). Report documentation problems inUFlinux-project/docs.