mosaicstack/stack
1
0
Fork 0
Code Issues 81 Pull Requests 1 Actions Packages Projects Releases 15 Wiki Activity

roster storage evolution: file (integrity-hardened) -> DB + RLS #800

New Issue
Open
opened 2026-07-16 20:11:45 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-07-16 20:11:45 +00:00
Owner
Copy Link

Part of EPIC #796 (design-first).

Storage evolution for the roster store.

  • NOW: file-form roster acceptable IFF protected against malicious corruption — integrity, ownership, permissions (non-world-writable, owned by the runtime user).
  • LATER: DB-centric persistence when better; RLS on the DB where possible, ESPECIALLY in federated environments.

Security: roster write-path integrity is a secrev surface (a corrupted roster = attacker-controlled terminal embeds in the webUI). Design the file-form integrity model and the DB+RLS migration path. Coordinate with sub-issue 1 (data model) and stack#791 (ownership/permissions manifest).

Part of EPIC #796 (design-first). Storage evolution for the roster store. - NOW: file-form roster acceptable IFF protected against malicious corruption — integrity, ownership, permissions (non-world-writable, owned by the runtime user). - LATER: DB-centric persistence when better; RLS on the DB where possible, ESPECIALLY in federated environments. Security: roster write-path integrity is a secrev surface (a corrupted roster = attacker-controlled terminal embeds in the webUI). Design the file-form integrity model and the DB+RLS migration path. Coordinate with sub-issue 1 (data model) and stack#791 (ownership/permissions manifest).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#800
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?