keri-http-auth
KERI HTTP message signatures and request authentication in Rust: the Signature and
Signature-Input headers, the exact bytes a signature covers, and the Signify-Timestamp header.
The behavior and wire bytes match signify-ts, checked
against fixtures it generates, and the header formats are the ones keripy and KERIA speak.
Extracted from the signify-rs project.
Modules
| Module | Purpose |
|---|---|
header |
Validated header names and values, and a bounded collection that refuses duplicates |
fields |
The Signature header: signages, markers and parameters, formatted and parsed strictly |
input |
The Signature-Input header and the signature base it describes |
authentication |
RequestSigner signs a request; ResponseVerifier checks a response |
timestamp |
The Signify-Timestamp header value |
A Signify client uses all five to sign what it sends to a KERIA agent and to verify what comes back. The parsers and the signature base are the same ones the agent needs on its side; signing a response and verifying a request are not provided yet.
Freshness is not decided here: created is returned to the caller, and replay policy belongs to
the transport.
Use
use ;
use KeyTransferability;
use RequestSigner;
use ;
use ;
Prerequisites
- Rust 1.97 or newer (
rustupinstalls the toolchain pinned inrust-toolchain.toml). - Nightly Rust and
cargo-fuzz, only for fuzzing. - Node 22 or newer, only to regenerate the fixtures.
Build and test
Reference fixtures
fixtures/ holds the expected outputs, generated by signify-ts at the commit pinned in
tools/reference-vectors/package.json. Tests read them and never need Node or the network.
Each fixture directory has a README with its provenance.
Fuzzing
License
Either of
- Apache License, Version 2.0 (LICENSE-APACHE)
- MIT license (LICENSE-MIT)
at your option. Contributions are dual licensed the same way unless you say otherwise.