In this RFC

It looks like Argon2i is now implemented in PHP with the password_* functions (though requires a compile flag ???)

Since the sodium extensions used the Argon2id variant by default, would it be prudent to make sure the php password_* functions can *verify* 2d and 2id variant hashes, even if it does not set them by default?

Real world scenario - WordPress plugin I am working on uses libsodium for WordPress password management, upgrading users to Argon2id hashes as the log in.

But if that plugin is every removed, those users with upgraded hashes then have to do a forgotten password reset because WordPress and PHP native functions don't know what to do with a Argon2id hash.

But if PHP knew what to do with it natively, then maybe at least WordPress installs on a new enough version of PHP wouldn't have an issue when this plugin is installed and then at a later date removed.

Anyway it just seems to me that if even if Argon2i is the only supported variant for creating hashes, if the argon2 libraries are going to be linked against, it wouldn't be a bad idea to support validating all three of the argon2 variants.

PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:

Reply via email to