It was a many months transition, and it’s finally done

Fun thing, you can actually make a backup of all* your messages, groups, contacts, etc. So before leaving you can have all of your data in case you need that one contact or something

The final red flag was as that allegedly Russian authorities were messing with people’s deleted messages. Not for the first time there are news that they could read, modify, delete, see location, and etc. Screw it, this is unsafe, I’m out.

Also, these days telegram is really at the state of a pile of garbage, bloated, buggy, and shady messenger.

  • @[email protected]
    10•4 months ago

    Session was at first a fork of Signal without usernames.

    Now by design it uses their own custom tor-like service (instead of just… using tor) and does not support forward secrecy or deniable authentication, so anyone who collects the messages in transit can either find a vulnerability in the encryption scheme, or spend enough GPU resources to crack it, and they have confirmation of who sent and received the message and what the contents of the message are. And is headquartered in Australia, which is 5EYES and much more against encryption than the US. Oh, and the server is closed-source.

    Regarding Australia’s 2018 bill…

    The Australian Parliament passed a contentious encryption bill on Thursday to require technology companies to provide law enforcement and security agencies with access to encrypted communications. Privacy advocates, technology companies and other businesses had strongly opposed the bill, but Prime Minister Scott Morrison’s government said it was needed to thwart criminals and terrorists who use encrypted messaging programs to communicate.

    Regarding the ‘vulnerability or cracking them later’ bit…

    Messages that are sent to you are actually sent to your swarm. The messages are temporarily stored on multiple Service Nodes within the swarm to provide redundancy. Once your device picks up the messages from the swarm, they are automatically deleted from the Service Nodes that were temporarily storing them.

    From Session’s own FAQ:

    Session clients do not act as nodes on the network, and do not relay or store messages for the network. Session’s network architecture is closer to a client-server model, where the Session application acts as the client and the Service Node swarm acts as the server. Session’s client-server architecture allows for easier asynchronous messaging (messaging when one party is offline) and onion routing-based IP address obfuscation, relative to peer-to-peer network architectures.

    I wouldn’t touch it with a 12ft ladder.

    • @[email protected]
      2•4 months ago

      Between forking Signal to make their desktop and mobile clients, and forking Monero to make their cryptocurrency… I’m surprised they came up with Lokinet.

      Edit: I’m pretty Session doesn’t even use Lokinet. So much for the claimed resiliency from “hackers”

      • @[email protected]
        1•4 months ago

        Session does use the Oxen network which is the renamed Lokinet, unless they made a change I’m wholly unaware of.

        • @[email protected]
          2•4 months ago

          I must have been thinking of their past implementations. Their FAQ says things were different:

          Proxy routing was an interim routing solution which Session used at launch while we worked to implement onion requests. When proxy routing was in use, instead of connecting directly to an Oxen Service Node to send or receive messages, Session clients connected to a service node which then connects to a second service node on behalf of the Session client… The proxy routing system has now been replaced by onion requests.

          It was even less clear to me because this is what it says in the app itself:

          Session hides your IP by bouncing your messages through several Service Nodes in Session’s decentralized network.

          Not “the Oxen network” but “Session’s network.”

          And then it has a graph of

          • You

          • Entry Node

          • Service Node

          • Service Node

          • Destination

          • @[email protected]
            2•4 months ago

            You’re not wrong. Lokinet and Session are both products from the same parent company. Lokinet was renamed to the Oxen protocol, and they run all the servers AFAIK, so it would be like tor, if tor ran every guard, entry, and exit node. AKA worthless. So you’re spot on, it’s a joy to the intelligence community and after the Encrochat debacle and Session stopped using Signal’s encryption algorithms and code, I would suggest no one use it for anything sensitive.