<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Delegated Credentials on Nalar</title>
    <link>https://nalar.dev/tags/delegated-credentials/</link>
    <description>Recent content in Delegated Credentials on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 21 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/delegated-credentials/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TLS Delegated Credentials Limit Front-End Key Exposure</title>
      <link>https://nalar.dev/tls-delegated-credentials-limit-front-end-key-exposure/</link>
      <pubDate>Mon, 21 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/tls-delegated-credentials-limit-front-end-key-exposure/</guid>
      <description>&lt;h1 id=&#34;tls-delegated-credentials-limit-front-end-key-exposure&#34;&gt;TLS Delegated Credentials Limit Front-End Key Exposure&lt;/h1&gt;&#xA;&lt;p&gt;A large TLS deployment often terminates connections on machines far from the system that manages its certificate private key. Copying that long-lived key to every front end simplifies handshakes, but it also enlarges the set of systems whose compromise can expose the certificate key.&lt;/p&gt;&#xA;&lt;p&gt;RFC 9345 defines delegated credentials for TLS and DTLS 1.3. A certificate holder can sign a separate, short-lived credential containing another public key. A compatible endpoint then uses the delegated credential and its private key for handshake authentication while the certificate private key can remain in a more restricted environment.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
