[jdev] Bug in jabberd2 (2.1.13) on win32

[Dan Hulme]

I'm using plain auth (with and without ntlogon).  I've tested with
Spark 2.5.8, Coccinella .96.4.1, and PSI 0.11.  All have the same
problem, they hang or return an error when doing SASL.  I'd like to
repeat for Thomas' sake that all three worked on the previous build
which used Cyrus SASL.

You say you are using TLS...have you tried SASL?

Here is a Coccinella log of it failing:
----------------------------------
<?xml version='1.0' encoding='UTF-8'?><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
xml:lang='en' to='chatter.example.com' version='1.0'><?xml
version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='chatter.example.com' version='1.0'
id='8pagx0e4s4hanl8fnsr3ou05bnhrvapuhgd0uu50'><stream:features
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism></mechanisms><auth
xmlns='http://jabber.org/features/iq-auth'/></stream:features><auth
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
mechanism='PLAIN'>ZGFuaFBjaGE0LmllbWSnLmNvcQBKYW5oAE9CRVNFWA==</auth><success
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
to='chatter.example.com' xml:lang='en'  version='1.0'><?xml
version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='chatter.example.com' version='1.0'
id='kncfraylp37okkurdzou43ns0gouuj44g1b5v52i'>
<stream:features xmlns:stream='http://etherx.jabber.org/streams'><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'><required/></bind><unbind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'/><session
xmlns='urn:ietf:params:xml:ns:xmpp-session'/></stream:features><iq
type='set' id='1038'><bind
xmlns='urn:ietf:params:xml:ns:xmpp-bind'><resource>Coccinella at comp1</resource></bind></iq><stream:error
xmlns:stream='http://etherx.jabber.org/streams'><internal-server-error
xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
xmlns='urn:ietf:params:xml:ns:xmpp-streams'>internal server
error</text></stream:error></stream:stream></stream:stream>
----------------------------------

Here is a PSI log of it failing:
----------------------------------
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams"
version="1.0" xmlns="jabber:client" to="chatter.example.com"
xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" >
<?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='chatter.example.com' version='1.0'
id='x9f8vk6mqnietkkd0u1qn2yy3sacgegfn0sp5jd3'>
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>PLAIN</mechanism>
</mechanisms>
<auth xmlns="http://jabber.org/features/iq-auth"/>
<register xmlns="http://jabber.org/features/iq-register"/>
</stream:features>
<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN"
>AHRvanllAbZhdGchdGZhdA==</auth>
<success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
<?xml version="1.0"?>
<stream:stream xmlns:stream="http://etherx.jabber.org/streams"
version="1.0" xmlns="jabber:client" to="chatter.example.com"
xml:lang="en" xmlns:xml="http://www.w3.org/XML/1998/namespace" >
<?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='chatter.example.com' version='1.0'
id='oweh5z1u573c5x4k9hq73fpittrpvze7en1qwncw'>
<stream:features>
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind">
<required/>
</bind>
<unbind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/>
<session xmlns="urn:ietf:params:xml:ns:xmpp-session"/>
</stream:features>
<iq type="set" id="bind_1" >
<bind xmlns="urn:ietf:params:xml:ns:xmpp-bind">
<resource>client-resource</resource>
</bind>
</iq>
----------------------------------
(When PSI fails, it causes a popup that says "details: disconnected")

-Dan

On Jan 31, 2008 5:25 AM, Tomasz Sterna <tomek at xiaoka.com> wrote:
> On Cz, 2008-01-31 at 12:00 +0100, Adam Strzelecki wrote:
> > Then it must be still something wrong with GSASL, I'll try to test it.
>
> Or with the client.
> Most older ones have broken SASL implementations.
>
> --
>
>   /\_./o__ Tomasz Sterna
>  (/^/(_^^' http://www.xiaoka.com/
> ._.(_.)_   im:smoku at xiaoka.com
>
>