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

Re: Adding usernames to pg_hba.conf

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:17:57
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I have been thinking about it and I think one file in data/global/
> > similar to pg_pwd will work.
> Yeah, if you model it on the pg_shadow trigger then at least it's no worse
> than it is now ;-).  Note the checks that exist in the pg_shadow trigger
> to require usernames not to contain any characters that would break the
> file formatting; this will have to be done for groupnames now too.

Yes, got it.

> Also note that (if you plan to write user names and not just user IDs)
> an update of pg_shadow will need to force rewrite of the group file not
> only the shadow file.

Good point.

> Thinking about that, I wonder why not stick to just one file: extend the
> content of pg_pwd to include group membership info, and rewrite it when
> either pg_shadow or pg_group changes.

Well, pg_pwd is really there for passwords, and hba.c doesn't touch it. 
It only gets read as part of actual authentication, while the group file
is used only in hba.c to load the connection patterns.  Seems like
mixing them would cause more confusion than it is worth.

  Bruce Momjian                        |
  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

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2002-03-19 16:54:44
Subject: Re: [HACKERS] Fixes gram.y
Previous:From: Yury BokhoncovichDate: 2002-03-19 16:17:55
Subject: Eurodates by default

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