2 jul 2007 kl. 14.42 skrev Philippe Sultan: > Hi everybody, > > I'd like to have your opinion on deprecating the use of non-SASL > authentication for res_jabber in Asterisk, as SASL is the way to go. > > Currently, res_jabber can be configured to authenticate as a client to > an XMPP server using SASL (the default) or non-SASL modes, through the > 'usesasl' option in jabber.conf. However, non-SASL authentication, > although still supported by most XMPP servers, is now deprecated (and > *not recommended* for clients) as stated here : > - http://www.xmpp.org/extensions/xep-0078.html (non-SASL > authentication) > - http://www.xmpp.org/extensions/xep-0073.html (basic IM protocol > suite) > > Forcing SASL authentication when connecting Asterisk as a client would > also simplify the code a little. If we agree on that, I'll modify the > SVN trunk accordingly, and simply add a warning message to the SVN 1.4 > branch without modifications. > > Note : authentication as a component would not be affected by these > changes. > > The important question here: Will it break communication with the clients that people use? We need to be compatible with existing clients more than future standards :-)
Jabber clients have very different levels of standard compatibility. /O _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
