Skip to content

Invalidate pending signatures by per-key policy generation - #205

Merged
GDR merged 1 commit into
ui/refactorfrom
codex/policy-generation-hardening
Oct 24, 2026
Merged

GDR merged 1 commit into
ui/refactorfrom
codex/policy-generation-hardening

Conversation

@GDR

@GDR GDR commented Oct 24, 2026

Copy link
Copy Markdown
Owner

Key revocation now advances a per-fingerprint policy generation shared by both socket listeners. Pending requests capture it and revalidate before returning a signature, so changing key type/capabilities away and back cannot revive an old request. Rename revocation also works after the old public-index entry disappears. Untrusted control requests cannot advance generations; daemon restarts discard prior generations with all pending requests.

Validation: all 938 tests passed before the final two focused additions; all 13 generation tests then passed, including actual authenticated policy ABA changes during prompts, fresh retry, both listeners, concurrent invalidation, restart, renamed keys, and cross-key token rejection. 302 changed lines. Targets ui/refactor; installed app unchanged.

@GDR
GDR merged commit 06b36c7 into ui/refactor Oct 24, 2026
1 check passed
@GDR
GDR deleted the codex/policy-generation-hardening branch October 24, 2026 15:25
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