• Dr. Wesker@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    17 hours ago

    The article explains everything. The gist is Russians are targeting Ukrainians with phishing attacks via Signal. There also is the suggestion they’re exploiting the linked devices functionality, though I’m not sure how.

    • sunzu2@thebrainbin.org
      link
      fedilink
      arrow-up
      2
      arrow-down
      30
      ·
      17 hours ago

      Appreciate this, I don’t click links lol

      Apparently if they can get you to scan some bogus qr code they can get you add their device to your account.

      Why signal not cooperating tho? Following us government?

      • qaz@lemmy.world
        link
        fedilink
        English
        arrow-up
        17
        ·
        16 hours ago

        …I don’t click links…

        I strongly suggest doing so if you want to understand what the article is about

      • variaatio@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        16 hours ago

        Because they can’t without backdooring the software? Just like they also refuse to co-operate with Swedish government and threatened to leave the market should Sweden try to force them.

        You know Russian spies can also use TOR onion routing and so on.

        As for phishing there is nothing Signal can do about someone scanning a signal contact sharing QR and adding it to their contracts list beyond informative “hey are you really sure, really really sure you want to add this contact”. If user trusts someone they shouldn’t, no amount of app policy protections help. Or maybe they manage to shish them to scan and approve “share account to another device”. Again nothing Signal can do about that.

      • Dr. Wesker@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        8
        ·
        edit-2
        17 hours ago

        Not sure. Might be political tension. Might be that phishing attacks are typically user error, and Signal feels like at a certain point it’s not their responsibility. Hard to say beyond conjecture, and I didn’t see a clear reason given in the article.