#296: remove the unsubscribe-token dual-verify window early #299
No reviewers
Labels
No Label
area:auth
area:docs
area:export
area:ops
area:storage
area:supply-chain
auth
backend
blocked
collab
deployment
docs
effort:L
effort:M
effort:S
frontend
plugins
qa
vs-nfd
vs-nfd:blocker
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: stwaidele/dorfteich#299
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "issue-296-remove-legacy-verify"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes the work for #296 (operator decision at the ADR 0020 acceptance): the dual-verify transition window is removed early —
LEGACY_VERIFY_UNTIL, the legacy derivation and its verify branch are gone; verification is subkey-only. Consequence stated honestly: unsubscribe links in mails sent before the #188 deploy stop working; recipients use the in-app notification settings. A regression test pins that the legacy derivation can never verify again;security.md§key hierarchy records the removal.Issue #296 will be closed manually after green CI + merge.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AUtYMxwTCMHG9mVHnwbFg8