[Juser] Changes due to Denial of Service Attacks

[Peter Saint-Andre]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/4/12 11:05 AM, Kevin Smith wrote:
> On Tue, Sep 4, 2012 at 12:43 AM, Rob Newton <robn at mirrabooka.com>
> wrote:
>> Since the recent denial of service attacks, I understand that
>> some measures were taken on the server side to prevent the
>> attacks.  In particular, this notice:
>> 
>> Below is the debug log.  Can anyone see what the problem might
>> be?  Would it be that Pidgin doesn't handle DNS SRV records
>> correctly?
> 
> It's not that Pidgin doesn't support SRV (I believe it does) but
> that either it's configured not to use it, or the DNS servers it's
> using are broken.
> 
>> (09:33:21) proxy: Attempting connection to 208.68.163.220 
>> (09:33:21) proxy: Connecting to jabber.org:5222 with no proxy
> 
> This is, as you surmised, not trying SRV.
> 
> So either somewhere in the account config in Pidgin you'll find
> that you've got it set with a manual connect host of jabber.org,
> port 5222, or running
> 
> dig -t srv _xmpp-client._tcp.jabber.org
> 
> won't give you the three results it should.

The Pidgin developers assure me that their code supports proper SRV
lookups, and they have tested against jabber.org successfully of late.
So I think the issue here is most likely misconfiguration on the
client side (hardcoding "jabber.org" as the host to connect to).

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBGNesACgkQNL8k5A2w/vzEUACfb0d/xaa4SIn04Ae2kqEJUN4t
BDoAn0pTzocRiMZkFTfTxiONTwFZf0bO
=QCiw
-----END PGP SIGNATURE-----