Bug 279830 - Connecting to jabme.de on port 443 doesn't work
Summary: Connecting to jabme.de on port 443 doesn't work
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: Jabber Plugin (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-08-10 17:44 UTC by Bernhard Walle
Modified: 2018-10-27 04:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernhard Walle 2011-08-10 17:44:30 UTC
Version:           unspecified (using KDE 4.7.0) 
OS:                Linux

The jabme.de Jabber server offers connecting to port 443 if the server "port443.jabme.de" is specified. With the Jabber clients PSI and Gajim, it works without problems.

However, in Kopete it doesn't work. When the "Use SSL" (does that also mean TLS or only the old SSL?) is checked, it complains about problems creating the TLS connection. If the tick is unchecked, it complains that there are authentication  problems, but doesn't specify a reason.

The password is correct, I double-checked that.

Using Kopete with that Jabber server with the normal port works, but I also want to use Jabber behind a firewall that blocks the normal ports.

Reproducible: Always

Steps to Reproduce:
1. Setup the Jabber connection as described above.
2. Connect.

Actual Results:  
Error message

----------------- 8< -----------------
Bei der Authentifizierung auf dem Server ist ein Fehler aufgetreten: Anmeldung aus unbekanntem Grund fehlgeschlagen.
----------------- >8 -----------------

Expected Results:  
It works. :-)

The Kopete version is 1.1.0 (doesn't appear in the list).

When starting Kopete in a terminal, following output appears

----------------- 8< -----------------
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
Unknown signature value:  795 
Unknown signature value:  668 
----------------- >8 -----------------
Comment 1 Pali Rohár 2013-10-23 08:33:15 UTC
Kopete from KDE 4.11 has updated libiris xmpp library and SSL support. Please check if this problem still exists.
Comment 2 Andrew Crouthamel 2018-09-25 03:39:29 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 04:00:30 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!