generated from erix/meta
WIP: Retain and erase original filesystem key material #2
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!2
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/posix-compat"
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?
Summary and rationale
Make derived filesystem keys private single owners and erase derivation intermediates through their original lifetimes. Content and filename transforms borrow the owned keys; key lookup remains the caller's authority.
Tracking and scope
The linked component audit, implementation and consumer requirements remain part of this WIP review. The phase-wide guest and toolchain build requirements stay with the phase completion issue.
Architecture, authority and failure behavior
Key ownership gives
FscryptV2Keysno Copy, Clone, Debug or raw-field access. All three derived keys erase on drop. Content operations and filename encryption/decryption borrow the same owner; master input and returned plaintext remain caller-owned.The separate derivation module guards extraction/expansion material, pads and intermediate digests. Original HMAC states and AES schedules retain their own retirement. The crate performs no I/O and acquires no runtime key storage or lookup authority.
This cleanup preserves the existing EriX-specific KDF; it does not establish Linux interoperability or side-channel resistance. Signed dependency coordination and complete filesystem-consumer acceptance remain part of the review.
Validation evidence
Formatting, strict Clippy, warning-denied builds and documentation, unit tests, and applicable native/VM and consumer regressions remain required for the declared scope. Authored controls and older successful runs do not establish current full acceptance.
Review checklist
This review remains WIP until its declared scope and dependent requirements are complete.
erikinkinen referenced this pull request from erix/docs2026-10-02 05:44:35 +02:00
erikinkinen referenced this pull request from erix/e2fsd2026-10-02 05:44:47 +02:00
erikinkinen referenced this pull request from erix/integration2026-10-02 05:44:54 +02:00
erikinkinen referenced this pull request from erix/lib-ipc2026-10-02 05:45:10 +02:00
WIP: Align signed runtime dependenciesto WIP: Retain and erase original filesystem key materialThis source is now split into feature PRs, starting at #4 and ending at #5. Each PR links its prerequisite. The complete stack preserves the runtime changes and dependency declarations; obsolete pin checkpoints and documented source-acquisition differences are separated from feature behavior.
Closing this aggregate without merging. The replacement PRs remain WIP for their remaining integration and review.
Pull request closed