I started experiencing this bug after upgrading my Jabber server (running ejabberd) to Debian wheezy. Someone created an associated bug report which can be found at <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654853>.
While this probably doesn't address the underlying bug (possibly in ejabberd) maybe Ubuntu can also ship the appropriate libraries for SCRAM-SHA1 support in SASL and fix user experience in this way.
I started experiencing this bug after upgrading my Jabber server (running ejabberd) to Debian wheezy. Someone created an associated bug report which can be found at <http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 654853>.
I also started to experience this bug on a different machine (previously not experiencing it there, even after the server upgrade) after upgrading it to Fedora 19. The Fedora people have fixed this bug (bug report at <https:/ /bugzilla. redhat. com/show_ bug.cgi? id=979052>) by explicitly adding a dependency on the cyrus-sasl-scram library (see <http:// pkgs.fedoraproj ect.org/ cgit/pidgin. git/commit/ ?id=a3d3522983e f0633e960dcaefa 1973c8667eb2ea>). I can confirm that this fix works for me: the pidgin SASL module will prefer SCRAM-SHA1 over DIGEST-MD5 and pidgin authenticates successfully.
While this probably doesn't address the underlying bug (possibly in ejabberd) maybe Ubuntu can also ship the appropriate libraries for SCRAM-SHA1 support in SASL and fix user experience in this way.