[jdev] serious jabberd's 1.4.3 violation of XMPP-Core

[Matthias Wimmer]

Hi Justin!

Justin schrieb am 2004-10-16 19:48:25:
> >jabberd 1.4.3 (at least on my host) sends stanzas immidiatedly upon 
> >connect, not waiting for dialback auth completion.

jabberd 1.4.3 supports two s2s protocols:
- legacy jabberd 1.0 protocol not using dialback, just sending stanzas
  (the reason why we have/had the <key/> element in many iq protocols.
- dialback

In jabberd 1.4.3 the legacy protocol is by default enabled (<legacy/>
configuration element). If the legacy protocol is enabled jabberd 1.4.3
will detect XMPP s2s connections without support for dialback as legacy
connections and just send/accept.

In any case I suggest anyone removing the <legacy/> element from jabberd
1.4.3's configuration as this is not needed anymore.

In jabberd14 CVS (and therefore in the upcomming 1.4.4 release) the
legacy protocol is disabled by default and XMPP s2s connections are
detected and handled as such.

> jabberd 1.4.3 is distinctly NOT xmpp compliant. It was written long 
> before xmpp and there are no active devlopers.

That's not true. Jabberd14 is under development, and there will be a
first release candidate for jabberd 1.4.4 soon.

> If you want xmpp compliance then select a modern jabber server.

jabberd14's xmpp compliance has improved much and jabberd 1.4.4 will be
a big step towards XMPP compliance (but it won't be complete). Missing
are still: Privacy lists and SASL ... but I will implement them later as
well.


Tot kijk
    Matthias

-- 
Fon: +49-(0)70 0770 07770       http://web.amessage.info
HAM: DB1MW                      xmpp:mawis at amessage.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.jabber.org/jdev/attachments/20041017/730e4d09/attachment-0002.pgp>