adiantum

README

Go adiantum SQLite VFS

This package wraps an SQLite VFS to offer encryption at rest.

The "adiantum" VFS wraps the default SQLite VFS using the Adiantum tweakable and length-preserving encryption.
In general, any HBSH construction can be used to wrap any VFS.

The default Adiantum construction uses XChaCha12 for its stream cipher, AES for its block cipher, and NH and Poly1305 for hashing.
Additionally, we use Argon2id to derive 256-bit keys from plain text where needed. File contents are encrypted in 4 KiB blocks, matching the default SQLite page size.

The VFS encrypts all files except super journals: these never contain database data, only filenames, and padding them to the block size is problematic. Temporary files are encrypted with random keys, as they may contain database data. To avoid the overhead of encrypting temporary files, keep them in memory:

PRAGMA temp_store = memory;

[!IMPORTANT] Adiantum is a cipher composition for disk encryption. The standard threat model for disk encryption considers an adversary that can read multiple snapshots of a disk. The only security property that disk encryption provides is that all information such an adversary can obtain is whether the data in a sector has or has not changed over time.

The encryption offered by this package is fully deterministic.

This means that an adversary who can get ahold of multiple snapshots (e.g. backups) of a database file can learn precisely: which blocks changed, which ones didn't, which got reverted.

This is weaker than other forms of SQLite encryption that include some nondeterminism. With limited nondeterminism, an adversary can't distinguish between pages that actually changed, and pages that got reverted; a VACUUM can fully rebuild the database file, preventing this differential analysis.

[!CAUTION] This package does not claim protect databases against tampering or forgery.

The major practical consequence of the above point is that, if you're keeping "adiantum" encrypted backups of your database, and want to protect against forgery, you should sign your backups, and verify signatures before restoring them.

This is weaker than other forms of SQLite encryption that include page-level MACs. Page-level MACs can protect against forging individual pages, but can't prevent them from being reverted to former versions of themselves.

[!TIP] The "xts" VFS also offers encryption at rest. AES-XTS uses only NIST and FIPS 140 approved cryptographic primitives.

Documentation

Overview

Package adiantum wraps an SQLite VFS to offer encryption at rest.

The "adiantum" vfs.VFS wraps the default VFS using the Adiantum tweakable, length-preserving encryption.

Importing package adiantum registers that VFS:

import _ "github.com/ncruces/go-sqlite3/vfs/adiantum"

To open an encrypted database you need to provide key material.

The simplest way to do that is to specify the key through an URI parameter:

• key: key material in binary (32 bytes)
• hexkey: key material in hex (64 hex digits)
• textkey: key material in text (any length)

However, this makes your key easily accessible to other parts of your application (e.g. through vfs.Filename.URIParameters).

To avoid this, invoke any of the following PRAGMAs immediately after opening a connection:

PRAGMA key='D41d8cD98f00b204e9800998eCf8427e';
PRAGMA hexkey='e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855';
PRAGMA textkey='your-secret-key';

For an ATTACH-ed database, you must specify the schema name:

ATTACH DATABASE 'demo.db' AS demo;
PRAGMA demo.textkey='your-secret-key';

Index

• func Wrap(base vfs.VFS, cipher HBSHCreator) vfs.VFS
• type HBSHCreator

Functions

func Wrap

func Wrap(base vfs.VFS, cipher HBSHCreator) vfs.VFS

Wrap wraps a base VFS to create an encrypting VFS, possibly using a custom HBSH cipher construction.

To use the default Adiantum construction, set cipher to nil.

The default construction uses a 32 byte key/hexkey. If a textkey is provided, the default KDF is Argon2id with 64 MiB of memory, 3 iterations, and 4 threads.

Types

type HBSHCreator

type HBSHCreator interface {
	// KDF derives an HBSH key from a secret.
	// If no secret is given, a random key is generated.
	KDF(secret string) (key []byte)

	// HBSH creates an HBSH cipher given a key.
	// If key is not appropriate, nil is returned.
	HBSH(key []byte) *hbsh.HBSH
}

HBSHCreator creates an hbsh.HBSH cipher given key material.