Feedback-ID: ia2694551:Fastmail
Date: Wed, 16 Oct 2024 16:37:11 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: mbork@mbork.pl
Cc: pgsql-general@postgresql.org
Subject: Re: What are best practices wrt passwords?
Message-ID: <202410161437.sw2xkl37rcmz@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87o73kgzkd.fsf@mbork.pl>
Archived-At: <https://www.postgresql.org/message-id/202410161437.sw2xkl37rcmz%40alvherre.pgsql>
Precedence: bulk

On 2024-Oct-16, mbork@mbork.pl wrote:

> I understand why giving the password on the command line or in an
> environment variable is a security risk (because of `ps`), but I do not
> understand why `psql` doesn't have an option like `--password-command`
> accepting a command which then prints the password on stdout.  For
> example, I could then use `pass` (https://www.passwordstore.org/) with
> gpg-agent.

We had a patch to add PGPASSCOMMAND once:
https://www.postgresql.org/message-id/flat/CAE35ztOGZqgwae3mBA%3DL97pSg3kvin2xycQh%3Dir%3D5NiwCApiYQ%40mail.gmail.com

I don't remember the overall conclusions (other than the patch being
rejected), but maybe you can give that a read.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/