[Exodus-dev] Exodus vs Jabber 2

[Sean Covel]

It appears to me from some testing today that Exodus and Jabber 2 do not
agree on the case sensitivity of usernames. I have a user, call him
John, who setup an account on my Jabber 2 server using Exodus. He
registered as ***@server.org. He registered successfully, and
participated in chats all day long. The next day when he tried to
connect, he kept getting failures. He asked me to look into it. It
happened to me too. My ID was working fine, but his said the password
was bad or the id was already in use (or some such garbage...). Finally
I deleted his account and re-created it. Worked just great! So I told
him to try it. It doesn't work again. So on a whim, i tried
***@server.org rather than ***@server.org, and it worked.

So, where does the fault lie? I don't know. Exodus and Jabber 2 were
both happy with the initial registration. After disconnecting, it
appears that the account was created in lower-case, but Exodus attempts
to connect with an upper-case username.

For testing purposes I also tried PSI, another client. I added
***@server.org and attempted a connection. No problems. It appears
the PSI send the username lowercase despite what I typed.

Sean

[Peter Millard]

Sean Covel wrote:
[Stuff deleted..]

Post by Sean Covel
So, where does the fault lie? I don't know. Exodus and Jabber 2 were
both happy with the initial registration. After disconnecting, it
appears that the account was created in lower-case, but Exodus attempts
to connect with an upper-case username.

Yeah, the problem is that Exodus is not "canonicalizing" the usernames. I'm
currently working on a solution to make Exodus use the GNU libidn library to do
all of this. The fix (obviously) is to have your user enter his username as
"john" instead of "John", and it should work fine. Stay tuned for a fix for this
in the next cpl of weeks.

pgm.

[Sameer Verma]

Post by Peter Millard
[Stuff deleted..]

Post by Sean Covel
So, where does the fault lie? I don't know. Exodus and Jabber 2 were
both happy with the initial registration. After disconnecting, it
appears that the account was created in lower-case, but Exodus attempts
to connect with an upper-case username.

Yeah, the problem is that Exodus is not "canonicalizing" the usernames. I'm
currently working on a solution to make Exodus use the GNU libidn library to do
all of this. The fix (obviously) is to have your user enter his username as
"john" instead of "John", and it should work fine. Stay tuned for a fix for this
in the next cpl of weeks.
pgm.
_______________________________________________
Exodus-dev mailing list
https://jabberstudio.org/mailman/listinfo/exodus-dev

I get the same error, although in my case, there is no confusion with
case. the user id is all lower case. I am also using Jabberd2

Here's the XML from the debug window.
Sameer


Looking up SRV: _xmpp-client._tcp.indigo.sfsu.edu
Got A: 130.212.14.69 5222
SENT: <stream:stream to="indigo.sfsu.edu" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" xml:lang="en"
version="1.0" >
RECV: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='indigo.sfsu.edu' version='1.0'
id='f47x5qkwzi6yfw34vd18i02u06j59ppptxnzo7vn'>
RECV: <stream:features
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5</mechanism><mechanism>PLAIN</mechanism></mechanisms></stream:features>
SENT: <auth mechanism="DIGEST-MD5"
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
RECV: <challenge
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImluZGlnby5zZnN1LmVkdSIsbm9uY2U9Ijg4ZTBiNTY4NzQxZmFhNzA0NDI2ZmE2NGZmM2NkNzIwYjdkNjFkYmYiLHFvcD1hdXRoLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kNS1zZXNz</challenge>
SENT: <response
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">dXNlcm5hbWU9InN2ZXJtYSIscmVhbG09ImluZGlnby5zZnN1LmVkdSIsbm9uY2U9Ijg4ZTBiNTY4NzQxZmFhNzA0NDI2ZmE2NGZmM2NkNzIwYjdkNjFkYmYiLGNub25jZT0iODkxYmJiMjZkY2E3NjBlZDU2M2FiMDg2OWI2ZTAzOTgiLG5jPTAwMDAwMDAxLHFvcD1hdXRoLGRpZ2VzdC11cmk9InhtcHAvaW5kaWdvLnNmc3UuZWR1IixjaGFyc2V0PXV0Zi04LHJlc3BvbnNlPTI5ZGM4ZjM0ZGJhYmM3ZTk0YzUzY2YyYjU1ZmExMzI5</response>
RECV: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><temporary-authentication-failure/></failure>

[Peter Millard]

Post by Sameer Verma
I get the same error, although in my case, there is no confusion with
case. the user id is all lower case. I am also using Jabberd2

Did you use any non-ascii, or Uppercase characters when you registered the
account?

pgm.

[Sameer Verma]

Post by Peter Millard

Post by Sameer Verma
I get the same error, although in my case, there is no confusion with
case. the user id is all lower case. I am also using Jabberd2

