Download

Download NAILS

NAILS ships as one static binary for x86-64 Linux. It supports NixOS, Debian 13, Ubuntu 24.04 and 26.04, with systemd 254 or newer. Download and verify it away from your decoy system, then copy it onto your hidden volume.

Alpha Release candidate v0.3.0-rc.3 Release notes

  1. Choose where to download

    Never download or verify NAILS on the decoy system

    A copy of nails on the decoy disk, even a deleted one, can be recovered and identifies the tool. The browser's download history and the shell history would point to it as well, and so would the files the checking tools keep in your home directory: cosign's copy of Sigstore's public keys in ~/.sigstore, and the GitHub CLI's copy in ~/.cache/gh and its login token in ~/.config/gh. Reading these pages in the decoy system's browser also leaves them in its history.

    First installation
    Start a live environment that keeps nothing, unlock and mount the hidden volume there, and download into it. Another machine works too. First install from Tails walks through it with Tails.
    Updates
    Download from inside an active hidden session, into the hidden volume.
    New releases
    They appear in the releases feed, which any feed reader can follow without a GitHub account. Follow it inside a hidden session or on another device, never on the decoy, where the reader's subscription would name the tool. The feed shows a version as soon as its tag is pushed, even one that never gets a release. A version is out once GitHub Releases lists it with its files.
  2. Download the release

    v0.3.0-rc.3 Published · Release notes on GitHub · Changelog · Release announcement

    v0.3.0-rc.3 is a release candidate, published as a prerelease. The docs on this site describe it. NAILS is alpha software: test your exact machine, storage backend and procedure before you rely on it.

    The security policy says that only the most recent 0.2.x release carries security fixes. A problem in a release candidate is fixed in a new -rc.N, because a published release never changes.

    Files in release v0.3.0-rc.3
    File Size
    nails Static x86-64 Linux binary 7.6 MB
    nails-0.3.0-rc.3-x86_64-unknown-linux-musl.tar.gz The same binary with LICENSE and README.md 3.2 MB
    checksums.txt SHA-256 of the binary and the archive 188 B
    provenance.sigstore.json Signed build provenance of the binary and the archive 11 KB
    musl.openvex.json OpenVEX statements that the musl in the binary is patched against the CVEs it names 1.2 KB
    sbom.cdx.json CycloneDX software bill of materials 149 KB
    sbom.sigstore.json Signed attestation that binds the SBOM to the binary and the archive 156 KB
    vex.sigstore.json Signed attestation that binds the VEX document to the binary and the archive 11 KB

    For most people, nails, checksums.txt and provenance.sigstore.json are enough.

    In the place you chose in step 1, download the files with a browser or with curl. Neither way needs a GitHub account.

    tag=v0.3.0-rc.3for file in nails checksums.txt provenance.sigstore.json; do  curl -fsSLO "https://github.com/WitteShadovv/nails/releases/download/$tag/$file"done

    Other releases

    The latest stable release, v0.2.0, is the earlier design for NixOS only, with per-directory overlays and a YAML configuration. The docs on this site do not apply to it. See the release notes for v0.2.0 on GitHub. If you set up NAILS with it, read Upgrading from 0.2 in the install guide before you upgrade.

  3. Verify it

    1. Check the checksum

    sha256sum --check --ignore-missing checksums.txt

    It prints nails: OK. --ignore-missing skips the entries of checksums.txt whose files you did not download. The command still fails when none of them is present.

    A matching checksum shows that the download is complete and unchanged relative to checksums.txt. It says nothing about who built the file, because checksums.txt comes from the same page. The next check does.

    2. Check the build provenance with cosign

    cosign, the Sigstore project's command-line tool, checks the signed provenance in provenance.sigstore.json, a Sigstore bundle. Use cosign 3.1.3 or later, or 2.6.5 or later on the older 2.x line. Earlier releases can print Verified OK for an attestation that the command below must refuse, as the advisories GHSA-w6c6-c85g-mmv6 and GHSA-fx35-mq7g-6g98 describe. cosign version prints the release you have.

    Distribution packages lag behind: those of Debian 13, Ubuntu 26.04 and Ubuntu 26.10 are too old, while NixOS 26.05 has 3.1.3. Sigstore's installation guide lists other ways to get it, among them the static cosign-linux-amd64 binary from cosign's releases, and how to check that binary.

    tag=v0.3.0-rc.3identity="https://github.com/WitteShadovv/nails/.github/workflows/release.yml@refs/tags/$tag"cosign verify-blob-attestation \  --bundle provenance.sigstore.json \  --type slsaprovenance1 \  --certificate-oidc-issuer https://token.actions.githubusercontent.com \  --certificate-identity "$identity" \  --check-claims=true \  nails

    It prints Verified OK only when all of this holds:

    • The certificate in the bundle was issued to a GitHub Actions run of the NAILS repository's release workflow for the tag you downloaded. The attestation is signed with it, and the signature is in Sigstore's public transparency log.
    • The attestation is build provenance, not another kind of signed statement.
    • The attestation names the SHA-256 of the file you check. Never set --check-claims to false: cosign then checks only the signature, and any file passes.

    cosign fetches Sigstore's current public keys from tuf-repo-cdn.sigstore.dev each time it runs, so it needs a network connection. It asks GitHub for nothing. To check without a connection, give cosign the keys as a file, as the offline steps in Verify a release show.

    You can check the same bundle with the GitHub CLI instead. With --bundle, it needs no GitHub login:

    tag=v0.3.0-rc.3identity="https://github.com/WitteShadovv/nails/.github/workflows/release.yml@refs/tags/$tag"gh attestation verify nails --repo WitteShadovv/nails \  --bundle provenance.sigstore.json \  --cert-identity "$identity"

    What the checks show

    Integrity
    The file is the one the release lists.
    Provenance
    The release workflow of the NAILS repository built it from the tagged commit on a GitHub-hosted runner. It signed the provenance only after every NixOS end-to-end test, apart from the informational performance tests, passed on that commit. This meets SLSA v1.0 Build Level 2, not Level 3.
    Reproducibility
    Before attesting, the workflow built the binary and the archive a second time on a fresh runner and compared them and checksums.txt byte for byte.

    Published releases are immutable: GitHub lets no one change their files or move their tag. None of these checks says that the code is free of flaws. The threat model sets out what NAILS does and does not protect against. If this page and Verify a release ever differ, follow the guide in the repository.

  4. Copy it onto the hidden volume

    sudo install -m0755 /path/to/verified/nails /mnt/data/nails

    The binary lives only on the hidden volume and runs by its full path. Never put a copy, a symlink or a PATH entry on the decoy. The commands assume the hidden volume is mounted at /mnt/data.

    For an update, install it as /mnt/data/nails.new instead. Move it over /mnt/data/nails after the session, before you activate again, as the install guide describes. After a first installation, lay out the volume and run your first session.

    Continue with the install guide

