Bcrypt + AES

README.md

Use Case

If you encrypt your hashes before you store them in a relational database, this creates another layer of defense against password leaking IF AND ONLY IF the database is on separate hardware from the webserver.

If an attacker can compromise your database, it's very likely they can also compromise your filesystem. "SELECT '<?php reverse_shell_code_here();' INTO OUTFILE /var/www/llehs.php;' and whatnot.

Dependencies

Depends on this:

• https://github.com/defuse/php-encryption/ for authenticated encryption (AES-128-CBC + HMAC-SHA-256)

And one of these two:

• PHP 5.5
• https://github.com/ircmaxell/password_compat

In response to http://blog.ircmaxell.com/2015/03/security-issue-combining-bcrypt-with.html

PasswordLock.php

<?php

namespace Sarciszewski\Gists;

/**
 * This is a proof of concept code! DO NOT USE THIS!
 */
class PasswordLock
{
    const KEY = '4ff556f7b1db2dd95906c21a45ef00344abdb38934450263ee7a908facc05070';
    // ^-- SHA-256("Has James Clapper Been Indicted For Perjury Yet?")
    
    /**
     * 1. Hash password
     * 2. Encrypt-then-MAC the hash
     * 
     * @param string $password
     * @return string
     */
    public static function hashAndEncrypt($password)
    {
        return \Crypto::encrypt(
            \password_hash($password, PASSWORD_DEFAULT),
            \hex2bin(self::KEY)
        );
    }
    
    /**
     * 1. VerifyHMAC-then-Decrypt the ciphertext to get the hash
     * 2. Verify that the password matches the hash
     * 
     * @param string $password
     * @param string $ciphertext
     * @return boolean
     */
    public static function decryptAndVerify($password, $ciphertext)
    {
        $hash = \Crypto::decrypt(
            $ciphertext,
            \hex2bin(self::KEY)
        );
        return \password_verify($password, $hash);
    }
}