Matthias

Hello, I want to use KeePass with several users (employees), where all employees access a "central/shared database". I am wondering what is the best-practice-approach to setup to the KeePass enviroment to prevent a user from taking the keyfile along to his/her private PC and open the keyfile there with a known password (or a certificate file which was also easily accessible to the user). I have come across several threads here that cover similar topics, such as enforced configuration (https://keepass.info/help/base/configuration.html#network)...

Thx for following up. What a pity - I really liked the PlugIn...

Thanks for your response. I have checked and KeeOTP is also no longer available at the link listed on the KeePass PlugIns page. So either Devin has moved the projects elsewhere (couldn't find it spontaneously on GitHub or BitBucket) or he has decided to stop the project. In case you have a way to obtain this information from Devin, that would be highly appreciated and also serve as a decision point whether the two plugins should be removed from the KeePass PlugIns page. What a pity. I really like...

Hello, the KeeCloud plugin listed on https://keepass.info/plugins.html is currently not available. I have no information whether this is a temporary issue or whether the author has ceded the project completeley. Does anybody have further information whether the PlugIn will become available again or whether KeePass should remove KeeCloud from the PlugIns page? Regards, Matthias

Thank you very much for your responses. I can confirm that "Start minimized and locked" has been unchecked, so that the tray icon did not show any synchronization progress. I have decided to set <showimportstatusdialog>True</showimportstatusdialog> in the UI section of KeePass.config, which restores the progress dialog successfully. Your support is highly appreciated.

Hello, I have also noticed the change in the Change Log. Frankly speaking, I am not very happy with that change When starting up KeePass, I sync my database with a remote location (using a trigger), which takes some 5 seconds. With v2.40, after starting up KeePass, I see "nothing" for those 5sec until the main window comes up and I always wonder whether my double-click action to start up KeePass was successful or not... Is this really the desired behavior? If so, what was the motivation for this...