| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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:39:47 |
| Message-ID: | 15309.1089949187@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-07-16 03:43:32 | Re: initdb authentication |
| Previous Message | Simon Riggs | 2004-07-16 00:02:38 | Re: Point in Time Recovery |