this post was submitted on 20 Aug 2023
2 points (62.5% liked)
Lemmy Support
4656 readers
21 users here now
Support / questions about Lemmy.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Ha ha yeah it's not easy peasy when you start with these kind of things for sure, thanks for the link! It seems it shows the day to say stuff (and the pubkey embedded in the json) thanks again.
So if I want to validate a user outside of the Lemmy service (the one that runs in a docker on my lemmy-box), I "just" have to get the public key from the Lemmy database and validate the digest/signature?
Cheers!
You shouldn't have to... as I understand it, if it's showing up on your server, that means your server authenticated it. Given the general flakiness of all this software and Lemmy in particular, I wouldn't put too much reliability on that, but that's the theory.
If you do want to double-check it yourself, I know partially how to do it. You don't have to get the key from the database; it's probably simpler and safer to get it from your user's JSON. Here's a super-basic script to dump a fediverse endpoint's contents:
If I want to validate your comment, I would start by getting your public key via your user's endpoint on your home server. I could save that script up above as
fetch
, then runpython fetch https://lemmy.mindoki.com/u/Loulou
, and in among with a bunch of other stuff I would see:I don't know off the top of my head how you could navigate your way to the fediverse JSON for your comment, or how to verify its signature once you find it (I tried to get the post by dumping your user's outbox and the lemmy_support community's outbox, but neither of those worked the way I expected it to), but that all might be a helpful starting point. I know that according to the docs, anything that was created by your user and then federated is supposed to be signed with that key so that other servers can authenticate it.