"Auth error" on Xabber

"Auth error" on Xabber

Postby ruawhitepaw » Sat Apr 15, 2017 6:17 pm

I just registered and I'm able to connect and chat just fine with Pidgin on my desktop. But on my phone using Xabber, I get "Auth error" whenever I try to connect, and the connection is closed. How can I fix this?
ruawhitepaw
 
Posts: 4
Joined: Sat Apr 15, 2017 6:14 pm

Re: "Auth error" on Xabber

Postby Nulani » Sat Apr 15, 2017 6:32 pm

Are there any more detailed error messages available? I am afraid I haven't got a phone with access to the Google Market myself, so I can't test. I do see that there's a beta version as well, have you tried that?

I am seeing a lot of malformed authentication requests in my logs from a single IP. Server is also throttling because of there being too many authentication requests from that IP. Could be the reason, but exactly what Xabber is doing wrong (or if it is indeed you), I can't say.
Evil is good.
Evil!
User avatar
Nulani
Site Admin
 
Posts: 255
Joined: Wed May 23, 2007 9:42 pm
Location: Norway

Re: "Auth error" on Xabber

Postby ruawhitepaw » Sat Apr 15, 2017 6:36 pm

The version I'm using is downloaded through F-Droid, so it's whatever was the latest on there, 1.0.155. There's not that many settings I could change in Xabber, that I can see. I enabled TLS, could that be the problem? What exactly is malformed about the requests?
ruawhitepaw
 
Posts: 4
Joined: Sat Apr 15, 2017 6:14 pm

Re: "Auth error" on Xabber

Postby Nulani » Sat Apr 15, 2017 6:38 pm

While I have no way to test, I expect it's related to this: https://prosody.im/issues/issue/854. Or something similar. Without debug logging enabled, I don't have any details beyond authentication request being malformed.

Edit: From what I can see the latest version of Xabber is 2.0.1, released 2017-04-12.
Evil is good.
Evil!
User avatar
Nulani
Site Admin
 
Posts: 255
Joined: Wed May 23, 2007 9:42 pm
Location: Norway

Re: "Auth error" on Xabber

Postby ruawhitepaw » Sat Apr 15, 2017 6:46 pm

Here is a bit of the log from Xabber.

