Your message dated Mon, 26 Jul 2010 14:02:46 +0100
with message-id <[email protected]>
and subject line Re: Bug#548280: [Pkg-telepathy-maintainers] Bug#548280:
telepathy-gabble: no longer connects
has caused the Debian Bug report #548280,
regarding telepathy-gabble: no longer connects
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
548280: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548280
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: telepathy-gabble
Version: 0.9.0-1
Severity: normal
The new version no longer connects to my oldssl server,
the server log says:
[record] (sipsolutions.net): login fail 213.182.114.190 406 (null)
With 0.8.3, it says:
[record] ([email protected]): login ok 213.182.114.190 Empathy
When I use TLS, empathy complains "Certificate hostname mismatch"
even though the certificate has the right name.
When I disable certificate validation, I again get
[record] (sipsolutions.net): login fail 213.182.114.190 406 (null)
in the server log.
Downgrading just telepathy-gabble to 0.8.3-1 fixes this problem,
but I can only connect with oldssl, when using TLS it says
"network error", which goes away when disabling certificate
validation.
The certificate is certainly valid for secure.sipsolutions.net
but not for sipsolutions.net, but I'm not sure how TLS negotiation
is supposed to work in the case where the ID is
[email protected], but the server name is
secure.sipsolutions.net.
It appears that gabble tries to negotiate with just "sipsolutions.net".
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-wl-38293-g1c37ce7-dirty (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages telepathy-gabble depends on:
ii libc6 2.10.1-0exp1 GNU C Library: Shared libraries
ii libdbus-1-3 1.2.16-2 simple interprocess messaging syst
ii libdbus-glib-1-2 0.82-1 simple interprocess messaging syst
ii libglib2.0-0 2.22.0-1 The GLib library of C routines
ii libgnutls26 2.8.3-3 the GNU TLS library - runtime libr
ii libsoup2.4-1 2.28.0-1 an HTTP library implementation in
ii libtelepathy-glib0 0.7.37-1 Telepathy framework - GLib library
ii libuuid1 2.16.1-3 Universally Unique ID library
ii libxml2 2.7.4.dfsg-2 GNOME XML library
telepathy-gabble recommends no packages.
telepathy-gabble suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.9.1
On Fri, 25 Sep 2009 at 13:50:50 +0200, Johannes Berg wrote:
> Thanks, that was quick. I'm indeed using jabberd 1.4 as well, and git
> (0.9.0.1, commit 271fd01cd5) connects fine with oldssl.
I believe this was fixed in 0.9.1, then.
On Sat, 10 Apr 2010 at 08:15:10 -0700, andy wrote:
> my symptoms were very similar but apparently unrelated. for me the
> issue was resolved with a downgrade from libgnutls26 2.9.9-1 to
> 2.8.6-1. i will file a bug against that package.
Since this turned out not to be the same thing, and Andy's log includes
"TLS Handshake Error: -59: GNUTLS_E_INTERNAL_ERROR" (which points the blame
towards gnutls), I'll consider this bug to have been closed by fixing
Johannes' original report.
Andy, did you open a bug against gnutls in the end? If not, please try with
the current experimental gnutls (2.10) and open a bug against gnutls if it's
still problematic.
Thanks,
Simon
--- End Message ---
