Stall while "Connecting" in Psi-plus and Kopete with jabberd2

[stbuehler]

Hi,

jabberd2 only sends one "challenge" for sasl auth (it seems other servers send a second challenge which is answered with an empty response by psi-plus/kopete).
Neither psi-plus nor kopete finish the connect after they get the success event from the server, both claim in the xml console they sent more data, but this never hits the network (checked with wireshark more than once).
(ekg2 works as it actually sends the data.)

[...]

server -> client
    <stream:features>
    <mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
    <mechanism>PLAIN</mechanism>
    <mechanism>DIGEST-MD5</mechanism>
    </mechanisms>
    <auth xmlns="http://jabber.org/features/iq-auth"/>
    <register xmlns="http://jabber.org/features/iq-register"/>
    </stream:features>

client -> server
    <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="DIGEST-MD5"/>

server -> client
    <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">[...]</challenge>

client -> server
    <response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">[...]</response>

server -> client
    <success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>

client -> server (only shown in console, never reaches the network)
    <?xml version="1.0"?>

    <stream:stream xmlns:stream="http://etherx.jabber.org/streams" version="1.0" xmlns="jabber:client" to="[...]">

[stbuehler]

8 months and no response... shame on you.

[wadealer]

Is this still actual?

[Ri0n]

According to Jebberd2 mail list that was a problem with some encryption library which is most likely fixed already since I see other reports with working Psi.