Last Password Modification Date swept over with current date and time

[JDB]

I have been using the "Last Password Modification Date" as a guide to find and change old passwords. I have been synchronizing the Keepass database with a 2nd computer. After a recent sync, ALL of the modification dates were changed to the current date and time. Now I can't tell which passwords are older vs. newer. I never used Expiry time, so they are all set to "Never expires". The creation date was not modified, but that's no help.

One of the steps I took after a recent synchronization was to clean the database by deleting History and the hidden Change Logging trail.

Why did this happen? Bug? Something I did wrong? Does clearing the History or Change Log wipe the Last Password Modification Date? (I don't think it should!)

Anyway, there's nothing I can do to fix it; I'm just reporting this in case it's an "undocumented feature".

-JB

[Paul]

There is no "change logging trail". Did you mean "deleted object information"?
Either way, database maintenance does not change data modification times of the current entry and KeePass doesn't bulk modify entries unless you specifically select all entries and make a change.
Did you use a 3rd party app to modify your database?

You can revert to a backup pre update and then work out what went wrong.

cheers, Paul

[Dominik Reichl]

As indicated in the main window column and in the entry dialog (by the suffix "(Based on History)"), the last password modification time is computed by inspecting the history. If you delete the history, KeePass uses the last modification time of the entry as last password modification time.

Best regards,
Dominik

[JDB]

Thank you Paul and Dominik for the clarification and explanation. My terminology was incorrect, I did mean "deleted object information". I used the Windows version 2.54. It would be a nightmare to reconstruct beginning with the pre-update :-) -- I exported the pre-update backup and current databases to HTML and compared them. The number of changes appear to be daunting.

For the future, Is it feasable to create a new database version that stores the last password modification date as a separate field? I can understand the portability issue, given all the derivative ports out there. In my case, I would be willing to export to the older format for use with my Android phones. However, you'd need many more issues than mine to make it worth doing! :-)

Thanks,
-John

[Paul]

There is no need to delete History or Deleted Object Information from your database unless it is extremely large, or you have a very large attachment in History, in which case you can delete the individual History item.

As Dominik said, the last password change is calculated, not stored separately, This will not change as it is only indicative - KeePass can't know if you actually changed the password on a remote system.

If you kept regular backups you would have been able to return to a previous copy to recover the History.
See the Backup Wiki for details.
https://sourceforge.net/p/keepass/wiki/Backup/

cheers, Paul

[JDB]

Thanks Paul, good suggestion.