Skip to content

fix(channels): restrict private-channel invitations - #4612

Open
jmecom wants to merge 1 commit into
mainfrom
codex/security-private-channel-invite-authority
Open

fix(channels): restrict private-channel invitations#4612
jmecom wants to merge 1 commit into
mainfrom
codex/security-private-channel-invite-authority

Conversation

@jmecom

@jmecom jmecom commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

This change requires an active owner or administrator for third-party additions to private channels. The relay validator and transactional database authority enforce the same rule, including removed-member reactivation and role-change paths.

Idempotent self-target behavior remains available, while ordinary members can no longer extend private-channel access to another identity.

Testing

  • git diff --check origin/main...codex/security-private-channel-invite-authority
  • Rebased onto origin/main at 5c98932
  • Full CI pending

Originating Buzz thread: buzz://message?channel=3928fe05-df61-4b5d-b9c7-d623b9b10ea1&id=3c6c02312f763fbe0d2bfc33a6c1a362f91d0354f3d18b039cf7a0558c1439d1

Require an active owner or admin for third-party private-channel additions in both relay validation and the transactional database authority. Preserve idempotent self-targeting.

Co-authored-by: Jordan Mecom <jm@squareup.com>
Signed-off-by: Jordan Mecom <jm@squareup.com>
@jmecom
jmecom marked this pull request as ready for review August 3, 2026 21:00
@jmecom
jmecom requested a review from a team as a code owner August 3, 2026 21:00
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