• ewenak@jlai.lu
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 hours ago

        Could you explain a bit? I see main issue with Signal (though I’m not an expert, and they’re not strictly related to security): it’s centralized (and the server isn’t even open-source).

        The question is also a lot about your threat model right?

        • DreamlandLividity@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          6 hours ago

          The encryption being crap really does not depend on the threat model. Sure, in some threat models you may not need e2ee at all but in that case, what’s wrong with WhatsApp?

          The issue with XMPP is that security really was an afterthought. Not only is e2ee an optional extension, but there are actually 2 incompatible extensions, each with multiple versions. Then you have some clients not implementing either, some clients implementing the older, less secure one. Some implement the newer one but older version of the spec with known issues. And of course, the few clients that implement it well become incompatible with other clients that don’t if you enable e2ee, so it is disabled by default.

          That is all before you start looking into security audits or metadata harvesting.

      • Alexander@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        2
        ·
        12 hours ago

        I guess that sucks because I make a living working in cyber security. What do I know, amirite? 🤷