I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

[mariusor@metalhead.club]

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library.

#ActivityPubDev #fedidev #httpsig

[mariusor@metalhead.club]

As always, as I start the work for the verifier in the auth module, the coverage is quite low:

Coveralls.io - Test Coverage History and Statistics

This repository has 82.96% test coverage and 18 builds.

Coveralls.io (coveralls.io)

[mariusor@metalhead.club]

The work is done, huzzah!! 🥳

With the coverage increased to +85% and with a couple of pending improvements to the common-fate/httpsig library. Until those land, I'm using a forked version.

The auth module has transformed during this work to only have logic related to extracting authorized actors from either OAuth2 and HTTP-Signature headers (both the widely used draft and the new RFC9421 version).

This makes me confident that the convergence of the library's modules that I'm planning for v1 is actually a good idea.

[fentiger@zotum.net]

@marius That library doesn't look like it's seen much activity recently.

I ended up using this one and I've found the maintainer to be very responsive.

[mariusor@metalhead.club]

@fentiger thanx, I'll check it out. This one had one large annoyance in the fact that they split all functionality in a thousand little packages...