zbox

ZboxFS

ZboxFS is a zero-details, privacy-focused in-app file system. Its goal is to help application store files securely, privately and reliably. By encapsulating files and directories into an encrypted repository, it provides a virtual file system and exclusive access to authorised application.

Unlike other system-level file systems, such as [ext4], [XFS] and [Btrfs], which provide shared access to multiple processes, ZboxFS is a file system that runs in the same memory space as the application. It provides access to only one process at a time.

By abstracting IO access, ZboxFS supports a variety of underlying storage layers, including memory, OS file system, RDBMS and key-value object store.

Disclaimer

ZboxFS is under active development, we are not responsible for any data loss or leak caused by using it. Always back up your files and use at your own risk!

Features

• Everything is encrypted :lock:, including metadata and directory structure, no knowledge can be leaked to underlying storage
• State-of-the-art cryptography: AES-256-GCM (hardware), XChaCha20-Poly1305, Argon2 password hashing and etc., powered by [libsodium]
• Support varieties of underlying storages, including memory, OS file system, RDBMS, Key-value object store and more
• Files and directories are packed into same-sized blocks to eliminate metadata leakage
• Content-based data chunk deduplication and file-based deduplication
• Data compression using [LZ4] in fast mode, optional
• Data integrity is guaranteed by authenticated encryption primitives (AEAD crypto)
• File contents versioning
• Copy-on-write (COW :cow:) semantics
• ACID transactional operations
• Built with [Rust] :hearts:

Comparison

Many OS-level file systems support encryption, such as [EncFS], [APFS] and [ZFS]. Some disk encryption tools also provide virtual file system, such as [TrueCrypt], [LUKS] and [VeraCrypt].

This diagram shows the difference between ZboxFS and them.

Below is the feature comparison list.

Supported Storage

ZboxFS supports a variety of underlying storages. Memory storage is enabled by default. All the other storages can be enabled individually by specifying its corresponding Cargo feature when building ZboxFS.

* Visit zbox.io to learn more about Zbox Cloud Storage.

Specs

Limits

Metadata

Capabilities

Allocation and layout policies

Storage fragmentation

How to use

For reference documentation, please visit documentation.

Requirements

• [Rust] stable >= 1.38
• [libsodium] >= 1.0.17

Supported Platforms

• 64-bit Debian-based Linux, such as Ubuntu
• 64-bit macOS
• 64-bit Windows
• 64-bit Android, API level >= 21

32-bit and other OS are NOT supported yet.

Usage

Add the following dependency to your Cargo.toml:

[dependencies]
zbox = "0.9.2"

If you don't want to install libsodium by yourself, simply specify libsodium-bundled feature in dependency, which will automatically download, verify and build libsodium.

[dependencies]
zbox = { version = "0.9.2", features = ["libsodium-bundled"] }

Example

…

Build with Docker

ZboxFS comes with [Docker] support, which made building ZboxFS easier. Check each repo for more details.

• [zboxfs/base] Base image for building ZboxFS on Linux

• [zboxfs/wasm] Docker image for building WebAssembly binding

• [zboxfs/nodejs] Docker image for building Node.js binding

• [zboxfs/android] Docker image for building Android Java binding

Static linking with libsodium

By default, ZboxFS uses dynamic linking when it is linked with libsodium. If you want to change this behavior and use static linking, you can enable below two environment variables.

On Linux/macOS,

export SODIUM_LIB_DIR=/path/to/your/libsodium/lib
export SODIUM_STATIC=true

On Windows,

set SODIUM_LIB_DIR=C:\path\to\your\libsodium\lib
set SODIUM_STATIC=true

And then re-build the code.

cargo build

Performance

The performance test is run on a Macbook Pro 2017 laptop with spec as below.

Test result: