<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Password-Hashing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/password-hashing/</link>
    <description>Recent content in Password-Hashing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/password-hashing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>bcrypt vs Argon2id vs scrypt in 2026: Which Password Hashing Algorithm Should You Actually Ship?</title>
      <link>https://www.pistack.xyz/posts/2026-10-10-password-hashing-libraries-bcrypt-argon2-scrypt-comparison/</link>
      <pubDate>Sat, 10 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-10-password-hashing-libraries-bcrypt-argon2-scrypt-comparison/</guid>
      <description>&lt;p&gt;Your database is one leaked backup away from being a credential dump. In 2026 the average attacker rents GPU time by the minute, and a password hash that cost 200 ms to produce on your server costs a few microseconds per guess on hardware that was designed for exactly this job. Hashing is the only control standing between a stolen table row and a working login — and the algorithm you pick decides how long that wall holds.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
