Could be potentially nice for fediverse server testing, as more implementations make the jump to final RFC 9421 HTTP signatures.
-
@smallcircles @mro @julian @fedify I'm glad you enjoy thinking through these issues. Good luck with your blog post!
Blog post is done already
and you and @silverpill the first ones I made reference to 
Here's the announcement, and be sure to fill in the #poll if you want.. https://social.coop/@smallcircles/116379158584600016
-
@gabboman I decided to hack on this the past few nights, and came up with an experimental, backwards-compatible implementation that I created a draft pull request for
@peertube/http-signature. I tried to follow the library’s coding style of the original as much as possible.The idea of backwards-compatibility is that you can drop this into an existing application and nothing will break. There are deprecation messages that may surface in logs to guide changing from using the function exports to the
cavage12Draftexport (and therfc9421export).I think the next step for anyone would be:
- manual...
-
@gabboman I decided to hack on this the past few nights, and came up with an experimental, backwards-compatible implementation that I created a draft pull request for
@peertube/http-signature. I tried to follow the library’s coding style of the original as much as possible.The idea of backwards-compatibility is that you can drop this into an existing application and nothing will break. There are deprecation messages that may surface in logs to guide changing from using the function exports to the
cavage12Draftexport (and therfc9421export).I think the next step for anyone would be:
- manual...
WOOOOO WE USE SAID LIBRARY
-
@gabboman I decided to hack on this the past few nights, and came up with an experimental, backwards-compatible implementation that I created a draft pull request for
@peertube/http-signature. I tried to follow the library’s coding style of the original as much as possible.The idea of backwards-compatibility is that you can drop this into an existing application and nothing will break. There are deprecation messages that may surface in logs to guide changing from using the function exports to the
cavage12Draftexport (and therfc9421export).I think the next step for anyone would be:
- manual...
When last I left off, I made a pull request to
peertube/http-signaturelibrary try to help the JavaScript ecosystem reach RFC 9421 parity while being backwards-compatible with cavage-12 draft implementations. There has not been any traction on this yet. Maybe because PeerTube has abandoned its own use of the library.So our current ecosystem state is the following:
- PeerTube uses
misskey-dev/node-http-message-signatureslibrary and owns the defacto unmaintainedpeertube/http-signaturelibrary. - Misskey and the rest of the ‘keyverse use
peertube/http-signaturelibrary and Misskey owns the defacto...
-
When last I left off, I made a pull request to
peertube/http-signaturelibrary try to help the JavaScript ecosystem reach RFC 9421 parity while being backwards-compatible with cavage-12 draft implementations. There has not been any traction on this yet. Maybe because PeerTube has abandoned its own use of the library.So our current ecosystem state is the following:
- PeerTube uses
misskey-dev/node-http-message-signatureslibrary and owns the defacto unmaintainedpeertube/http-signaturelibrary. - Misskey and the rest of the ‘keyverse use
peertube/http-signaturelibrary and Misskey owns the defacto...
I did a quick experiment, and I think there are too many differences to make this an easy swap out library. It would take a lot of refactoring in wafrn to make use of fedify’s library, for instance.
- PeerTube uses
-
I did a quick experiment, and I think there are too many differences to make this an easy swap out library. It would take a lot of refactoring in wafrn to make use of fedify’s library, for instance.
Hi @mradcliffe@nokoto.org — NodeBB is built on Node and we'd be interested in using this library.
Is your work still on a branch? Are you able to share it with me?
If it is still used but unmaintained, it's probably time for a fork.
-
Hi @julian, you mean my pull request into peertube/http-signature? Have at it. Working with the test framework that the original library is annoying.
Recently I found that I made a mistake requiring
algsignature parameter in my RFC 9421 implementation, which I carried over there, but that node library also requires it. -
Hi @julian, you mean my pull request into peertube/http-signature? Have at it. Working with the test framework that the original library is annoying.
Recently I found that I made a mistake requiring
algsignature parameter in my RFC 9421 implementation, which I carried over there, but that node library also requires it.@mradcliffe@nokoto.org if Iceshrimp wafrn and Misskey use that lib that's pretty good isn't it? Does the base package not support the latest RFC 9421?
-
@julian No, TritonDataCenter/node-http-signature, the original http-signature npm lib, that PeerTube forked doesn’t support RFC 9421.
-
@julian No, TritonDataCenter/node-http-signature, the original http-signature npm lib, that PeerTube forked doesn’t support RFC 9421.
@mradcliffe@nokoto.org on thanks, I will take a look at your fork and see if I am able to integrate it into NodeBB. Will DM you shortly.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login