Skip Navigation

Authorized Fetch Circumvented by Alt-Right Developers

wedistribute.org Authorized Fetch Circumvented by Alt-Right Developers

A controversial developer circumvented one of Mastodon's primary tools for blocking bad actors, all so that his servers could connect to Threads.

Authorized Fetch Circumvented by Alt-Right Developers

Authorized Fetch (also referred to as Secure Mode in Mastodon) was recently circumvented by a stupidly easy solution: just sign your fetch requests with some other domain name.

73

You're viewing a single thread.

73 comments
  • What I think a lot of conversations about privacy and security on the Fediverse miss is that the Fediverse is radically public.

    A protocol that sends everything you share to a long list of servers that haven't been pre-screened and could be anything from a professionally-managed instance of vanilla Mastodon to an ad hoc, informally-specified, bug-ridden, slow implementation of half of ActivityPub running on a jailbroken smart light bulb can only ever be radically public. It's possible to block most interactions with someone you don't want to talk to, but not to reliably prevent them from seeing content you share to anything more than a short list of vetted followers.

    There probably isn't any reasonable way to change that while keeping the open federation model, though it's possible to build closed networks on top of ActivityPub for those who want the formats it supports for a curated group. This isn't a problem to be solved in my view, but an inherent reality: the Fediverse is for things you want to make public.

    • Exactly! The only way that we can make sure that the Internet is not controlled by anyone is to make it available for everyone. If we are fighting for an open internet, we need to understand that this type of thing will be part of the package.

      • We, by which I mean some loose group of people who want decentralized tools to thrive should also be building things for secure, private communication, and we are. Matrix, for example offers strongly end-to-end encrypted federated chat rooms and private messages. It also has a kind of rough UX and, IIRC resource-intensive server software. We should work toward improving that.

        I'm not advocating against privacy at all. I want people to understand as clearly as possible that Mastodon, Lemmy, and anything that works like them isn't private and can't be private when part of an open federated network so they can decide whether that's a good fit for how they're using it. The block evasion described in the link is just run a server on a domain that isn't blocked, and I imagine any other mitigations bolted onto Mastodon that don't break open federation will be little better.

You've viewed 73 comments.