| 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: | mlw <pgsql(at)mohawksoft(dot)com>, Devrim GUNDUZ <devrim(at)tr(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL Password Cracker |
| Date: | 2003-01-02 04:27:59 |
| Message-ID: | 200301020427.h024Rxd24517@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Yes, I have been feeling we should do that. Justin pointed out just
yesterday that .pgpass is only mentioned in libpq documentation, and in
fact there is lots of stuff mentioned in libpq that releates to the
other interfaces, so it should be pulled out and put in one place.
Does anyone want to tackle this?
---------------------------------------------------------------------------
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > What do others think? I am not sure myself.
>
> There should definitely be someplace that recommends using SSL across
> insecure networks (if there's not already). But it doesn't seem to me
> to qualify as a FAQ entry. Somewhere in the admin guide seems more
> appropriate. Perhaps under Client Authentication?
>
> Maybe someone could even put together enough material to create a whole
> chapter on security considerations --- this is hardly the only item
> worthy of mention.
>
> regards, tom lane
>
--
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 | Serguei Mokhov | 2003-01-02 06:16:58 | pg_dump.options.diff |
| Previous Message | Tom Lane | 2003-01-02 04:17:59 | Re: PostgreSQL Password Cracker |