[JDEV] Re: Protocol Change

Peter Saint-Andre stpeter at jabber.org
Mon Mar 18 17:09:26 CST 2002

However, note that the use of the <key> element is probably deprecated at
this point -- it was used in the 1.0 server as a way to help prevent
spoofing, but that problem was solved more elegantly and generally with
server dialback.


Peter Saint-Andre
email+jabber: stpeter at jabber.org
weblog: http://www.saint-andre.com/blog/

On Mon, 18 Mar 2002, Stephen Pendleton wrote:

> That may be exactly what is happening (the key tag is malformed), because a
> key was not sent from the server - so the client is sending a malformed one
> back. I should of figured that one out! :-) Apparently on earlier versions
> of jabberd the key was always sent and the client expected it. Now
> apparently it is optional.
> Thank you!
> On Mon, Mar 18, 2002 at 12:02:07PM -0500, Stephen Pendleton wrote:
> > It seems that there has been a slight protocol change on the jabber.org
> > development server. In particular, when registering on a gateway it used
> to
> > be required that a "key" was exchanged between the client and the server.
> > Now it seems that the requirement has been dropped and clients that send
> the
> > key in the XML stream get disconnected. Unfortunately this requires that
> all
> Gosh, I'd say that a disconnection is a rather heavy handed approach
> from the server, if that's what is really happening. Could it be
> perhaps a malformed key tag (rather than just the presence of the tag)
> that's causing an XML error?
> Can you post some of the debug XML here at all?
> cheers
> dj
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

More information about the JDev mailing list