Argon2id settings. Higher values = better?

[grb]

@Jirka_xxgmxx Welcome to the forum!

Increasing iterations definitely makes the master password harder to crack, but it also slows down the time it takes for you to log in or unlock your vault.

The effects of increasing parallelism is harder to understand. You can read some discussion in previous threads:

Recommended settings for Argon2

Argon2 support has been added, but I don’t see anything in the Bitwarden knowledge base to explain the different settings for Argon2: in particular the user settings for KDF parallelism and KDF memory (MB). Will Bitwarden be updating the knowledge base? And can anyone point to a resource explaining how to configure the above settings?

Argon2id Parallelism explanation

I’m having trouble understanding the meaning of the Parallelism setting for Argon2id. Does increasing parallelism make it harder or easier to brute force my password (assuming all other settings are kept the same)? my understanding is that increasing iterations and memory makes it harder to brute force my password. Does Parallelism also work like this where increasing it (e.g., from 2 to 4) make the password harder to brute force?

 

I think the main consensus is that if you increase parallelism, you should also increase memory. One way to think about it is that your main goal should be to increase memory; by increasing parallelism, you may be able to further increase the memory setting without unduly slowing down your own login/unlock experience.