From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Use "samehost" by default in pg_hba.conf? |
Date: | 2009-10-01 05:24:59 |
Message-ID: | 3EFF89A0-F705-4A97-88A1-FB5044A36736@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1 okt 2009, at 06.53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> On Wed, 2009-09-30 at 22:08 -0400, Tom Lane wrote:
>>> (Note that you would still need a non-default setting of
>>> listen_addresses for "-h machine_name" to actually work.)
>
>> Which makes this proposal kind of uninteresting.
>
> Although come to think of it ... is there any reason besides sheer
> conservatism to not make the default listen_addresses value '*'?
> It won't result in letting in any outside connections unless you
> also add pg_hba.conf entries.
Absolutely. One less opportunity to DOS the server - it's certainly
cheaper to deal with connection floods by never even answering the
socket. Also, showing up in portscans for example.
Now, that trust authentication is a different issue ;)
/Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Casanova | 2009-10-01 05:36:13 | Re: Use "samehost" by default in pg_hba.conf? |
Previous Message | Tom Lane | 2009-10-01 04:53:08 | Re: Use "samehost" by default in pg_hba.conf? |