<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Replay on Nalar</title>
    <link>https://nalar.dev/tags/replay/</link>
    <description>Recent content in Replay on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/replay/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TLS 1.3 Early Data Trades One Round Trip for Replay Exposure</title>
      <link>https://nalar.dev/tls-1-3-early-data-trades-one-round-trip-for-replay-exposure/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/tls-1-3-early-data-trades-one-round-trip-for-replay-exposure/</guid>
      <description>&lt;p&gt;A resumed TLS 1.3 connection can carry application bytes before the server finishes the new handshake. That latency reduction changes a security boundary: early data is protected in transit, yet the protocol does not give it the same replay property as ordinary post-handshake application data.&lt;/p&gt;&#xA;&lt;p&gt;The distinction matters when an endpoint maps one request to a state-changing operation. A captured early-data flight can be presented again under conditions in which a server accepts it, so confidentiality and integrity on the wire do not imply single execution.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
