qutterr / keepassdroid

Automatically exported from code.google.com/p/keepassdroid
0 stars 0 forks source link

Adding entries in KeePassDroid corrupts the database, but modifying existing entries does not #804

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Add a new entry (with a username and password) to the kdbx database using 
KeePassDroid 2.0.3 on my Android Moto G
2. Copy that kdbx database and its key file over to my Windows 8 laptop, using 
Windows File Explorer
3. Try to open the kdbx database (entering the key file and master password) on 
my Windows 8 laptop, using KeePass 2.29

What is the expected output? What do you see instead?
Failed to load the specified file!
The file is corrupted.

What version of the product are you using? On what operating system?
I am using KeePass 2.29 on my Windows 8 computer
I am using KeePassDroid 2.0.3 on my Android 5.0.2 Moto G 

Please provide any additional information below.
This problem also happens if the database does not use a key file, and also 
happens if the database is a kdb not a kdbx and in that case I open it with 
Keepass 1.

When I add new entries on KeePassDroid it DOES WORK on my Android phone (the 
database opens, functions, and everything) but DOES NOT WORK on KeePass on my 
Windows 8 laptop.  Because KeePass on my Windows 8 laptop claims that the 
database is corrupted.

I am able to recover the "corrupted" kdb database by using the KeePass 1 
recovery tool, and it recovers the entries and any modifications to them that I 
had made in KeePassDroid, BUT it DOES NOT recover the new entry or entries that 
I had added in KeePassDroid.  In fact, in the recovery report the ONLY 
"corrupted" part of the database was the mismatch between the expected number 
of entries and the actual number of entries (the actual number of entries 
includes the ones I added in KeePassDroid but the expected number does not).

I am unable to recover the "corrupted" kdbx database using the KeePass 2 
recovery tool: I order KeePass 2.29 to completely overwrite the new database 
with the corrupted database's information, but it does nothing except create a 
second Group folder, which is empty and has no name.

I can work around this by only adding new entries using KeePass 2.29 on my 
Windows 8 laptop, but that is inconvenient.

Would it be helpful to attach my "corrupted" kdbx database (without the Key 
file of course, to keep my passwords secret)?

Original issue reported on code.google.com by nano...@gmail.com on 16 Jul 2015 at 4:41

GoogleCodeExporter commented 8 years ago
This issue is also occurring running Keepass 2.29 on Windows 7 professional, 
using Keepassdroid 2.0.3 on Android 5.1.1 Samsung Galaxy S3

Original comment by ghost...@gmail.com on 4 Aug 2015 at 5:27

GoogleCodeExporter commented 8 years ago
Fixed in KeePass 2.30! :)

Original comment by nano...@gmail.com on 17 Aug 2015 at 8:16