[BUG] Preserve endpoint-source custody during partial initialization #65

Open
opened 2026-11-15 05:11:04 +01:00 by erikinkinen · 0 comments
Owner

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

  • Component: Rootd native bootstrap and endpoint-source initialization.
  • Source: the service provisioning and cleanup contracts retained by this branch.
  • Platform: x86-64 native bootstrap; a guest failure is not claimed.
  • Authority: only the explicitly selected source destinations and original kernel
    control roles; no added child recipients or rights.
  • Last known working revision: not established.

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.

## 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 - Component: Rootd native bootstrap and endpoint-source initialization. - Source: the service provisioning and cleanup contracts retained by this branch. - Platform: x86-64 native bootstrap; a guest failure is not claimed. - Authority: only the explicitly selected source destinations and original kernel control roles; no added child recipients or rights. - Last known working revision: not established. ## 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](https://git.erikinkinen.fi/erix/rootd/pulls/22) and [Alpha 1 acceptance](https://git.erikinkinen.fi/erix/integration/issues/65).
erikinkinen added this to the Alpha 1 milestone 2026-11-15 05:11:04 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/rootd#65
No description provided.