These articles also demonstrate that cloud chats have weak forensic protection. Only secret chats offer decent protection against message recovery, but files can still be restored, and secret chats are not available in the desktop client. I added these articles to the wiki (If Patrick approves my changes)
I am not sure forensic protection is a fair criteria.
Which messengers do have anti-forensics?
Then we can also exclude issues on mobile operating systems, Windows and macOS - because Whonix is Linux based and a mobile version is not in sight at time of writing. (Whonix Mobile Operating System)
Okay. Then I will only add the first link to the section about MTProto criticism (the article compares encryption protocols and Telegram lags behind its competitors).
I think on this page Phone Number Validation vs User Privacy we should change ‘For this reason alone, alternative options like Gajim, and Tox’ to ‘Simplex, Swtch, and Gajim / Dino’. I don’t see an edit button on this page. Update it when you have some free time. Thank you
Actually, I don’t want to maintain different lists of recommendations in different places as recommendations may change over time. Easier to just point at the main documentation.
Therefore, I’ve removed just now.
like [[Chat#Gajim|Gajim]], and [[Chat#Tox|Tox]]
The sentence reads now:
For this reason alone, alternative options should be investigated instead; see Instant Messenger Chat for further information.
Done! Patrick, could you please check? Instant Messenger Chat and Send Signal Messages over Tor with Whonix ™ and Whonix Documentation If I write something incorrectly or inaccurately, please correct.
I got in touch with the lead developer of Simplex to clarify some details for the table. I also noticed that the Cwtch code page is unavailable – I had to use an internet search with reviews.
Additionally, I edited the messengers section in Kicksecure Software Recommendations – I added links to the original websites (you can copy the messenger pages to Kicksecure wiki, and then I’ll replace links).
Thank you!
• Reproducible builds
Reproducible: servers, CLIs for all platforms. Linux Desktop app will be reproducible from the next release.
No yet: mobile apps, desktop apps for other platforms.
Avoid Matrix (shadey relations to Amdocs) and Avoid Telegram (e.g Telegram reads your computer model saves this to account amoung others SMS verification required)
Another thing is it should be mentioned about in wiki is which messengers enable automatic previews by default and how to disable them in settings. Automatic previews has been used to exploit zero days in iMessage and even private messengers. The other thing about this is if “Automatic previews” or the equvilent is turned on this means any group chats that your are actively in will automatically download the files shared in a chat to your cache. This means that if someone spams something illegal, well now you have those illegal bytes on your PC.
Patrick I added sections about the messengers Briar and Session - this is now a review of all popular chats on this wiki page. I also added a section to the “message panding” in table. And a small change to the Kicksecure wiki Software Recommendations. Please check. Thank you
I am not sure if that’s a different kind of padding and if that is enough to say “OMEMO has no padding”?
The table for Dino IM still states
Audited protocol/crypto/client
Yes, protocol/crypto (Radically Open Security: 2016)
I cannot find that. Copy/paste error?
Signed source code:
No/Partially
There’s no need for all git commits to be signed. It’s sufficient if the git head is signed by a developer. Or the availability of signed git tags is even better.
cwtch (and similar cases) we could just say “no” instead of “partial” unless:
git head is signed by a developer by convention; or
there are signed git tags; or
there are signed source code tarballs
I’ve requested signed git tags from a number of projects in the past. See web search:
site:github.com "adrelanos" "signed git tags"
Maybe something you’d like to look into and send feature requests to projects that don’t sign git tags yet?
Maybe later. For now, let’s finish and confirm the ready edits I think your idea of referencing source code links is very good, and any user will always be able to study the up-to-date information if this wiki page becomes outdated in a year or two.
And I found information about verifiability in Onionshare - it uses E2EE authentication of Onion services:
When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion. No impersonation is possible, which is generally not the case.
When the client receives the signed descriptor, they verify the signature of the descriptor using the public key that is encoded in the onion address. This provides the end-to-end authentication security property, since we are now sure that this descriptor could only be produced by that Onion Service and no one else.
And I changed “No risks introduced for hosting an Onion Service” for Cwtch, as it uses its own encryption protocol and uses tor for transport
p.s. If you don’t like my phrasing - please change it to more correct text