HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
sadasystems
private-message
HISTORICAL RECORD2015–2015
sadasystems / private-message · Not publicly available

private-message

Discover this repository through its Hacker News conversations.

2Distinct people
4Mentions
0Explicit recommenders
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, 3:56:07 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 6-hour interval4 dated mentions

Observed mentions: 2015-09-02 12:53:26 UTC to 2015-09-08 20:45:02 UTC.

0122015-09-02 12:00:00 UTC to 2015-09-02 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsSep 2, 12:002015-09-02 18:00:00 UTC to 2015-09-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-03 00:00:00 UTC to 2015-09-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-03 06:00:00 UTC to 2015-09-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-03 12:00:00 UTC to 2015-09-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-03 18:00:00 UTC to 2015-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-04 00:00:00 UTC to 2015-09-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-04 06:00:00 UTC to 2015-09-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-04 12:00:00 UTC to 2015-09-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-04 18:00:00 UTC to 2015-09-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-05 00:00:00 UTC to 2015-09-05 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-05 06:00:00 UTC to 2015-09-05 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-05 12:00:00 UTC to 2015-09-05 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 5, 12:002015-09-05 18:00:00 UTC to 2015-09-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-06 00:00:00 UTC to 2015-09-06 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-06 06:00:00 UTC to 2015-09-06 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-06 12:00:00 UTC to 2015-09-06 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-06 18:00:00 UTC to 2015-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 00:00:00 UTC to 2015-09-07 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 06:00:00 UTC to 2015-09-07 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 12:00:00 UTC to 2015-09-07 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 18:00:00 UTC to 2015-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-08 00:00:00 UTC to 2015-09-08 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-08 06:00:00 UTC to 2015-09-08 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-08 12:00:00 UTC to 2015-09-08 18:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2015-09-08 18:00:00 UTC to 2015-09-09 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 8, 18:00

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
Sep 2, 12:002015-09-02 12:00:00 UTC2015-09-02 18:00:00 UTC110
Sep 2, 18:002015-09-02 18:00:00 UTC2015-09-03 00:00:00 UTC000
Sep 3, 00:002015-09-03 00:00:00 UTC2015-09-03 06:00:00 UTC000
Sep 3, 06:002015-09-03 06:00:00 UTC2015-09-03 12:00:00 UTC000
Sep 3, 12:002015-09-03 12:00:00 UTC2015-09-03 18:00:00 UTC000
Sep 3, 18:002015-09-03 18:00:00 UTC2015-09-04 00:00:00 UTC000
Sep 4, 00:002015-09-04 00:00:00 UTC2015-09-04 06:00:00 UTC000
Sep 4, 06:002015-09-04 06:00:00 UTC2015-09-04 12:00:00 UTC000
Sep 4, 12:002015-09-04 12:00:00 UTC2015-09-04 18:00:00 UTC000
Sep 4, 18:002015-09-04 18:00:00 UTC2015-09-05 00:00:00 UTC000
Sep 5, 00:002015-09-05 00:00:00 UTC2015-09-05 06:00:00 UTC000
Sep 5, 06:002015-09-05 06:00:00 UTC2015-09-05 12:00:00 UTC000
Sep 5, 12:002015-09-05 12:00:00 UTC2015-09-05 18:00:00 UTC000
Sep 5, 18:002015-09-05 18:00:00 UTC2015-09-06 00:00:00 UTC000
Sep 6, 00:002015-09-06 00:00:00 UTC2015-09-06 06:00:00 UTC000
Sep 6, 06:002015-09-06 06:00:00 UTC2015-09-06 12:00:00 UTC000
Sep 6, 12:002015-09-06 12:00:00 UTC2015-09-06 18:00:00 UTC000
Sep 6, 18:002015-09-06 18:00:00 UTC2015-09-07 00:00:00 UTC000
Sep 7, 00:002015-09-07 00:00:00 UTC2015-09-07 06:00:00 UTC000
Sep 7, 06:002015-09-07 06:00:00 UTC2015-09-07 12:00:00 UTC000
Sep 7, 12:002015-09-07 12:00:00 UTC2015-09-07 18:00:00 UTC000
Sep 7, 18:002015-09-07 18:00:00 UTC2015-09-08 00:00:00 UTC000
Sep 8, 00:002015-09-08 00:00:00 UTC2015-09-08 06:00:00 UTC000
Sep 8, 06:002015-09-08 06:00:00 UTC2015-09-08 12:00:00 UTC000
Sep 8, 12:002015-09-08 12:00:00 UTC2015-09-08 18:00:00 UTC211
Sep 8, 18:002015-09-08 18:00:00 UTC2015-09-09 00:00:00 UTC101

What Hacker News says

4 sources
Hey no problem! Should I still open that issue? Seems like you have one made already (https://github.com/sadasystems/private-message/issues/5). I ended up doing this for a project that I wanted to have use RSA for large chunks of data, for sending it was: 1. Generate random AES cipher key (I used a 16 byte key) using any available secure rng (it all depends on where the thing gets it's entropy, I think node's crypto.getRandomBytes is supposed to be strong) 2. Pad & Encrypt data with AES 3. Encrypt randomly-generated key with RSA 4. Send the message in an envelope like: {key: <RSA encrypted AES key>, data: <AES encrypted data>} For me, the devil was in the details -- padding took an especially long time for me to understand and solve (the thing I was working on was cross platform, so ruby->js or python->ruby, and of course not all impleme
Read the rest
ntations pad the same way), but once that was solved, most other things were easy. The node part was also particularly troubling because I had to deal with the way to specify encodings in node, which was kind of confusing (I spent a lot of time messing with base64/binary encoding and having my terminal start showing gibberish when I tried to print binary data) I don't have access to that code now (I actually wrote it in order to get around the fact that internal networks at a certain company I used to work at didn't have a custom rootCA/support TLS properly), otherwise I'd just post it. Would love to help with the implementation though
In Show HN: Encrypted Communication via GitHub Using Node.js and SSH Keys

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.