Could not deserialize object to XML

[alexgleason]

Hi, I opened sorz/TinyKeePass#9 and then realized that TinyKeePass relies on this library, which is actually throwing the error.

I have a KeePass file that openkeepass cannot parse. It says "Could not deserialize object to XML." I wish I could provide the kdbx, but it contains real passwords.

The same kdbx can be opened properly with KeeWeb, KeePassDroid, and KeePass Tusk. It's possible the file is corrupted and these other tools are just very lenient when parsing the XML. I'm not sure how to check.

[alexgleason]

I opened the kdbx file with KeePass2 on Ubuntu and saved the file without making changes. This allowed the file to be parsed by openkeepass successfully.

This could be an issue with KeeWeb, which I used to create the file initially, although if the XML parser here were as lenient as the others that would be nice.

[timendum]

I've managed to replicate the error, see attached file (password "demo").

The issue is due to Property, KeeWeb saves a null Value (ie <Value/>) but the field is not nullable.

Can you make Property.propertyValue nullable?

Thanks.

[cternes]

Thank you for the investigation. I will have a look at it.

[alexgleason]

Thanks! Does keepass have a spec? Should we open this bug with KeeWeb also? If KeeWeb is creating nonstandard files this should probably be changed on their end also.

[cternes]

@timendum It seems not to be a problem with the null Values. They should be working fine.
@alexgleason Unfortunately keepass does not have a spec. It's all based on reengineering the whole stuff and hoping that the reengineering is correct. That is why it is so difficult to get the stuff working correctly .

[timendum]

Anyway I've also opened a ticket on keeweb and indeed KeePass opens file with null values.

[cternes]

I think I've found the issue. The problem was that keeweb rearranged the XML tags and that messed up my decryption. I've tested with the attached database file and it seems to work now.