#2231 how to find the cause of an error message?

[AlBundy33]

it seems that keeweb creates an invalid kdbx4 file
see https://github.com/keeweb/keeweb/issues/2001

is there a way to find out whats exactly not base64 encoded?

[Dominik Reichl]

If you post an example KDBX file, I'll have a look at it.

Thanks and best regards,
Dominik

[AlBundy33]

no problem
1. I've created a new database with one test entry in keeweb: 1_create_with_keeweb.kdbx
2. I opened the database i keepass -> keepass show immediately with a * that the database has unsaved changed, so I've saved the database again: 2_saved_with_keepass.kdbx
3. I opend the database from step 2 in keeweb, saved it again and tried to open it in keepass

so the last file is that one with the base64 issue.
but the file from step 1 seems also wrong because keepas shows unsaved changes.

[AlBundy33]

maybe you need the masterpassword :D
it's 123

[Dominik Reichl]

Great, thanks!

I cannot reproduce your first issue with KeePass alone. Directly after opening '1_create_with_keeweb.kdbx', there are no unsaved changes.

From '1_create_with_keeweb.kdbx' to '2_saved_with_keepass.kdbx', a custom data item named 'KeePassOTPDB.MigrationStatus' has been added. So, it seems that you are using the KeePassOTP plugin, and the plugin has added the custom data item immediately after the database has been opened (and this also explains why '1_create_with_keeweb.kdbx' is a KDBX 4 database, whereas '2_saved_with_keepass.kdbx' is a KDBX 4.1 database).

The Base64 error in '3_saved_with_keeweb.kdbx' is related to the custom data item. Since KeePass 2.48 / KDBX 4.1, the last modification time of a custom data item is saved (see [1]), and KeeWeb doesn't seem to handle this specific time field correctly (it has stored the string '2023-02-28T12:59:19Z' instead of the Base64 form). All other times in '3_saved_with_keeweb.kdbx' seem to be correct.

To put it clearly again: the unsaved database issue seems to be caused by the KeePassOTP plugin, but KeeWeb (not KeePassOTP) is responsible for the database file corruption.

Best regards,
Dominik

[1] https://keepass.info/help/kb/kdbx_4.1.html#cd_lastmod

[Rookiestyle]

the unsaved database issue seems to be caused by the KeePassOTP plugin, but KeeWeb (not KeePassOTP) is responsible for the database file corruption.

Regarding the topic of unsaved changes due to keePassOTP:
https://github.com/Rookiestyle/KeePassOTP/issues/130

If you do Tools -> Database Tools -> Database Maintenance -> Plugin data you will see an entry named KeePassOTP.Migration.Status

This entry does not exist initially and is created the first time you open the database after you saved OTP data.
If you save, this entry is saved and you should be fine.

[AlBundy33]

Thanks - added this info to https://github.com/keeweb/keeweb/issues/2001