Argon2
Argon2 is modern ASIC-resistant and GPU-resistant secure key derivation function. It has better password cracking resistance (when configured correctly) than PBKDF2, Bcrypt and Scrypt (for similar configuration parameters for CPU and RAM usage).
Variants of Argon2
The Argon2 function has several variants:
Argon2d – provides strong GPU resistance, but has potential side-channel attacks (possible in very special situations).
Argon2i – provides less GPU resistance, but has no side-channel attacks.
Argon2id – recommended (combines the Argon2d and Argon2i).
Config Parameters of Argon2
Argon2 has the following config parameters, which are very similar to Scrypt:
password
P
: the password (or message) to be hashedsalt
S
: random-generated salt (16 bytes recommended for password hashing)iterations
t
: number of iterations to performmemorySizeKB
m
: amount of memory (in kilobytes) to useparallelism
p
: degree of parallelism (i.e. number of threads)outputKeyLength
T
: desired number of returned bytes
Argon2 - Example
You can play with the Argon2 password to key derivation function online here: http://antelle.net/argon2-browser.
Argon2 Calculation in Python - Example
Now, we shall write some code in Python to derive a key from a password using the Argon2 algorithm.
First, install the Python package argon2_cffi
using the command:
Now, write the Python code to calculate Argon2:
Run the above code example: https://repl.it/@nakov/Argon2-in-Python.
The above code first derives a "raw hash" (256-bit key), which is argon2-based key derivation, just like with scrypt. It also derives a "argon2 hash", which holds the algorithm parameters, along with random salt and derived key. The later is used for password storing and verification. Finally, the calculated hashes are tested agains a correct and wrong password.
The Argon2 calculation takes several input configuration settings: time_cost (number of iterations), memory_cost (memory to use in KB), parallelism (how many parallel threads to use), hash_len (the size of the derived key), salt_len (the size of the random generated salt, typically 128 bits / 16 bytes).
Sample output from the above code execution:
Note that the argon2 hash in the above output is written in a standardized format, which holds the Argon2 algorithm config parameters + the derived key + the random salt. By design, the salt and the derived key should be different at each code execution.
Try to execute the above code several times to ensure that the derived key will be the same (because the salt is fixed) and the derived argon2 hash will be different at each execution (because a random salt is generated internally by the algorithm).
Try to change the time_cost or the memory_cost settings and see how they affect the execution time for the key derivation.
Storing Algorithm Settings + Salt + Hash Together
In many applications, frameworks and tools, Argon2 encrypted passwords are stored together with the algorithm settings and salt, into a single string (in certain format, like it was shown above), consisting of several parts, separated by $
character. For example, the password p@ss~123
can be stored in the Argon2 standard format like this (several examples are given, to make the pattern apparent):
All the above hashes hold the same password, but with different algotihm settings and different salt.
When to Use Argon2?
When configured properly Argon2 is considered a highly secure KDF function, one of the best available in the industry, so you can use it as general purpose password to key derivation algorithm, e.g. to when encrypting wallets, documents, files or app passwords. In the general case Argon2 is recommended over Scrypt, Bcrypt and PBKDF2.
Last updated