Adrian Nesse Wiik

This is the most sensible post in this entire discussion, and I agree wholeheartedly. Thank you for your accurate description of the situation. It's outrageous that the KeePass team doesn't see the nuances (as far as I've read this thread), but choose to live in a black and white world. If a simple change in a human-readable and -writable config file can lead to my entire encrypted database to be dumped in plain text, this is a huge deal. This "feature" should either be removed, or at least be protected...

Hi, I'm not sure if this is intentional or not (I hope not), but I see that when you override the default sequence for an entry and that sequence has an invalid format (ex. "{USERNAME}[ENTER}{DELAY 2000}{PASSWORD}{ENTER}" (see the "[" instead of "{"), all the placeholders are converted to their actual values, and displayed for everyone to see in the error message that pops up when you try to use Auto-Type on that entry. I think this is a security risk since if anyone is watching your screen and you...

Today's update (KeePass 2.46) gives us the ability to edit multiple entries at once by selecting them and doing right-click -> Edit entry, which is an even better and more flexible way to do this. This ticket can be closed, thank you for this great new feature!

Today's update (KeePass 2.46) gives us the ability to edit multiple entries at once by selecting them and doing right-click -> Edit entry, which is an even better and more flexible way to do this. This ticket can be closed, thank you for this great new feature!

As long as the security aspect is not lagging behind and you don't need the newest features, I guess that sounds fair.

Why is KeePass 1.x still alive? According to the comparison table, KeePass 2 can do everything KeePass 1 can do, and more. All I see is maintenance work for a version that should have been obsoleted shortly after implementing good migration options from 1.x to 2.x. Accoring to the KeePass help section, this is already as easy as importing the old DB with the KDB format to a new DB with the KDBX format. I would take the old version down by now as it will probably speed up development work on the current...

Why is KeePass 1.x still alive? According to the feature list, KeePass 2 can do everything KeePass 1 can do, and more. All I see is maintenance work for a version that should have been obsoleted shortly after implementing good migration options from 1.x to 2.x. Accoring to the KeePass help section, this is already as easy as importing the old DB with the KDB format to a new DB with the KDBX format. I would take the old version down by now as it will probably speed up development work on the current...

This is a good one. I usually make entries when actually making the respective user account, and the passwords are auto-generated and looong. Stuff can happen that make me forget to save. It would be unfortunate if I clicked "Discard changes" after creating or changing a root user for a database system, for example. There is no recovering or changing that password.