From: | Nick Sayer <nsayer(at)quack(dot)kfu(dot)com> |
---|---|
To: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Problems with user-level security |
Date: | 2001-11-07 02:19:27 |
Message-ID: | 1709.66.126.254.34.1005099567.squirrel@medusa.kfu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Maybe it's just me, but I think pg_hba.conf needs a user column in it.
On the one hand, I need
local sameuser password
because I have untrusted users who should only have access to their own
databases.
On the other hand, I do a nightly pg_dumpall as part of the backups so that
I don't have to dump the actual database working areas. For that to work, I
need to say
local all password
so that my backup script will work.
What I *really* want is for an extra column to be added to pg_hba.conf to
specify the user of interest. Like this:
all local sameuser password
backups local all password
pgsql local all password
Does this make any sense? Is there some way to achieve this I am missing?
The only way I can do backups at the moment is introduce a race condition
so that anyone can connect to any database they like at certain times of
day. Not good.
From | Date | Subject | |
---|---|---|---|
Next Message | Radoslaw Stachowiak | 2001-11-07 10:52:49 | Re: update in rule |
Previous Message | Manuel Duran Aguete | 2001-11-06 23:01:50 | Perfomance problems |