Bug 336353

Summary:	incorrect Error message: das Zertifikat der Beglaubigungsstelle ist ungültig
Product:	[Applications] kmail2	Reporter:	Gottfried Krause <krause>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bjoernv, kdenis
Priority:	NOR	Keywords:	triaged
Version:	4.11.5
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:

Description Gottfried Krause 2014-06-17 10:03:49 UTC

(please excuse, my knowledge of the english language is not good)
my provider informed me: we have installed a new SSL-certificate(?), but Kmail stays messaging (s.a.) "das Zertifikat der Beglaubigungsstelle ist ungültig"; after a series of proofs today I got the following message from my provider:
"Hallo Herr Krause,

folgende Nachricht haben wir gestern von GlobalSign erhalten bzgl. Ihres
Zertifikatsfehlers:

Wir haben die Datei überprüft und festgestellt, dass diese das notwendige
Rootzertifikat enthält, auch ist das Zwischenzertifikat des AlphaSSL SHA-256
korrekt installiert. Dementsprechend scheint von der Installation des
Zertifikats und der Zertifikatskette her in Ordnung zu sein. 

Das einzige, dass wir uns vorstellen könnten, ist, dass es sich um eine alte
Version von KMail handelt, die noch nicht mit SHA-256 kompatibel ist. Es
wäre daher eventuell zu empfehlen, mit dem SUSE Support Kontakt aufzunehmen
um zu prüfen, ob es etwas gibt, das getan werden kann.

Leider können wir in diesem Fall weiter nichts mehr für Sie tun, als auf
obiges Aussage zu verweisen.

Mit freundlichen Grüßen
CPU-NET Support
"
so one question is: is Kmail 4.11.5 already compatible with SHA-256?
What can we do to solve the problem?
Kindly regards
Gottfried Krause

Reproducible: Always




I installed openSUSE 13.1 and use my home-directory, that I already used in 12.2

Comment 1 bjoernv 2016-09-21 07:32:32 UTC

This is one of the most annoying KDE bugs. It's still present in latest KDE versions.

Comment 2 Denis Kurz 2017-06-25 11:48:05 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please make sure to state your version of the KDE PIM suite (Help -> About <Application>).

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 3 Andrew Crouthamel 2018-09-28 02:40:31 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 4 Andrew Crouthamel 2018-10-28 03:38:11 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!