[Standards] [Fwd: Re: jingle client authentication error in jabber server]

Peter Saint-Andre stpeter at jabber.org
Tue Jan 30 22:34:03 UTC 2007

Do we need more SASL error conditions?

-------- Original Message --------
Subject: Re: jingle client authentication error in jabber server
Date: Tue, 30 Jan 2007 14:20:16 -0800
From: stpeter <stpeter at gmail.com>
Reply-To: google-talk-open at googlegroups.com
To: google-talk-open <google-talk-open at googlegroups.com>
References: <1170184687.810379.278270 at s48g2000cws.googlegroups.com> 
<1170185653.150626.273240 at v33g2000cwv.googlegroups.com> 
<87ac00i4sm.fsf at freemail.hu>

On Jan 30, 2:27 pm, Magnus Henoch <m... at freemail.hu> wrote:
> "stpeter" <stpe... at gmail.com> writes:
> > That's odd, there is no <bad-auth/> error in XMPP's use of SASL:
> A bug in ejabberd, it seems.  I just reported it:http://www.jabber.ru/bugzilla/show_bug.cgi?id=315


> However, ejabberd sometimes returns <bad-protocol/>, when the client
> sends invalid SASL data.  That's also not in the RFC.  What should be
> used instead?

The only defined errors are here:




If we need more error conditions, we can define them in the next
version of the spec.


You received this message because you are subscribed to the Google 
Groups "google-talk-open" group.
To post to this group, send email to google-talk-open at googlegroups.com
To unsubscribe from this group, send email to 
google-talk-open-unsubscribe at googlegroups.com
For more options, visit this group at 

Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070130/f0f74309/attachment.bin>

More information about the Standards mailing list