SCscosman·Aug 21, 2026Submission
Show HN: secret_share - simple CLI to share secrets with PKE
1 points · Open discussionscosman
secret_share
Go2025–2026
scosman / secret_share
secret_share
Share Secrets/Passwords Securely with with a CLI in 15 Seconds
2Distinct people
4Mentions
0Explicit recommenders
26GitHub stars
What to know before exploring
What it is
Share Secrets/Passwords Securely with with a CLI in 15 Seconds
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 month4 dated mentions
Observed mentions: 2025-08-09 13:57:59 UTC to 2026-08-21 19:46:35 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 |
|---|---|---|---|---|---|
| Aug 2025 | 2025-08-01 00:00:00 UTC | 2025-09-01 00:00:00 UTC | 2 | 2 | 0 |
| Sep 2025 | 2025-09-01 00:00:00 UTC | 2025-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2026 | 2026-06-01 00:00:00 UTC | 2026-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2026 | 2026-07-01 00:00:00 UTC | 2026-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2026 | 2026-08-01 00:00:00 UTC | 2026-09-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
4 sourcesShow HN: CLI to share secrets using one-time public keys
4 points · Open discussionSecretShare: Secure One Time Secret Sharing
3 points · Open discussionShow HN: SecretShare – Easy, secure one time secret sharing CLI
I built a easy to use CLI for sharing secrets. I’ve had to share a ton of API keys lately, and it seems wild there isn’t a simple hacker friendly way to do this.
The whole process takes about 15 seconds:
1 The receiver runs secret_share and it generates a one-time public key they can send to the sender
2 The sender runs secret_share, pastes in the public key from the receiver, types the secret, and gets an encrypted response they can send back
3 The receiver pastes in the encrypted response and sees the secret
There are no servers. It’s using very standard/boring/secure crypto (RSA-OAEP and AES-GCM). The private key is never written to disk and is evicted from memory as soon as the payload is decoded (new keys every time). It’s user friendly for a CLI (clear messages, clipboard integration). You can use any chat tool as the communication
Read the rest
channel never sees the private key. The only dependencies are Google maintained go packages (term and sys).
Inspired by another project I saw in here 2 days ago, but answering the questions: does this really need a server when we can just use public keys? Can we minimize the codebase and dependencies?
https://github.com/scosman/secret_share