Bad security practice in oid2name and pgbench - Mailing list pgsql-hackers

From Tom Lane
Subject Bad security practice in oid2name and pgbench
Date
Msg-id 1740.1197171721@sss.pgh.pa.us
Whole thread Raw
Responses Re: Bad security practice in oid2name and pgbench  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [BUGS] BUG #3799: csvlog skips some logs
Next
From: Robert Treat
Date:
Subject: Re: Release Note Changes