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.
Both directions interoperate with the Signify scheme, and fixtures generated by
signify-ts and
KERIA pin the exact bytes.
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 |
server |
RequestVerifier checks a request; ResponseSigner signs a response; Freshness bounds created |
timestamp |
The Signify-Timestamp header value |
A client uses authentication, and a server uses server. RequestVerifier does no replay check
until it is given a Freshness.
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, and each directory has a README with its provenance. Tests
read them and never need Node or the network. tools/reference-vectors regenerates authing and
ending:
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.