Did you use any non-ascii, or Uppercase characters when you registered the
account?
pgm.
_______________________________________________

No, the accounts were created from a script and dumped into MySQL. The
accounts in MySQL are all lowercase ascii.

Sameer

[Peter Millard]

Post by Sameer Verma
No, the accounts were created from a script and dumped into MySQL. The
accounts in MySQL are all lowercase ascii.

Hmm.. thats odd.. I can connect to jabberd2 all day long w/ lowercase-ascii
usernames. All of the issues that I've seen are case/normalization related.

Perhaps post something to the jabberd2 mailing lists??

pgm.

[Sean Covel]

The user registered as John, so yes, a capitol "J" was used. No other
non-visible, non-ascii characters were used.

My backend database is Berkley DB, Jabber 2.

Post by Peter Millard

Post by Sameer Verma
I get the same error, although in my case, there is no confusion with
case. the user id is all lower case. I am also using Jabberd2

Did you use any non-ascii, or Uppercase characters when you registered the
account?
pgm.
_______________________________________________
Exodus-dev mailing list
https://jabberstudio.org/mailman/listinfo/exodus-dev

[Joe Hildebrand]

I've seen this temporary-authentication-failure with jabber2, also. If you stop the server, and restart it, the error will sometimes go away, which leads me to believe it's a server problem.

PGM: it might be cool to log the base64-decoded challenges and responses (not for PLAIN), so that we can diagnose this easier.
--
Joe Hildebrand
Denver, CO, USA

-----Original Message-----
Sent: Tuesday, June 08, 2004 11:52 AM
To: Exodus development
Subject: Re: [Exodus-dev] Exodus vs Jabber 2

Post by Peter Millard
[Stuff deleted..]

Post by Sean Covel
So, where does the fault lie? I don't know. Exodus and

Jabber 2 were

Post by Peter Millard

Post by Sean Covel
both happy with the initial registration. After disconnecting, it
appears that the account was created in lower-case, but Exodus
attempts to connect with an upper-case username.

Yeah, the problem is that Exodus is not "canonicalizing" the

usernames.

Post by Peter Millard
I'm currently working on a solution to make Exodus use the

GNU libidn

Post by Peter Millard
library to do all of this. The fix (obviously) is to have your user
enter his username as "john" instead of "John", and it should work
fine. Stay tuned for a fix for this in the next cpl of weeks.
pgm.
_______________________________________________
Exodus-dev mailing list
https://jabberstudio.org/mailman/listinfo/exodus-dev

I get the same error, although in my case, there is no confusion with
case. the user id is all lower case. I am also using Jabberd2
Here's the XML from the debug window.
Sameer
Looking up SRV: _xmpp-client._tcp.indigo.sfsu.edu
Got A: 130.212.14.69 5222
SENT: <stream:stream to="indigo.sfsu.edu" xmlns="jabber:client"
xmlns:stream="http://etherx.jabber.org/streams" xml:lang="en"
version="1.0" >
RECV: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='indigo.sfsu.edu' version='1.0'
id='f47x5qkwzi6yfw34vd18i02u06j59ppptxnzo7vn'>
RECV: <stream:features
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>DIGEST-MD5
features>
SENT: <auth mechanism="DIGEST-MD5"
xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
RECV: <challenge
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>cmVhbG09ImluZGlnby5zZ
nN1LmVkdSIsbm9uY2U9Ijg4ZTBiNTY4NzQxZmFhNzA0NDI2ZmE2NGZmM2NkNzI
wYjdkNjFkYmYiLHFvcD1hdXRoLGNoYXJzZXQ9dXRmLTgsYWxnb3JpdGhtPW1kN
S1zZXNz</challenge>
SENT: <response
xmlns="urn:ietf:params:xml:ns:xmpp-sasl">dXNlcm5hbWU9InN2ZXJtY
SIscmVhbG09ImluZGlnby5zZnN1LmVkdSIsbm9uY2U9Ijg4ZTBiNTY4NzQxZmF
hNzA0NDI2ZmE2NGZmM2NkNzIwYjdkNjFkYmYiLGNub25jZT0iODkxYmJiMjZkY
2E3NjBlZDU2M2FiMDg2OWI2ZTAzOTgiLG5jPTAwMDAwMDAxLHFvcD1hdXRoLGR
pZ2VzdC11cmk9InhtcHAvaW5kaWdvLnNmc3UuZWR1IixjaGFyc2V0PXV0Zi04L
HJlc3BvbnNlPTI5ZGM4ZjM0ZGJhYmM3ZTk0YzUzY2YyYjU1ZmExMzI5</response>
RECV: <failure
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><temporary-authentica
tion-failure/></failure>
_______________________________________________
Exodus-dev mailing list
https://jabberstudio.org/mailman/listinfo/exod> us-dev