-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Investigate memory footprint of Argon hashing #650
Comments
The private static final int ALGORITHM_ID = Argon2Parameters.ARGON2_i;
private static final int VERSION = Argon2Parameters.ARGON2_VERSION_13;
private static final int ITERATIONS = 3;
private static final int MEMORY_POW_2 = 15;
private static final int PARALLELISM = 16;
private static final int SALT_SIZE = 16; The memory usage of one computation is 32 MB. High memory usage is expected during high load. We can introduce a limit for maximum number of concurrent hash computations in PowerAuth server. I do not think we should change the |
@romanstrobl After reading some articles about this, I think we should allow overriding these parameters to enable benchmark based settings in particular environment. See https://datatracker.ietf.org/doc/html/draft-irtf-cfrg-argon2-04#section-4 We could suggest using some benchmarking tool to select the right attributes: |
Yes, I guess we can do that, with a warning that insecure settings may cause possibility of leakage of secrets. |
We can probably set some bare minimum. Where did we take the current values? |
Juraj did an analysis. |
From performance testing under a very heavy load, we obtained the following stack trace indicating that our password hashing might have larger memory impact then desired:
The text was updated successfully, but these errors were encountered: