From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Allowing usernames in pg_hba.conf |
Date: | 2002-03-10 06:20:13 |
Message-ID: | 200203100620.g2A6KDn20576@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
We have the following TODO item:
* Allow usernames to be specified directly in pg_hba.conf (Bruce)
My idea is to allow comma-separated usernames in the AUTH_ARGUMENT
column. Right now we use it for ident user map files and secondary
password files. It seems both easily already allow username
restrictions. Adding usernames directly in pg_hba.conf is basically a
shortcut to creating such secondary files.
My idea is that if AUTH_ARGUMENT starts with "=", it represents a list
of comma-separated usernames.
host template1 192.168.12.10 255.255.255.255 md5 =bmomjian,jeffw
Do I need to allow usernames with spaces or quoted usernames? I don't
think so.
For implementation, I was going to simulate a secondary password file
with no passwords. We already support that internally as a username
restriction option. Those are loaded into memory as linked lists of text
lines, if I remember correclty.
--
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 | Tom Lane | 2002-03-10 07:31:39 | Re: Allowing usernames in pg_hba.conf |
Previous Message | Bruce Momjian | 2002-03-10 06:01:37 | Re: Index USING in pg_dump |