Решение ошибки аутентификации при подключении xmpp в pidgine?

Question

[Дмитрий]

Есть проблема с не подключением jabber'a(xmpp) в клиенте pidgin'a к серверу c характерной ошибкой:
"Server does not use any supported authentication method"
Решение было найдено в том, что не хватает строки в hosts вида:
127.0.1.1 $name_host
Но. При подключении, же клиента gajima, подключение производится без плясок вокруг hosts.
Каково значение 127.0.1.1 и как сей адрес связан с Pidgin'om?
Прилагаю так же содержимое hosts во время эксперемента на своей машине и дебаг-лог pidgin'a.

127.0.0.1	localhost
#127.0.1.1	 username

Pidgin Debug Log : Thu 09 Jan 2014 06:40:52 PM MSK
(18:20:38) account: Connecting to account [e-mail]/.
(18:20:38) connection: Connecting. gc = 0x7f952e9b2770
(18:20:38) dnssrv: querying SRV record for servername.com: _xmpp-client._tcp.servername.com
(18:20:38) dnssrv: res_query returned an error
(18:20:38) dnsquery: Performing DNS lookup for servername.com
(18:20:38) dns: Wait for DNS child 26693 failed: No child processes
(18:20:38) dns: Created new DNS child 26705, there are now 1 children.
(18:20:38) dns: Successfully sent DNS request to child 26705
(18:20:38) dns: Got response for 'servername.com'
(18:20:38) dnsquery: IP resolved for servername.com
(18:20:38) proxy: Attempting connection to 213.180.204.3
(18:20:38) proxy: Connecting to servername.com:5222 with no proxy
(18:20:38) proxy: Connection in progress
(18:20:38) proxy: Connecting to servername.com:5222.
(18:20:38) proxy: Connected to servername.com:5222.
(18:20:38) jabber: Sending ([e-mail]): <?xml version='1.0' ?>
(18:20:38) jabber: Sending ([e-mail]): <stream:stream to='servername.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(18:20:39) jabber: Recv (191): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="servername.com" id="3df4f547" xml:lang="en" version="1.0">
(18:20:39) jabber: Recv (436): <stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>JIVE-SHAREDSECRET</mechanism><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features>
(18:20:39) jabber: Sending ([e-mail]): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
(18:20:39) jabber: Recv (50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
(18:20:39) nss: subject=CN=d3015.serverclub.com issuer=CN=d3015.serverclub.com
(18:20:39) certificate/x509/tls_cached: Starting verify for servername.com
(18:20:39) certificate/x509/tls_cached: Checking for cached cert...
(18:20:39) certificate/x509/tls_cached: ...Found cached cert
(18:20:39) nss/x509: Loading certificate from /home/username/.purple/certificates/x509/tls_peers/servername.com
(18:20:39) certificate/x509/tls_cached: Peer cert matched cached
(18:20:39) nss/x509: Exporting certificate to /home/username/.purple/certificates/x509/tls_peers/servername.com
(18:20:39) util: Writing file /home/username/.purple/certificates/x509/tls_peers/servername.com
(18:20:39) certificate: Successfully verified certificate for servername.com
(18:20:39) jabber: Sending (ssl) ([e-mail]): <stream:stream to='servername.com' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
(18:20:39) jabber: Recv (ssl)(566): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="servername.com" id="3df4f547" xml:lang="en" version="1.0"><stream:features><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>DIGEST-MD5</mechanism><mechanism>JIVE-SHAREDSECRET</mechanism><mechanism>PLAIN</mechanism><mechanism>CRAM-MD5</mechanism></mechanisms><compression xmlns="http://jabber.org/features/compress"><method>zlib</method></compression><auth xmlns="http://jabber.org/features/iq-auth"/></stream:features>
(18:20:39) sasl: sasl_state is -1, failing the mech and trying again
(18:20:39) connection: Connection error on 0x7f952e9b2770 (reason: 3 description: Server does not use any supported authentication method)
(18:20:39) account: Disconnecting account [e-mail]/ (0x7f952dd3f6d0)
(18:20:39) connection: Disconnecting connection 0x7f952e9b2770
(18:20:39) jabber: Sending (ssl) ([e-mail]): </stream:stream>
(18:20:39) connection: Destroying connection 0x7f952e9b2770
(18:20:39) util: Writing file prefs.xml to directory /home/username/.purple
(18:20:39) util: Writing file /home/username/.purple/prefs.xml
(18:20:44) util: Writing file accounts.xml to directory /home/username/.purple
(18:20:44) util: Writing file /home/username/.purple/accounts.xml
(18:40:52) prefs: /pidgin/filelocations/last_save_folder changed, scheduling save.

Comments

[Ilya Evseev]

Точно 127.0.1.1?
Не 127.0.0.1?

[Дмитрий]

Точно

root@host_name:/var/log# cat /etc/hosts
127.0.0.1	localhost
127.0.1.1	host_name

[Дмитрий]

Впрочем, если изменить 127.0.1.1 на 127.0.0.1. Pidgin работает. а вот если закоментировать кчертям, то нет. Также адиум не захотел сегодня как обычно заводиться, пришлось подсовывать ему вместо его хостнейма в настройках - локалхост.

Answer 1

[pr0l]

127.0.0.1 внутренняя петля для виртуального интерфейса, некоторые программы общаются по нему обращаясь к localhost. раньше уже задавали вопрос про локалхост и давали правильный ответ на него

Comments

[Дмитрий]

Наверное, вы правы.

Answer 2

[maxaon]

Возможно виноват "reverse dns lookup" при ssl подключении