Actually, I disagree, salts are used to prevent rainbow tables/pre computed KDFs, and it's a standard that's highly recommended. You can store the salt with the database. KeePass uses a random salt.
For example, if an attacker pre computed password, and tried it on another user's machine if they're lucky their password is also password, and the database decrypts. This wouldn't happen if you used salts.
Just because the KDF isn't stored, doesn't mean you can't do rainbow tables.
Oh okay, that makes sense now. I thought you were using a salt legitimately.
Yeah, it is kinda a strange use case haha
Actually, I disagree, salts are used to prevent rainbow tables/pre computed KDFs, and it's a standard that's highly recommended. You can store the salt with the database. KeePass uses a random salt.
For example, if an attacker pre computed
password, and tried it on another user's machine if they're lucky their password is alsopassword, and the database decrypts. This wouldn't happen if you used salts.Just because the KDF isn't stored, doesn't mean you can't do rainbow tables.
Yup, we added random salts several months back!
Oh. That's great to hear! FYI, Qvault looks nice. Do you think you'll be able to do duel encryption via file(s), or physical security keys?
Yes, that is something we are looking into. First we want to add box-level encryption though.
I've tried searching, but I can't seem to find anything about box-level encryption. What do you mean?