Date: Wed, 16 Oct 2024 14:16:45 +0000 (UTC)
From: felix.quintgz@yahoo.com
To: pgsql-general@postgresql.org
Message-ID: <48574746.2559694.1729088205609@mail.yahoo.com>
In-Reply-To: <87o73kgzkd.fsf@mbork.pl>
References: <87o73kgzkd.fsf@mbork.pl>
Subject: Re: What are best practices wrt passwords?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Length: 1292
Archived-At: <https://www.postgresql.org/message-id/48574746.2559694.1729088205609%40mail.yahoo.com>
Precedence: bulk

Use the PGPASSWORD environment variable.
Example:

SET PGPASSWORD=3DP0stgres
psql -h localhost -p 5432 -U postgres -d postgres -c "SELECT 1;'"

https://www.postgresql.org/docs/current/libpq-envars.html


 On Wednesday, October 16, 2024 at 08:26:05 AM GMT-4, <mbork@mbork.pl> wrot=
e:

 Hello all,

I'd like to be able to use psql without typing passwords again and
again.=C2=A0 I know about `.pgpass` and PGPASSFILE, but I specifically do n=
ot
want to use it - I have the password in the `.env` file, and having it
in _two_ places comes with its own set of problems, like how to make
sure they don't get out of sync.

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.=C2=A0 For
example, I could then use `pass` (https://www.passwordstore.org/) with
gpg-agent.

Is there any risk associated with this usage pattern?=C2=A0 What is the
recommended practice in my case other than using `.pgpass`?

Thanks in advance,

P.S. Please CC me in replies, since I'm not subscribed to the list.
Thanks.

--
Marcin Borkowski
https://mbork.pl
https://crimsonelevendelightpetrichor.net/