From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Bad security practice in oid2name and pgbench |
Date: | 2007-12-09 04:54:49 |
Message-ID: | 475B7519.7040609@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> While going through the contrib documentation, I notice that both
> oid2name and pgbench allow specifying a password on the command line,
> ie
> -P password
>
> This is known to be horribly bad security practice (because the password
> is exposed to everyone else on the machine), and we don't allow any of
> our standard applications to do it. Why is contrib getting a free pass?
>
> I think we should fix these two programs to work the same as our
> other apps, ie, interactively prompt for password when needed.
>
>
Maybe we should also refuse to take passwords from conninfo strings
passed as dbname params, for the same reason. Probably the simplest way
would be add a flag to the arguments to
libpq/fe-connect.c::connectOptions1() to indicate whether or not to get
the password out of the string.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Adriaan van Os | 2007-12-09 09:24:34 | BUG #3811: Getting multiple values from a sequence generator |
Previous Message | Robert Treat | 2007-12-09 04:42:51 | Re: Release Note Changes |