Created attachment 778904 [details] Evolution certificate prompt Upon upgrade to Fedora 19, I now get the attached prompt for my mail server. This did not occur with Fedora 18. The prompt is mysteriously missing a "Reason" line as well. Also, if I connect via the openssl command (openssl s_client -connect pophm.sympatico.ca:995), there doesn't seem to be any certificate issues. Version-Release number of selected component (if applicable): evolution-3.8.3-2.fc19.x86_64 Steps to Reproduce: 1. Open Evolution 2. Wait for it to connect to mail server
Thanks for a bug report. I can reproduce it too. The reason is that the 'Entrust.net Certification Authority (2048)' certificate in Edit->Preferenecs-> Certificates->Authorities tab, is not trusted for some reason. This certificate is imported from the global certificate database. Editing its trust (by clicking the Edit button on the right) and checking all three checkboxes (none were checked for me), makes the certificate prompt go away. The missing Reason line is due to no exact mapping between this state and GTlsCertificateFlags flags, I guess. In any case, this is not an issue on evolution's side as such, thus I'm closing this.
Maybe this should be re-assigned to the ca-certificates component to see why the certificate in the global database is not trusted?
OK, I'm moving it there.
Updating Entrust's certificate manually seems to fix the issue. I did the following: 1) Download "entrust_ssl_ca.der" from https://www.entrust.net/downloads/root_index.cfm (select the first option then click "Root Certificates"). 2) Copy it into "/etc/pki/ca-trust/source/anchors" or "/usr/share/pki/ca-trust-source/anchors/" 3) run "update-ca-trust extract" as root And now Entrust is trusted again.
Hello, I assume this is a duplicate of bug 988745? I'm working on updated ca-certificates package for f19 and rawhide now.
I don't see how it's a duplicate of bug 988745. This bug is about Entrust certificate not being trusted by Fedora (possibly old root certificate, I don't know for sure). 988745 is about a specific error message.
Entrust is a very old certificate, which requires us patching it to be accepted. Starting with p11-kit 0.19.2, a different patch is necessary to make it work. That's what bug 988745 is about. Which version of p11-kit do you have installed?
Kai, although this may indeed be related .... it's worth noting that p11-kit 0.19.x is not in Fedora 19. It's in rawhide and Fedora 20.
I have p11-kit 0.18.5-1.fc19 installed here (Fedora 19). I don't know what that is though. And I don't understand the other bug to know if it's the same, sorry :) My problem was that some websites (examples: https://apple.com , https://migs.mastercard.com.au , https://www.gulfair.com ) did not work on Fedora because Entrust is not trusted. Downloading the certificate from Entrust and manually installing it (as per my above comment) fixed the issue. There was no patching necessary. As long as a fix makes these websites work out of the box in Fedora, I'd consider it a fix to this issue.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The most recent ca-certificates package version 2013.1.94-1.fc19 might be sufficient to work around this issue. Unfortunately I don't understand the real issue yet. The Entrust root should have been trusted, even with the older 2012.87-10.2.fc19 version of ca-certificates. (Comment 5, 6, 7, 8 until comment 9 are probably irrelevant for this bug.) I was temporarily able to reproduce what Elliot, Milan and imgx64 saw, but then suddenly, I was no longer. I'm worried this might be a "Heisenbug" :( Maybe related to a random memory issue. I don't know yet. More investigation will be necessary. I'll file a separate bug against p11-kit for further investigation. Although I don't understand the issue yet, but let me start providing background information that influences this bug. Multiple versions of the CA certificate with subject name CN=Entrust.net Certification Authority (2048), OU=(c) 1999 Entrust.net Limited, OU=www.entrust.net/CPS_2048 incorp. by ref. (limits liab.), O=Entrust.net exist: (1) An original version, self signed (same subject and issuer), with serial number 38:63:b9:66 SHA1: 80:1D:62:D0:7B:44:9D:5C:5C:03:5C:98:EA:61:FA:44:3C:2A:58:FE This old certificate has a problem, it doesn't contain the "basic constraints extension: true" which many applications require to accept it as a valid CA. (2) A replacement version, self signed (same subject and issuer), with serial number 38:63:de:f8 SHA1: 50:30:06:09:1D:97:D4:F5:AE:39:F7:CB:E7:92:7D:7D:65:2D:34:31 This certificate fixes the defect of (1). (3) At least one "cross signed" cert, with the same subject name, but a different issuer name, intended to enable a trust chain, if software has neither (1) nor (2) marked as trusted. Until very recently, Fedora 19 has shipped the package ca-certificates version 2012.87-10.2.fc19 - which still contained (1), and which contained a patch that fixed the issue of (1). A while ago, the Mozilla CA program has worked in https://bugzilla.mozilla.org/show_bug.cgi?id=694536 to get (1) removed, and replaced by (2). The new ca-certificates package version 2013.1.94-1.fc19 has recently been made available, which removed (1) and contains (2). I believe that (2) is identical to the certificate that imgx64 downloaded and installed, as explained in comment 4. I don't know which version of the ca-certificates package imgx64 had installed at the time of testing comment 4, but it shouldn't have made a difference. Because of our workarounds, either package should have worked for him.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Unfortunately, I don't use Evolution anymore, so I guess if everyone else thinks it's working, then it probably is.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.