[GH-ISSUE #563] native: positional header decoding and remaining unvalidated parser coercions #291

Closed
opened 2026-10-15 18:23:31 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/563

Remaining scope

Remaining findings are positional otool header decoding, permissive Mach-O slice offset/size coercion, lipo alignment admission, codesign runtime-field interpretation, and the unused load-command file_offset surface. Admit complete producer representations and reject malformed values with actionable diagnostics. Format fixtures can establish parser behavior; they do not replace real native-tool verification for support claims.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/563 ## Remaining scope Remaining findings are positional otool header decoding, permissive Mach-O slice offset/size coercion, lipo alignment admission, codesign runtime-field interpretation, and the unused load-command file_offset surface. Admit complete producer representations and reject malformed values with actionable diagnostics. Format fixtures can establish parser behavior; they do not replace real native-tool verification for support claims. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.
bsakaguchi 2026-10-15 18:23:31 +00: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
morluto/rea#291
No description provided.