Repository navigation
v0.22.0
Opens the crates.io roster: 29 crates for the registry, seven in-repo tools that stay out of it. The workspace previously set publish = false throughout, so the roster was implied rather than stated.
Breaking — the integrity key and slot magics changed. Any binary signed with the earlier key fails its power-up integrity check and must be re-signed with fips-integrity-sign --sign.
The command-line interface publishes as oxicrypt-cli. cargo install oxicrypt-cli installs an oxi binary, and nothing changes for anyone building from the repository. The crate name oxi was already registered on crates.io by an unrelated project.
Prebuilt C libraries are attached below — shared and static objects with oxicrypt.h for linux x86_64/aarch64, macOS x86_64/aarch64 and windows x86_64. 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.
LAMA manifest conformance is gated on every push, and the quickstart examples the manifest carries are compiled by the test suite rather than asserted in a YAML file.
Build toolchain pinned to Rust 1.97.1; MSRV held at 1.95.
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.