<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenSSL on Nalar</title>
    <link>https://nalar.dev/tags/openssl/</link>
    <description>Recent content in OpenSSL 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/openssl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Random Hex Is Not a Hash: Generating Cryptographic Random Values on Linux</title>
      <link>https://nalar.dev/generating-cryptographic-random-values-on-linux/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/generating-cryptographic-random-values-on-linux/</guid>
      <description>&lt;p&gt;A command such as &lt;code&gt;openssl rand -hex 32&lt;/code&gt; is often described as generating a &amp;ldquo;random hash.&amp;rdquo; The output certainly looks like a SHA-256 digest: 64 hexadecimal characters. But no hash operation has happened. OpenSSL generated 32 random bytes and encoded them as hexadecimal.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters. A hash function transforms input into a fixed-size digest. A cryptographically secure random number generator produces unpredictable bytes. If the requirement is a token, session secret, API credential, nonce, or other fresh random value, the random bytes are the important part. Hashing them afterward usually adds no useful unpredictability.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
