v0.1.0

Verify your download

Cryptographic provenance (GitHub / Sigstore attestation)

Every artifact below is signed via GitHub Artifact
Attestations,
which uses Sigstore under the hood. The signature proves
the artifact was produced by this exact workflow run on
this exact commit SHA, no human had a chance to swap it
after the fact.

Verify with the GitHub CLI (one-liner):

# Install gh once if you don't have it:
#   sudo apt install gh   |   sudo dnf install gh   |   brew install gh
gh attestation verify <downloaded-file> --owner penthertz
# Prints "Loaded digest ..." then "PASS" with the
# workflow run + commit SHA the artifact came from.

Offline check (no gh needed)

Every artifact also has a SHA-256 in SHA256SUMS.txt
(attached to this release):

# Linux / macOS:
sha256sum -c SHA256SUMS.txt   # Linux
shasum -a 256 -c SHA256SUMS.txt   # macOS

# Windows (PowerShell):
Get-FileHash luksbox-*.msi -Algorithm SHA256
# then compare to the `*.msi` row in SHA256SUMS.txt

Trust chain summary

Artifacts on this release page are uploaded only by the
GitHub Actions release workflow that ran on this tagged
commit (.github/workflows/release.yml in the repo).
The commit itself is GPG-signed by the maintainer, the
upload uses GitHub's OIDC release token, and the
Sigstore attestation above pins the signature to that
workflow run. GPG-signed release tarballs
(SHA256SUMS.txt.asc) and full SLSA L3 provenance are
on the roadmap.

For at-a-glance SHA-256 checking against the published
values:

File	SHA-256
luksbox-0.1.0-1.aarch64.rpm	903e9ebb3e12bea8fa17b17dfd3b93370664ef3e625c1e1431feae066ffbc2ca
luksbox-0.1.0-1.x86_64.rpm	f47082d7d8cfa97e43873dca87d1094206e3691b69bc459eb242b14d7dcc93e2
luksbox-v0.1.0-aarch64-linux-jammy.tar.gz	a26320117dab7d333dcc95ff2be6c76663d473124739177924cf9bc3d4ca0ef7
luksbox-v0.1.0-aarch64-macos-portable.tar.gz	36c9c70192d6d59551875e1742b74c6bd94f39e24e6845990a421107fe8983ca
luksbox-v0.1.0-aarch64-macos.dmg	68978046cfef646d457f3e707ac42124a5efc4e75ba69ac50ccaafc6185c45cb
luksbox-v0.1.0-x86_64-linux-noble.tar.gz	67e8984cfa93bf623c89b73cdc21159fb7842a071587212bea8fc17c39113002
luksbox-v0.1.0-x86_64-windows.msi	d1b712657f238791edaf51f2a058e67f7c9e90fcd5c3539d217e793e73b5de84
luksbox-v0.1.0-x86_64-windows.zip	ee1a3aabc3fc596d4233420f7928b5050c88ab9cc2e7863c0cc6b54f17e91e46
luksbox_0.1.0-1_jammy_amd64.deb	4c82f3d984a7fccee0770138254810c36eaff36a5df5d640b866d535d0dd09d0
luksbox_0.1.0-1_jammy_arm64.deb	9920fe669b99b18ea8d060331575e608d02b66bfe4fa0d0874a6e38ec9399592
luksbox_0.1.0-1_noble_amd64.deb	548d97b00d22d29d5c9a012d6c488e4d3c007dd7f65fe909409a595c095ae1a9
luksbox_0.1.0-1_noble_arm64.deb	97e070f0087acaaa015afeaf939ee10a4b69fc9693755b068e48befd2df04a92

Install

Linux (Ubuntu 22.04, Debian 11/12, Mint 21.x, .deb):
download luksbox_*_jammy_amd64.deb (or _arm64) and
install with sudo apt install ./luksbox_*_jammy_amd64.deb.
Pulls in libfido2-1, libfuse3-3, and libtss2-*
automatically. Registers a luksbox-gui desktop
launcher and a MIME type for .lbx files.

Linux (Ubuntu 24.04+, Debian 13+ trixie, .deb):
download luksbox_*_noble_amd64.deb (or _arm64) and
install with sudo apt install ./luksbox_*_noble_amd64.deb.
Same package layout as the jammy build, but with
t64-transitioned dependency names (libssl3t64,
libfido2-1t64, libtss2-mu-4.0.1-0t64, etc.). The
jammy and noble .deb files cannot be installed
interchangeably, the dependency names differ.

Linux (Fedora / RHEL / Rocky / Alma, .rpm): download
luksbox-*.x86_64.rpm (or aarch64.rpm) and install
with sudo dnf install ./luksbox-*.x86_64.rpm (or
sudo rpm -i). One .rpm covers every rpm-based
distro, RPM uses SONAMEs for shared-library
dependencies which are stable across releases.
Pulls in libfido2 and fuse3-libs automatically.

