HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
CHURPTeam
CHURP
Go2019–2019
CHURPTeam / CHURP

CHURP

Decentralize your secrets!

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

What to know before exploring

What it is

Decentralize your secrets!

GitHub

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 hour2 dated mentions

Observed mentions: 2019-09-01 18:23:33 UTC to 2019-09-01 18:49:25 UTC.

0122019-09-01 18:00:00 UTC to 2019-09-01 19:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 1, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC. One observed period does not establish a trend.

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
Sep 1, 18:002019-09-01 18:00:00 UTC2019-09-01 19:00:00 UTC202

What Hacker News says

2 sources
Even a very very cursory review of the code turns up giant red flags. As another comment noted it lacks tests, uses poor project structure and has private deps. Much more seriously, though, the encryption looks very very unsafe. The encryption uses math/rand. This alone clearly shows the authors have absolutely no clue what they are doing. The encryption itself is also very unsafe - loads of obvious side channel attacks and really far too many flaws to cover here. This isn't just a few mistakes, this is a group of people who don't know enough to do this safely. Sorry, this stuff is hard and this project doesn't come close to meeting even the lowest bar. 1: https://github.com/CHURPTeam/CHURP/blob/master/src/utils/enc...
In CHURP: Dynamic-Committee Proactive Secret Sharing
Not sure if OP is the author but thanks for sharing. Secret management is a challenge for a lot of folks. For the authors, here are a couple of items that made it hard for me to evaluate the project: 1. This project doesn't build for me and some of the dependencies don't exist or are private repos which prevent me from building the project (https://github.com/CHURPTeam/CHURP/blob/master/src/cmd/bb.go...) 2. It's lacking godoc documentation which means it's hard for me to quickly see how the API works. As such, some of the API methods seem less than useful. For example, `(Optional) storeSecret(SK)`. What does "optional" mean? What's the return value? What's SK? (Optional) retrieveSecret() -> SK: What? I can only store a single secret? Without passing params to this, it seems so. 3. Project structure is not conventional (cmd/ inside src/) T
Read the rest
his may not seem like a big deal but am I really going to trust my secrets without someone who didn't learn enough about go to use godoc and use a conventional project structure? 4. No tests Again, doubtful I'm going to trust my secrets to a distributed network that's not tested.
In CHURP: Dynamic-Committee Proactive Secret Sharing

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.