Re: Use "samehost" by default in pg_hba.conf? - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: Use "samehost" by default in pg_hba.conf?
Date
Msg-id 87my4b34bl.fsf@hi-media-techno.com
Whole thread Raw
In response to Re: Use "samehost" by default in pg_hba.conf?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi,

Tom Lane <tgl@sss.pgh.pa.us> writes:
> Peter Eisentraut <peter_e@gmx.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.

As already said, it's one less step to have it working. This hba file is
hard to get at for a lot of newbies we see on IRC. +1 for default
configuration using samehost.

> 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.

Everywhere possible I have listen_addresses set to '127.0.0.1' a
pgbouncer instance for clients to connect to, on the non loopback
interface. That allows me to be sure that developers won't accidently
bypass pgbouncer. But as we're only talking about default setup, Magnus
argument weights much more (no DOS or portscan).

Regards,
-- 
dim


pgsql-hackers by date:

Previous
From: Richard Huxton
Date:
Subject: Re: navigation menu for documents
Next
From: Abhijit Menon-Sen
Date:
Subject: Re: Use "samehost" by default in pg_hba.conf?