<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mutual TLS on Nalar</title>
    <link>https://nalar.dev/tags/mutual-tls/</link>
    <description>Recent content in Mutual TLS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/mutual-tls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mutual TLS Moves Client Identity Into the Handshake</title>
      <link>https://nalar.dev/mutual-tls-moves-client-identity-into-the-handshake/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/mutual-tls-moves-client-identity-into-the-handshake/</guid>
      <description>&lt;h1 id=&#34;mutual-tls-moves-client-identity-into-the-handshake&#34;&gt;Mutual TLS Moves Client Identity Into the Handshake&lt;/h1&gt;&#xA;&lt;p&gt;An internal API can receive a perfectly encrypted TLS connection and still have no cryptographic evidence about the process at the other end. Ordinary server-authenticated TLS proves the server&amp;rsquo;s identity to the client and protects traffic in transit, but the application still needs another mechanism to identify its caller.&lt;/p&gt;&#xA;&lt;p&gt;Mutual TLS, commonly shortened to mTLS, adds certificate-based client authentication to that exchange. The server requests a client certificate, validates the presented chain according to its trust policy, and verifies a signature proving possession of the corresponding private key. The result is a transport connection associated with a cryptographic client identity before ordinary application requests are processed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
