Re: [jabberd2] jabberd-2.1.24 release
Dnia 2008-04-25, pią o godzinie 07:27 +0200, Tomasz Sterna pisze: > > Seeing as there is the outstanding GSASL bug, does this upgrade fix any of > > that? > This is a GSASL bug, so you need to wait for GSASL fix. > I don't see anything that could be done on jabberd side. :-( Well... I see one thing. You may disable digest-md5 mechanism in ssl-mechanisms section of c2s.xml like in the distributed etc/c2s.xml.dist. This way you will not provide problematic DIGEST-MD5 mechanism to clients over encrypted connection - most of the clients support and enable TLS. -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED] -- To unsubscribe send a mail to [EMAIL PROTECTED]
Re: [jabberd2] jabberd-2.1.24 release
Dnia 2008-04-24, czw o godzinie 15:27 -0700, Scott Baker pisze: > Seeing as there is the outstanding GSASL bug, does this upgrade fix any of > that? This is a GSASL bug, so you need to wait for GSASL fix. I don't see anything that could be done on jabberd side. :-( > It's my understanding that GSASL bug is a show stopper as 80% of > clients won't authenticate against jabberd while that bug is still present. I don't really think Pidgin is 80% of clients. Please refer to http://jabberd2.xiaoka.com/wiki/ClientCompatibility for a list of working clients. -- /\_./o__ Tomasz Sterna (/^/(_^^' http://www.xiaoka.com/ ._.(_.)_ im:[EMAIL PROTECTED]
Re: [jabberd2] jabberd-2.1.24 release
http://jabberd2.xiaoka.com/search?q=gsasl you can find the status of all the filed jabberd2 bugs on the bug tracker, and Tomasz posted a link to the Changelog as well, which usually lists all the major (and even many minor) code changes since the last version. you might be able to find the answer to your question there, and if the issue isn't resolved, that's definitely somewhere to find out and discuss why. cheers, michael -- To unsubscribe send a mail to [EMAIL PROTECTED]
Re: [jabberd2] jabberd-2.1.24 release
Tomasz Sterna wrote: It's finally time for next jabberd 2.1 series release. Get 2.1.24 release as usual at: http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.1.24.tar.gz http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.1.24.tar.bz2 and read: http://svn.xiaoka.com/jabberd2/trunk/UPGRADE Seeing as there is the outstanding GSASL bug, does this upgrade fix any of that? It's my understanding that GSASL bug is a show stopper as 80% of clients won't authenticate against jabberd while that bug is still present. I really want to upgrade my server, but I can't until that bug is fixed! -- Scott Baker - Canby Telcom RHCE - System Administrator - 503.266.8253 -- To unsubscribe send a mail to [EMAIL PROTECTED]