James D. Howard

Allow Selection of Root Dirs Without Drive Letters

I'm using KeePass2 across Windows and Linux machines, with a Cloud-stored (MSFT OneDrive) .kdbx file as synchronization target. Triggers operate on DB load and save to synchronize loaded (in memory) and Cloud copies - all called .../Jimbo.kdbx When KeePass2 is run on Windows, a file is sometimes created at the remote Cloud location with the Windows machine name injected, as: .../Jimbo-%MyWindowsBoxHostname%.kdbx (using Windows variable syntax) That file is usually the same size and date-time as the...

KDBX4 support timeframe?

Unless carefully written, it is common for un-install procedures, themselves, fail to clean out old app crud when the installation directory is missing. (For example, upon a disk failure or a remote machine disconnection.) Can KeePass2's uninstall successfully clean up enough in such problematic situations to allow a full re-install to be successful?

As I understand it, entry-by-entry synchronization is performed by referring to the Create, Modify and Access times recorded in the .kdbx database for entries, etc. This allows judgement of newer or older/superseded entries during the synchronization process. I understand how this can work if all writers of the database have a uniform idea of time-of-day. However, it is still somewhat common for machines to have differing views of what time "Now" is (sometimes by numerous minutes) - even in this...

When opening KeePass2 (in my case, on Linux+Mono), and a database, I'm presented with the dialog box [Enter Master key], as expected. However, if I have a couple of databases stored in a long-ish pathname, the Dialog Box shows me a tail-truncated version of the pathname - and the suppressed, important bit of the pathname (usually, the leaf filename) is not visible. See example attached .png file. Can some method be chosen to show the full pathname - or at least elide characters from the middle, not...

Refer to the sync example mentioned above, and pretend that the green box on the right is your Android phone. The following sequence is only needed once on each box you'll want to synchronize - to get DBs and Cloud Stores and synchronization set up. After that it's simply automatic. 1. Make sure that your Android(s) and any computers that might run KeePass2 and/or KeePass2Android can connect to your chosen Cloud Store: Dropbox, MSFT's OneDrive, Google Drive or some other - preferably by some mounted/mapped...

Unless I'm misunderstading terminology, I don't see where in Password Change Assistant (PCA) I can specify some non-default set of characters for an entry (or set of entries) from which a new password can be generated. (I was pleased to find a mechanism for moving PCA info from just the KeePass2 config area into the DB, so it can be cross-platform and -machine synchronized.)