Bug 347497

Summary:	Failed authenticity check on all resources
Product:	[Frameworks and Libraries] Akonadi	Reporter:	skaumo
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:

Description skaumo 2015-05-10 08:31:13 UTC

At every system start, I got the following error for all connected (Google) accounts:

The server failed the authenticity check (www.googleapis.com).

The certificate authority's certificate is invalid
The root certificate authority's certificate is not trusted for this purpose


Despite the above, e-mails get sent and received anyway.
I understand there may be an issue with some certificate somewhere, but I would have expected all IMAP communication to be blocked by Akonadi as a security measure, if any invalid certificate issue was suspected.

Nonetheless, I don`t believe all Google certificates are invalid. However, clicking on [details] in the above warning, I see no hint that anything would be wrong.



Reproducible: Always

Steps to Reproduce:
1. Akonadi and Kmail are started automatically at system start


Expected Results:  
- If there is any issue with certificates, show exactly what that is
- give the user the options to permanently/temporarily accept/reject the certificate and handle the connections accordingly

Comment 1 Denis Kurz 2017-06-23 19:57:21 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those 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 oportunity 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 understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 2 Denis Kurz 2018-02-01 09:46:26 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.