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: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de>, PG Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: worried about PGPASSWORD drop |
Date: | 2002-08-28 14:13:12 |
Message-ID: | 200208281413.g7SEDCL14546@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
Tom Lane wrote:
> It is not our job to dictate security policy to users. Even on a
> platform where environment variables are insecure, the user might be
> willing to use PGPASSWORD. For example, suppose it's a laptop with
> only one user, connecting via psql to a remote server that demands
> passwords. PGPASSWORD could be a perfectly convenient and safe
> solution.
Good point.
> We should deprecate it, explain exactly why it's deprecated (which the
> current docs fail to do), and leave it up to the user to decide whether
> it's safe to use in his context.
>
> If you want to put in security restrictions that are actually useful,
> where is the code to verify that PGPASSWORDFILE points at a
> non-world-readable file? That needs to be there now, not later, or
> we'll have people moaning about backward compatibility when we finally
> do plug that hole.
Agreed.
--
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 | Andrew Sullivan | 2002-08-28 14:22:20 | Re: Performance Tuning / RAM Usage |
Previous Message | Tom Lane | 2002-08-28 14:01:21 | Re: worried about PGPASSWORD drop |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-28 14:50:59 | Re: [HACKERS] pg_attribute.attisinherited ? |
Previous Message | Tom Lane | 2002-08-28 14:01:21 | Re: worried about PGPASSWORD drop |