id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,irc_client,os,os_version 866,Workaround broken SASL implementation(s),brmiller@…,wilmer,"I am using Bitlbee against a broken OpenFire server which fails in the SASL Digest-MD5 negotiation. I debugged this a month ago or so, and came up with the attached patch. The server offers DIGEST-MD5, PLAIN, ANONYMOUS, and CRAM-MD5 authentication mechanisms: 08:44 RX: DIGEST-MD5PLAINANONYMOUSCRAM-MD5zlib The [Bitlbee] client chooses DIGEST-MD5 08:44 TX: The server sends the auth challenge: 08:44 RX: --bunch of base64 removed-- The client sends the resposne. 08:44 TX: --some more base64 data-- The server says this is not authorized. 08:44 RX: And then my negotiation is dead in the water. I noted that other clients (the purlpley one, for example) do the same thing but then retry PLAIN after DIGEST-MD5 fails. To get around this (on a production server I cannot upgrade), I created the following ""ignore_broken_sasl_digest_md5"" patch/hack. I don't know if this is useful for anyway, bad style, never-gonna-be-incorporated, etc. or not, but I wanted to ""give back"" as it were. I also note that this //feels// a little like overlap with #863, but that patch did not solve my particular problem. ",enhancement,closed,normal,,Jabber,3.0.3,fixed,SASL patch,,Client-independent,Linux,