Hide Forgot
Created attachment 1593416 [details] Output of pidgin -d Description of problem: Logging in to google talk account fails because of handshake failed. When I try to log in on rhel 8.1 (pidgin-2.13.0-5.el8) it works properly. I run pidgin with -d and the conversation and the communication with server looks like this: (09:39:53) jabber: Sending (pidgintest.2@gmail.com): <?xml version='1.0' ?> (09:39:53) jabber: Sending (pidgintest.2@gmail.com): <stream:stream to='gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'> (09:39:53) jabber: Recv (138): <stream:stream from="gmail.com" id="34811A54270E58B7" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client"> (09:39:53) jabber: Recv (241): <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-OAUTH2</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features> (09:39:53) jabber: Sending (pidgintest.2@gmail.com): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/> (09:39:53) jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/> (09:39:53) nss: Handshake failed (-12286) You can find output from the whole run attached. Version-Release number of selected component (if applicable): pidgin-2.10.11-8.el7.x86_64 How reproducible: always Steps to Reproduce: 1. Open pidgin. Go to Accounts -> Manage accounts and click on Add 2. Choose protocol Google talk. fill username and password, click on remember passwd and click add. 3. Actual results: Connection fails becouse of ssl handshake failed Expected results: Account is connected Additional info:
There is the same version of pidgin on 7.8 as it is on 7.7 (pidgin-2.10.11-8.el7.x86_64) so this bug still persists.
RHEL 7 is approaching its Extended Life Cycle Support phase. Given that this bug isn't present in RHEL 8, and there's no customer case associated with this for RHEL 7, I am inclined to WONTFIX it.
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain the issue receives the proper prioritization with product and development management. https://www.redhat.com/support/process/production/#howto