Bug 403342

Summary:	Requests to an hbci account result into the message "Signer not found"
Product:	[Applications] kmymoney	Reporter:	Ralf Habacker <ralf.habacker>
Component:	importer	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	major
Priority:	NOR
Version:	4.8.2
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:	4.8.3
Bug Depends on:
Bug Blocks:	394780

Description Ralf Habacker 2019-01-18 07:05:52 UTC

Importing from a hbci account mentioned 

STEPS TO REPRODUCE
1. start kmymoney
2. configure a hbci user e.g. Ing-Diba
3. In the hbci user settings try to get the certificate

OBSERVED RESULT
The log from the connection dialog mentions "Signer not found" and "Certificate is not trusted"

EXPECTED RESULT
This message should not appear

SOFTWARE/OS VERSIONS
Windows: 7
KDE  Version: 4.14
Qt Version: 4.8

ADDITIONAL INFORMATION
This is a problem with the embedded gwenhywfar package, not with kmymoney itself, so the kmymoney version is independent. This ticket was opened to track this bug for kmymoney.

Comment 1 Ralf Habacker 2019-01-18 08:43:14 UTC

Reported upstream at https://www.aquamaniac.de/rdm/issues/22

Comment 2 Ralf Habacker 2019-01-18 10:53:16 UTC

(In reply to Ralf Habacker from comment #1)
> Reported upstream at https://www.aquamaniac.de/rdm/issues/22

Patch has bee applied

Comment 3 Ralf Habacker 2019-04-26 06:20:01 UTC

Patch has not been applied upstream until now.

Comment 4 Ralf Habacker 2019-08-31 07:56:09 UTC

Patch wurde bisher noch nicht angenommen.

Comment 5 Thomas Baumgart 2019-08-31 14:52:02 UTC

That patch is not enough. Even on Linux the file resides in different locations. See https://serverfault.com/questions/62496/ssl-certificate-location-on-unix-linux for some examples for various distros.