Repository navigation
SQLite3 Multiple Ciphers 2.7.0 (based on SQLite 3.54.1)
Changes since previous release
This release focuses on robustness and security hardening.
An update is strongly recommended.
Details can be found in the change log and the commit history.
Security
- Key setup errors (URI parameters,
ATTACH, also with another VFS) can no longer silently result in an unencrypted database - VLE: the scope is now cryptographically bound to encrypted values (new value format version 2). Existing values stay readable until re-encrypted, see the CHANGELOG for the migration.
- Argon2: the result of the key derivation is now checked; invalid parameters are rejected
Fixes
- Backup API could deliver corrupted databases (#280)
- Reworked rekey handling, hot-journal detection and handling of partial page reads (#291–#294)
- ChaCha20 counter overflow prevented, so that all implementations deliver identical results
- Many mutex/thread-safety and out-of-memory fixes, including a deadlock with sorter worker threads
- Build fixes for WebAssembly/WASI (#286, new option
SQLITE3MC_WASM_USE_GETENTROPY) and for platforms withoutmemset_s(wxSQLite3 #134)
New
- VLE:
sqlite3mc_vle_version(), optionlegacy=0|1, INTEGER scopes - Raw keys/salts can be specified unambiguously with the prefixes
raw:hex:andraw:bin:
Compatibility notes
- WAL legacy mode is no longer supported
aes256cbcnow obeyskdf_iter;sqlite3mc_configreturns the actually active value and is, likesqlite3mc_codec_data, direct-only- VLE passphrase/salt in UTF-16 databases are now interpreted as UTF-8
- Encryption for temporary files must be enabled before a temporary database is used
Release Summary
Important
📌 The amalgamation source package including configure is still experimental. 📌
Currently, only POSIX compliant systems are supported. Support files for building on Windows are included, but will only be adapted if the need arises.
Please report any issue you may experience using the GitHub issue tracker.
❗ Please share your experiences with this source package. TIA. ❗
Notes
This release contains the following precompiled binaries:
- SQLite3 binaries for Windows (SQLite3 shell and DLLs) with resp. without enabled ICU support in variants for 32-bit and 64-bit Windows. The SQLite3 shell applications support the SQLite Archive feature,
- Source code amalgamation (amalgamation) - a single C source file and a single C header file,
- Source code amalgamation (autoconf) - a single C source file and a single C header file - including a
configurescript for POSIX compliant systems, - Precompiled SQLite Android library (see SQLite Android Bindings),
- Precompiled bundles of
sqlite3.wasmand its JavaScript APIs, ready for use in web applications (see SQLite3 WebAssembly), in two variants:*-wasm.zip: baseline build, runs in any WebAssembly runtime,*-wasm-simd128.zip: build with WebAssembly SIMD128 enabled for better performance (e.g. for ChaCha20); requires a runtime with SIMD support (current versions of Chrome, Firefox, Safari and Node.js).
The variant is fixed at build time. Applications that need to support both should select the matching binary when loading the module, e.g. via feature detection (WebAssembly.validate()or the wasm-feature-detect library).
Verification
Release artifacts were built by GitHub Actions and are published with GitHub Artifact Attestations for provenance verification.
The SHA256SUMS file containing the checksums of the release artifacts is additionally signed using Sigstore Cosign.
To verify the integrity and authenticity of the checksum file, install Cosign and run:
cosign verify-blob \
--certificate sqlite3mc-2.7.0-SHA256SUMS.pem \
--signature sqlite3mc-2.7.0-SHA256SUMS.sig \
--certificate-identity-regexp '^https://github.com/utelle/SQLite3MultipleCiphers/.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
sqlite3mc-2.7.0-SHA256SUMS