As most people here might know, Session utilises a TOR-like onion routing system with some changes to route traffic. The username is the public key whilst the password is the private key.
Recently, a new project built on top of this seems to be in the works: https://simplifiedprivacy.com/freespeech/
I’d like to know the community’s opinion of session and how much would you trust its technology. Thanks!
Session is very much not a clone of Signal. They forked it way back and the entire back end and front end are different. Session uses the lokinet behind the scenes which stores messages encrypted and routes traffic. Session isn’t completely decentralized to my knowledge as its a work in progress but for now it is harder to block or censor compared to signal.
Even if you have your doubts, its been audited and found to be reasonably secure so it shouldn’t be a security risk. I still don’t use it due to its lack of invites but if they add stable calls I might just switch. For now I use it to send text between my devices.
Localsend can also do text!
An alternative that I use is QR codes
Android:
- some F-Droid Apps (over Obtainium of course ;D)
- now I just use Mull + the offline QR code generator Addon. I have all in my custom Addon collection
Linux:
- Decoder with the fix mentioned on the Link. That at least deals with autodeletion of history, but the text still has no password function. (Basically I use the awesomeness of Flatpak app storage and always delete it after the process is finished, works flawlessly and can be used with every app)
The encryption is a fundamental problem because they removed Signal’s forward secrecy and replaced it all with a single leakable key you share among all your devices.
According to Season devs, Session does not use LokiNet but some other thing. It’s been that way since way back…
