Prefer legacy ActivityPub publicKey for Mastodon #47
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!47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "task-d213c262-legacy-publickey-only"
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
assertionMethodfrom local actor serialization for nowpublicKeypointing at/activitypub/keys/{actor}/main-keyacct:{actor}@{domain}Why
Mastodon 4.7 prefers
assertionMethodover legacypublicKeyduring actor refresh. With a poisoned cached key state, that prevents refresh from producing a usable legacy RSA key. Publishing only legacypublicKeyshould make the refresh path use the same key we sign with.Verification
Task: task-d213c262