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.

  • rglullis@communick.news
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    6 months ago

    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.

    • Zak@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 months ago

      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.

      • rglullis@communick.news
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        6 months ago

        tools to thrive should also be building things for secure, private communication.

        Sure, but this should not be seen on the same class of software of “social media” or even “the web”.