bridgy-fed icon indicating copy to clipboard operation
bridgy-fed copied to clipboard

AP: Don't serve Webfinger for accounts we don't own

Open snarfed opened this issue 9 months ago • 3 comments

Right now, a bit embarrassingly, we serve Webfinger responses for any addresses that comes in, regardless of whether we actually own it. Example: /.well-known/webfinger?resource=acct:[email protected], which we oddly get ~1-2qps for, steady state, from a ton of different instances. We should return 404 (I assume?) instead for addresses we don't own.

snarfed avatar May 06 '24 14:05 snarfed

Ah right. This isn't quite as easy because of our support for web sites on arbitrary domains. We'd need to detect when a domain is an AP instance so that we know when to serve a 400 and not try to handle them as a normal web site.

snarfed avatar May 07 '24 21:05 snarfed

Manual workaround for now is to just opt out any problematic domains here.

snarfed avatar May 07 '24 21:05 snarfed

Related: #348

snarfed avatar May 08 '24 05:05 snarfed