Description of problem: Tried to set up Empathy for a Groupwise messaging account. The messaging server has an unverifiable certificate. The empathy debug log shows: purple/certificate/x509/tls_cached-MESSAGE: 04/02/2010 13:35:17.172142: Checking for a CA with DN=O=SERVICES2,OU=Organizational CA purple/certificate/x509/tls_cached-WARNING: 04/02/2010 13:35:17.172291: Certificate Authority with DN='O=SERVICES2,OU=Organizational CA' not found. I'll prompt the user, I guess. But it never does prompt the user. Under Pidgin, when setting up this account, you get a new window asking you to accept the unverifiable certificate like: Accept certificate for xxx.xxxx.com? The certificate for xxx.xxxx.com could not be validated. The certificate is not trusted because no certificate that can verify it is currently trusted. Version-Release number of selected component (if applicable): empathy-2.29.93-1.fc13.x86_64 How reproducible: Every time. Steps to Reproduce: 1.Connect to a messaging server that has an unverifiable certificate. 2.Witness Empathy not ask you to approve. 3.Fail to progress during the login routine. Actual results: Empathy never asks you to accept the certificate. Expected results: Empathy does ask you to accept the certificate. Additional info:
I can confirm I have this same issue in F13 x86_64. Empathy never prompts for certificate install/verification for Groupwise IM. Version installed: empathy-2.30.2-3.fc13.x86_64 Related bug tracking: https://bugzilla.gnome.org/show_bug.cgi?id=592627 https://bugs.launchpad.net/ubuntu/+source/telepathy-haze/+bug/417432 (including workaround)
Re-assigning to tp-haze since the problem lies there.
I ran into the same issue using pidgin-sipe for Office Communicator (OCS). As a temporary workaround, you can copy the cert of the CA that signed the cert being validated (or the cert itself if it's self-signed) in /usr/share/purple/ca-certs/. You may also be able to copy the just the cert itself into ~/.purple/certificates/x509/tls_peers/. The cert must be in PEM format (Base64 encoded). In some setups (OCS with load balancing), the cert seems to change frequently and thus the ca-certs approach is best. To get the cert that a site is using, you can use the following command line (this is for OCS/SIPE, your host/port may vary): openssl s_client -showcerts -connect hostname.yourcompany.com:sip-tls Then just copy everything from "-----BEGIN CERTIFICATE-----" through "-----END CERTIFICATE-----" (including the header/footer) into a text file named hostname.yourcompany.com.pem or something similar.
Confirmed the same behavior in F14 x86_64. I have tried to add CAs into the NSS db and it didn't work. [root@mars ca-certs]# uname -a Linux mars.astro.net 2.6.35.6-48.fc14.x86_64 #1 SMP Fri Oct 22 15:36:08 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux [root@mars ca-certs]# more /etc/redhat-release Fedora release 14 (Laughlin) [root@mars ca-certs]# rpm -q empathy empathy-2.32.0.1-2.fc14.x86_64
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Changing version to 15 as Empathy's debug window in Fedora 15 still shows this issue: No Certificate Authorities with either DN found found. I'll prompt the user, I guess.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still the case in F-18.
Talking about root cert here. No prompt to accept or decline - just silently doesn't work.
*** Bug 967844 has been marked as a duplicate of this bug. ***
FYI: this should come as no surprise, because this functionality is simply missing in telepathy-haze. It would require someone to sit down and write code to (a) intercept the libpurple request UI operation for the certificate accept/reject user interaction, and (b) implement Telepathy TLS Manager/Channel/Certificate classes that use the data from (a)
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.