Opened at 2017-10-06T22:35:06Z
Last modified at 2018-03-14T11:23:17Z
#1296 reopened defect
Gtalk => Certificate verification problem 0x204
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Unspecified / other | Version: | Unspecified |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
Using either im.bitlbee.org or testing.bitlbee.org, I get the following error when my GTalk account tries to connect:
"gtalk - Login error: Certificate verification problem 0x204: certificate hostname mismatch"
Attachments (0)
Change History (6)
comment:1 Changed at 2017-10-12T08:37:56Z by
comment:2 Changed at 2017-10-17T18:08:47Z by
I reported the 0x14 error. I can confirm that testing.bitlbee.org works for me, but im.bitlbee.org is still reporting the same error.
comment:5 Changed at 2017-11-28T09:47:42Z by
Resolution: | → fixed |
---|---|
Status: | new → closed |
I think this is/was an incompatibility between BitlBee/its use of GnuTLS, the GnuTLS version that comes with Ubuntu 14.04, and probably new TLS certs at Google.
Fortunately I've fixed this on im.bitlbee.org by upgrading to the new LTS release, so this is all fine again there now.
If anyone else has this problem, again on 14.04 ... sorry, I did not actually find out what's wrong. GnuTLS debugging logs were utterly unhelpful as well, and the gnutls-cli cmdline utility did not reproduce this either as it was also compiled against a different libgnutls. :<
comment:6 Changed at 2018-03-14T11:23:17Z by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Same problem here today on both im & testing :{
And in #1297 someone is running into 08:47:48 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer)
I can repro this on im.bitlbee.org. testing.bitlbee.org is however working fine.
Both openssl s_client and gnutls-bin on the same machine see no problem and can find the right CA cert. I have no clue what GnuTLS (the lib actually used by BitlBee) is doing wrong here... I do see BitlBee opening the right ca-certificates.crt bulk file.