Red Hat Bugzilla – Bug 249605
Connecting to DJabberd fails TLS logins
Last modified: 2007-11-30 17:12:11 EST
Description of problem:
When connecting to DJabberd using TLS, pidgin fails to connect. DJabberd logs a
SSL_read 23061: 1 - error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number
SSL Read error: SSL_read 23061: 1 - error:1408F10B:SSL
routines:SSL3_GET_RECORD:wrong version number
Error when 64bit pidgin connects.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup DJabberd w/ an SSL certificate.
2. Connect w/ pidgin
Pidgin fails to connect and DJabberd reports a "wrong version number" error
Pidgin to connect.
64bit PSI connects fine using qca-tls, which uses openssl.
32bit pidgin on windows and F7 works fine (exact same configuration)
64bit pidgin works when compiled with gnutls ONLY and NOT nss (f7 pidgin build
use NSS only and windows pidgin builds use NSS only).
64bit pidgin w/ gnutls AND nss support built in does not work (thinking pidgin
favors nss over gnutls)
If I configure pidgin to use "Old SSL" AND change the port to 5223 AND specify
the hostname to connect to, it connects fine on 64bit.
Not sure if this is a bug in pidgin specifically or a bug in NSS.
I've only tested this against djabberd as the only other jabber server I have
readily available is an OLD install of jabberd14 which doesn't support TLS.
Issue has gone away w/ Pidgin 2.1.0. (though nothing noted in their changelog,
something they did fixed it)