<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Sun, 19 May 2013 14:14:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Anthony Ferrara: Seven Ways To Screw Up BCrypt]]></title>
      <guid>http://www.phpdeveloper.org/news/18934</guid>
      <link>http://www.phpdeveloper.org/news/18934</link>
      <description><![CDATA[<p>
If you're going to be rolling your own user handling in your application, no doubt you've heard that something like bcrypt-ing your passwords is a good idea. Well, <i>Anthony Ferrara</i> <a href="http://blog.ircmaxell.com/2012/12/seven-ways-to-screw-up-bcrypt.html">has some suggestions</a> for you and shows you seven ways you can "screw up" when trying ti implement it.
</p>
<blockquote>
There are numerous articles on the web about how to properly use bcrypt in PHP. So this time, rather than write yet-another-how-to-use-bcrypt article, I'm going to focus on the mistakes that are commonly made when implementing bcrypt. 
</blockquote>
<p>Here's the list of seven ways (each has its own description in the post):</p>
<ul>
<li>Using A Non-Random Salt
<li>Using An Incorrect Random Source for Salt Generation
<li>Using Too Weak Of A Cost Parameter
<li>Using The Wrong PHP Version
<li>Using The Wrong Prefix
<li>Not Checking For Errors
<li>Not Using A Library
</ul>
<p>
He also includes two "bonus" things to consider: "Not Using A Timing Safe Comparison" and "Not Encoding The Salt Correctly".
</p>]]></description>
      <pubDate>Fri, 21 Dec 2012 12:20:04 -0600</pubDate>
    </item>
  </channel>
</rss>