Other ways

Build from source

Build from source only for updates, from inside an active hidden session. Before a session there is no upper layer to catch the build caches, so a first build would leave them on the decoy.

Build the binary

git clone https://github.com/WitteShadovv/nails /mnt/data/src/nailscd /mnt/data/src/nailsnix build .#nailssudo install -m0755 ./result/bin/nails /mnt/data/nails.new

This builds the same static x86-64 binary the releases ship. A plain cargo build --release builds for your host instead, linked against its C library. Move nails.new into place only while no session is active, as the install guide describes.

Reproduce a release

git clone https://github.com/WitteShadovv/nails && cd nailsgit checkout v0.3.0-rc.3nix build -L .#nails-release -o result --option accept-flake-config falsediff result/checksums.txt /path/to/downloaded/checksums.txt

No output from diff means your build produced the same binary and archive as the release. As when you verify a download, do this in a live environment or inside an active hidden session, never on the decoy. See what the reproducibility claim covers.

Channels that are not offered

There is no crates.io crate, no nixpkgs package, no .deb or .rpm package and no NixOS module for the decoy. Each would write a lasting record onto the decoy or into a public index. Distribution channels in the repository explains why.

Release history

Earlier releases

A fix reaches you as a new release, because a published release never changes. Interfaces and workflows can change between alpha releases, and the docs on this site describe NAILS 0.3.

All releases and prereleases on GitHub