I referenced the OWASP cheat sheet for password storage and the pre-hashing of passwords, after reviewing the BitWarden cli/jslib source code, as a means to further secure the master password and subsequent hash and encryption key generation.
The enforcement of strong passwords in v1.8.0 is laxed, and should be addressed. An alternative would be to pre-hash the master password with SHA-256, then iterate the result with a stronger algorithm, such as ARGON2. Pre-hashing provides uniform password lengths, devoid of special characters, and consistent response times regardless of the passwords complexity.
Argon2 Argon2 is the winner of the Password Hashing Competition. The main advantage of Argon2 over AES-KDF is that it provides a better resistance against GPU/ASIC attacks (due to being a memory-hard function).
The number of iterations scales linearly with the required time. By increasing the memory parameter, GPU/ASIC attacks become harder (and the required time increases). The parallelism parameter can be used to specify how many threads should be used.
This is a dupe. The devs haven’t ignored the suggestion, it’s just a complicated logistical issue that hasn’t been solved. If you have the resources, I would be willing to fix it.