-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jabber:iq:auth not working - fix #100
Comments
I don't mind adding in jabber:iq:auth as long as it's advertised as a a feature in stream:features and can be detected. Note that it's not part of XMPP 1.0 at all. |
Oh I've misunderstood your patch. This causes it to keep looping waiting for stream:features? |
Indeed, its looking for the mechanism tag, and its ostensible (and in my testing with the SASL module disabled :P ) , that the tag will not be offered. In that case, its an infinite loop. Of course as you say, its not part of the spec, and its also deprecated, but for completeness, that was it. |
Bugfix. item-not-found error caused by long term request. fixes metajack#25
When writing my own XMPP service using DJabbberd , I found i could log in using BOSH and Pidgin, but not strophejs. jabber:iq:auth is deprecated, but when testing, I had SASL disabled.
At what point a server advertises the iq-auth stream feature is up to the implementation or deployment, and in my case, this is as per Example 9 Xep-0078. The code looks for the mechanism tag, and if not found, loops infinitely in the case this is never offered.
My fix may not be relevant or suitable, but here it is for completeness or if anyone else is curious
From 2958 on
The text was updated successfully, but these errors were encountered: