libsignal-protocol-c VS wire-server

Signal wrote their own open source protocol, libsignal, to provide end to end encryption; or as they put it "a ratcheting forward secrecy protocol that works in synchronous and asynchronous messaging environments." Source I'd wager good money a chunk of that space is for said library and dependencies PLUS the regular rigamarole for an Android app.

The whitepaper at [1] is more impressive than I expected it to be, not for what is built today (which on a quick read appears to be rather unexciting), but for the class of attacks recognised as unsolved, and identified as requiring future work.

Improvements identified include:

1) Encrypted messages should have a constant size (padded). Note that the Signal protocol used by Session currently uses variable length messages[2].

2) Encrypted messages should be sent as noise by clients through the onion network and back to themselves at random intervals frequent enough that messages to/from other parties are statistically indistinguishable to Eve from the noise generated.

3) Intermediate nodes in the onion network should hold and delay encrypted messages so they are adequately mixed before being sent forward. This makes it statistically difficult for Eve to match up a message entering a node and a message leaving a node. Ideally messages would be mixed across enough nodes of the onion network that

4) Proof of work should be replaced with a better technique for preventing degradation of service or spam attacks. The paper quite rightly identifies that proof of work would favour Eve who has setup a data center filled with custom ASICs solving proof of work problems, rather than favouring Alice or Bob with an energy efficient mobile phone SoC. CAPTCHAs are identified as a possible future solution to this class of attacks.

I doubt those improvements would have much application outside of labs and experiments though. Unless a significant part of the global economy surprisingly becomes dependent on a traffic analysis resistant anonymising protocol, it is too easy to just block such protocols similar to what China does with its Great Firewall.

[1] https://arxiv.org/pdf/2002.04609.pdf

[2] https://github.com/signalapp/libsignal-protocol-c/blob/maste...

Signal protocol library for C/C++.

Use encrypted messaging apps. Several apps allow you to connect with others securely if you're using a smartphone. These include Signal and WhatsApp (both owned by Facebook), as well as Telegram and Wire (owned by Google). These services use end-to-end encryption, so they don't store any data on their servers or share it with anyone else.

For work each service it its own cabal project, and has src/ (the service) and test/ (in 3 styles)

Codes here: https://github.com/wireapp/wire-server

Haha. I stated using reddit after finding it when wire.com. Back in the day the top 10 reddit posts would show on Wire. This was around 2006/07. I specifically remember there being a science. You made me think, maybe I'm losing my mind so I checked into it. Sure enough there is a timeline available. Here is a 2007 accolade for r/ science, " For most of the year, "science" and "programming" are the most popular subreddits. I like the info for year 2008, "This year is dominated by the launch of numerous new subreddits." I do appreciate how confident you were in your incorrect answer though. You are probably a Digg.com refugee.

Is there any way if I self-host element, I can make it completely private? like somehow to remove the explore room option? like the users can't join any public room kind of what rocket chat does. or even wire.com. is it possible ? i want to make it completely private for the company

Also, I use it for my work @ https://wire.com

The backend of Wire messenger, with the server code publicly available in the company’s repository and detailed documentation, also written in Haskell.

The Client is GPL-3.0 Licensed. (WebApp,Desktop,iOS,Android) The Server is AGPL-3.0 Licensed. Both Client and Server are Open-Source.