Guillaume

Maybe my post was unclear, but I am not talking about a multi user keypass or a keypass server. My use case is about distributing keypass files to a team while limiting the risk of a file being wholly copied or exported.

Hi The idea is that the kbdx files are distributed manually, directly at the user workstation by a "distributor" : - The distributor meets the user at his workstation, the following operations are done in the user session. - The distributor opens the original file from a network share or USB stick using a master password - The distributor changes the key, the policy and saves the resulting file on the user workstation - There is not need to unfreeze the database, but the policy may allow the users...

Thanks for the quick answer and for the information. I don't think that managing the enforced configuration files on a network drive is a workable mechanism for us (we can't prevent the users to install a new copy on Keepass, so they can circumvent the enforced configuration). I think the best solution for this use case would be to have 1/ the ability to embed some policy options directly in the kbdx file, which would override any value found in the configuration files. 2/ the addition of a "Freeze...

Hi, First : thanks for this very neat software. I submit here a feature request : I would like to have an option to lock a database in "Windows User Account" master key without the ability for the user to swtich back to "Master Password" or "Key File". The use case is that I want to need kbdx files to some users (developpers), but I want to limit the possible use of these files to the sole computer of each user, without any possibility to change the key to Master Password and then open the file on...