<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>TLS 1.3 on Nalar</title>
    <link>https://nalar.dev/tags/tls-1.3/</link>
    <description>Recent content in TLS 1.3 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/tls-1.3/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TLS 1.3 Early Data Trades a Round Trip for Replay Exposure</title>
      <link>https://nalar.dev/tls-1-3-early-data-trades-a-round-trip-for-replay-exposure/</link>
      <pubDate>Tue, 15 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/tls-1-3-early-data-trades-a-round-trip-for-replay-exposure/</guid>
      <description>&lt;h1 id=&#34;tls-13-early-data-trades-a-round-trip-for-replay-exposure&#34;&gt;TLS 1.3 Early Data Trades a Round Trip for Replay Exposure&lt;/h1&gt;&#xA;&lt;p&gt;A resumed TLS 1.3 connection can carry application bytes before the server has completed the new handshake. That latency reduction is attractive on paths where a round trip is expensive, but it changes a security property that applications often assume without naming it: a protected request is not necessarily fresh merely because the server decrypted it successfully.&lt;/p&gt;&#xA;&lt;p&gt;TLS 1.3 calls this facility early data, commonly described as 0-RTT. It is available when the client and server share a pre-shared key, including one established through a prior connection. The client can derive keys and send application data in its first flight rather than waiting for the server&amp;rsquo;s handshake messages.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
