Add ability to customize password profiles for each database

[ba32107]

When generating a new password for an existing entry, I would like an option that generates a new password using the existing settings for the given entry.

Some sites only allow alphanumerical characters and/or has a max character limit. This feature would allow to easiily generate a new password for any site using different patterns.

Thanks, Balazs

[droidmonkey]

This was discussed before. The problem with this is you have to store the current profile for each entry in order to replicate it exactly each time. This is better handled through pre-defined and customizable password profiles that are available database-wide. We cannot "guess" what password settings you are using based on your current password since it is random.

[ba32107]

Thanks, this would work great as well.

[joshualibrarian]

Even if pre-defined password profiles are available database-wide, that doesn't really solve the problem presented in (closed) #3091. Whatever profile I started with, when I go to generate a password for a new site, I invariably have to customize the generator settings. Just now, I had to select the right boxes and then paste the list of "additional allowed characters" into the allowed box. These generator settings should be preserved and associated with THAT entry so that next time I go to change the password for that entry, the generator is already set correctly. Is it not viable to store this data in the database with the entry, whether as reference to database-wide profile or not?

[droidmonkey]

Also allow setting a default configuration that is easily chosen.

[GenocideStomper]

I would also love to see password profiles for the "Password Generator" tool. Sometimes I need to change settings, and don't want to lose the characters from the "Also choose from:" and "Do not include:" fields.

[Massimo-B]

Just to give an idea here is a screenshot of the keepass2android application Password Generator with profiles.

[mattesony]

I really like this feature and miss having it in my previous password manager. I'd be happy to take a stab at it either with the profiles or by storing the generating character set/length on an entry-by-entry basis. I think it could be built on by adding some form of inheritance of the character set/length from the groups the entries are in if the character set/length is unset for the entry, then the profiles would just be a further refinement to allow easier management.

[michaelk83]

The profiles should be compatible with OG KeePass. As I recall, there was a specification of it somewhere.

[droidmonkey]

This should being implemented exactly how saved searches was implemented, except of course in the password generator. I don't think this is in the kdbx specifications.

[michaelk83]

I think I saw some sort of spec or similar document on the OG KeePass website a while back, but I can't find it now. In any case, it does have password generator profiles, and so does Keepass2Android, as noted above. So KeePassXC shouldn't reinvent its own system for this.

[droidmonkey]

Depends on how much I like the way they implemented it. Our password generator is decidedly different then KeePass2 and KeePass2Android actually uses the KeePass2 binaries under the hood.

[michaelk83]

It could be an issue for some users if they make password profiles in OG KeePass (or on android), and can't use them in KeePassXC, or vice versa. Though currently that is already the case (since KeePassXC doesn't support profiles at all).

If your new way is that much better, I suppose it can be standardized in KDBX5.