Comment on FireChat was a tool for revolution. Then it disappeared.

• Cube6392@beehaw.org ⁨7⁩ ⁨months⁩ ago

  Session has made some insecure solution surrounding important design elements like forward secrecy

  source
• xnx@slrpnk.net ⁨7⁩ ⁨months⁩ ago

  That is meshnet based

  source

  • sxan@midwest.social ⁨7⁩ ⁨months⁩ ago

    And? It works on iOS.

    I’m missing the point. Was it that systems like Briar can’t work in iOS because they aren’t mesh net? If so, why not choose one that does, like Session?

    source

    • KLISHDFSDF@lemmy.ml ⁨7⁩ ⁨months⁩ ago

      For anyone considering Session messenger:

      ---

      The Session developers dropped Perfect Forward Secrecy because it would be hard to work around it.

      First things first, let’s talk about what we’re leaving behind: Perfect Forward Secrecy (PFS) and deniability.

      Source: getsession.org/session-protocol-explained

      In plain English, they dropped a security feature for their convenience to the detriment of their users’ security.

      For anyone unsure what PFS provides:

      The value of forward secrecy is that it protects past communication.

      Source: en.wikipedia.org/wiki/Forward_secrecy

      The Session devs also claim:

      Session provides protections against these types of threats in other ways — through fully anonymous account creation, onion routing, and metadata minimisation, for example.

      Reading between the lines, we can interpret that as introducing security through obscurity, which is generally considered bad practice - cwe.mitre.org/data/definitions/656.html

      source
    • xnx@slrpnk.net ⁨7⁩ ⁨months⁩ ago

      The point is being able to communicate when the internet is shut off

      source