26
Announcing Key Transparency for the Fediverse (soatok.blog)
submitted 10 months ago by to c/privacy@lemmy.dbzer0.com
11 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 10 months ago (6 children)

If you want E2EE for Mastodon, you need key management to be solved first.

This solves a lot of the key management pain. It's not v1.0 stable yet, but it's finally implemented. I've been working on the spec for nearly 2 years.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 10 months ago (5 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 10 months ago (4 children)

    No, if you read the post it will make more sense.

    Or the specification if you're more technical.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 10 months ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 10 months ago (2 children)

    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).

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •