Nicolai Schirawski

Thank you for both answers. I now limited the number of history items to 3. Unfortunately T.Bug-Reporters method doesn't work in my case: I don't have access to all the copies of the file; so "re-infection" would be unavoidable. Meanwhile I found another method to reset single entries: I just copy the entry (without history!) and than delete the original one. Since deletes get synced between the different databases, this works...

We are successfully using keepass for years now in a shared linux/windows/mac-Environement. Every user has a local copy of the Keepass-Database, and on every save-action a trigger is activated that synchronises the local DB with a central database-storage. Since every user synchronises on every save with the same DB, all users have access to the same keys. Up to that, all is fine. The problem starts over time: On every change of an entry, one more item is added to the history of the entry. Meanwhile...

I installed Keepass 2.23 on Mac OSX 10.10, where it runs under mono 4.01. Keepass...

Thnks for the clarification! I misunderstood the following lines on http://keepass.info/help/v2/sync.html:...

I use Keepass with a local DB. On a ftp-Server there is a copy of the DB. I can manually...

Thank you! That works (after I installed mono-devel additionally)

Hi list, is it possible to use KPScript Extension on Ubuntu? I installed Keepass2...