<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cryptography on Nalar</title>
    <link>https://nalar.dev/tags/cryptography/</link>
    <description>Recent content in Cryptography on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/cryptography/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Constant-Time Comparison for Authentication Tags and Secret Values</title>
      <link>https://nalar.dev/constant-time-comparison-for-authentication-tags-and-secret-values/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/constant-time-comparison-for-authentication-tags-and-secret-values/</guid>
      <description>&lt;p&gt;Security-sensitive verification often ends with a simple question: does an untrusted value equal the value the server expected? For ordinary application data, a normal equality operator is appropriate. For authentication tags and some secret values, however, an equality operation that stops at the first mismatch can expose information through execution time.&lt;/p&gt;&#xA;&lt;p&gt;Timing-safe comparison APIs reduce that risk by avoiding content-dependent short-circuit behavior. They are small tools, but using them correctly requires more than replacing one equality operator.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
