<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Password Hash Upgrade on Rietta Cybersecurity</title>
    <link>https://rietta.com/glossary/password-hash-upgrade/</link>
    <description>Recent content in Password Hash Upgrade on Rietta Cybersecurity</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>1999-2026 Rietta Inc. All Rights Reserved.</copyright>
    <lastBuildDate>Fri, 02 Oct 2026 08:57:59 -0400</lastBuildDate>
    <atom:link href="https://rietta.com/glossary/password-hash-upgrade/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What is the difference between bcrypt and SHA256?</title>
      <link>https://rietta.com/blog/bcrypt-not-sha-for-passwords/</link>
      <pubDate>Fri, 05 Feb 2016 10:23:27 -0500</pubDate>
      <guid>https://rietta.com/blog/bcrypt-not-sha-for-passwords/</guid>
      <description>&lt;p&gt;TL;DR; SHA1, SHA256, and SHA512 are all &lt;em&gt;fast hashes&lt;/em&gt; and are bad for passwords. SCRYPT and BCRYPT are both a &lt;em&gt;slow hash&lt;/em&gt; and are good for passwords. Always use slow hashes, never fast hashes.&lt;/p&gt;&#xA;&lt;p&gt;SANS&amp;rsquo; &lt;a href=&#34;https://software-security.sans.org/resources/swat&#34;&gt;Securing Web Application Technologies&#xA;[SWAT] Checklist&lt;/a&gt; is offering a bit of bad security advice for the everyday web application developer, under the heading &amp;ldquo;Store User Passwords Using A Strong, Iterative, Salted Hash&amp;rdquo;:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;User passwords must be stored using secure hashing techniques with a strong algorithm like SHA-256. Simply hashing the password a single time does not sufficiently protect the password. Use iterative hashing with a random salt to make the hash strong.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
  </channel>
</rss>
