fix(federation): reject actors that point at other hosts
A remote actor could set its inbox or shared inbox to a third-party host, so our signed deliveries went there. It could also claim another actor's followers collection, which the visibility checks trust. Validate fetched actors and incoming actor Updates: inbox, endpoints.sharedInbox, followers, following, featured and the publicKey id must be on the same host as the actor id. Based on Akkoma f07eb4cb5. The Bridgy fixture gets the key id that current Bridgy Fed serves.
This commit is contained in:
parent
d54ff52691
commit
695dd340de
9 changed files with 201 additions and 8 deletions
1
changelog.d/actor-containment.security
Normal file
1
changelog.d/actor-containment.security
Normal file
|
|
@ -0,0 +1 @@
|
|||
Reject remote actors whose inbox, shared inbox, followers, following or featured collection, or key id is on another host
|
||||
Loading…
Add table
Add a link
Reference in a new issue