<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Re: @peertube&#x2F;http-signature]]></title><description><![CDATA[<p dir="auto"><a href="https://activitypub.space/user/chocobozzz%40framapiaf.org" rel="nofollow ugc">@chocobozzz@framapiaf.org</a> I have a question for you... I'm seeing in <a href="https://arewehs2019yet.vpzom.click/" rel="nofollow ugc">Are we HS2019 yet?</a> that Peertube and Misskey both use your package: @peertube/http-signature</p>
<p dir="auto">NodeBB currently rolls its own cavage-12 support but and I did some preliminary research into updating to the latest HTTP Signatures draft, but quickly got overwhelmed.</p>
<p dir="auto">For a variety of reasons, but mainly to avoid NIH, I'd consider switching to a dependency.</p>
<p dir="auto">My question is: does your library support verification for non-hs2019 signatures, or will I need to invoke your library in front, and fall back to existing cavage-12 verification otherwise?</p>
<p dir="auto">I suppose, same question re: double-knocking.</p>
]]></description><link>https://fedi.wiki/topic/993e4a15-e44b-458a-bfdc-8f90bfffc6fd/re-@peertube-http-signature</link><generator>RSS for Node</generator><lastBuildDate>Mon, 25 May 2026 01:49:44 GMT</lastBuildDate><atom:link href="https://fedi.wiki/topic/993e4a15-e44b-458a-bfdc-8f90bfffc6fd.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 13 May 2026 17:24:32 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Re: @peertube&#x2F;http-signature on Thu, 21 May 2026 20:07:50 GMT]]></title><description><![CDATA[<p dir="auto">Thanks <a href="https://activitypub.space/user/chocobozzz%40framapiaf.org" rel="nofollow ugc">@chocobozzz@framapiaf.org</a> for the explanation. It does seem like the library is still usable.</p>
<p dir="auto">In a separate thread, <a href="https://activitypub.space/user/mradcliffe%40nokoto.org" rel="nofollow ugc">@mradcliffe@nokoto.org</a> mentioned that he had a PR/branch that introduced RFC 9421 support:</p>
<p dir="auto"><a href="https://nokoto.org/user/3/replies/317" rel="nofollow ugc">https://nokoto.org/user/3/replies/317</a></p>
<p dir="auto">It looks like you're the maintainer... would you be open to having that merged if someone (aka me) implements and tests it?</p>
]]></description><link>https://fedi.wiki/post/https://activitypub.space/post/1927</link><guid isPermaLink="true">https://fedi.wiki/post/https://activitypub.space/post/1927</guid><dc:creator><![CDATA[julian@activitypub.space]]></dc:creator><pubDate>Thu, 21 May 2026 20:07:50 GMT</pubDate></item><item><title><![CDATA[Reply to Re: @peertube&#x2F;http-signature on Fri, 15 May 2026 12:54:29 GMT]]></title><description><![CDATA[<p dir="auto"><a href="https://activitypub.space/user/chocobozzz" rel="nofollow ugc">@Chocobozzz</a> thanks! I'll take a look at the library you linked to.</p>
<p dir="auto">Also I'll figure out why your message didn't come through <img src="https://fedi.wiki/assets/plugins/nodebb-plugin-emoji/emoji/android/1f914.png?v=cfc437c8754" class="not-responsive emoji emoji-android emoji--thinking_face" style="height:23px;width:auto;vertical-align:middle" title="🤔" alt="🤔" /></p>
]]></description><link>https://fedi.wiki/post/https://activitypub.space/post/1882</link><guid isPermaLink="true">https://fedi.wiki/post/https://activitypub.space/post/1882</guid><dc:creator><![CDATA[julian@activitypub.space]]></dc:creator><pubDate>Fri, 15 May 2026 12:54:29 GMT</pubDate></item><item><title><![CDATA[Reply to Re: @peertube&#x2F;http-signature on Fri, 15 May 2026 12:51:17 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">My answer seems to not have been received here so I copy the link: <a href="https://framapiaf.org/%5B@Chocobozzz%5D(https://activitypub.space/user/chocobozzz)/116577305060483143" rel="nofollow ugc">https://framapiaf.org/[@Chocobozzz](https://activitypub.space/user/chocobozzz)/116577305060483143</a></p>
]]></description><link>https://fedi.wiki/post/https://activitypub.space/post/1881</link><guid isPermaLink="true">https://fedi.wiki/post/https://activitypub.space/post/1881</guid><dc:creator><![CDATA[chocobozzz@activitypub.space]]></dc:creator><pubDate>Fri, 15 May 2026 12:51:17 GMT</pubDate></item><item><title><![CDATA[Reply to Re: @peertube&#x2F;http-signature on Fri, 15 May 2026 07:01:47 GMT]]></title><description><![CDATA[<p><span><a href="/user/julian%40activitypub.space">@<span>julian</span></a></span> Hi,</p><p>In fact peertube doesn't use this library anymore. We switched to <a href="https://github.com/misskey-dev/node-http-message-signatures" rel="nofollow noopener"><span>https://</span><span>github.com/misskey-dev/node-ht</span><span>tp-message-signatures</span></a></p><p>Ironically, Misskey still uses <span><a href="https://framapiaf.org/@peertube">@<span>peertube</span></a></span>/http-signature. </p><p>The former dev of @misskey-dev/node-http-message-signatures expressed concerns about the maintenance status of the library: <a href="https://github.com/Chocobozzz/PeerTube/issues/7372" rel="nofollow noopener"><span>https://</span><span>github.com/Chocobozzz/PeerTube</span><span>/issues/7372</span></a></p><p>However, upon reviewing it, I found no issues or security considerations with the library. <span><a href="https://framapiaf.org/@peertube">@<span>peertube</span></a></span>/http-signature (based on <a href="https://github.com/TritonDataCenter/node-http-signature" rel="nofollow noopener"><span>https://</span><span>github.com/TritonDataCenter/no</span><span>de-http-signature</span></a>) isn't really maintained either</p>]]></description><link>https://fedi.wiki/post/https://framapiaf.org/users/Chocobozzz/statuses/116577305060483143</link><guid isPermaLink="true">https://fedi.wiki/post/https://framapiaf.org/users/Chocobozzz/statuses/116577305060483143</guid><dc:creator><![CDATA[chocobozzz@framapiaf.org]]></dc:creator><pubDate>Fri, 15 May 2026 07:01:47 GMT</pubDate></item></channel></rss>