Closed ldsenow closed 4 years ago
I believe the issue was with the behavior that, by default, there was a calculation of the maximum lockable size on any lock fail in SecureArray. That calculation takes a lot of time and is really only useful for debugging or giggles. It is now off by default and settable by a static variable.
Not sure why is so slow on one of the servers that I have, the spec of the server is 4 cores, 2.5ghz, 16g memory, win2012 server and bellow is my argon2i config (.net 4.72)
I don't think it is a very high requirement. However, it takes 20s to hash a password. I don't what is wrong there.
Is there any gotcha?
Look forward to hearing the response