From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Rod Taylor <rbt(at)zort(dot)ca>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Adding usernames to pg_hba.conf |
Date: | 2002-03-19 16:04:05 |
Message-ID: | 200203191604.g2JG45U28563@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The only thing I can think of is to dump the groups out as files and
> > enable those in pg_hba.conf, perhaps just like we allow @file includes.
> > I would probably use % for group names and dump them in data/global.
>
> > How does that sound?
>
> You mean as files named after groups? That would add a large pile of
> synchronization and security issues. (If you don't think there's a
> security issue, consider a group named "../pg_hba.conf".)
>
> My advice is not to do it.
I have been thinking about it and I think one file in data/global/
similar to pg_pwd will work. It will contain "groupname<tab>username"
and can be read in with a limited amount of code and dumped out like we
do pg_pwd. It will basically expand to the comma-separated list of
users in the current code.
We can mark group names with "+", e.g. +staff.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-19 16:05:42 | Re: Adding usernames to pg_hba.conf |
Previous Message | Peter Eisentraut | 2002-03-19 15:56:46 | Re: [HACKERS] Fixes gram.y |