Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently using KeePass 2 and syncing them via dropbox. I have a few KeePass files (one for websites, one to store software licenses, etc...)

Every time I need a new KeePass file, I just create a copy of the kbdx file, open it, remove all existing entries, change the key transformation rounds to another pseudo-random value.

I do not change the master password and I understand the risk of doing that. I imagine that the salt used for the encryption of the kbdx file is the same for every of my kbdx files since it's probably generated upon creation of the kbdx file.

By using the same master password and salt in every kbdx and just changing the transformation rounds, I believe that it guarantees myself at least the same security than having everything in a single kbdx file.

Am I wrong in believing that? Is my practice actually a security risk by lessening the amount of effort to crack a kbdx file?

share|improve this question

It's the same.

What is not "safe" is the fact that you have a single master password for all your databases, but you probably get that idea yourself.

How you configure and organize your keepass db is your call and it should not affect the basic security settings.

share|improve this answer
I was thinking more along the lines of having (probably) the same salt used, I'll edit the question. – BlakBat Sep 4 '12 at 13:50

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .