Repository navigation
gate: keep the user-agent policy under an unverified claim - #32
Merged
Merged
Conversation
An unsigned or invalid Signature-Agent claim set the attribution to the claim and skipped the user-agent lookup, so a request naming a blocked agent in its user agent was decided by the claim's default policy. The user-agent policy is now always evaluated for unverified requests and the stricter of the two applies.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
jaschadub
added a commit
that referenced
this pull request
Nov 4, 2026
gate: keep the user-agent policy under an unverified claim
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An unsigned or invalid
Signature-Agentclaim set the attribution to the claim and skipped the user-agent lookup, so withagent_actions.meta_muse: blockanddefault_agent_action: allow, amuse-agent/1.0request that added a bogusSignature-Agentheader was allowed. The user-agent policy is now always evaluated for unverified requests and the stricter of the two policies applies. Only a cryptographically verified identity bypasses the user-agent check.Regression test:
unsigned_claim_cannot_lift_a_user_agent_block.