Re: Use "samehost" by default in pg_hba.conf?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-03 23:11:32
Message-ID: 200910032311.n93NBWR08653@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander wrote:
> 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 ;)

I seems the purpose of listen_addresses was not clear to everyone, so I
have added the attached documentation sentence to specify its purpose.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 1.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2009-10-03 23:14:55 Re: Lock Wait Statistics (next commitfest)
Previous Message Tom Lane 2009-10-03 17:40:50 Re: Getting the red out (of the buildfarm)