This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Need help for using StudiVZ (Jabber-Protokoll) with Kopete (SSL-Problem?)

Tags: None
(comma "," separated)
markum
Registered Member
Posts
165
Karma
1
Hi,
i am trying to use the Chat of the German social network studivz with Kopete. It is known that they use a modified XMPP/Jabber-protocol. It works with pidgin now. It tried to set it up with Kopete, but it fails for unknown reason.
My theory is that it fails because Kopete does not handle the SSL-certificate. When I set up the account with pidgin, the first time it connects, I get asked if I want to accept the unknown certificate. After I do that, it works. Kopete never asks about that certificate. So I assume that is the problem. To verify that I want to know if there is a way to initiate communication with the XMPP-server manually and import the server-certificate into KDE. Does anyone know if this is possible and how to do this?
May be can some else try. The server is nimbuzz.com, the port is 5222/ 5223.

Markum


markum, proud to be a member of KDE forums since 2008-Nov.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
If you can ask Konqueror to import their certificate, it should apply to Kopete also.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
markum
Registered Member
Posts
165
Karma
1
bcooksley wrote:If you can ask Konqueror to import their certificate, it should apply to Kopete also.

That is what why tried first. But unfortunately opening the page with https://nimbuzz.com tells me the connection was rejected. So it seems like they do not operate on http with ssl. That is why I asked for another solution.

Markum[hr]
bcooksley wrote:If you can ask Konqueror to import their certificate, it should apply to Kopete also.

That is what why tried first. But unfortunately opening the page with https://nimbuzz.com tells me the connection was rejected. So it seems like they do not operate on http with ssl. That is why I asked for another solution.

Markum

Last edited by markum on Tue Jun 02, 2009 12:17 pm, edited 1 time in total.


markum, proud to be a member of KDE forums since 2008-Nov.
markum
Registered Member
Posts
165
Karma
1
Hi,

I now have found out via wireshark that Kopete and Pidgin to totally different things with the same setting. It looks like Kopete never gets a real answer. May be the contact to the Jabber-Server is never even established.

Kopete:
Code: Select all
1        0.000000        192.168.178.20        nimbuzz.com        TCP        39334 > xmpp-client [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=2319462 TSER=0 WS=6
2        0.004707        fritz.fonwlan.box        192.168.178.20        TCP        4881 > 14013 [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=8678211 TSER=0 WS=1


Pidgin:
Code: Select all
2991        207.708054        192.168.178.20        fritz.fonwlan.box        DNS        Standard query SRV _xmpp-client._tcp.nimbuzz.com
2992        207.724035        fritz.fonwlan.box        192.168.178.20        DNS        Standard query response SRV 0 0 5222 o.nimbuzz.com
2993        208.174001        192.168.178.20        fritz.fonwlan.box        DNS        Standard query A o.nimbuzz.com
2994        208.177764        fritz.fonwlan.box        192.168.178.20        DNS        Standard query response A 194.229.27.29
2995        208.178209        192.168.178.20        o.nimbuzz.com        TCP        54872 > xmpp-client [SYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=2371507 TSER=0 WS=6
2996        208.202411        o.nimbuzz.com        192.168.178.20        TCP        xmpp-client > 54872 [SYN, ACK] Seq=0 Ack=1 Win=4356 Len=0 MSS=1452 WS=0
2997        208.202487        192.168.178.20        o.nimbuzz.com        TCP        54872 > xmpp-client [ACK] Seq=1 Ack=1 Win=5888 Len=0
2998        208.203424        192.168.178.20        o.nimbuzz.com        Jabber/XML        Request:
2999        208.325878        o.nimbuzz.com        192.168.178.20        TCP        xmpp-client > 54872 [ACK]

Could this be a port being blocked? I have also read something about the lack out UPNP-support in KDE/Kopete causing problems. I have googled around a little, but I have not understood, what the exact problem is and how to possibly solve it. I have opened up the ports 5222 and 5223 in my router, but this did not change anything. Does anyone have an idea for a possible workaround?

Markum


markum, proud to be a member of KDE forums since 2008-Nov.


Bookmarks



Who is online

Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]