Soatok Dreamseeker on Nostr: A while ago, I announced that I was going to build #E2EE for the Fediverse, so that ...
A while ago, I announced that I was going to build #E2EE for the Fediverse, so that we might have private direct messaging.
Then I stumbled over the lack of available tooling for Key Transparency in a federated environment. So I started working on a specification for a Public Key Directory server.
I'm happy to announce that I finally have all my ideas on paper.
https://github.com/fedi-e2ee/public-key-directory-specification/tree/main
This specification is not complete. It still needs:
Additional rounds of copy-editing, to ensure terms are consistent and easily understood.
Peer review, especially from cryptography experts.
A reference implementation.
Machine-verifiable security proofs of the security of the protocols described.
More peer review.
Third-party testing of the reference implementation.
Other people's ideas.
That last one is optional, but if anyone identifies an opportunity to make this project more successful, I'd love to hear it.
Then I stumbled over the lack of available tooling for Key Transparency in a federated environment. So I started working on a specification for a Public Key Directory server.
I'm happy to announce that I finally have all my ideas on paper.
https://github.com/fedi-e2ee/public-key-directory-specification/tree/main
This specification is not complete. It still needs:
Additional rounds of copy-editing, to ensure terms are consistent and easily understood.
Peer review, especially from cryptography experts.
A reference implementation.
Machine-verifiable security proofs of the security of the protocols described.
More peer review.
Third-party testing of the reference implementation.
Other people's ideas.
That last one is optional, but if anyone identifies an opportunity to make this project more successful, I'd love to hear it.