<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cryptographic Randomness on Nalar</title>
    <link>https://nalar.dev/tags/cryptographic-randomness/</link>
    <description>Recent content in Cryptographic Randomness on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/cryptographic-randomness/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Generate Security Tokens with Cryptographic Randomness</title>
      <link>https://nalar.dev/generate-security-tokens-with-cryptographic-randomness/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/generate-security-tokens-with-cryptographic-randomness/</guid>
      <description>&lt;p&gt;Many security features depend on a value that an attacker must not be able to guess. Password-reset links, email-verification links, invitation codes, session identifiers, and one-time capability URLs are common examples. If such a token is predictable, an attacker may not need to steal it. They may be able to guess a valid value instead.&lt;/p&gt;&#xA;&lt;p&gt;The defensive requirement is therefore stronger than “make the token look random.” A security token needs enough &lt;strong&gt;entropy&lt;/strong&gt;, meaning uncertainty from the attacker&amp;rsquo;s point of view, and it needs to come from a generator designed for security-sensitive randomness.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
