Project

General

Profile

Bug #2018

[Xoox] Certificate errors aren't shown

Added by krigstask almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
Plugins: Azoth
Target version:
Start date:
10/30/2016
Due date:
% Done:

100%

Estimated time:
10.00 h
Reported in:
master

Description

After updating from git/master (I think that was on Oct 27) my Azoth cannot connect to servers (I have accounts on gentoo.ru and jabber.se, both worked fine before that update). Pidgin continues to work fine, so there's nothing wrong with network or servers themselves.
Console log:

→→→→→→ [14:50:10.649] →→→→→→
?xml version='1.0'?><stream:stream to='gentoo.ru' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'

←←←←←← [14:50:10.666] ←←←←←←
?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='312731050' from='gentoo.ru' version='1.0' xml:lang='ru'><stream:features><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/><compression xmlns='http://jabber.org/features/compress'><method>zlib</method></compression><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism></mechanisms><c xmlns='http://jabber.org/protocol/caps' hash='sha-1' node='http://www.process-one.net/en/ejabberd/' ver='kxldlsZuzEZzrZKi50X/YdUuN44='/></stream:features

→→→→→→ [14:50:10.666] →→→→→→
  <starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

←←←←←← [14:50:10.683] ←←←←←←
  <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>

#1

Updated by 0xd34df00d almost 4 years ago

Nothing in Azoth has been changed recently. What else has been updated around that date?

#2

Updated by krigstask almost 4 years ago

0xd34df00d wrote:

Nothing in Azoth has been changed recently. What else has been updated around that date?

Hm...

Tue Oct 11 22:46:42 2016 >>> net-libs/qxmpp-9999
Sun Oct 30 14:20:34 2016 >>> net-libs/qxmpp-9999

Rolling back to version built on Oct 11th doesn't help. What else is worth checking?

#3

Updated by 0xd34df00d almost 4 years ago

Qt (particularly qtnetwork), SSL-related libs, ca-certificates perhaps.

#4

Updated by krigstask almost 4 years ago

You're right, it's ca-certificates, which have introduced `insecure_certs` flag, disabled by default. I kinda thought I'll get a message about certificate if it's untrusted or something. Why could that be not the case here?

#5

Updated by 0xd34df00d almost 4 years ago

  • Target version set to 0.6.75
  • Status changed from New to Assigned
  • Subject changed from [Xoox] Azoth stopped connecting to Jabber servers to [Xoox] Certificate errors aren't shown

Good question. QXmpp didn't expose the necessary APIs for this to work back in the day. It does now.

#6

Updated by 0xd34df00d almost 4 years ago

  • Estimated time set to 10.00 h
  • % Done changed from 0 to 100
  • Status changed from Assigned to Resolved

Now the errors are being shown.

#7

Updated by 0xd34df00d over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF