FS#33421 - bitlbee still using OpenSSL rather than GnuTLS
Attached to Project:
Arch Linux
Opened by Benjamin Cathey (becatlibra) - Wednesday, 16 January 2013, 18:17 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 18 April 2013, 13:16 GMT
Opened by Benjamin Cathey (becatlibra) - Wednesday, 16 January 2013, 18:17 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 18 April 2013, 13:16 GMT
|
Details
Description:
bitlbee still has issues with google (gtalk) which, according to the developer, should be resolved by switching from OpenSSL to GnuTLS. At this point, the latest version (3.2) has consistent issues with gtalk accounts which render the entire program unuseable. When a gtalk count is enabled (with SSL) after a period of time the entire bitlbee gateway stops responding and eventually seems to reset. Talked in the #bitlbee IRC room about this, GnuTLS is the recommended lib rather than OpenSSL and the supposed fix. Steps to reproduce: |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 18 April 2013, 13:16 GMT
Reason for closing: Fixed
Additional comments about closing: back to gnutls we go...
Thursday, 18 April 2013, 13:16 GMT
Reason for closing: Fixed
Additional comments about closing: back to gnutls we go...
He's also talking about disabling openssl support altogether if the channel keeps getting complaints stemming from this. I and several other users all came with the same problem and all of us had our problems magically go away when recompiling with gnutls.
I understand that there was some churn with this back in 2011, but upstream seems to view it as a problem with only one solution, and the Arch way usually means siding with upstream, right?
I'm not able to publicly discuss the reasons why bitlbee stopped working with gtalk last time around.
(EDIT: nevermind what i said here before - I wasn't aware that falconindy works for google, so it makes sense now)
Several others on #bitlbee are experiencing the same as I'm writing this.