[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 n...@nils-griebner.de changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #7 from n...@nils-griebner.de --- (In reply to Jack from comment #6) > Since this really isn't a bug in KMyMoney, should we close it as WORKSFORME? > The only alternative I can think of is to make it a wishlist for KMyMoney > to recognize a v3 sqlcipher file when running with v4, and automatically > convert the file to v4. Yep let's close this one. Would be great if mymoney would do the conversion automatically. Thanks for your help. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #6 from Jack --- Since this really isn't a bug in KMyMoney, should we close it as WORKSFORME? The only alternative I can think of is to make it a wishlist for KMyMoney to recognize a v3 sqlcipher file when running with v4, and automatically convert the file to v4. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #5 from n...@nils-griebner.de --- (In reply to nils from comment #4) > (In reply to Jack from comment #3) > > I suspect that either you will need to explicitly convert your database > > from version 3 to version 4, or else we need to figure out how to get > > KMyMoney to invoke sqlcipher with the compatability setting. I don't use > > sqlcipher, so I'm only guessing, but is there a config file where you can > > specify to always use compatability mode? > > I took that from https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 I got mymoney running again by: 1. Let mymoney create a new encrypted sqlite db 2. Follow step 3 (custom export migration) from https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #4 from n...@nils-griebner.de --- (In reply to Jack from comment #3) > I suspect that either you will need to explicitly convert your database > from version 3 to version 4, or else we need to figure out how to get > KMyMoney to invoke sqlcipher with the compatability setting. I don't use > sqlcipher, so I'm only guessing, but is there a config file where you can > specify to always use compatability mode? I took that from https://discuss.zetetic.net/t/upgrading-to-sqlcipher-4/3283 -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #3 from Jack --- I suspect that either you will need to explicitly convert your database from version 3 to version 4, or else we need to figure out how to get KMyMoney to invoke sqlcipher with the compatability setting. I don't use sqlcipher, so I'm only guessing, but is there a config file where you can specify to always use compatability mode? -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 --- Comment #2 from n...@nils-griebner.de --- (In reply to Jack from comment #1) > As I remember (I don't use that backend) sqlite itself does not handle > encryption, but requires sqlcipher. Your problem is likely a version issue > with that, and doesn't really have anything at all to do with KMymoney. > What are the relevant version of sqlcipher on your two machines? > Minor question - is your item 5 above a typo? I would expect it IS NOT > possible but SHOULD be possible. > (Even if sqlite on Ubuntu handle encryption itself without using sqlcipher, > I would raise this issue on an Ubuntu forum or a sqlite related list or > forum. If the database itself cannot open your file, there is nothing > KMyMoney can do.) Thanks for your reply. I made an interesting observation regarding sqlcipher. I'm able to open the database with sqlcipher version 3.x.x from local cli. Versions = 4.x.x throw an error. But it is possible to enable a v3 compatibility mode with "PRAGMA cipher_compatibility = 3;" . Then I can open the db with sqlcipher = 4.x.x. However mymoney is still broken for me. -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 479251] kmymoney is not working on Debian testing with latest packages
https://bugs.kde.org/show_bug.cgi?id=479251 Jack changed: What|Removed |Added Component|general |database Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jack --- As I remember (I don't use that backend) sqlite itself does not handle encryption, but requires sqlcipher. Your problem is likely a version issue with that, and doesn't really have anything at all to do with KMymoney. What are the relevant version of sqlcipher on your two machines? Minor question - is your item 5 above a typo? I would expect it IS NOT possible but SHOULD be possible. (Even if sqlite on Ubuntu handle encryption itself without using sqlcipher, I would raise this issue on an Ubuntu forum or a sqlite related list or forum. If the database itself cannot open your file, there is nothing KMyMoney can do.) -- You are receiving this mail because: You are the assignee for the bug.
