Found in the 0.E security review (Minor). Only the storage key is length-validated (try_into::<[u8;32]>); WORM/ledger keys loaded from the vault are not. Not exploitable (HMAC accepts any length; keys always minted at 32 bytes) but a truncated stored key would be used silently. Add explicit length validation.
Found in the 0.E security review (Minor). Only the storage key is length-validated (try_into::<[u8;32]>); WORM/ledger keys loaded from the vault are not. Not exploitable (HMAC accepts any length; keys always minted at 32 bytes) but a truncated stored key would be used silently. Add explicit length validation.
Superseded by #200 (M6) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.
Superseded by #200 (M6) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in the 0.E security review (Minor). Only the storage key is length-validated (try_into::<[u8;32]>); WORM/ledger keys loaded from the vault are not. Not exploitable (HMAC accepts any length; keys always minted at 32 bytes) but a truncated stored key would be used silently. Add explicit length validation.
Superseded by #200 (M6) in the roadmap restructuring (milestones M1–M7). The replacement story carries the full, self-contained spec for a remote implementer. See docs/ROADMAP.md, docs/STORY-WORKFLOW.md, docs/HANDOFF.md.