Ubuntu
pidgin package

Server does not use any supported authentication method

Bug #975478 reported by Miron Cuperman
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Here is the relevant section of the debug log:

(13:30:34) jabber: Recv (ssl)(438): <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='24258d04-fa4b-4383-b717-11ce6bacaa61' from='hyper.to' version='1.0' xml:lang='en'><stream:features><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms><auth xmlns='http://jabber.org/features/iq-auth'/></stream:features>
(13:30:34) sasl: sasl_state is -1, failing the mech and trying again
(13:30:34) connection: Connection error on 0x7f420cb73110 (reason: 3 description: Server does not use any supported authentication method)

The issue is somewhat intermittent, but when it happens it persists for awhile.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: pidgin 1:2.10.2-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Fri Apr 6 13:17:48 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: pidgin
UpgradeStatus: Upgraded to precise on 2012-03-09 (28 days ago)

Revision history for this message
Miron Cuperman (devrandom) wrote :
Revision history for this message
Miron Cuperman (devrandom) wrote :

gajim works fine (latest source), although the server XML is slightly different (ordering):

<?xml version='1.0'?>
<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='2f2c7c1d-0444-44f8-976b-49d9d46c1420' from='hyper.to' version='1.0' xml:lang='en'>
<stream:features>
<auth xmlns='http://jabber.org/features/iq-auth'/>
<mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'>
<mechanism>PLAIN</mechanism>
<mechanism>SCRAM-SHA-1</mechanism>
<mechanism>DIGEST-MD5</mechanism>
</mechanisms>
</stream:features>

Revision history for this message
Miron Cuperman (devrandom) wrote :

The server sometimes changes the order of auth and mechanisms tags - doesn't make a different to pidgin's issue.

Revision history for this message
Miron Cuperman (devrandom) wrote :

On ubuntu 11.10, pidgin version 2.10.0-0ubuntu2 it works:

(23:07:05) jabber: Recv (ssl)(438): <?xml version='1.0'?><stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' id='1c416073-378a-445b-a02c-37054b4ab9e7' from='hyper.to' version='1.0' xml:lang='en'><stream:features><auth xmlns='http://jabber.org/features/iq-auth'/><mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms></stream:features>
(23:07:05) sasl: Mechs found: PLAIN SCRAM-SHA-1 DIGEST-MD5
(23:07:05) jabber: Sending (ssl) (<email address hidden>/Desk): <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl' mechanism='PLAIN' xmlns:ga='http://www.google.com/talk/protocol/auth' ga:client-uses-full-bind-result='true'>password removed</auth>
(23:07:05) jabber: Recv (ssl)(60): <success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'></success>

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pidgin (Ubuntu):
status: New → Confirmed
Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

FWIW, it seems that Cyrus SASL used by pidgin's libpurple is simply failing with error -1 SASL_FAIL, which is a generic failure.
Starting pidgin in debug mode (pidgin -d) doesn't reveal anything.

This thread on the pidgin support list caught my attention: http://pidgin.10357.n7.nabble.com/XMPP-Server-does-not-use-any-supported-authentication-method-td78689.html

One of the things that are suggested it to check /etc/hostname and /etc/hosts, and to make sure that the hostname is actually present in /etc/hosts on the 127.0.0.1 line. I checked and indeed it was not the case, for some obscure reason. Adding it certainly fixed the issue in pidgin.

If that does not work for you, the thread also gives pointers to start debugging libsasl and find out where it's failing exactly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.