Skip to content

v0.24.0

Choose a tag to compare

@caraka caraka released this 19 Aug 19:14
· 37 commits to main since this release

Note: the oxi binary in oxicrypt-cli-v0.24.0-macos-aarch64.tar.gz does not launch on Apple silicon, because macOS rejects its code signature after integrity signing (issue #280). Use v0.25.0, where the macOS artifacts are code signed after integrity signing and launch.

Completes the pre-operational software integrity test on macOS and Windows. The signer could produce a Mach-O or PE artifact the runtime had no way to verify, so the module never became operational on either; both now verify the bytes the loader mapped. Two crates carry the work and both publish for the first time — oxicrypt-imageread, which reads the module's own loaded image through mach_vm_read_overwrite and ReadProcessMemory, and oxicrypt-integrity-sign, the signer, so cargo install oxicrypt-integrity-sign now resolves.

Signed oxi binaries ship for the first time, one per platform, in their own oxicrypt-cli- tarball with a provenance record. oxi selftest runs the module's self-tests on demand and reports each one by name with the vector it is checked against, ending in an explicit indicator; a failure places the module in the error state. oxi --integrity reports the pre-operational integrity test's outcome, the extent it covered, and the two commands that make an unsigned build start.

Four notices for consumers

The release artifacts are renamed. The C library archive is oxicrypt-ffi-<tag>-<platform>.tar.gz, was oxicrypt-<tag>-<platform>.tar.gz through v0.23.2 — it is one delivery form of the module rather than the module. Releases up to v0.23.2 keep their original names; a script that fetches by asset name needs updating.

The integrity slot format is not backward compatible: every artifact must be re-signed. initialize() is removed. initialize_with_tests(integrity, tests) and initialize_with_profile take the integrity group as a parameter, and a module initialized with an empty group enters the new IntegrityUnverified state instead of becoming operational. No interface exists, at any visibility, to declare the test passed without running it.

oxicrypt-xmss is scoped to signature verification. keygen, sign and XmssPrivateKey are removed from the crate, and oxi_xmss_keygen and oxi_xmss_sign from the C ABI. Address encoding is aligned with RFC 8391, so signatures at any leaf index other than zero verify differently than in earlier versions. The crate now carries externally produced verification vectors from six independent sources, and its power-up self-test is a CAST over one of them.

The CNSA profiles match CNSSP-15 as published, each membership citing the clause that admits it. Services outside the suite return Error::AlgorithmRestricted where earlier versions permitted them — under CNSA 1.0 that includes SHA-256, SHA-512 and their HMAC, DRBG and KDF variants, the post-quantum algorithms and the stateful hash-based schemes; under CNSA 2.0, the Keccak-family hashes and XOFs. A deployment that needs the previous breadth selects the new AlgorithmProfile::Migration, or Unrestricted for anything beyond the two suites.

Artifacts

Prebuilt binaries are attached below for linux x86_64/aarch64, macOS x86_64/aarch64 and windows x86_64. oxicrypt-ffi- carries the shared and static objects with oxicrypt.h; oxicrypt-cli- carries the signed oxi binary. Each archive carries both licences and a BUILD-PROVENANCE.txt recording the target triple, glibc floor, rustc version, source commit and integrity MACs, alongside a SHA-256 checksum. Consuming the module from C needs no Rust toolchain.

Full detail in CHANGELOG.md.


oxicrypt holds no NIST certifications. It implements FIPS 140-3 Level 1 requirements and its algorithms are validated on NIST's ACVP demonstration server.