KEkemitchell·Oct 6, 2018
re iOS store, have a look at: https://github.com/signalapp/libsignal-protocol-c#license
If you need legal advice for your specific project and situation, speak to a lawyer.
In Don’t sign a CLAsignalapp
libsignal-protocol-c
C2016–2021
signalapp / libsignal-protocol-c · Archived
libsignal-protocol-c
Discover this repository through its Hacker News conversations.
10Distinct people
10Mentions
0Explicit recommenders
1.4KGitHub stars
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 3:38:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2016-05-18 21:00:32 UTC to 2021-10-01 16:24:24 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sourcesYes, and Telegram being open allows us to confirm with absolute certainty that it uses no E2EE by default.
We don't have the WhatsApp source code, but we don't have to do a lot of reverse engineering to see that it uses this:
https://github.com/signalapp/libsignal-protocol-c
But yeah, you're right, it could be sending plaintext or deliberately leaking keys somewhere. Unless someone really reverses it we won't know it doesn't as surely as we know that Telegram doesn't use encryption at all.
In WhatsApp sends Cease and Desists for apps that use native Android APIs