| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PGPASSWORD and client tools |
| Date: | 2004-08-19 10:02:52 |
| Message-ID: | 41247ACC.1010605@pse-consulting.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Christopher Kings-Lynne 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.
>
>
> OK, but say you have a phpPgAdmin installation that's servicing 20
> users. Then you have to put a .pgpass file in the www home dir (if
> there is one) with the usernames and passwords of all those users -
> pretty damn annoying...
Even worse, if you have a server registered more than once with
different credentials...
I tried redirecting pg_dump's stdin but that locked up under win32.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-08-19 10:10:24 | Re: [HACKERS] 8.0 libpq: missing get_home_path() |
| Previous Message | Fabien COELHO | 2004-08-19 08:31:17 | Re: tablespace and sequences? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-08-19 10:10:24 | Re: [HACKERS] 8.0 libpq: missing get_home_path() |
| Previous Message | Martin Münstermann | 2004-08-19 07:44:43 | Re: [BUGS] 8.0.0beta1: -lpthread missing |