<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Encrypted ClientHello on Nalar</title>
    <link>https://nalar.dev/tags/encrypted-clienthello/</link>
    <description>Recent content in Encrypted ClientHello on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/encrypted-clienthello/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Encrypted ClientHello Separates Public Routing From Private TLS Identity</title>
      <link>https://nalar.dev/encrypted-clienthello-separates-public-routing-from-private-tls-identity/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/encrypted-clienthello-separates-public-routing-from-private-tls-identity/</guid>
      <description>&lt;h1 id=&#34;encrypted-clienthello-separates-public-routing-from-private-tls-identity&#34;&gt;Encrypted ClientHello Separates Public Routing From Private TLS Identity&lt;/h1&gt;&#xA;&lt;p&gt;TLS 1.3 encrypts most handshake messages, yet a conventional connection still exposes the initial &lt;code&gt;ClientHello&lt;/code&gt;. That message can contain Server Name Indication, allowing an on-path observer to associate a connection with a requested hostname before application traffic is protected.&lt;/p&gt;&#xA;&lt;p&gt;Encrypted ClientHello, standardized in RFC 9849, changes that boundary. The client constructs a private &lt;code&gt;ClientHelloInner&lt;/code&gt; containing the service-specific parameters and wraps it inside a public &lt;code&gt;ClientHelloOuter&lt;/code&gt;. The outer message remains usable by the client-facing infrastructure, while sensitive inner fields are protected with Hybrid Public Key Encryption.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
