Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
-
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
-
R relay@relay.mycrowd.ca shared this topic
-
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
The last time I checked, Lemmy, GoToSocial, Friendica, and the ‘keys to name a few did not handle it. Mastodon didn’t if you included requiring ed25519. But I haven’t checked the code bases or my logs in a month or two, @julian. At that time there wasn’t much progress on peertube/http-signatures or superseriousbusiness/httpsig.
I should probably check again...
-
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
@julian@fietkau.social by "can't handle" do you mean "still reliant on cavage-12"?
️ -
@julian@activitypub.space As I understand the migration path, it's like
1. Able to receive RFC 9421 in addition to draft-cavage
2. Able to send RFC 9421 in addition to draft-cavage
3. Send RFC 9421 by default, but be able to fall back to draft-cavage if neededSo by “can't handle” I meant step 1.
Although the unspoken step 4 is to remove draft-cavage support once everyone else has taken step 1, I'm ultimately also wondering when we'll get there. -
RE: https://mastodon.social/@bagder/116359048796181736
Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
On the flip side, ever more complex curl invocations (here: Accept header plus signature fields plus key file, presumably) suggest use of more specialized CLI tools, such as provided by @fedify, or at least scripts/aliases.
Speaking of RFC 9421, which notable fediverse implementations can't handle it yet? Anyone keeping track?
@fedify@hollo.social @julian@fietkau.social
I still cant! but I wonder, any example of a software in node/javascript that uses the new signature standard?
-
@fedify@hollo.social @julian@fietkau.social
I still cant! but I wonder, any example of a software in node/javascript that uses the new signature standard?
-
-
-
GitHub - evanp/activitypub-bot: An ActivityPub server-side bot framework
An ActivityPub server-side bot framework. Contribute to evanp/activitypub-bot development by creating an account on GitHub.
GitHub (github.com)
-
GitHub - evanp/activitypub-bot: An ActivityPub server-side bot framework
An ActivityPub server-side bot framework. Contribute to evanp/activitypub-bot development by creating an account on GitHub.
GitHub (github.com)
@julian@fietkau.social @fedify@hollo.social @evan@cosocial.ca
If you send me the part of send signature code that would bee neat
#Thankss -
R relay@relay.an.exchange shared this topic