[FEATURE] Transport complete access ACL entries on retained permission revisions #3

Closed
opened 2026-09-29 10:17:23 +02:00 by erikinkinen · 0 comments
Owner

Problem and motivation

Permission snapshots can report a present access ACL and its complete count, but consumers cannot acquire the entries. A count or an incomplete ACL cannot support a deny-only compatibility decision. Transport must retain original object/revision correlation without imposing an unrelated small ACL limit.

Proposed behavior and scope

Exact canonical pages bind the original handle/revision, complete count and contiguous range. E2fsd rechecks complete metadata and both attribute stores, preserves valid observations for later pages/conditional effects, and retires observed failures while clearing staging. Ramfsd explicitly refuses pages for absent storage. Libposixabi joins pages in caller-owned storage, poisons and clears failed or abandoned assembly, and exposes only complete canonical, mode-consistent metadata. Known absence has a separate constructor. No codec, ID, hash or collected view supplies native caller/provider authentication or authority.

Nineteen controls are authored but unrun: six wire, seven collection, four actual ext dispatch and two Ramfsd dispatch controls. They cover full IDs, large ACLs, malformed/mixed/stale evidence, incomplete cleanup, reply capacity, close and later conditional truncation. The original reduced decoder and checked ACL fixture are shared. Changed Rust files are below 1,000 lines (maximum 891), inline rustdoc and existing missing_docs enforcement are retained, and Rust 2021 formatting is applied. Component contracts and both relevant manual sections are updated. Full ext scans per page cost O(A * P) ACL work; no measured performance claim is made.

Native Vfsd/Posixd caller/route/effect integration, value-inode ACL payloads, persistent ACL-aware mutation and remaining provider effects remain open in the permission feature.

Add private ACCESS_ACL_PAGE_V1 at 0x63E. A 40-byte request carries correlation/opcode, original handle, snapshot revision, first entry ordinal, positive maximum returned count and reserved zero. A successful response has a 56-byte prefix: correlation/opcode/status/reserved, original handle/revision, complete total count, first ordinal, returned count and reserved zero. It carries that many eight-byte canonical entries: u16 tag, u16 read/write/execute bits, and u32 qualifier. Tags distinguish owner, named user, owning group, named group, mask and other; base qualifiers are zero and named IDs retain all 32 bits. Invalid tags/bits, duplicate or reversed rows, lengths, ranges and reserved fields refuse.

Pages are nonempty ranges within a present ACL. Buffer geometry bounds each transfer, with no extra total-entry ceiling. Failure returns only the fixed correlated prefix with zero evidence fields. Parsing validates representation; correlation against the original request/snapshot and complete cross-page ACL validation remain necessary.

E2fsd serves canonical local ACL pages through its existing private dispatch. Each read revalidates the complete original permission fingerprint and epoch; matching reads preserve the snapshot for later pages and conditional effects. Refused reads clear private output staging, and evidence invalidated by observed failure/change cannot later revive. Separate value-inode payloads remain unsupported and explicitly refuse until their integrity/acquisition implementation is completed. Providers with proven absent ACLs return no synthetic entries.

Libposixabi adds a borrowed caller-storage assembler bound to a complete snapshot. It accepts only contiguous, correlated pages, poisons and clears staging on failed assembly, and returns a canonical mode-consistent metadata view only after all entries arrive. No partial ACL, failed fetch or unknown provider support becomes mode-only fallback. A mode-only view requires explicit known fields and proven ACL absence.

Authority, security and reliability

The mediator must retain actual native caller/operation admission and original provider-route custody before reading or using this descriptive protocol. IDs, ordinals, revisions, hashes and local assembly do not supply those capabilities. Snapshot lifetime ends with handle/route retirement; stale revisions cannot select replacement metadata. No new path, mount selector, credential, endpoint or receipt is accepted. All provider scratch and consumer collection storage are caller/deployment-owned. Reply capacity is checked before provider work; error prefixes contain no usable metadata.

Acceptance criteria

Checklist
  • Implement exact request, response and canonical-entry codecs with complete framing, reserved-field, overflow, order and correlation checks.
  • Serve actual E2fsd pages from the retained original snapshot and complete checked local ACL, with stale/unsupported/failure staging refusal and ordinary descriptor semantics preserved.
  • Assemble complete contiguous pages in caller-owned storage, validating cross-page ordering, final completeness, mode correspondence and explicit absence without claiming native authentication.
  • Author wire, real-provider and consumer positive/negative/large-input controls; execution remains waived by user.
  • Update component contracts, technical manual, signed immutable dependency/catalog adoption and related reviews/master checklist.

Alternatives and tradeoffs

An unbounded one-message ACL would confuse transport capacity with filesystem support. A fixed small entry array would silently limit valid ACLs. Paging preserves full counts while allowing explicit deployment storage policy. Fresh full evidence checks conservatively detect observed media changes; they cost a complete local ACL scan per page. The normal caller requests the available payload capacity. Measurement and further optimization must preserve freshness and remain deferred under the testing override. Source parsing/collection alone is deliberately insufficient to authenticate native authority.

Tracking and rollout

Coordinate native policy, shared ABI review, compatibility metadata review, ext review, manual, catalog adoption and phase completion. Existing snapshot and conditional-operation encodings stay stable. Publish original source revisions bottom-up across the complete affected dependency graph. Native Vfsd/Posixd enforcement, value-inode payload support, ACL-aware persistent mutation and full EriX/toolchain guest builds remain open.

