Changelog¶
Versions are year-based with a strict backward compatibility policy. The third digit is only for regressions.
16.0.0 (2016-01-02)¶
Vendoring argon2
@ 421dafd2a8af5cbb215e16da5953663eb101d139.
Deprecations:¶
hash_password()
,hash_password_raw()
, andverify_password()
should not be used anymore. For hashing passwords, use the newargon2.PasswordHasher
. If you want to implement your own higher-level abstractions, use the new low-level APIshash_secret()
,hash_secret_raw()
, andverify_secret()
from theargon2.low_level
module. If you want to go really low-level,core()
is for you. The old functions will not raise any warnings though and there are no immediate plans to remove them.
Changes:¶
- Add
argon2.PasswordHasher
. A higher-level class specifically for hashing passwords that also works on Unicode strings. - Add
argon2.low_level
module with low-level API bindings for building own high-level abstractions.
15.0.1 (2015-12-18)¶
Vendoring argon2
@ 4fe0d8cda37691228dd5a96a310be57369403a4b.
Changes:¶
- Fix
long_description
on PyPI.
15.0.0 (2015-12-18)¶
Vendoring argon2
@ 4fe0d8cda37691228dd5a96a310be57369403a4b.
Changes:¶
verify_password()
doesn’t guess the hash type if passedNone
anymore. Supporting this resulted in measurable overhead (~ 0.6ms vs 0.8ms on my notebook) since it had to happen in Python. That means that naïve usage of the API would give attackers an edge. The new behavior is that it has the same default value ashash_password()
such thatverify_password(hash_password(b"password"), b"password")
still works.- Conditionally use the SSE2-optimized version of
argon2
on x86 architectures. - More packaging fixes. Most notably compilation on Visual Studio 2010 for Python 3.3 and 3.4.
- Tweaked default parameters to more reasonable values. Verification should take between 0.5ms and 1ms on recent-ish hardware.
15.0.0b5 (2015-12-10)¶
Vendoring argon2
@ 4fe0d8cda37691228dd5a96a310be57369403a4b.
Initial work.
Previous betas were only for fixing Windows packaging.
The authors of argon2
were kind enough to help me to get it building under Visual Studio 2008 that we’re forced to use for Python 2.7 on Windows.