Title: how to force bcrypt hashing algorithm?
Last modified: November 15, 2020

---

# how to force bcrypt hashing algorithm?

 *  Resolved [Thomymaster](https://wordpress.org/support/users/thomymaster/)
 * (@thomymaster)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/how-to-force-bcrypt-hashing-algorithm/)
 * Hello
 * WP Version: 5.5.3
 * How can i force to use the bcrypt hashing algorithm and not the Argon2 algo even
   if its available?
 * Best,
    Thomas

Viewing 1 replies (of 1 total)

 *  Plugin Author [Ayesh Karunaratne](https://wordpress.org/support/users/ayeshrajans/)
 * (@ayeshrajans)
 * [5 years, 6 months ago](https://wordpress.org/support/topic/how-to-force-bcrypt-hashing-algorithm/#post-13667357)
 * Hi [@thomymaster](https://wordpress.org/support/users/thomymaster/),
    This plugin
   uses the default hashing algorithm PHP itself suggests. From all versions PHP
   from 5.6 through 7.4 and even 8.0, that is bcrypt. Even if you don’t make any
   configuration changes, this plugin uses bcrypt. You need explicitly configure
   it to use Argon2(ID).
 * Hope that answers question. Feel free to re-open otherwise. Cheers.

Viewing 1 replies (of 1 total)

The topic ‘how to force bcrypt hashing algorithm?’ is closed to new replies.

 * ![](https://ps.w.org/password-hash/assets/icon-256x256.png?rev=1569084)
 * [PHP Native Password Hash](https://wordpress.org/plugins/password-hash/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/password-hash/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/password-hash/)
 * [Active Topics](https://wordpress.org/support/plugin/password-hash/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/password-hash/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/password-hash/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Ayesh Karunaratne](https://wordpress.org/support/users/ayeshrajans/)
 * Last activity: [5 years, 6 months ago](https://wordpress.org/support/topic/how-to-force-bcrypt-hashing-algorithm/#post-13667357)
 * Status: resolved