Related records and contracts
Repository Links
lib-ipc issue 3
## Problem and motivation Permission snapshots can report a present access ACL and its complete count, but consumers cannot acquire the entries. A count or an incomplete ACL cannot support a deny-only compatibility decision. Transport must retain original object/revision correlation without imposing an unrelated small ACL limit. ## Proposed behavior and scope Exact canonical pages bind the original handle/revision, complete count and contiguous range. E2fsd rechecks complete metadata and both attribute stores, preserves valid observations for later pages/conditional effects, and retires observed failures while clearing staging. Ramfsd explicitly refuses pages for absent storage. Libposixabi joins pages in caller-owned storage, poisons and clears failed or abandoned assembly, and exposes only complete canonical, mode-consistent metadata. Known absence has a separate constructor. No codec, ID, hash or collected view supplies native caller/provider authentication or authority. Nineteen controls are authored but unrun: six wire, seven collection, four actual ext dispatch and two Ramfsd dispatch controls. They cover full IDs, large ACLs, malformed/mixed/stale evidence, incomplete cleanup, reply capacity, close and later conditional truncation. The original reduced decoder and checked ACL fixture are shared. Changed Rust files are below 1,000 lines (maximum 891), inline rustdoc and existing missing_docs enforcement are retained, and Rust 2021 formatting is applied. Component contracts and both relevant manual sections are updated. Full ext scans per page cost O(A * P) ACL work; no measured performance claim is made. Native Vfsd/Posixd caller/route/effect integration, value-inode ACL payloads, persistent ACL-aware mutation and remaining provider effects remain open in [the permission feature](https://git.erikinkinen.fi/erix/posixd/issues/10). Add private ACCESS_ACL_PAGE_V1 at 0x63E. A 40-byte request carries correlation/opcode, original handle, snapshot revision, first entry ordinal, positive maximum returned count and reserved zero. A successful response has a 56-byte prefix: correlation/opcode/status/reserved, original handle/revision, complete total count, first ordinal, returned count and reserved zero. It carries that many eight-byte canonical entries: u16 tag, u16 read/write/execute bits, and u32 qualifier. Tags distinguish owner, named user, owning group, named group, mask and other; base qualifiers are zero and named IDs retain all 32 bits. Invalid tags/bits, duplicate or reversed rows, lengths, ranges and reserved fields refuse. Pages are nonempty ranges within a present ACL. Buffer geometry bounds each transfer, with no extra total-entry ceiling. Failure returns only the fixed correlated prefix with zero evidence fields. Parsing validates representation; correlation against the original request/snapshot and complete cross-page ACL validation remain necessary. E2fsd serves canonical local ACL pages through its existing private dispatch. Each read revalidates the complete original permission fingerprint and epoch; matching reads preserve the snapshot for later pages and conditional effects. Refused reads clear private output staging, and evidence invalidated by observed failure/change cannot later revive. Separate value-inode payloads remain unsupported and explicitly refuse until their integrity/acquisition implementation is completed. Providers with proven absent ACLs return no synthetic entries. Libposixabi adds a borrowed caller-storage assembler bound to a complete snapshot. It accepts only contiguous, correlated pages, poisons and clears staging on failed assembly, and returns a canonical mode-consistent metadata view only after all entries arrive. No partial ACL, failed fetch or unknown provider support becomes mode-only fallback. A mode-only view requires explicit known fields and proven ACL absence. ## Authority, security and reliability The mediator must retain actual native caller/operation admission and original provider-route custody before reading or using this descriptive protocol. IDs, ordinals, revisions, hashes and local assembly do not supply those capabilities. Snapshot lifetime ends with handle/route retirement; stale revisions cannot select replacement metadata. No new path, mount selector, credential, endpoint or receipt is accepted. All provider scratch and consumer collection storage are caller/deployment-owned. Reply capacity is checked before provider work; error prefixes contain no usable metadata. ## Acceptance criteria <details> <summary>Checklist</summary> - [x] Implement exact request, response and canonical-entry codecs with complete framing, reserved-field, overflow, order and correlation checks. - [x] Serve actual E2fsd pages from the retained original snapshot and complete checked local ACL, with stale/unsupported/failure staging refusal and ordinary descriptor semantics preserved. - [x] Assemble complete contiguous pages in caller-owned storage, validating cross-page ordering, final completeness, mode correspondence and explicit absence without claiming native authentication. - [x] Author wire, real-provider and consumer positive/negative/large-input controls; execution remains waived by user. - [x] Update component contracts, technical manual, signed immutable dependency/catalog adoption and related reviews/master checklist. </details> ## Alternatives and tradeoffs An unbounded one-message ACL would confuse transport capacity with filesystem support. A fixed small entry array would silently limit valid ACLs. Paging preserves full counts while allowing explicit deployment storage policy. Fresh full evidence checks conservatively detect observed media changes; they cost a complete local ACL scan per page. The normal caller requests the available payload capacity. Measurement and further optimization must preserve freshness and remain deferred under the testing override. Source parsing/collection alone is deliberately insufficient to authenticate native authority. ## Tracking and rollout Coordinate [native policy](https://git.erikinkinen.fi/erix/posixd/issues/10), [shared ABI review](https://git.erikinkinen.fi/erix/lib-ipc/pulls/2), [compatibility metadata review](https://git.erikinkinen.fi/erix/lib-posixabi/pulls/3), [ext review](https://git.erikinkinen.fi/erix/e2fsd/pulls/3), [manual](https://git.erikinkinen.fi/erix/docs/pulls/4), [catalog adoption](https://git.erikinkinen.fi/erix/integration/pulls/12) and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). Existing snapshot and conditional-operation encodings stay stable. Publish original source revisions bottom-up across the complete affected dependency graph. Native Vfsd/Posixd enforcement, value-inode payload support, ACL-aware persistent mutation and full EriX/toolchain guest builds remain open. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | lib-ipc | [issue 3](https://git.erikinkinen.fi/erix/lib-ipc/issues/3) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:46 +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/lib-ipc#3
No description provided.