<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Signatures on Nalar</title>
    <link>https://nalar.dev/tags/signatures/</link>
    <description>Recent content in Signatures on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/signatures/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HTTP Message Signatures Bind Selected HTTP Components</title>
      <link>https://nalar.dev/http-message-signatures-bind-selected-http-components/</link>
      <pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/http-message-signatures-bind-selected-http-components/</guid>
      <description>&lt;p&gt;TLS protects an HTTP exchange while traffic moves across a TLS connection, but some application designs need a cryptographic assertion attached to the HTTP message itself. A gateway may terminate TLS before forwarding a request, a service may need to authenticate selected request metadata, or a message may cross several HTTP hops where transport protection and application trust are separate concerns.&lt;/p&gt;&#xA;&lt;p&gt;HTTP Message Signatures, specified in RFC 9421, address that boundary. A signer chooses HTTP message components, constructs a defined signature base, signs it, and sends metadata that tells a verifier which components and parameters were covered. The mechanism is selective by design: a signature does not automatically cover every field or every property of the message.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
