<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Entropy on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/entropy/</link>
    <description>Recent content in Entropy on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/entropy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Hardware Entropy Management: haveged vs rng-tools vs jitterentropy-rngd</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-hardware-entropy-management-haveged-rng-tools-jitterentropy-rngd-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-hardware-entropy-management-haveged-rng-tools-jitterentropy-rngd-guide/</guid>
      <description>&lt;p&gt;Linux systems depend on a steady supply of high-quality randomness for cryptographic operations — TLS handshakes, SSH key generation, GPG encryption, and secure token creation all draw from the kernel&amp;rsquo;s entropy pool. On virtual machines, embedded devices, and headless servers, the traditional entropy sources (keyboard, mouse, disk I/O) are often insufficient, leading to blocked reads from &lt;code&gt;/dev/random&lt;/code&gt; and degraded system performance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
