HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
facebookarchive
BOLT
Command Line2018–2022
facebookarchive / BOLT · Archived

BOLT

Binary Optimization and Layout Tool - A linux command-line utility used for optimizing performance of binaries

17Distinct people
17Mentions
0Explicit recommenders
2.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Binary Optimization and Layout Tool - A linux command-line utility used for optimizing performance of binaries

GitHub

Where it is used

No documented product use was verified in the last source check.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 year17 dated mentions

Observed mentions: 2018-06-21 02:34:03 UTC to 2022-11-09 16:55:07 UTC.

02468102018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 6 submissions, 4 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1064
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

What Hacker News says

1 sources
From what I understand: The blog answers, how does one store a secret without it being subject to brute force (and other offline) attacks [0], with: Generation of the secret (on the client): 1. Generate sk: Key-stretch user-provided pass-phrase to 256 bits using Argon2 [1]. 2. Generate a verifiable auth-token, token = hmac-sha256(sk, "auth key encrpytion") [2] 3. Generate a split secret-key: 3a. split1 = hmac-sha256(sk, "master key encryption") 3b. split2 = high-entropy-random-256-bits 4. Send key-pair (token, split2) to remote machines running BOLTed [3] server code in a SGX enclave [4] that replicate it using raft-consensus protocol [5] over Noise [6] in an hardware-encrypted RAM [7] and never on-disk. 5. Generate master-key = hmac-sha256(split1, split2) 6. Generate as many application-keys as required, and use these to encrypt user's d
Read the rest
ata, for instance, app-key-sge = hmac-sha256(master_key, "social graph encryption") and so on... - Recovery of the secret (by the client): 1. On the client, using user-provided pass-phrase, generate sk, token, and split1, like above. 2. Send the token to a remote machine. If the token is valid, remote lets the client retrieve split2 [8] with which the client can now generate the master-key and app-keys, as before. 3. If the token sent is invalid, remote lets the client retry a very limited number of times before destroying the secret key-pair. --- [0] From the post, ...we’ve been working on new techniques based on secure enclaves and key splitting that are designed to enhance and expand general capabilities for private cloud storage. Our aim is to unlock new possibilities and new functionality within Signal which require cross-platform long-term durable state, while verifiably keeping this state inaccessible to everyone but the user who created it. [1] https://en.wikipedia.org/wiki/Argon2 (end-users prefer shorter passwords but one gets better entropy with longer passwords... which is what Argon2 brings to the table) [2] https://en.wikipedia.org/wiki/HMAC [3] https://github.com/facebookincubator/BOLT (prevents speculative execution exploits: https://en.wikipedia.org/wiki/Speculative_execution) [4] https://blog.quarkslab.com/overview-of-intel-sgx-part-1-sgx-... (used for strict code and hardware attestation) [5] https://www.youtube-nocookie.com/embed/YbZ3zDzDnrw [6] http://www.noiseprotocol.org/ (Wireguard and WhatsApp use it, too, for end-to-end communication) [7] https://eprint.iacr.org/2016/204.pdf [8] Thanks u/jlund: https://news.ycombinator.com/item?id=21839394
In Technology Preview for secure value recovery

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.