New try, with a (probably bad english) documentation patch this time :)
This patch againsts postgresql 7.1.2 allows you to control access based on the
virtual host address only (virtualhost access type), or both the remote
address and the local address (connection access type).
connection all 192.168.42.0 255.255.255.0 192.168.1.42 255.255.255.255 trust
This patch also allows keyword "samehost", similar to "sameuser" but for
virtualhost sameuser samehost.sql.domain.com 255.255.255.255 trust
will prevent you from doing 1 entry per user, all you need is a
(local) dns entry for each host (user foo needs foo.sql.domain.com).
If the dns entry is not found, the line is dropped, so rejecting with
samehost is not a good idea for the moment.
Any comments are welcome.
Please not that I'm not on the list.
In response to
pgsql-hackers by date
|Next:||From: Colin Strickland||Date: 2001-07-04 13:28:46|
|Subject: CREATE TABLE .. PRIMARY KEY quirk|
|Previous:||From: Michel Soto||Date: 2001-07-04 12:12:51|
|Subject: Strange query execution time|
pgsql-patches by date
|Next:||From: Bruce Momjian||Date: 2001-07-04 15:07:52|
|Subject: Re: Patch to remove connection hook and JDK 1.3 dependencies|
|Previous:||From: Tom Lane||Date: 2001-07-03 19:45:59|
|Subject: Re: [PATCH] Patch to make pg_hba.conf handle virtualhost access control and samehost keyword |