It’s extremely easy to increase the number of iterations in the default ASP.NET Core Identity
PasswordHasher. ASP.NET Core Identity will also take care of rehashing the password if it was previously hashed with a lower iteration count, so you can increase this at any time. However, test the performance of the login page of your application before changing this number, to make sure you don’t set it too high.
Password Hashing and Salting Basics
I’m not going to cover why you should be hashing passwords in your application. Presumably, if you’ve landed on this blog post, you already know why hashing passwords is infinitely more secure than encrypting them (or worse… storing them in plaintext). Andrew Lock goes into detail why if you’re looking for that information. Instead, I’m going to talk about hashing iterations, specifically.
ASP.NET Core Identity Default – 10,000 iterations
As Andrew mentions in his blog post linked above, the default password hashing algorithm is PBKDF2 with HMAC-256, a 128-bit salt, 256-bit subkey, and 10,000 iterations. The 10,000 iterations is the part we’re interested in for this blog post. In June 2017, the NIST recommended at least 10,000 iterations on the 25th page of their report under section 220.127.116.11, so this is a reasonable default.
Why do iterations matter?
Iterations is the “work factor” for how many times you hash a password before you store it in your database (if you’re not using something like Auth0 that stores your application’s password hashes for you). In the default ASP.NET Core Identity implementation, you would take a password and hash it once. Then you hash the hash, then you hash that double hash, and so on until you’ve hashed the password 10,000 times.
The more times you hash the password, the longer it takes your CPU to complete that operation, and therefore the longer it would take someone to brute force the password, if someone were to ever get your password hash. So if someone malicious were to ever compromise your database containing your application’s usernames and password hashes (it’s not like that’s ever happened before), the higher your iteration count is, the harder it is for them to crack your password hashes. The goal here is to buy time, because eventually (given enough time), they will crack a user’s password hash. The more time you have to notify a user and give them a chance to change their password, the better.
So if you increase the number of iterations from 10,000 to 100,000, you are making it 10x harder for someone to crack your hash, because their CPU/GPU has 10x more work to do.
While 10,000 iterations may (or may not) be enough for your application today, as hardware gets faster and faster, there will come a day when 10,000 iterations with this algorithm will certainly not be enough. We’ve already seen weaker algorithms get cracked like MD-5 and SHA-1. Therefore, it is critical that we’re able to change this at some point to maintain the proper security for our application.
How can I change it?
As mentioned in the tldr; – it’s just a one-liner to change it in ASP.NET Core Identity, which is a HUGE upgrade from regular ASP.NET Identity where you had to provide a whole new PasswordHasher implementation. Simply go to
ConfigureServices and configure
PasswordHasherOptions.IterationCount and that’s it!
But won’t this break my existing users?
Nope, it won’t break your existing users! That’s the cherry on top. The iteration count is also stored as part of the password hash in the Identity database (more details here).
For example, let’s say you started your application with the default of 10,000 iterations, and then later you decided to increase it to 25,000. When a user provides a valid username and password combination to your login page/endpoint, the
PasswordHasher checks to see how many iterations the current password is hashed with. It then checks to see if that database-stored iteration count is less than
PasswordHasherOptions.IterationCount. In this case, the hash is stored in the database with an iteration count of 10,000 and the
PasswordHasherOptions.IterationCount is 25,000. Therefore, the
PasswordHasher will rehash the password using 25,000 iterations and save it back to the database. This allows you to progressively upgrade your site to a stronger iteration count.
If you’re curious how this works, check out the source code.
Obviously, if a user never logs in again, their password will be stored at the lower iteration count forever, which may be a problem. There are ways to solve this problem, but that’s outside the scope of this post.
NOTE: It was mentioned subtly, so I’m going to call it out again. It will only re-hash the password if the database-stored iteration count is LESS than the
PasswordHasherOptions.IterationCount. So if you do something silly like set the
PasswordHasherOptions.IterationCount to 1 trillion temporarily, and then reset it back to 10,000 later, every user who logged into your site when it was 1 trillion will NEVER be downgraded to 10,000. This will likely be a performance problem and leave you in a world of hurt. More on performance next.
Like anything in software, there are always trade-offs. There is no free lunch. If you increase the number of iterations, then your server(s) will have to do extra work every time you log someone in. So you probably don’t want to set this number to something like 1 trillion, because your server probably won’t return in a timely manner. As mentioned in bold above, if you set this iteration count to a high number and then later lower it, the
PasswordHasher will NOT downgrade the password hash for you. So you will need to do appropriate stress testing on what your environment can handle.
As always, there’s a trade-off between security and convenience. You can’t have both. You will likely need to find a happy medium between a strong iteration count and how long it takes a user to login. I’m not a security expert, but Brock Allen (who is a security expert) said in 2014 that – “The general consensus is that it should take about one second to compute a password hash.” In that same article, Brock gives a formula that says we should be using 512,000 iterations in 2018. Using 512,000 iterations running on my laptop’s 8th gen i7 results in a login process that takes ~900ms on average. Again – do what makes sense for your scenario and make sure you test appropriately.
If you’re using something like Auth0, Okta, Azure B2C, any other cloud identity-as-a-service solution, or you’re exclusively using Social Logins, then you likely won’t need to worry about any of this. They are choosing an iteration count/work factor/algorithm for you. However, there are still many apps who store password hashes in their own proprietary databases, and I didn’t see a post on how to configure this, so that’s why I typed this up.
As mentioned a few times in this post, I am not a security expert and I’ve tried to stray away from giving specific advice in this post. Do what makes sense for your application.
Hope this helps!