[BUG] Preserve endpoint-source custody during partial initialization #65
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/rootd#65
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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
Endpoint-source initialization and terminal cleanup need one original ownership
record across partial construction and failed acknowledgements. This repair
covers authenticated service sources and the Named and Deviced source families.
Reproduction
Exercise source initialization with explicit failures before admission, during
creation and after an earlier source succeeds. Check that cleanup accounts for
each admitted source and leaves unrelated bindings untouched. Detailed security
analysis is retained privately under SECURITY.md.
Expected and actual behavior
Expected: prove the selected destination absent before admission, record its
prospective custody before entering creation, and preserve that custody until
exact retirement is established. Repeated admission must refuse. Existing
initialization and cleanup do not consistently share this per-source record.
Environment and identity
control roles; no added child recipients or rights.
Evidence and prior checks
The repair must cover partial construction, returned creation uncertainty,
occupied destinations, repeated admission, and exact drop/absence cleanup.
Original native gates and configured image limits remain required. No exploit,
private diagnostic paths or guest acceptance claims are included here.
Tracking
Related: terminal clock provisioning
and Alpha 1 acceptance.