Skip to content

Avoid false secret detections for authenticated canary attestations #467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
8Dionysus merged 2 commits into from
Sep 8, 2026
Merged

Avoid false secret detections for authenticated canary attestations #467

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2aed2f2
fix(mcp): exclude authenticated canary attestations from secret scan
8Dionysus Sep 8, 2026
f86ddf5
chore(kag): regenerate owner family for canary fix
8Dionysus Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,9 @@ Tracking starts with the community-docs baseline for this repository.
- Compact recognized nested session-evidence packet containers within the
existing MCP output ceiling while preserving owner refs, freshness reasons,
and explicit omissions; unknown oversized payloads remain blocked.
- Keep authenticated canary attestations out of generic secret-material
screening while scanning all other model and owner payload fields, so
generated Ed25519 signatures cannot trigger false secret detections.

- Preserve all parallel pytest failures in the ordinary last-failed cache for
explicit edit-time retries, retaining unfinished work conservatively and
Expand Down
Loading