Re: PGPASSWORD and client tools

From: Andrej Czapszys <czapszys(at)comcast(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PGPASSWORD and client tools
Date: 2004-08-19 04:18:28
Message-ID: 41242A14.1000204@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

> It's deprecated because it's insecure, on platforms where other users can
>
>see the environment variables passed to pg_dump (which apparently is
>quite a few variants of Unix). You wouldn't pass the password on the
>command line either ...
>
>Painful as .pgpass may be for an admin tool, I do not know of any other
>method I'd recommend on a multiuser machine.
>
>
>
Another possibility would be to add a switch like --password-fd=n
indicating an inherited file descriptor from which the password could be
read. That's not any easier than dynamic .pgpass, but it avoids
all filesystem permissions issues.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Treat 2004-08-19 04:18:32 Re: tablespace and sequences?
Previous Message Bruce Momjian 2004-08-19 04:12:03 Re: $libdir and 8.0

Browse pgsql-patches by date

  From Date Subject
Next Message Martin Münstermann 2004-08-19 07:44:43 Re: [BUGS] 8.0.0beta1: -lpthread missing
Previous Message Bruce Momjian 2004-08-19 02:45:42 Re: 7.4.3 & 8.0.0beta1 + Solaris 9: default pg_hba.conf breaks