Re: pg_hba.conf hostname todo

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: pg_hba.conf hostname todo
Дата
Msg-id 20061227214108.GM24675@kenobi.snowman.net
обсуждение исходный текст
Ответ на pg_hba.conf hostname todo  ("Joshua D. Drake" <jd@commandprompt.com>)
Ответы Re: pg_hba.conf hostname todo  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: pg_hba.conf hostname todo  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
* Joshua D. Drake (jd@commandprompt.com) wrote:
> Allow pg_hba.conf to specify host names along with IP addresses

Excellent.

> Host name lookup could occur when the postmaster reads the pg_hba.conf
> file, or when the backend starts. Another solution would be to reverse
> lookup the connection IP and check that hostname against the host names
> in pg_hba.conf. We could also then check that the host name maps to the
> IP address.

I'm inclined towards doing the reverse-DNS of the connecting IP and then
checking that the forward of that matches.

> Allow one to specify a FQDN or a simple wild card DN. E.g;
> *.commandprompt.com.
>
> A valid entry would look like this:
>
> host    all         all         *.commandprompt.com          trust
> host    all        all        www1.postgresql.org         md5
>
> Thoughts?

While a wildcard does make sense (ie: www*.postgresql.org), I would
generally expect 'commandprompt.com' to mean '*.commandprompt.com'
implicitly.
Thanks!
    Stephen

В списке pgsql-hackers по дате отправления:

Предыдущее
От: David Fetter
Дата:
Сообщение: Re: Per-database search_path
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: [PATCHES] [BUGS] BUG #2846: inconsistent and confusing