So I did a bit more digging. The "use old SSL" checkbox tells empathy to use the ancient method of using SSL for the entire jabber connection, rather than the modern XMPP starttls command. That is not what we want for the webex connect case -- we just want to use TLS 1.0 instead of 1.1. However, as I look through the stack, I see that empathy uses telepathy-gabble which in turn uses libloudmouth for Jabber/XMPP. And unfortunately the libloudmouth API does not have any way to specify a TLS version, so any fix will have to start by extending that API, and then plumbing it up through telepathy-gabble and empathy.
Also it's not clear that Todd Kennedy's bug is the same as the bug I originally reported, which is (stil?!) on the webex connect server side. One could work around it with a "force TLS 1.0" option on the empathy side, but as I described above, that may take a bit of work. -- gnutls can't negotiate tls connection to webex connect (empathy vs pidgin regression) https://bugs.launchpad.net/bugs/418935 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
