Cisco has fixed this issue on their WebEx Connect servers -- I am
running Ubuntu 12.10 and am able to connect to the WebEx Connect IM
service using the Empathy that ships with Ubuntu 12.10. Just in case it
is not clear from the comments in the bug, this bug was never a bug in
GNU TLS, or anything
Any update on this? I (and many others) would really like to use empathy
to connect to webex.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418935
Title:
gnutls can't negotiate tls connection to
Aravinth (and many others): let Webex know this is a problem for you and
get them to fix their broken server. If a lot of customers complain
about this, it will get fixed I'm sure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnutls26 (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418935
Title:
gnutls can't negotiate tls connection to webex connect (empathy vs
i am using empathy in ubuntu 11.10 alpha 3 and this is still not fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418935
Title:
gnutls can't negotiate tls connection to webex connect (empathy
Hi,
I am on holiday till the 12th August 2011 inclusive.
For urgent issues, please call me on my mobile number, +32 478751048.
Regards,
Olivier Godart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
I am on holiday till the 12th August 2011 inclusive.
For urgent issues, please call me on my mobile number, +32 478751048.
Regards,
Olivier Godart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I find this hard to believe that this bug is still in a 'new' status and
not assigned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418935
Title:
gnutls can't negotiate tls connection to webex
I'm told by managers there that the SSL backend is currently being re-
written with OpenSSL. This means that at some point in the future WebEx
servers still probably just starting working with Empathy as it behaves
today.
That said, I don't want to wait for one day when. We should work to
make
I do work at Cisco, and I'll work on finding someone in the WebEx team
to address this. I'll post back shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/418935
Title:
gnutls can't negotiate
Joshua, good luck; I spent a fair amount of effort without finding
anyone who really cared. You might want to point them at my original
report http://wwwin-forums.cisco.com/thread.jspa?threadID=32270 (if it's
still there). The best contact I found within the Webex team was Tory
Patnoe (tpatnoe).
Oddly enough, I'm Cisco as well. Unfortunately I don't have access to
their Rally/Agile area to chase down the US Although I did find what I
think is a semi-related defect. Thanks Roland for the link. Joshua and
I have both posted into it for clarification on status.
--
You received this
Roland,
Do you have the Cisco Defect id to attach to this bug so we can track
progress? I've been searching for it and have come up empty so far.
Thanks
Jeff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Webex Connect / Jabber team at Cisco use their own tracking system;
this issue was US766 in their Rally.
I no longer work at Cisco so I don't really have any good way to get
more information about this (and I no longer have a personal stake,
since I don't use Webex Connect any more).
--
You
There is no fix. This is 100% confirmed as a bug in the Webex Connect
server TLS code as described above, and after a lot of work I finally
managed to get the Webex developers to add this to their bug tracker.
However the earliest release of Webex that this could be fixed in will
not be out until
This was fixed upstream in 2.8.4:
ChangeLog-
* NEWS: Version 2.8.4.
[...]
2009-08-31 Simon Josefsson si...@josefsson.org
* lib/x509/x509.c: Handle XMPP SANs properly. Reported by Howard
Chu h...@symas.com
Nevermind, paste error in wrong window.
--
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
This is confusing. Is there a fix or not?
2010/11/20, Andreas Metzler 418...@bugs.launchpad.net:
Nevermind, paste error in wrong window.
--
gnutls can't negotiate tls connection to webex connect (empathy vs pidgin
regression)
https://bugs.launchpad.net/bugs/418935
You received this bug
Could you please retry using Ubuntu 10.10 ? We've done lot of
improvements regarding TLS in telepathy-gabble. If it still don't work,
please open a bug on bugs.freedesktop.org : telepathy-gabble.
--
gnutls can't negotiate tls connection to webex connect (empathy vs pidgin
regression)
Hi Roland,
Did you find a way to have empathy use TLS 1.0?
--
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.
I am trying to use Empathy to connect to an Company internal Jabber/XMMP
service which is using SSL, which empathy is not able to connect. I
suspect it's due to this same reason. is there some work around I can
do?
This is my logfile from empathy
_gabble_connection_connect: disabling SRV because
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,
So does use old SSL not work in Empathy for the Jabber protocol? Does
use old SSL tell gnutls not to try 1.1 TLS but instead just use TLS
1.0 ?
--
gnutls can't negotiate tls connection to webex connect (empathy vs pidgin
regression)
https://bugs.launchpad.net/bugs/418935
You received this bug
I did double check again for grins. The Use old SSL option does not
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
Sorry, meant to update this bug. After further debugging, this turns
out to be a bug in the Webex Connect TLS implementation -- it only
implements TLS 1.0 (gnutls tries 1.1 first), and the Webex side has a
bug in how it handles negotiation back to TLS 1.0. Basically it's the
bug described in
I have the same problem - it shows up 'network error' for my webex
connect account. This is on karmic beta where empathy is default IM
client. Things were working fine with pidgin.
--
gnutls can't negotiate tls connection to webex connect (empathy vs pidgin
regression)
As another datapoint, adding a call to gnutls_protocol_set_priority in
loudmouth so it uses GNUTLS_TLS1_0 (version 3.1) instead of
GNUTLS_TLS1_1 lets empathy connect to webex connect. So it really does
seem to be something related to TLS 1.1.
--
gnutls can't negotiate tls connection to webex
** Attachment added: loudmouth/gnutls debugging output from failed (empathy)
connection
http://launchpadlibrarian.net/30834629/loudmouth.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/30834630/Dependencies.txt
--
gnutls can't negotiate tls connection to webex
Also attaching ssldump output.
I'm happy to debug this further based on any suggestions... would be
nice to be able to use empathy for all my IM accounts, but right now
webex connect only works with pidgin (and it's what my work has chosen).
** Attachment added: ssldump of working connection
29 matches
Mail list logo
