Skip to content

Access groups for cracker binaries - #2500

Open
s3inlc wants to merge 3 commits into
886-stack-1-uploadfrom
886-stack-2-cracker-access-group
Open

s3inlc wants to merge 3 commits into
886-stack-1-uploadfrom
886-stack-2-cracker-access-group

Conversation

@s3inlc

@s3inlc s3inlc commented Sep 17, 2026

Copy link
Copy Markdown
Member

Adds access-group isolation for cracker binaries. Each binary now belongs to an access group, and API visibility, creation, updates, task selection, agent assignment, and downloads enforce user/agent membership. Existing binaries migrate to the default group, and binaries are reassigned there when a group is deleted.

@s3inlc
s3inlc added this pull request to stack #2501 September 17, 2026 12:36
@s3inlc
s3inlc force-pushed the 886-stack-2-cracker-access-group branch 2 times, most recently from c4f469c to a32ce4d Compare September 22, 2026 12:17
@s3inlc
s3inlc marked this pull request as ready for review September 22, 2026 12:24
@s3inlc
s3inlc requested a review from jessevz September 22, 2026 12:24
@s3inlc
s3inlc force-pushed the 886-stack-2-cracker-access-group branch from a32ce4d to da5fdb3 Compare September 22, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant