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: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: initdb authentication |
Date: | 2004-07-16 03:43:32 |
Message-ID: | 200407160343.i6G3hWK16980@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I think the basic problem is that right now there is no way to do an
> > initdb and have it be secure _before_ you edit pg_hba.conf. That isn't
> > acceptable. If I am on an insecure machine, the window if time between
> > initdb and editing of pg_hba.conf is pretty bad.
>
> Bruce, you of all people should be aware that there is no such window.
> The postmaster *is not running* and cannot accept any hostile
> connections if you haven't started it.
>
> Argue all you like about the potential for novice error, but don't try
> to scare us by claiming that it's inherently insecure.
Ah, I forgot about postmaster start. (My scripts do it automatically
here.) Maybe we just need to print a warning telling people they should
secure pg_hba.conf before starting the postmaster on an insecure
machine.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-07-16 03:49:04 | Re: Point in Time Recovery |
Previous Message | Tom Lane | 2004-07-16 03:39:47 | Re: initdb authentication |