Bug 342539 - "wrong passphrase" while opening kmymoney
Summary: "wrong passphrase" while opening kmymoney
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.7.1
Platform: Ubuntu Linux
: NOR grave
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-01-05 23:08 UTC by Ösel
Modified: 2018-10-27 03:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ösel 2015-01-05 23:08:17 UTC
Hi,

since a few weeks I have the problem, that I can't open any file in kmymoney.
I get an error message with "wrong encryption" and that the "passphrase is wrong".
But this error message comes at once. I can't enter any password!
And the same problem happens with different .kmy-files.

For checking I generated a new file without a password, added a bank account and saved the file directly after a minute.
While I want to open the file, I got the same error message as above.


Reproducible: Always

Steps to Reproduce:
1. start kmymoney
2. open a *.kmy file



Ubuntu 14.04 LTS
Comment 1 Jack 2015-01-05 23:46:43 UTC
Were any of these files actually saved with encryption?  I think the problem might be different in each case.
You can check whether the file is actually encrypted or not by opening a command prompt, going to the directory where the file is located, and typing "file myMoneyFile.kmy".  A non encrypted file is "gzip comressed data" but an encrypted file will be "PGP message Public-Key Encrypted".

Also, can you please clarify the exact order of events.  If you just type kmymoney, it will try to open the last file it had open.  I assume this is when you get the error, and KMyMoney is still running, but with no file open?  If so, select the menu Settings/Configure KMyMoney and select the Encryption tab to confirm wheether or not you have encryption turned on.

Do you use encryption for anything else?  Are you haveing any other problems related to use of gnupg keys?
Comment 2 Ösel 2015-01-06 16:42:57 UTC
Hi,

all kmy-files are saved with the encryption.
file ***.kmy: PGP message

If I open KMyMoney, I will directly get the error message, because the KMyMoney tried to start the last file. This is correct.
When I click "OK" on the error message, the software is still running with no open file. Correct.

I checked the encryption and it is still running.

As I can remember, I'm not using the encryption for anything else. Sorry.
Comment 3 Thomas Baumgart 2015-01-06 19:28:43 UTC
Can you check if your gpg-agent is running? Simply open a Konsole and issue the following command:

thb@thb-nb:~$ echo $GPG_AGENT_INFO
/tmp/gpg-fpUXIg/S.gpg-agent:6145:1

This is how it shows here. Without the agent running, KMyMoney cannot use GPG encryption.

Workaround to get to your data:
----------------------------------------

Decrypt the file on the cli and store it in an XML file.

gpg -d oesel.kmy > oesel.xml
kmymoney oesel.xml

This is just to get to your data. Be aware, that KMyMoney tries to save encrypted again, as information about usage of encryption is contained inside the file.
Comment 4 Ösel 2015-01-11 10:19:53 UTC
my gpg-agent is running all the time
/tmp/gpg-JgiGsD/S.gpg-agent:1943:1

Thanks a lot for the workaround to get my data back and this works fine.

But I ask myself, where is the problem, because I really want to save my files again encrypted.
Comment 5 Cristian Oneț 2015-02-17 08:50:22 UTC
Even if gpg-agent is running it's not a guarantee of the fact that GPG is properly configured. I would go trough this wiki page https://wiki.archlinux.org/index.php/GnuPG to check that GnuPG is properly working on the system. 

Do you have a pinentry program configured?

https://wiki.archlinux.org/index.php/GnuPG#pinentry

What does the KMyMoney 'Encryption' settings page say?
Comment 6 Andrew Crouthamel 2018-09-25 21:42:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-10-27 03:54:46 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!