The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Libsignal-protocol-c Alternatives
Similar projects and alternatives to libsignal-protocol-c
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
libsignal-protocol-javascript
Discontinued This library is no longer maintained. libsignal-protocol-javascript was an implementation of the Signal Protocol, written in JavaScript. It has been replaced by libsignal-client’s typesafe TypeScript API.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
libsignal-protocol-c reviews and mentions
-
I wonder why Signal’s download size is so much larger than the competition? Intuition says it would be smaller
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.
-
Session Encrypted Messenger
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...
-
Are There Any Tutorials On How To Use The Signal
Signal protocol library for C/C++.
- Millions Flock to Telegram and Signal as Fears Grow Over Big Tech
-
A note from our sponsor - WorkOS
workos.com | 29 Apr 2024
Stats
signalapp/libsignal-protocol-c is an open source project licensed under GNU General Public License v3.0 only which is an OSI approved license.
The primary programming language of libsignal-protocol-c is C.
Sponsored