Opened 8 years ago

Closed 8 years ago

#13117 closed defect (fixed)

google talk (xmpp) error: Server does not use any supported authentication method

Reported by: dfjueior Owned by: deryni
Milestone: Component: XMPP
Version: 2.7.5 Keywords: authentication connection xmpp
Cc: nedrigaylov.arz@…

Description

Hello! Every time when I trying to connect to Google Talk, appears this error: Server does not use any supported authentication method.

Pidgin from Tor Browser package.

My settings are:

domain: gmail.com;
resource: Home;
Connection security: require encryption OR use encryption if available;
Allow plaintext auth... - checked or not;
Connection port: 5222
Connection server: <blank> or talk.google.com
Proxy: NO PROXY or Use global proxy settings (TOR)

Build information is:

Pidgin 2.7.5 (libpurple 2.7.5)
da2f4b4aea9c7f3e28c13f28b1ec087d4f589f25

Build Information
  Plugins: Enabled
  SSL: SSL support is present.
  GTK+ Runtime: 2.16.6
  Glib Runtime: 2.20.5

  Library Support
    Cyrus SASL: Enabled
    Gadu-Gadu library (libgadu): Internal
    GtkSpell: Enabled
    GnuTLS: Disabled
    Network Security Services (NSS): Enabled
    Perl: Disabled
    Tcl: Disabled
    Tk: Disabled
    UTF-8 DNS (IDN): Disabled
    Voice and Video: Disabled

There is debug log:

(08:54:23) account: Connecting to account atc.arz@gmail.com/Home.
(08:54:23) connection: Connecting. gc = 027BBFA8
(08:54:23) dnssrv: querying SRV record for gmail.com: _xmpp-client._tcp.gmail.com
(08:54:23) dnssrv: found 5 SRV entries
(08:54:23) dnsquery: Performing DNS lookup for talk.l.google.com
(08:54:23) dnsquery: IP resolved for talk.l.google.com
(08:54:23) proxy: Attempting connection to 74.125.77.125
(08:54:23) proxy: Connecting to talk.l.google.com:5222 with no proxy
(08:54:23) proxy: Connection in progress
(08:54:23) proxy: Connecting to talk.l.google.com:5222.
(08:54:23) proxy: Connected to talk.l.google.com:5222.
(08:54:23) jabber: Sending (atc.arz@gmail.com/Home): <?xml version='1.0' ?>
(08:54:23) jabber: Sending (atc.arz@gmail.com/Home): <stream:stream to='gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(08:54:24) jabber: Recv (138): <stream:stream from="gmail.com" id="384823B6F36968E3" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
(08:54:24) jabber: Recv (210): <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"><required/></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features>
(08:54:24) jabber: Sending (atc.arz@gmail.com/Home): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(08:54:24) jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
(08:54:24) nss: subject=CN=gmail.com,O=Google Inc.,L=Mountain View,ST=California,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(08:54:24) nss: subject=OU=Equifax Secure Certificate Authority,O=Equifax,C=US issuer=OU=Equifax Secure Certificate Authority,O=Equifax,C=US
(08:54:24) certificate/x509/tls_cached: Starting verify for gmail.com
(08:54:24) certificate/x509/tls_cached: Checking for cached cert...
(08:54:24) certificate/x509/tls_cached: ...Found cached cert
(08:54:24) nss/x509: Loading certificate from C:\Documents and Settings\root\Рабочий стол\Tor Browser\PidginPortable\Data\settings\.purple\certificates\x509\tls_peers\gmail.com
(08:54:24) certificate/x509/tls_cached: Peer cert matched cached
(08:54:24) nss/x509: Exporting certificate to C:\Documents and Settings\root\Рабочий стол\Tor Browser\PidginPortable\Data\settings\.purple\certificates\x509\tls_peers\gmail.com
(08:54:24) util: Writing file C:\Documents and Settings\root\Рабочий стол\Tor Browser\PidginPortable\Data\settings\.purple\certificates\x509\tls_peers\gmail.com
(08:54:24) certificate: Successfully verified certificate for gmail.com
(08:54:24) jabber: Sending (ssl) (atc.arz@gmail.com/Home): <stream:stream to='gmail.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(08:54:24) jabber: Recv (ssl)(138): <stream:stream from="gmail.com" id="1838F100B6627BF0" version="1.0" xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client">
(08:54:24) jabber: Recv (ssl)(166): <stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism><mechanism>X-GOOGLE-TOKEN</mechanism></mechanisms></stream:features>
(08:54:24) sasl: Mechs found: PLAIN X-GOOGLE-TOKEN
(08:54:24) sasl: No worthy mechs found
(08:54:24) connection: Connection error on 027BBFA8 (reason: 3 description: Server does not use any supported authentication method)
(08:54:24) account: Disconnecting account atc.arz@gmail.com/Home (02564B10)
(08:54:24) connection: Disconnecting connection 027BBFA8
(08:54:24) jabber: Sending (ssl) (atc.arz@gmail.com/Home): </stream:stream>
(08:54:24) connection: Destroying connection 027BBFA8

Change History (2)

comment:1 follow-up: Changed 8 years ago by deryni

  • Status changed from new to pending
  • Version changed from 2.7.8 to 2.7.5

The first thing to do is to upgrade to pidgin 2.7.8.

If it still doesn't work at that point then you should check the contents of your pidgin installation directories sasl2/ directory and tell us what files you see there.

comment:2 in reply to: ↑ 1 Changed 8 years ago by dfjueior

  • Resolution set to fixed
  • Status changed from pending to closed

Replying to deryni: After upgrade to 2.7.8 the problem vas solved. Thank you.

The first thing to do is to upgrade to pidgin 2.7.8.

If it still doesn't work at that point then you should check the contents of your pidgin installation directories sasl2/ directory and tell us what files you see there.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!