diff options
author | ThibG <thib@sitedethib.com> | 2020-09-14 13:04:29 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-09-14 13:04:29 +0200 |
commit | cd4ec7cd74c0975c7ff9aa832ed7e1bb10966439 (patch) | |
tree | 7f8c77f396e375b5ea02afe2ca54de3b484f164d /public/emoji/1f9cf-1f3fe-200d-2642-fe0f.svg | |
parent | 42c4322ce72f33a12bffdc42c7ffe27a08dcba44 (diff) |
Do not serve account actors at all in limited federation mode (#14800)
* Do not serve account actors at all in limited federation mode When an account is fetched without a signature from an allowed instance, return an error. This isn't really an improvement in security, as the only information that was previously returned was required protocol-level info, and the only personal bit was the existence of the account. The existence of the account can still be checked by issuing a webfinger query, as those are accepted without signatures. However, this change makes it so that unallowed instances won't create account records on their end when they find a reference to an unknown account. The previous behavior of rendering a limited list of fields, instead of not rendering the actor at all, was in order to prevent situations in which two instances in Authorized Fetch mode or Limited Federation mode would fail to reach each other because resolving an account would require a signed query… from an account which can only be fetched with a signed query itself. However, this should now be fine as fetching accounts is done by signing on behalf of the special instance actor, which does not require any kind of valid signature to be fetched. * Fix tests
Diffstat (limited to 'public/emoji/1f9cf-1f3fe-200d-2642-fe0f.svg')
0 files changed, 0 insertions, 0 deletions