[jdev] ejabberd & feature advertisement

[Stephan Maka]

Justin Karneges wrote:
> Right, TLS is not required, doesn't matter if you are using SASL or legacy 
> auth.

But SASL is required if the client does TLS?

I've put in TLS support for XMPP4R and tested it against jabberd1 and
jabberd2. I've then heard complaints from ejabberd users that they can't
authenticate. This urged me to implement SASL and provide Non-SASL auth
for fallback only.

I've been told that this was discussed a while ago, but I can't find the
thread...

Stephan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20060215/95da0285/attachment-0002.pgp>