Frame conditional regular file creation custody #81
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-ipc!81
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/conditional-regular-file-creation"
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?
Create and retain the same original regular-file candidate only under fresh parent permission evidence and explicit creation metadata. Preserve original keys through uncertain replies and keep native and provider creation families distinct.
Depends on #80.
WIP: Frame conditional regular file creation custodyto Frame conditional regular file creation custodyPrepared the merge history at 9fcfc8d3 to remove duplicate upstream patches and integrate the feature on its prepared prerequisite history. The feature tree is unchanged.
Conditional regular-file creation is now composed onto the current creation-mask history. It preserves fresh parent permission evidence, explicit metadata and the original cleanup key. Parsing those fields does not authenticate a caller or authorize a provider operation.
The signed current-parent preview is
8d497850a21fd3d4a67c5c3f9f30bf77ce1e59fa. The original feature branch is preserved. This rewritten history needs its own review.