I’m pleased to announce the immediate availability of a reference implementation for the Public Key Directory server. This software implements the Key Transparency specification I’ve be…
I’ll take a look when I get a chance, but like you said, it’s a public key directory. I thought you were claiming to have a solution to client side keys. Is there trouble with using some existing PK directory scheme?
I’ll see if I can read the post but when I tried this morning, it was way too long. I’ll look at the specification. I’ve been involved in crypto implementation since forever, which is why this looked interesting. But I think the client side also has to be figured out, if it hasn’t been yet.
I’ll take a look when I get a chance, but like you said, it’s a public key directory. I thought you were claiming to have a solution to client side keys. Is there trouble with using some existing PK directory scheme?
No, if you read the post it will make more sense.
Or the specification if you’re more technical.
I’ll see if I can read the post but when I tried this morning, it was way too long. I’ll look at the specification. I’ve been involved in crypto implementation since forever, which is why this looked interesting. But I think the client side also has to be figured out, if it hasn’t been yet.
The client side is its own beast. See https://github.com/soatok/mastodon-e2ee-specification?tab=readme-ov-file#components from my initial project (the “key transparency” thing from today slots neatly into the “Federated PKI” hole).
Thanks. I’ll look and post comments later if you want them.
Certainly. Thanks <3