Documentation

Documentation

Everything you need to install, use, and understand LUKSbox.

LUKSbox is a Rust-based encrypted-container manager with four keyslot families: passphrase, FIDO2 / Windows Hello, TPM 2.0 (Linux), and hybrid post-quantum (passphrase / FIDO2 / TPM combined with ML-KEM). The container mounts as a real drive on Linux (FUSE), macOS (macFUSE), and Windows (WinFsp), and ships in three flavours that share the same on-disk format and the same Container core: the luksbox CLI, the luksbox wizard interactive TUI, and the luksbox-gui desktop application.

Use LUKSbox for shared or backup copies, not as your only copy

LUKSbox is built to make a secondary copy of your data safe to put in places you don't control: a cloud sync folder, a USB stick you carry around, a vault you send to a colleague or client. It is not designed to be the sole place a file lives.

Like every encrypted container, a LUKSbox vault is a single point of failure. If the .lbx file is corrupted, lost, or every keyslot becomes inaccessible, the data is gone. The forensic toolkit helps with many damage scenarios but cannot recover bytes that are no longer on disk or no longer AEAD-tagged.

Best fits:

Always keep an unencrypted copy somewhere you trust (your local disk, a personal cloud, a NAS) for any file you cannot afford to lose. Treat the LUKSbox vault as the travelling copy, not the master copy.

The full no-warranty / no-liability / export-controls / data-loss notice lives on the Disclaimer page and in DISCLAIMER.md in the source repository. The Apache 2.0 license covers the legal floor; the disclaimer restates it in plain English.

Pick a path

Documentation map

Section Contents
Getting started Install, quickstart, platform notes
Keyslots Passphrase, FIDO2, TPM 2.0, post-quantum
CLI Every subcommand with examples
TUI Interactive wizard walkthrough
GUI Desktop application screen-by-screen
Operations Recovery, backup, mount lifecycle
Security Architecture, threat model, cryptography, tests, audit, disclosure
Build From source, reproducible builds, verification

The full spec for what happens cryptographically per operation lives in the source repository at docs/CRYPTO_SPEC.md.