Revert main-key ActivityPub signature regression #41
No reviewers
Labels
No labels
activitypub
actor
admin
ai-safety
article
articles
atproto
bug
cli
configuration
content
dev-environment
docker
enhancement
feature
federation
fediverse
forgejo
garage
health
how-to
logging
markdown
mastodon
media
navigation
opengraph
passkeys
preview
priority:medium
production
release
rendering
s3
settings
setup
status:active
status:done
status:inprogress
technical
webauthn
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
erik/slugkit.com!41
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task-d213c262-revert-main-key-regression"
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?
Summary
#multikey-1task-becaf72balready established that Mastodon stores the Fedify 2 RSA key as#multikey-1and rejects#main-keydeliveryVerification
Task: task-d213c262
Follow-up: investigate actor Update-specific rejection with
#multikey-1without regressing the known working post/follow delivery key.Review summary
Approved. This reverts PR #40, which contradicted the previously verified Mastodon fix in
task-becaf72b. That task established that Mastodon stores the Fedify 2 actor key as#multikey-1and rejects outbound delivery signed with#main-key.Acceptance criteria coverage
#multikey-1.#multikey-1and rejecting#main-keyfor delivery signatures.Verification
npm run typechecknpm test -- --run src/federation/__tests__/delivery.test.ts src/federation/__tests__/routes.test.tsnpm testnpm run buildFollow-up
The actor Update-specific Mastodon rejection still needs investigation, but we should not regress the known-working follow/post fanout key behavior while doing that.
Blocking issues
None.
Verdict
Approved.