Linux (x86_64, generic tarball): tar xzf luksbox-v0.1.0-x86_64-linux-jammy.tar.gz && cd luksbox-v0.1.0-x86_64-linux-jammy && ./install.sh
For Arch / NixOS / Alpine / any non-deb non-rpm distro.
The jammy variant has the broadest glibc compatibility;
if you are on a very recent distro and prefer the noble
build, swap -jammy for -noble in the filename.
Installs to ~/.local/bin and registers a desktop launcher.
Use ./install.sh --system for system-wide install, or
./install.sh --uninstall to remove. Requires
libfido2-1 (and libfuse3-3 for mount):
sudo apt install libfido2-1 libfuse3-3 (Debian/Ubuntu)
or sudo dnf install libfido2 fuse3-libs (Fedora/RHEL).

Linux (aarch64): tar xzf luksbox-v0.1.0-aarch64-linux-jammy.tar.gz && cd luksbox-v0.1.0-aarch64-linux-jammy && ./install.sh
Same runtime deps and installer as x86_64. Built natively
on a GitHub ARM64 runner, no QEMU emulation. Same
jammy/noble distinction applies as for the .deb above.

macOS (Apple Silicon), .dmg (recommended): download
luksbox-v0.1.0-aarch64-macos.dmg,
double-click, drag LUKSbox.app onto the Applications
link, eject. The .app is self-contained, libfido2 +
transitive dependencies are bundled inside, you do NOT
need brew install libfido2. Double-clicking a .lbx
file in Finder opens it directly in LUKSbox.

macOS (Apple Silicon), portable .tar.gz: download
luksbox-v0.1.0-aarch64-macos-portable.tar.gz,
extract from Terminal with
tar xzf luksbox-v0.1.0-aarch64-macos-portable.tar.gz.
Ships the bare CLI + GUI binaries (bin/luksbox,
bin/luksbox-gui) with their dylib closure under
Frameworks/. Run in place: ./bin/luksbox --help or
./bin/luksbox-gui &. No .app, no Gatekeeper warning,
no quarantine xattr to clear (when extracted via
Terminal). See README-MACOS.txt inside for the full
layout + caveats.

mount (both builds) requires macFUSE
(https://macfuse.io/). Install with:

  brew install --cask macfuse

macFUSE installs a kernel extension. macOS will block
it on first install — approve under System Settings
→ Privacy & Security, then reboot. On Apple Silicon
you may also need to lower the security policy via
Recovery Mode → Startup Security Utility → Reduced
Security before the kext can load. Both are one-time
per-machine setup. Once macFUSE is approved,
luksbox mount works directly.

(FUSE-T (https://www.fuse-t.org/) is a kext-free
alternative we'd love to support, but the underlying
fuser Rust crate hard-requires the macFUSE libfuse2
ABI on macOS. FUSE-T provides only libfuse3. Switching
would require swapping our FUSE wrapper crate.)

macOS (Intel): not shipped, build from source with
cargo build --profile release-hardened on an Intel Mac
with brew install libfido2 (the release-hardened
profile matches the hardening flags used for the shipped
Apple-Silicon binary). The CI matrix entry for
x86_64-apple-darwin is commented out in
.github/workflows/release.yml, GitHub's macos-13
runner has been intermittently blocking releases.

Windows prerequisite (both flavors below): install
WinFsp 2.x first from https://winfsp.dev/rel/.
The LUKSbox binary statically links against
winfsp-x64.dll (provided by WinFsp), so without it the
binary fails to start with STATUS_DLL_NOT_FOUND. The
MSI refuses to install if WinFsp is missing and shows a
clear message; the portable .zip has no installer to
warn you, so install WinFsp first either way.

Windows (x86_64), recommended: download
luksbox-v0.1.0-x86_64-windows.msi,
double-click. The MSI installs LUKSbox to
C:\Program Files\LUKSbox\, prepends both
C:\Program Files\LUKSbox\ and <WinFspInstall>\bin
to the system PATH (so the loader resolves
winfsp-x64.dll and luksbox works in cmd /
PowerShell), drops a Start menu shortcut, and registers
the .lbx file extension (double-click any .lbx in
Explorer to open it). Uninstall via Apps & Features.

Windows (x86_64), portable: unzip
luksbox-v0.1.0-x86_64-windows.zip
and run the .exe in place. No installation, no Start
menu entry, no PATH change. Same binaries as the MSI.
Because nothing was added to PATH, you must either
(a) run from a shell where <WinFspInstall>\bin is on
PATH, or (b) drop a copy of winfsp-x64.dll next to
luksbox.exe in the unzipped folder.

libfido2 is statically linked into the .exe; no runtime
install needed for FIDO2.

See the Verify your download section at the top for
checksum verification commands.

Full Changelog: https://github.com/PentHertz/LUKSbox/commits/v0.1.0