rfc:password_registry
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
rfc:password_registry [2018/11/06 16:56] – pollita | rfc:password_registry [2018/11/06 19:47] – pollita | ||
---|---|---|---|
Line 63: | Line 63: | ||
====== Minimizing impact to BC ====== | ====== Minimizing impact to BC ====== | ||
- | In order to minimize the impact of the above BC. we could overload the **password_hash()** and **password_needs_rehash()** methods to accept integer values 0, 1, 2, and 3 to function as aliases for DEFAULT, BCRYPT, ARGIN2I, and ARGON2ID, respectively. | + | In order to minimize the impact of the above BC. we could overload the **password_hash()** and **password_needs_rehash()** methods to accept integer values 0, 1, 2, and 3 to function as aliases for DEFAULT, BCRYPT, ARGIN2I, and ARGON2ID, respectively. Using an int would therefore work, but would produce a deprecation warning. This is being presented as a separate vote below. |
===== Extension Changes ===== | ===== Extension Changes ===== |
rfc/password_registry.txt · Last modified: 2018/12/25 13:07 by cmb