Bug #7453
Pidgin cannot find out the correct XMPP server to connect to, without SRV DNS lookups
0%
Description
Google recently broke XMPP for many accounts. Without gtalk support in Pidgin, I am unable to connect to my Google account. Please (re-)add Pidgin support for gtalk.
Subtasks
Related issues
| Related to Tails - Bug #8573: Hopefully replace Pidgin some day | In Progress | 2015-01-07 | |
| Blocked by Tails - Feature #6070: Support arbitrary DNS queries | Confirmed |
History
#1 Updated by intrigeri 2014-06-23 11:58:45
Hi Runa,
> Please (re-)add Pidgin support for gtalk.
It might we worth testing if we have disabled it at build time:
sudo apt-get update && sudo apt-get --reinstall install libpurple0Then, restart Pidgin, and try to add a gtalk account.
If this is not enough, do you know what Debian package we need to install to support gtalk in Pidgin?
Cheers!
#2 Updated by runa 2014-06-23 16:33:14
Reinstalling libpurple0 gives me a version of Pidgin with more account options, but I am still unable to connect to my Google account. Earlier today, DrWhax pasted the following line in #tails: “tails repo —> ./config/chroot_local-hooks/09-remove_unsupported_pidgin_libs”, perhaps related to this?
#3 Updated by intrigeri 2014-06-24 08:10:51
> Reinstalling libpurple0 gives me a version of Pidgin with more account options, but
> I am still unable to connect to my Google account.
OK, so someone needs to find out what Pidgin plugin/extension/whatever
supports gtalk, if any.
> Earlier today, DrWhax pasted the following line in #tails […]
Yeah, that’s the script that removes support for most protocols,
but reinstalling libpurple0 reverts it.
#4 Updated by runa 2014-06-29 19:57:42
Without reinstalling libpurple0, here’s how connect to a Google Talk account: choose either Google Talk or XMPP as the protocol and enter your username and password. Click the advanced tab and enter “talk.google.com” in the “Connect server” field. Hit save and enable the account.
Would it be possible to set the server name as a default value for Google Talk accounts?
#5 Updated by sajolida 2014-07-03 21:34:56
- Tracker changed from Feature to Bug
- Subject changed from Add gtalk support in Pidgin to GTalk server in Pidgin is not set to talk.google.com by default
- Status changed from New to Confirmed
#6 Updated by intrigeri 2014-07-04 07:25:02
Is there a way, in XMPP-speak, to have the “login domain => server to connect to” mapping automatically guessed?
I suspect this info is available in the DNS (e.g. SRV or TXT), and then this would be solved if we had Pidgin use a resolver that supported more than A records.
#7 Updated by intrigeri 2014-08-12 13:55:44
- Category set to 213
#8 Updated by intrigeri 2015-01-07 15:04:15
- Subject changed from GTalk server in Pidgin is not set to talk.google.com by default to Pidgin cannot find out the correct XMPP server to connect to, without SRV DNS lookups
Indeed, the preferred way to get the connect server is a SRV DNS lookup. E.g.:
$ dig @127.0.0.2 _xmpp-client._tcp.google.com srv
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @127.0.0.2 _xmpp-client._tcp.google.com srv
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8302
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;_xmpp-client._tcp.google.com. IN SRV
;; ANSWER SECTION:
_xmpp-client._tcp.google.com. 900 IN SRV 5 0 5222 xmpp.l.google.com.
_xmpp-client._tcp.google.com. 900 IN SRV 20 0 5222 alt4.xmpp.l.google.com.
_xmpp-client._tcp.google.com. 900 IN SRV 20 0 5222 alt2.xmpp.l.google.com.
_xmpp-client._tcp.google.com. 900 IN SRV 20 0 5222 alt1.xmpp.l.google.com.
_xmpp-client._tcp.google.com. 900 IN SRV 20 0 5222 alt3.xmpp.l.google.comSo indeed, to get this automatically working, we’ll need to point Pidgin at a DNS resolver that supports SRV requests.
#9 Updated by intrigeri 2015-01-07 15:04:56
- blocked by Feature #6070: Support arbitrary DNS queries added
#10 Updated by Anonymous 2018-08-18 13:44:05
- related to Bug #8573: Hopefully replace Pidgin some day added