Jabber handshake fails

dpeterka · Post by **dpeterka** » Mon Oct 09, 2006 8:35 am

Greetings we're running a Java based Jabber server , Wildfire. When sending an alert to the server it would seem the handshake fails. We're using ssl/tls as an encryption method. Any guidance to sort this out would be appreciated.

Output from standard logs on Jabber server >

2006.10.09 10:10:37 [org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:104)] Connection closed before session established

Output from logs with debug level set on Jabber server >
2006.10.09 10:30:48 Connect Socket[addr=/192.168.xx.xx,port=2166,localport=5222]
2006.10.09 10:30:48 Error creating session
java.io.EOFException: input contained no data
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:3003)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3046)
at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1410)
at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at org.jivesoftware.wildfire.net.SocketReader.createSession(SocketReader.java:432)
at org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java:53)
at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:123)
at java.lang.Thread.run(Unknown Source)
2006.10.09 10:32:04 Connect Socket[addr=/192.168.xx.xx,port=2208,localport=5222]
2006.10.09 10:32:04 Logging off wildfire.operative.com/f24b8397 on org.jivesoftware.wildfire.net.SocketConnection@198252f socket: Socket[addr=/192.168.xx.xx,port=2208,localport=5222] session: org.jivesoftware.wildfire.ClientSession@1fec571 status: -1 address: jabber.domain.com/f24b8397 id: f24b8397 presence:
<presence type="unavailable" from="jabber.domain.com/f24b8397"/>

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Oct 09, 2006 9:05 am

dpeterka wrote:We're using ssl/tls as an encryption method.

Sorry, HM does not support ssl/tls authentification method for Jabber client yet. Perhaps, it will be implemented in future versions.

Regards,
Max

sherrera · Post by **sherrera** » Mon Oct 09, 2006 12:35 pm

We also use Wildfire without ssl/tls authentication and get:

2006.10.09 14:27:11 Connect Socket[addr=/10.10.x.x,port=2666,localport=5222]
2006.10.09 14:27:12 Logging off rubicon/53188b3c on org.jivesoftware.wildfire.net.SocketConnection@ac6782 socket: Socket[addr=/10.10.1.12,port=2666,localport=5222] session: org.jivesoftware.wildfire.ClientSession@d31bf8 status: 1 address: rubicon/53188b3c id: 53188b3c presence:
<presence type="unavailable"/>

It seems to disconnect as soon as it connects. No message is ever sent.

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Oct 09, 2006 12:50 pm

HostMonitor uses its own implementation of XMPP protocol to send messages and for now, it does not support TLS/SSL authentification. I think, you may enable other authentification methods on your Jabber server to make it work.

Regards,
Max

sherrera · Post by **sherrera** » Mon Oct 09, 2006 1:05 pm

We are not using the TLS/SSL authentification.

KS-Soft Europe · Post by **KS-Soft Europe** » Mon Oct 09, 2006 1:16 pm

sherrera wrote:We are not using the TLS/SSL authentification.

Hm. What error do you see in system log (Options > System Log)?
Could you create an account on jabber.org to test it?

Regards,
Max

sherrera · Post by **sherrera** » Thu Oct 12, 2006 12:44 pm

It does work correctly on Jabber.org. Seems to be a problem with Wildfire and I think it is still in the handshake as originally posted. The error in syslog is:

Error: Cannot send message to Jabber account sherrera. Your username or password is incorrect;

I did get some packet captures if you would like to seem them? I am not sure how high the priority is on this for you guys but it would be nice to be alerted through the jabber client.

KS-Soft Europe · Post by **KS-Soft Europe** » Thu Oct 12, 2006 1:09 pm

sherrera wrote:It does work correctly on Jabber.org. Seems to be a problem with Wildfire and I think it is still in the handshake as originally posted.

There are several ways to authenticate user on Jabber server. We have implemented the most common method, which should be supported by every server. However, such method is less secure than others, so, for the most of servers it might be disabled.

sherrera wrote:I did get some packet captures if you would like to seem them? I am not sure how high the priority is on this for you guys but it would be nice to be alerted through the jabber client.

Could you send the captured files to the support@ks-soft.net?

Regards,
Max

KS-Soft · Post by **KS-Soft** » Fri Oct 13, 2006 6:13 pm

Could you try this update www.ks-soft.net/download/hm624c.zip ?
Please install version 6.24 before using this update

Regards
Alex

sherrera · Post by **sherrera** » Wed Oct 18, 2006 11:40 am

6.24c works. Thank you.

dpeterka2 · Post by **dpeterka2** » Tue Feb 06, 2007 3:55 pm

Is this patch in the main build, now?

KS-Soft · Post by **KS-Soft** » Tue Feb 06, 2007 4:02 pm

Yes

Regards
Alex

rasqual · Post by **rasqual** » Fri Mar 09, 2007 12:44 pm

Nuts. Jabber notifications still aren't working for us.

KS-Soft Europe · Post by **KS-Soft Europe** » Fri Mar 09, 2007 12:52 pm

rasqual wrote:Nuts. Jabber notifications still aren't working for us.

What error do you see in System Log (file is specified in "Options" > "System Log" tab)?
Have you provided correct data into "Options" > "Jabber" tab? Have you specified full recipient JID (with server name, like recipient@jab_server) in "Action Properties" window?

Regards,
Max

KS-Soft · Post by **KS-Soft** » Fri Mar 09, 2007 12:52 pm

What exactly means "aren't working"? What error do you see in the log? What version of HostMonitor do you use?

Regards
Alex

Jabber handshake fails

Jabber handshake fails

Re: Jabber handshake fails