The goal of this plugin is to shore up the WordPress authentication using standard security practice recommendations. At this time, the plugin improves WordPress authentication by doing the following:
Enforcing uncompromised passwords
This plugin prevents someone from using passwords that have appeared in data breaches. Whenever someone logs into a WordPress site, it’ll verify their password using the Have I been pwned? API. If their password appeared in a data breach, the plugin will prevent them from logging in until they reset their password.
By default, this level of enforcement is only done on an account that has the “administrator” role. You can change which roles have their passwords enforced from the settings page. For people that have a role where there’s no password enforcement, the plugin will show a warning when they log in with a compromised password.
The enforcement of uncompromised password also extends to when someone resets or changes their password. That said, in those situations, using an uncompromised password is mandatory. Someone will never be able to reset or change their password to one that’s appeared in a security breach. (As long as the plugin is able to contact the API.)
Using stronger password hashing
The plugin also encrypts passwords using either the bcrypt and Argon2 hashing functions. These are the strongest hashing functions available in PHP. Argon2 is available natively starting with PHP 7.2, but the plugin can also encrypt passwords on older PHP versions using the libsodium compatibility layer introduced in WordPress 5.2.
You don’t have to do anything to convert your password hash to a stronger encryption standard. The plugin will take care of converting it the next time that you log in after installing the plugin. If you decide to remove the plugin, your password will continue working and remain encrypted until you reset it.
It’s also worth noting that using a stronger hashing function is only important in the advent of a data breach. A stronger password hashing function makes decrypting the passwords from the data breach a lot harder to do. This combined with the enforcement of uncompromised passwords will help ensure that those passwords are never decrypted. (Or at least without significant effort.)
Wait so are you sending my password to a 3rd party!?
No, the plugin never sends your full password to a 3rd party for verification. The plugin only sends the first five characters of the SHA-1 hashed password to a 3rd party. The 3rd party then sends back all passwords with a hash that starts with those five characters.
The plugin then handles the rest of the password validation itself. It compares the SHA-1 hashed version of your password to the passwords returned by the 3rd party. We call this process k-anonymity. (You can read more about validating leaked passwords with it here.)
བྱས་རྗེས་འཇོག་མཁན། & གསར་འབྱེད་པ།
“Passwords Evolved” is open source software. The following people have contributed to this plugin.བྱས་རྗེས་འཇོག་མཁན།
“Passwords Evolved” has been translated into 3 locales. Thank you to the translators for their contributions.
ཁྱེད་ཀྱི་སྐད་ཡིག་ནང་ལ་ “Passwords Evolved” ཡིག་སྒྱུར་བྱོས།
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
- Use different capabilities for admin pages so that they work when plugins directory isn’t writeable [carlalexander]
- Add missing echo on
- Remove call to api on every request [carlalexander]
- Add informal (default) and formal german translations [carstenbach]
- Fixed fatal error when installed as a mu-plugin [carlalexander]
- Added support for libsodium [carlalexander]
- Bump minimum PHP version to 5.6 [carlalexander]
- Fixed missing
settings_savedstring in English translation [carlalexander]
- Added missing echo when translating
- Added Brazilian Portuguese translation [celsobessa]
- Reworked how the plugin handles its default translation [carlalexander]
Improved how the API client and password generator handled if the API was online or not.
Reworked plugin to use the new version of the HIBP API (Have I been pwned? API) which supports k-anonymity. This allows the plugin to be used in production now.