From: | Christoph Dalitz <christoph(dot)dalitz(at)hs-niederrhein(dot)de> |
---|---|
To: | PG Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | worried about PGPASSWORD drop |
Date: | 2002-08-28 13:35:52 |
Message-ID: | 20020828153552.2a1b1cc3.christoph.dalitz@hs-niederrhein.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
In the TODO list on http://developer.postgresql.org/todo.php,
I found the following entry:
- Remove PGPASSWORD because it is insecure on some OS's, in 7.4
Why?
I see the following problems:
- This will make psql no longer usable in scripts as PGPASSWORD is
currently the *only* way to pass a password to psql
- The alternative (a new command line option for password) is much more insecure,
as then the password is readable by everybody from the process table
In case PGPASSWORD is dropped, there should be a working way to use psql
in scripts. Maybe you could manage to make the following code work:
psql -U user dbname <<EOF
password
/* SQL-Statements */
EOF
(For some strange reason this works with Oracle's sqlplus, but not with psql)
Christoph Dalitz
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-08-28 13:36:55 | Re: Uninitialized page on pg_class ? |
Previous Message | David Link | 2002-08-28 13:25:58 | Re: Screwy behavior with SUM and multiple joins to same |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-08-28 13:46:44 | Re: worried about PGPASSWORD drop |
Previous Message | Yury Bokhoncovich | 2002-08-28 11:29:28 | Fix for spec-file to avoid problems when building w/o tcl |