[Standards-JIG] stream:error for dialback with no SASL support

JD Conley jconley at winfessor.com
Sat Jul 24 17:53:31 UTC 2004

I assume you mean you're implementing STARTTLS for S2S with SASL
EXTERNAL, not implementing STARTTLS in dialback.

Right now the SoapBox Server sends an invalid-namespace stream exception
in the case where an incoming stream is not one of the configured types,
but I think I like not-authorized better.

The biggest pain with implementing SASL for S2S was the fallback
mechanism.  If your local system supports SASL, for external connections
you have to try SASL first and then drop back to dialback if the remote
system doesn't support SASL.  The problem is the different flavors of
servers will reject you in various ways.

Let me know if you want a server to test with that already has
STARTTLS/SASL EXTERNAL implemented for S2S or if you want to chat about
the implementation.

Email/IM: jconley at winfessor.com

> -----Original Message-----
> From: Matthias Wimmer [mailto:m at tthias.net]
> Sent: Saturday, July 24, 2004 10:37 AM
> To: standards-jig at jabber.org
> Subject: [Standards-JIG] stream:error for dialback with no SASL
> Hi!
> I am implementing STARTTLS for dialback in jabberd14 at present and in
> that context I thought about what is the correct error message, if we
> only support Dialback but no SASL and the other party only supports
> but no Dialback? The best seems to be to generate a <not-authorized/>
> error, but I am not sure. What do the others think about that?
> Tot kijk
>     Matthias
> --
> Fon: +49-(0)70 0770 07770       http://web.amessage.info
> HAM: DB1MW                      xmpp:mawis at amessage.info

More information about the Standards mailing list