HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
SilentCircle
silent-phone-base
C2013–2013
SilentCircle / silent-phone-base

silent-phone-base

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
54GitHub stars
REPOSITORY AT A GLANCE

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 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 week2 dated mentions

Observed mentions: 2013-02-14 09:56:28 UTC to 2013-07-09 11:21:58 UTC. Weeks start Monday, UTC.

012013-02-11 00:00:00 UTC to 2013-02-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 112013-02-18 00:00:00 UTC to 2013-02-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-02-25 00:00:00 UTC to 2013-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-03-04 00:00:00 UTC to 2013-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-03-11 00:00:00 UTC to 2013-03-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-03-18 00:00:00 UTC to 2013-03-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-03-25 00:00:00 UTC to 2013-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-01 00:00:00 UTC to 2013-04-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-08 00:00:00 UTC to 2013-04-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-15 00:00:00 UTC to 2013-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-04-22 00:00:00 UTC to 2013-04-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 222013-04-29 00:00:00 UTC to 2013-05-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-06 00:00:00 UTC to 2013-05-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-13 00:00:00 UTC to 2013-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-20 00:00:00 UTC to 2013-05-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-27 00:00:00 UTC to 2013-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-03 00:00:00 UTC to 2013-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-10 00:00:00 UTC to 2013-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-17 00:00:00 UTC to 2013-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-24 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-01 00:00:00 UTC to 2013-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-08 00:00:00 UTC to 2013-07-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 8

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 112013-02-11 00:00:00 UTC2013-02-18 00:00:00 UTC110
Feb 182013-02-18 00:00:00 UTC2013-02-25 00:00:00 UTC000
Feb 252013-02-25 00:00:00 UTC2013-03-04 00:00:00 UTC000
Mar 42013-03-04 00:00:00 UTC2013-03-11 00:00:00 UTC000
Mar 112013-03-11 00:00:00 UTC2013-03-18 00:00:00 UTC000
Mar 182013-03-18 00:00:00 UTC2013-03-25 00:00:00 UTC000
Mar 252013-03-25 00:00:00 UTC2013-04-01 00:00:00 UTC000
Apr 12013-04-01 00:00:00 UTC2013-04-08 00:00:00 UTC000
Apr 82013-04-08 00:00:00 UTC2013-04-15 00:00:00 UTC000
Apr 152013-04-15 00:00:00 UTC2013-04-22 00:00:00 UTC000
Apr 222013-04-22 00:00:00 UTC2013-04-29 00:00:00 UTC000
Apr 292013-04-29 00:00:00 UTC2013-05-06 00:00:00 UTC000
May 62013-05-06 00:00:00 UTC2013-05-13 00:00:00 UTC000
May 132013-05-13 00:00:00 UTC2013-05-20 00:00:00 UTC000
May 202013-05-20 00:00:00 UTC2013-05-27 00:00:00 UTC000
May 272013-05-27 00:00:00 UTC2013-06-03 00:00:00 UTC000
Jun 32013-06-03 00:00:00 UTC2013-06-10 00:00:00 UTC000
Jun 102013-06-10 00:00:00 UTC2013-06-17 00:00:00 UTC000
Jun 172013-06-17 00:00:00 UTC2013-06-24 00:00:00 UTC000
Jun 242013-06-24 00:00:00 UTC2013-07-01 00:00:00 UTC000
Jul 12013-07-01 00:00:00 UTC2013-07-08 00:00:00 UTC000
Jul 82013-07-08 00:00:00 UTC2013-07-15 00:00:00 UTC101

What Hacker News says

2 sources
I am totally, completely in the dark as to which coding errors (there have been several in the past few months) attach to which CVEs and which versions, and about when these vulnerabilities were reported to the project and when they were subsequently disclosed. I can't be the only one confused, and I do wonder whether that confusion is strategic. Pointing this out would be be gratuitous, except that Cryptocat's project leader has very high standards when it comes to the disclosure behavior of that project's competitors: https://github.com/SilentCircle/silent-phone-base/issues/5 (Cryptocat is "kaepora" in that thread; the context there is that Mark Dowd had reviewed ZRTPCPP, an open source implementation of the ZRTP protocol that Silent Circle funds and relies on, and found several memory corruption vulnerabilities. Mark had gone public wi
Read the rest
th those vulnerabilities quickly as a result of a miscommunication with the Silent Circle team, but then redacted his disclosure and agreed to embargo the findings while Silent Circle coordinated fixes with all of the Silent Circle competitors that relied on that library; what you see in that thread is, apparently, the lead developer of Cryptocat, which doesn't use ZRTPCPP, repeatedly criticizing Silent Circle's handling of the incident.) The project should meet the standards that it has loudly set for others, and I don't think it has. I'd be happy to be corrected on this.
In Anatomy of a pseudorandom number generator – visualising Cryptocat's buggy PRNG

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.