Don’t Use Session (Signal Fork) - Dhole Moments
soatok.blog
Last year, I outlined the specific requirements that an app needs to have in order for me to consider it a Signal competitor. Afterwards, I had several people ask me what I think of a Signal fork c…
  • vollkorntomate@infosec.pubEnglish
    1·
    2 days ago

    […] it uses the X25519 public key… as a symmetric key, for AES-GCM.
    […] anyone that knows the public key can decrypt it.

    Ouch.

    • itslilith@lemmy.blahaj.zoneEnglish
      11·
      1 day ago

      Don’t care too much about the supposed hardening, but it’s on FDroid and has UnifiedPush, so I use it over Signal

    • kbal@fedia.io
      0·
      2 days ago

      It’s centralized, it doesn’t officially allow 3rd-party clients, it requires a phone number, and the desktop app kinda sucks. I use it anyway, but it could be better.

      • rottingleaf@lemmy.worldEnglish
        1·
        1 day ago

        The “centralized” part is not a problem with their protocol and it’s well explained.

        The 3rd-party clients thing … I agree with, but one can find justifications for that too. They probably don’t want people to use it for filesharing with uuencode and base64. Or even for VPNs, like they did with Tox when it seemed to have a future.

        The phone number thing sucks, but there’s a need to defend against bot registrations somehow.

        The desktop app sucks absolutely and conclusively. If there were a library one can use to make a Pidgin plugin, it would be a godly gift.