Code: Select all
2017-04-15_18-03-42 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Trying to establish TCP connection to /178.62.253.85 at port 5222
2017-04-15_18-03-42 D/org.jivesoftware.smack.tcp.XMPPTCPConnection﹕ Established TCP connection to /178.62.253.85 at port 5222
2017-04-15_18-03-42 D/Smack﹕ SENT (0): <stream:stream xmlns='jabber:client' to='neko.im' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='ruawhitepaw@neko.im' xml:lang='en'>
2017-04-15_18-03-42 D/Smack﹕ RECV (0): <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='neko.im' id='be88b497-98bb-4de2-956f-bd96a99ec5b0' version='1.0' xmlns='jabber:client'><stream:features><c hash='sha-1' ver='jTzFaMJbCixIFZTbRg2AIpj/30U=' node='http://prosody.im' xmlns='http://jabber.org/protocol/caps'/><starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'><required/></starttls></stream:features>
2017-04-15_18-03-42 D/Smack﹕ SENT (0): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'></starttls>
2017-04-15_18-03-42 D/Smack﹕ RECV (0): <proceed xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
2017-04-15_18-03-42 D/ReconnectionManager﹕ ruawhitepaw@neko.im/Xabber_Ozrp85zm not authenticated. State: connecting waiting... seconds from last reconnection 1
2017-04-15_18-03-43 D/Smack﹕ SENT (0): <stream:stream xmlns='jabber:client' to='neko.im' xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='ruawhitepaw@neko.im' xml:lang='en'>
2017-04-15_18-03-43 D/Smack﹕ RECV (0): <?xml version='1.0'?><stream:stream xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' from='neko.im' id='9dfdc803-cdfd-4e8a-933d-fd1a29369a0b' version='1.0' xmlns='jabber:client'><stream:features><c hash='sha-1' ver='jTzFaMJbCixIFZTbRg2AIpj/30U=' node='http://prosody.im' xmlns='http://jabber.org/protocol/caps'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>SCRAM-SHA-1</mechanism><mechanism>SCRAM-SHA-1-PLUS</mechanism></mechanisms></stream:features>
2017-04-15_18-03-43 D/ConnectionListener: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ connected
2017-04-15_18-03-43 D/Smack﹕ SENT (0): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='SCRAM-SHA-1'>eSwsbj1ydWF3aGl0ZXBhdyxyPXx5ZlAtZCtKOytZSlBkYmtEbkJcdTE7ZSVsaHFFcUdZ</auth>
2017-04-15_18-03-43 D/Smack﹕ RECV (0): <failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><malformed-request/></failure>
2017-04-15_18-03-43 D/AccountItem: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ updateState authentication
2017-04-15_18-03-43 D/ReconnectionManager﹕ onConnected ruawhitepaw@neko.im/Xabber_Ozrp85zm
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: malformed-request
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.SASLAuthentication.authenticationFailed(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ java.lang.Thread.run(Thread.java:818)
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Error. SASLError using SCRAM-SHA-1: malformed-request Exception class: SASLErrorException
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Connection thread finished
2017-04-15_18-03-43 D/com.xabber.android.data.notification.NotificationManager@fe5db67﹕ updatePersistentNotification account ruawhitepaw@neko.im/Xabber_Ozrp85zm state authentication
2017-04-15_18-03-43 D/com.xabber.android.data.notification.NotificationManager@fe5db67﹕ Notification: 1, ticker: null, sound: null, vibro: 0, light: 0
2017-04-15_18-03-43 D/AccountItem: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ connect
2017-04-15_18-03-43 D/AccountItem: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ updateState connecting
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Connection thread is finished, creating new one...
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Creating new connection thread
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Connection thread is new, starting...
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Trying to connect and login...
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Already connected
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.sasl.SASLErrorException: SASLError using SCRAM-SHA-1: malformed-request
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.SASLAuthentication.authenticationFailed(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.parsePackets(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader.access$300(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ org.jivesoftware.smack.tcp.XMPPTCPConnection$PacketReader$1.run(Unknown Source)
2017-04-15_18-03-43 E/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ java.lang.Thread.run(Thread.java:818)
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Error. SASLError using SCRAM-SHA-1: malformed-request Exception class: SASLErrorException
2017-04-15_18-03-43 D/ConnectionThread: ruawhitepaw@neko.im/Xabber_Ozrp85zm﹕ Connection thread finished


I hope this is useful at all. It does seem related to that SCRAM-SHA-1 thing, but I have no idea what's going on.

Edit: apparently F-Droid are unable to build any version more recent: https://f-droid.org/wiki/page/com.xabber.androiddev
ruawhitepaw
 
Posts: 4
Joined: Sat Apr 15, 2017 6:14 pm

Re: "Auth error" on Xabber

Postby Nulani » Sat Apr 15, 2017 6:54 pm

That is indeed the issue I linked. From what I can work out, the problem is that the version of smack that version of Xabber is built on tries to authenticate with SCRAM-SHA-1, and at the same time saying it supports SCRAM-SHA1-PLUS. Since it says it supports a superior authentication protocol, it gets rejected by my server and it is supposed to re-authenticate using SCRAM-SHA1-PLUS. Except that it doesn't. That issue seems to have been fixed in smack back in March, which means the fix might have made it into Xabber 2.0.1, but it won't be in 1.1.155.
Evil is good.
Evil!
User avatar
Nulani
Site Admin
 
Posts: 255
Joined: Wed May 23, 2007 9:42 pm
Location: Norway

Re: "Auth error" on Xabber

Postby ruawhitepaw » Sat Apr 15, 2017 6:59 pm

Ok, I'll just have to wait until F-Droid comes with an update then. In the meantime I tried another Jabber client, which works. Thank you for the help!
ruawhitepaw
 
Posts: 4
Joined: Sat Apr 15, 2017 6:14 pm


Return to Neko IM!

Who is online

Users browsing this forum: No registered users and 1 guest

cron