Skip site navigation (1) Skip section navigation (2)

Re: Problems with user-level security

From: "Sean K(dot) Sell" <sean(at)nist(dot)gov>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Problems with user-level security
Date: 2001-11-07 14:56:56
Message-ID: 3BE94BB8.93F58096@nist.gov (view raw or flat)
Thread:
Lists: pgsql-admin
I agree a user column would VERY nice especially when you have several machines doing replication
or users that are connecting with ODBC and have to use password instead of crypt authentication.

Nick Sayer wrote:

> 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.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

In response to

pgsql-admin by date

Next:From: Chad R. LarsonDate: 2001-11-07 15:25:07
Subject: Re: Problems with user-level security
Previous:From: Sean K. SellDate: 2001-11-07 12:43:16
Subject: Re: update in rule

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group