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-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Open 7.3 items |
Date: | 2002-07-31 21:22:22 |
Message-ID: | 200207312122.g6VLMMY22500@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> >> Another idea is to change pg_hba.conf to not default to 'trust' but then
> >> the installing user is going to have to choose a password.
>
> Well, initdb already has an option to request a password. It would
> perhaps make sense for initdb to alter the installed pg_hba.conf file
> to select local md5 mode instead of local trust mode when this option is
> specified.
>
> > I like this approach. Set it to password (or md5) on local, and force
> > the request of a password during initdb.
>
> I don't like "forcing" people to do anything, especially not things that
> aren't necessarily useful to them. On a single-user machine there is
> no advantage to using database passwords.
Yes, on a single-user machine, socket permissions are a better approach.
--
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 | Ron Snyder | 2002-07-31 21:29:32 | Re: Open 7.3 items |
Previous Message | Bruce Momjian | 2002-07-31 21:18:52 | Re: Open 7.3 items |