Checks if the particular crypt algorithm is compatible with the salt string or crypted password.

Checks if the crypted password matches the given password bytes.

Checks if the crypted password matches the given password string.

Creates a one-way password hash (crypted password) from password bytes.

Creates a one-way password hash (crypted password) from a password string.

Creates a one-way password hash (crypted password) from password bytes. Options modify the crypt operation.

Creates a one-way password hash (crypted password) from password bytes and a salt string. The salt can be produced using GenerateSalt(CrypterOptions). Because crypted passwords take the form algorithm+salt+hash, if you pass a crypted password as the salt parameter, the same algorithm and salt will be used to re-crypt the password. Since randomness comes from the salt, the same salt means the same hash, and so the same crypted password will result. Therefore, this method can both generate *and* verify crypted passwords.

Creates a one-way password hash (crypted password) from a password string. Options modify the crypt operation.

Creates a one-way password hash (crypted password) from a password string and a salt string. The salt can be produced using GenerateSalt(CrypterOptions). Because crypted passwords take the form algorithm+salt+hash, if you pass a crypted password as the salt parameter, the same algorithm and salt will be used to re-crypt the password. Since randomness comes from the salt, the same salt means the same hash, and so the same crypted password will result. Therefore, this method can both generate *and* verify crypted passwords.

Generates a salt string with default options. The purpose of salt is to make dictionary attacks against a whole password database much harder, by causing the crypted password to be different even if two users have the same uncrypted password.

Generates a salt string. Options are used to modify the salt generation. The purpose of salt is to make dictionary attacks against a whole password database much harder, by causing the crypted password to be different even if two users have the same uncrypted password. Randomness in a crypted password comes from its salt string, as do all recorded options. The same salt string, when combined with the same password, will generate the same crypted password. If the salt string differs, the same password will generate a different crypted password (crypted passwords have the form algorithm+salt+hash, so the salt is always carried along with the crypted password).

Searches for a crypt algorithm compatible with the specified crypted password or prefix.

Blowfish crypt, sometimes called BCrypt. A very good choice.

Extended DES crypt.

LDAP schemes such as {SHA}.

MD5 crypt, supported by nearly all systems. A variant supports Apache htpasswd files.

PHPass crypt. Used by WordPress. Variants support phpBB and Drupal 7+.

Properties inherent to the particular crypt algorithm. These cannot be modified. See CrypterProperty for possible keys.

SHA256 crypt. A reasonable choice if you cannot use Blowfish crypt for policy reasons.

SHA512 crypt. A reasonable choice if you cannot use Blowfish crypt for policy reasons.

Traditional DES crypt.