simplexmq VS simplex-chat

Of course https://github.com/simplex-chat/simplexmq

It's about ntf-server-ubuntu-20_04-x86-64 https://github.com/simplex-chat/simplexmq/releases/tag/v5.1.3

Also, it is covered in whitepaper here: https://github.com/simplex-chat/simplexmq/blob/stable/protocol/overview-tjr.md

Please review the whitepaper and / or website home page. I also wrote this post some time ago about why I believe that using pairwise identifiers should be a minimal requirement for a communication system to be considered private.

For more information see Simplex development roadmap xftp branch in github

The source code: https://github.com/simplex-chat/simplexmq/tree/xftp

You can download XFTP CLI (Linux) to send and receive files via the command line here - you need the file named xftp-ubuntu-20_04-x86-64, rename it to xftp.

We absolutely should assume they can be compromised, but as SimpleX servers do not participate in the initial key exchange for e2e encryption, the server compromise will not lead to the compromise of e2e encryption security. I wrote more on MITM issue in this post. Further, the threat model here explains other consequences of compromised SimpleX servers.

For messaging I'm currently on Olvid (E2E with physical key exchange) but since it still use their servers, I'm currently testing SimpleX where I can host my own servers.

Notice how SimpleX (https://simplex.chat/) has no push notifications by default because of this issue.

I've been using SimpleX [0] with a couple of friends recently. It appears to work as advertised.

[0] https://simplex.chat

If you have a mobile phone number, the domestic intelligence agency knows exactly where you are at all times and any LEO (without a warrant) can also find you. In addition, there have been numerous CCC presentations showing how insecure the global (excluding US) and (separately) US carriers are guilty of promiscuous metadata trafficking ($$) and insecure SS7 setups. As a consequence, for low $, you can go to any one of several shady websites and find the last location of almost any phone number (person unique ID) globally. There are additional varying exploitable vulnerabilities depending on the exact combination of {handset x carrier x country} to impersonate them, tap their line, reveal their exact location, and redirect their phone number through a third-party handset or even a PBX. These are more expensive and some capabilities are forbidden for all but a few selective intelligence uses.

Session (Signal fork) doesn't use phone numbers. It's pretty well-designed overall and uses an onion routing approach. It's already a superset of Signal except it doesn't use phone numbers. https://getsession.org

Also look interesting:

* (unproven) https://www.olvid.io/technology

* (unproven) https://simplex.chat

PS: Using regular TOR on home broadband or cloud servers is relatively risky and inefficient. Sybil attacks on it are common. And to network operators and security agencies it gives an easy "flow tag" of your uplink and exit node data traffic as automatically suspicious.

Why not open up a Feature request on https://github.com/simplex-chat/simplex-chat/issues