Hacker GitHub

← All repos

fedi-e2ee/public-key-directory-specification

View on GitHub ↗ ★ 182 PHP

Specification for a Fediverse Directory Server for Public Keys

13 mentions on Hacker News by 4 people: 2 stories, 11 comments · first 2024-08-25 · latest 2026-01-23

Mentions per year 13 mentions · busiest year 2024 (6)
20082026
AllStoriesComments NewestTopOldest
  1. One of the projects I alluded to in that post makes a technological solution to what you want easy to build, but the harder problem to solve is societal (i.e., getting it adopted). https://github.com/fedi-e2ee/public-key-directory-specifica…
    comment by some_furry · 2026-01-04 · in The PGP problem (2019)
  2. > The so-called web of trust is meaningless security theatre. Ignoring your comment’s lack of constructive criticism, I’m going to post this meaningful implementation that an excellent cryptographer, Soatok Dreamseeker, is working on: [1].…
    comment by Diti · 2026-01-03 · in The PGP problem (2019)
  3. Why is a keyring important to you? Would "fetch a short-lived age public key" serve your use case? If so, then an age plugin that build atop the AuxData feature in my Fediverse Public Key Directory spec might be a solution.…
    comment by some_furry · 2025-12-27 · in Gpg.fail
  4. Cryptography stuff! ----- COCKTAIL-DKG - A distributed key generation protocol for FROST, based on ChillDKG (but generalized to more elliptic curve groups) -- https://github.com/C2SP/C2SP/pull/164 | https://github.com/C2SP/C2SP/issues/159…
    comment by some_furry · 2025-10-12 · in Ask HN: What are you working on? (October 2025)
  5. Mostly decentralized/federated crypto stuff. 1. COCKTAIL-DKG - A distributed key generation protocol for FROST, based on ChillDKG (but generalized to more elliptic curve groups) -- https://github.com/C2SP/C2SP/issues/159 2. FREEON…
    comment by some_furry · 2025-09-30 · in Ask HN: What are you working on? (September 2025)
  6. Key Transparency for the Fediverse (so that we can build E2EE for DMs atop it) https://github.com/fedi-e2ee/public-key-directory-specificat...
    comment by some_furry · 2025-02-24 · in Ask HN: What are you working on? (February 2025)
  7. > If you have some hash function H = sha256 let us say, you could calculate h = H('{"name" : "bob", "pubkey" : "1A1zP1e"}')[:N] and then set record[57] = h (I'll use a 24-bit h = 71b686 for my examples, OP suggests a 48-bit). You're…
    comment by some_furry · 2024-11-22 · in Key transparency and the right to be forgotten
  8. > How does the attacker learn anything about the salt without breaking Argon2id first? It’s not like the salt is included in the Sigsum ledger. Take a close look at https://github.com/fedi-e2ee/public-key-directory-specificat... The…
    comment by some_furry · 2024-11-22 · in Key transparency and the right to be forgotten
  9. > Is the intention that E2EE have a separate, parallel account recovery mechanism with more difficult requirements? I'm not sure the wording here is helpful. Let's start with a simple diagram: https://github.com/fedi-e2ee/public-key-directo…
    comment by soatok · 2024-11-22 · in Key transparency and the right to be forgotten
  10. Not if the admin tampers with your bio! Not if the instance software itself gets hacked, either. See https://github.com/fedi-e2ee/public-key-directory-specificat... for a detailed threat model.
    comment by some_furry · 2024-11-22 · in Key transparency and the right to be forgotten
  11. I'm building an open source Federated Public Key Directory, so that I can then build end-to-end encryption for the Fediverse. https://github.com/fedi-e2ee/public-key-directory-specificat... Think: Encrypted DMs for Mastodon. I wrote…
    comment by some_furry · 2024-08-25 · in Ask HN: What are you working on (August 2024)?