FS#46701 - [qca-qt4] Can't connect to SSL/TLS XMPP servers

Attached to Project: Arch Linux
Opened by IONOFF Joachim (LinLo) - Tuesday, 13 October 2015, 18:11 GMT
Last edited by Antonio Rojas (arojas) - Friday, 17 February 2017, 16:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Kopete/Psi doesn't not seems to connect to SSL/TLS XMPP servers.
Works with old qca / qca-ossl / qca-gnupg package.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Try to connect to SSL/TLS XMPP server.
"There was an error authenticating with the server: No appropriate authentication mechanism available. Offered mechanisms: EXTERNAL, PLAIN"
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 17 February 2017, 16:18 GMT
Reason for closing:  Works for me
Comment by IONOFF Joachim (LinLo) - Tuesday, 13 October 2015, 18:14 GMT
Sorry forgot to enter SUMMARY. Is there a way to modify it ?
Comment by Antonio Rojas (arojas) - Tuesday, 13 October 2015, 19:20 GMT
Works for me on jwchal (SSL) and Google. Can you tell me a public server that doesn't work for you where I can create an account to test?
Comment by IONOFF Joachim (LinLo) - Wednesday, 14 October 2015, 18:20 GMT
I'm using jabberd2 server with STARTTLS (tcp 5222) and self-signed certificate.
I attached pcapng capture.
   pcapng_starttls_kopete_jabber... (7.1 KiB)
Comment by Antonio Rojas (arojas) - Wednesday, 14 October 2015, 19:49 GMT
Seems to be an upstream issue, since all plugins are being correctly loaded. Unfortunately qca is currently unmaintained, but you should still report it.
Comment by IONOFF Joachim (LinLo) - Wednesday, 14 October 2015, 20:06 GMT
Thank you, I will try to report this issue.
Comment by Antonio Rojas (arojas) - Thursday, 16 February 2017, 10:00 GMT
Status with 2.1.3?
Comment by IONOFF Joachim (LinLo) - Friday, 17 February 2017, 16:15 GMT
We can close this bug report.
Not reproduced anymore (new client, new server).
Thank you.

Loading...