[kmymoney] [Bug 410688] Password problem with database SQLCipher

[Jack]

https://bugs.kde.org/show_bug.cgi?id=410688

Jack <ostroffjh at users.sourceforge.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REPORTED                    |CONFIRMED
     Ever confirmed|0                           |1

--- Comment #14 from Jack <ostroffjh at users.sourceforge.net> ---
OK, I can finally confirm this.  If KMyMoney is built with verions 3 or 4 of
sqlcipher, it can only open database files created with that same version.  The
one exception is that a version 3 sqlcipher file can be converted to the
version 4 format (see link in previous comment).  Note that even with command
line sqlcipher version 4, until you convert the file, it cannot read it.

I suspect it would be possible for KMyMoney built against version 4 sqlcipher
to to the conversion programmatically, but that's probably not a good idea, as
it would have no way to be sure that it couldn't open a file for that reason,
as opposed to either having the wrong password or it simply not being a valid
file.

Actually, reading further into that link above, it IS possible for a program
compiled with sqlcipher 4 to request the current database be treated as version
3.  I suppose it is also possible for KMM to apply the version upgrade process,
but I am NOT sure how it can tell if that is the right thing to do, other than
by confirming it can't open the database with version 4 but can open it as
version 3.  

This is going to take some thinking, to decide the best approach for KMyMoney.
However, at least the problem is now understood.

-- 
You are receiving this mail because:
You are the assignee for the bug.