libsoliton/soliton/fuzz/fuzz_targets/fuzz_auth_respond.rs
Kamal Tufekcic 1d99048c95
Some checks failed
CI / lint (push) Successful in 1m37s
CI / test-python (push) Successful in 1m49s
CI / test-zig (push) Successful in 1m39s
CI / test-wasm (push) Successful in 1m54s
CI / test (push) Successful in 14m44s
CI / miri (push) Successful in 14m18s
CI / build (push) Successful in 1m9s
CI / fuzz-regression (push) Successful in 9m9s
CI / publish (push) Failing after 1m10s
CI / publish-python (push) Failing after 1m46s
CI / publish-wasm (push) Has been cancelled
initial commit
Signed-off-by: Kamal Tufekcic <kamal@lo.sh>
2026-04-02 23:48:10 +03:00

33 lines
1 KiB
Rust

#![no_main]
use libfuzzer_sys::fuzz_target;
use soliton::{
auth::auth_respond,
identity::{generate_identity, GeneratedIdentity, IdentitySecretKey},
primitives::xwing,
};
use std::sync::LazyLock;
struct ClientKeys {
sk: IdentitySecretKey,
}
// Fixed client identity — keygen is expensive, amortise across corpus runs.
static CLIENT: LazyLock<ClientKeys> = LazyLock::new(|| {
let GeneratedIdentity { secret_key: sk, .. } = generate_identity().unwrap();
ClientKeys { sk }
});
const CT_SIZE: usize = 1120;
fuzz_target!(|data: &[u8]| {
if data.len() < CT_SIZE {
return;
}
let Ok(ct) = xwing::Ciphertext::from_bytes(data[..CT_SIZE].to_vec()) else { return; };
// auth_respond must never panic regardless of ciphertext content.
// Exercises: X-Wing decapsulation with arbitrary ct, HMAC-SHA256 derivation.
// KEM decapsulation always "succeeds" (returns some shared secret); the HMAC
// path always runs and the result is returned as Zeroizing<[u8; 32]>.
let _ = auth_respond(&CLIENT.sk, &ct);
});