Repository navigation
chore: update 9 stale fuzz targets for cachekit-core 0.1.1 API #114
Description
Problem
9 of 14 fuzz targets in rust/fuzz/ fail to compile against cachekit-core 0.1.1. The API has evolved (e.g., encrypt_aes_gcm renamed to encrypt_with_keys, StorageEnvelope field changes) but the fuzz targets were never updated.
Broken targets
| Target | Error |
|---|---|
encryption_roundtrip |
no method named encrypt_aes_gcm |
encryption_nonce_reuse |
no method named encrypt_aes_gcm |
encryption_truncated_ciphertext |
no method named decrypt_aes_gcm |
encryption_aad_injection |
no method named encrypt_aes_gcm |
encryption_large_payload |
no method named encrypt_aes_gcm |
integration_layered_security |
no method named encrypt_aes_gcm + trait bounds |
byte_storage_corrupted_envelope |
StorageEnvelope field access changes |
byte_storage_integer_overflow |
StorageEnvelope field access changes |
byte_storage_empty_data |
StorageEnvelope field access changes |
byte_storage_checksum_collision |
StorageEnvelope field access changes |
Working targets (4)
byte_storage_compressbyte_storage_decompressbyte_storage_format_injectionencryption_key_derivation
Additional fix needed
rust/fuzz/Cargo.toml previously depended on the non-existent package cachekit-storage. Fixed in PR #113 to depend on cachekit-core directly (the fuzz targets use cachekit-core's internal module paths).
Scope
Update all 9 broken fuzz targets to match cachekit-core 0.1.1's current API. No new targets needed.
Activity
ci: fix fuzz-smoke — correct crate dependency, skip broken targets
ci: fix EXDEV error in fuzz-smoke rustup nightly install (#113)
chore(deps): bump cachekit-core from 0.1.1 to 0.2.0 (#140)
ci: restore Security Deep pipeline and gate publish on attestation (#137
test: fix 9 broken fuzz targets and track cachekit-core 0.2.0 (#145)
fix(fuzz): fuzz the codec that ships — core 0.4.0, all 14 targets, fa…