Description of problem: According to my nightly yum log, a new openssl was installed: Oct 22 02:36:37 Updated: 1:openssl-libs-1.0.1e-28.fc19.x86_64 Oct 22 02:37:09 Updated: 1:openssl-devel-1.0.1e-28.fc19.x86_64 Oct 22 02:37:11 Updated: 1:openssl-1.0.1e-28.fc19.x86_64 Oct 22 02:37:23 Updated: 1:openssl-libs-1.0.1e-28.fc19.i686 Since then, my Psi (Jabber client) fails to perform a TLS handshake. Version-Release number of selected component (if applicable): 1.0.1e-28 How reproducible: Always Steps to Reproduce: 1. Update openssl 2. Start Psi connecting to an XMPP server using TLS 3. Actual results: A dialog appears, displaying the following error: "There was an error communicating with the server. Details: TLS handshake error" Expected results: Connection should work. Additional info: Since Psi does not use openssl directly but uses the qca2 framework. Any QT-App which uses that framework might be affected too. I also performed the following test in order to prove that this version of openssl is the actual culprit: 1. Fetch the old openssl rpms 2. Unpack those using rpm2cpio into a local dir: /home/felfert/ssltest/x 3. Use LD_LIBRARY_PATH=/home/felfert/ssltest/x/usr/lib64 to force psi using the older openssl => Psi works like before the update.
Looks like the same problem as I got with gajim (bug 1022493)
Can you please try openssl-1.0.1e-29.fc19 ?
openssl-1.0.1e-29.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/openssl-1.0.1e-29.fc19
openssl-1.0.1e-29.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/openssl-1.0.1e-29.fc20
openssl-1.0.1e-29.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openssl-1.0.1e-29.fc18
Package openssl-1.0.1e-29.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openssl-1.0.1e-29.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19845/openssl-1.0.1e-29.fc20 then log in and leave karma (feedback).
Fetched 1.0.1e-29 from koji manually (it had not hit the repo yet) and it indeed fixes the Psi TLS issue :) - Thanks a lot!
I also confirm the TLS fix, Psi+ client. x86_64 Thanks
*** Bug 1022365 has been marked as a duplicate of this bug. ***
openssl-1.0.1e-29.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
openssl-1.0.1e-30.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openssl-1.0.1e-30.fc18
openssl-1.0.1e-30.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/openssl-1.0.1e-30.fc19
openssl-1.0.1e-30.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/openssl-1.0.1e-30.fc20
Package openssl-1.0.1e-30.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openssl-1.0.1e-30.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-20263/openssl-1.0.1e-30.fc18 then log in and leave karma (feedback).
openssl-1.0.1e-30.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
openssl-1.0.1e-29.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
openssl-1.0.1e-30.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
openssl-1.0.1e-30.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 1033070 has been marked as a duplicate of this bug. ***
the bug 1033070 is not corrected. the latest version has not corrected the problem 1033070. Moreover, since it is the bug fix 1022647 that the problem occurred