Skip site navigation (1) Skip section navigation (2)

host name support in pg_hba.conf

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: host name support in pg_hba.conf
Date: 2010-08-09 18:47:56
Message-ID: 1281379676.23513.34.camel@vanquo.pezone.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Here is a patch for host name support in pg_hba.conf.  I have reviewed
various past threads about this, and there appeared to have been a 50/50
split of for and against reverse lookup.  I went with the reverse
lookup, because

0) I like it.

1) It is more secure.

2) It allows extending it to wildcards in the future.

3) Apache (Allow from) does it that way.

To clarify how it works:  The client's IP address (known from the
kernel) is reverse looked up, which results in a host name.  That host
name is compared with the line in pg_hba.conf.  If it matches, a forward
lookup is performed on the host name to check if any of the resulting IP
addresses match the client's IP address.  If yes, the line is considered
to match and the authentication method is selected.

Anyway, assuming we will go with this, you will also notice that in the
patch I changed the default pg_hba.conf to match against "localhost"
instead of numeric addresses.  Initially thought of as a temporary
change for testing this patch, I think this might actually have some
permanent value because it saves you from having to change the IPv4 and
IPv6 lines in tandem most of the times, which is a moderately common
mistake.  We already rely on localhost being (forward) resolvable for
the stats collector.

Something to think about: Maybe we need a quoting mechanism in case
someone names their hosts "samenet".

Attachment: hba-hostnames.patch
Description: text/x-patch (16.4 KB)

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-08-09 18:48:53
Subject: Re: dynamically allocating chunks from shared memory
Previous:From: Robert HaasDate: 2010-08-09 18:45:53
Subject: Re: dynamically allocating chunks from shared memory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group