Skip to content

fix(acp): admit explicit allowlist authors only in verified DMs - #7642

Open
KanjiTheryo wants to merge 1 commit into
block:mainfrom
KanjiTheryo:fix/acp-dm-verified-allowlist
Open

KanjiTheryo wants to merge 1 commit into
block:mainfrom
KanjiTheryo:fix/acp-dm-verified-allowlist

Conversation

@KanjiTheryo

Copy link
Copy Markdown

Summary

Selected-people / --respond-to=allowlist currently admits listed authors in group channels but drops their 1:1 DMs. The inbound author gate treats DMs as owner/sibling-only, so an allowlisted person can talk to the agent in a stream and then look like a dead agent in DM.

This change admits explicit allowlist keys only in verified DMs. It does not open DMs for anyone, and missing/failed/unrecognized channel metadata never grants an external author access.

Mode Verified DM Unknown/unrecognized metadata
owner-only Owner and verified siblings Owner and verified siblings
allowlist Explicit keys, owner, verified siblings Owner and verified siblings; listed externals denied
anyone Owner and verified siblings Owner and verified siblings
nobody Everyone denied Everyone denied

Removing a key from the effective allowlist revokes admission. Signature checks, membership, workflow attribution, and session/audience boundaries are unchanged. Normal and setup listeners share the policy.

Closest existing PRs

CONTRIBUTING asked for a duplicate search. Closest open work:

Happy to close this in favor of one of those if maintainers prefer that shape.

Related: #4487 (respond-to not reaching the running process is separate; this only fixes the author gate).

Testing

  • bin/cargo test -p buzz-acp author_gate: 29 passed, including dm_allowlist::signed_dm_policy_matrix_and_revocation and production-listener DM boundaries.
  • No installer, desktop package, or hosted-relay change.

Rosie/Theryo runtime notes stay on our private fork and are not in this PR.

Signed-off-by: Kanji Kawanabe <kanji@aipersona.com>
(cherry picked from commit 2ac51d9)
Signed-off-by: Kanji Kawanabe <kanji@aipersona.com>
(cherry picked from commit 02e1ffc)
Signed-off-by: Kanji Kawanabe <kanji@aipersona.com>
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 4cd82f513214aad11c2b742ce7cc7c681e8e32a0...56ea9ef0f6909f63514096dbf1c4f9fda34fb44b.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 56ea9ef0f6909f63514096dbf1c4f9fda34fb44b to authorize a new review.
Any previous review applies only to its recorded range.

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