[GH-ISSUE #318] Implement Windows native authority Node-API package #163

Open
opened 2026-10-15 18:21:54 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @morluto on GitHub (Jul 20, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/318

Build the native Node-API package that exposes the Windows primitives required by REA's trusted native authority boundary: reparse-safe handle-based file admission, private DACL creation/readback, and Job Object process ownership.

Acceptance:

  • Native addon compiles for Windows x64 with Node-API.
  • Each primitive is exposed as a typed, parseable observation that fails closed on unsupported OS/filesystem/reparse-tag.
  • No pathname-based authority is passed back as proof.
  • Unit tests on the native boundary shape pass.

Part of #287.

Originally created by @morluto on GitHub (Jul 20, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/318 Build the native Node-API package that exposes the Windows primitives required by REA's trusted native authority boundary: reparse-safe handle-based file admission, private DACL creation/readback, and Job Object process ownership. Acceptance: - Native addon compiles for Windows x64 with Node-API. - Each primitive is exposed as a typed, parseable observation that fails closed on unsupported OS/filesystem/reparse-tag. - No pathname-based authority is passed back as proof. - Unit tests on the native boundary shape pass. Part of #287.
Author
Owner

@tony-sebastian commented on GitHub (Oct 5, 2026):

I'd like to take this on, per the invitation in #287.

Plan: implement the three primitives as a Node-API addon under the accepted ADR-0004 shape — typed fail-closed observations, no pathname-based authority as proof, PROC_THREAD_ATTRIBUTE_JOB_LIST at creation (no post-creation assignment fallback) — carrying over the real-Windows adversarial cases from my #287 comment (junction/symlink substitution, DACL readback verification, breakaway/kill-on-close).

I'll open the PR from my fork. Could you assign this to me?

<!-- gh-comment-id:5999245923 --> @tony-sebastian commented on GitHub (Oct 5, 2026): I'd like to take this on, per the invitation in #287. Plan: implement the three primitives as a Node-API addon under the accepted ADR-0004 shape — typed fail-closed observations, no pathname-based authority as proof, `PROC_THREAD_ATTRIBUTE_JOB_LIST` at creation (no post-creation assignment fallback) — carrying over the real-Windows adversarial cases from my #287 comment (junction/symlink substitution, DACL readback verification, breakaway/kill-on-close). I'll open the PR from my fork. Could you assign this to me?
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
morluto/rea#163
No description provided.