search

licq-im / licq

An instant messaging client for UNIX
http://www.licq.org/
16 stars 4 forks source link

Connection to jabber.org needs to be changed #21

Closed root42 closed 12 years ago

root42 commented 12 years ago

Jabber.org recently had some DoS attacks (http://www.jabber.org/notices.html), which led them to refuse connections to jabber.org:5222. Instead, a SRV lookup is supposed to be used, as can be done with gloox::Client (http://camaya.net/api/gloox/classgloox_1_1Client.html#a1).

A SRV lookup on the command line yields e.g. this:

$ dig -t srv _xmpp-client._tcp.jabber.org

; <<>> DiG 9.8.1-P1 <<>> -t srv _xmpp-client._tcp.jabber.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16168
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 5, ADDITIONAL: 9

;; QUESTION SECTION:
;_xmpp-client._tcp.jabber.org.  IN  SRV

;; ANSWER SECTION:
_xmpp-client._tcp.jabber.org. 900 IN    SRV 30 30 5222 hermes6.jabber.org.
_xmpp-client._tcp.jabber.org. 900 IN    SRV 31 31 5222 fallback.jabber.org.
_xmpp-client._tcp.jabber.org. 900 IN    SRV 30 30 5222 hermes.jabber.org.

;; AUTHORITY SECTION:
jabber.org.     337 IN  NS  ns2.jeremie.com.
jabber.org.     337 IN  NS  ns1.jabber.org.
jabber.org.     337 IN  NS  ns1.jeremie.com.
jabber.org.     337 IN  NS  ns2.jabber.org.
jabber.org.     337 IN  NS  ns3.jabber.org.

;; ADDITIONAL SECTION:
hermes.jabber.org.  416 IN  A   208.68.163.220
hermes6.jabber.org. 411 IN  A   208.68.163.220
hermes6.jabber.org. 143 IN  AAAA    2605:da00:5222:5269::2:1
fallback.jabber.org.    624 IN  A   208.68.163.218
ns1.jabber.org.     9335    IN  A   208.68.163.214
ns1.jeremie.com.    335 IN  A   208.68.163.244
ns2.jabber.org.     9335    IN  A   91.121.109.155
ns2.jeremie.com.    335 IN  A   208.68.163.251
ns3.jabber.org.     9335    IN  A   213.186.33.199

;; Query time: 43 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sat Aug 18 16:09:09 2012
;; MSG SIZE  rcvd: 417

So as a workaround one can use the server fallback.jabber.org to connect with Licq to jabber.

flynd commented 12 years ago

Clearing the server name and setting port to zero in Licq will let gloox look it up by itself so it already works like it should. However, I'll give some thought on how to make this apparent from the GUI.

flynd commented 12 years ago

0f4691856a82d7efc7f17f93e1beb0d18252c1fc updates GUI to use blank server and port as default to let protocols determine defaults their own way.