Skip to content

SQLite3 Multiple Ciphers 2.6.1 (based on SQLite 3.54.0)

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 12:25
· 3 commits to main since this release
v2.6.1
This tag was signed with the committer’s verified signature.
utelle Ulrich Telle
GPG key ID: 5CDE3A2F37D1A951
Verified
Learn about vigilant mode.
45d4ed3
This commit was signed with the committer’s verified signature.
utelle Ulrich Telle
GPG key ID: 5CDE3A2F37D1A951
Verified
Learn about vigilant mode.

Changes since previous release

This is a maintenance release. It fixes build problems with some toolchains and
target platforms that were discovered after the release of version 2.6.0.
There are no functional changes. For the changes introduced in version 2.6.0
please refer to the release notes of version 2.6.0.

Fixed

  • Fixed build failure with older Emscripten versions (for example, emsdk 2.0.23 as used for .NET 6.0 WebAssembly): explicit_bzero() is now only used with Emscripten 3.x or newer. Older versions fall back to the generic implementation in sqlite3mcSecureZeroMemory().
  • Fixed build failure on 32-bit targets (for example, armhf) caused by the 128-bit integer type used in the poly1305 code: the 128-bit type (and the 64-bit poly1305 implementation based on it) is now only used if the compiler provides __int128 (__SIZEOF_INT128__ is defined). Otherwise, the 32-bit implementation is used.

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 configure script for POSIX compliant systems,
  • Precompiled SQLite Android library (see SQLite Android Bindings),
  • Precompiled bundles of sqlite3.wasm and 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.6.1-SHA256SUMS.pem \
  --signature sqlite3mc-2.6.1-SHA256SUMS.sig \
  --certificate-identity-regexp '^https://github.com/utelle/SQLite3MultipleCiphers/.*' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com \
  sqlite3mc-2.6.1-SHA256SUMS
Assets 14
Loading