generated from erix/meta
Bound derived filesystem key lifetimes #5
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-fs-crypto!5
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/owned-filesystem-key-lifetimes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Keep derived filesystem keys in one private owner and borrow them for content and filename operations. Guard extraction, expansion, pads and intermediate digests through their original lifetimes.
Caller inputs, returned plaintext and compiler-created copies remain outside this storage-erasure guarantee.
This branch also includes the completed downstream features from #8.
This branch also includes the completed downstream features from #6, #8.
WIP: Bound derived filesystem key lifetimesto Bound derived filesystem key lifetimesReady for review. The library ownership contract and its controls are complete; the remaining linked prerequisites are merge gates.
The filename format has a separate CBC-CS3 correction in #8, backed by independent raw and padded ciphertext answers and AES #11. This key-ownership PR is unchanged. Any persisted nonstandard prototype bytes need explicit migration; no cipher-mode fallback is introduced.
Merged the approved downstream work from #8. The upstream PR retains its own remaining scope and completion requirements.
Merged the approved downstream work from #6, #8. The upstream PR retains its own remaining scope and completion requirements.