Re: How to fork pg_dump or psql w/o leaking secrets? - Mailing list pgsql-general

From David G. Johnston
Subject Re: How to fork pg_dump or psql w/o leaking secrets?
Date
Msg-id CAKFQuwYqituJYWixouf-h1ipQa1ZGaRTDffQHOGyYZ3WwpWaQg@mail.gmail.com
Whole thread Raw
In response to Re: How to fork pg_dump or psql w/o leaking secrets?  (Dominique Devienne <ddevienne@gmail.com>)
Responses Re: How to fork pg_dump or psql w/o leaking secrets?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Friday, September 22, 2023, Dominique Devienne <ddevienne@gmail.com> wrote:

I already told you my app is LIBPQ aware, including about PGPASSWORD and PGSERVICE.
It's users who decide to use these mechanisms (which have plain-text passwords BTW...), not my tool.
The same way PSQL prompts for a password when not using these mechanism, so does my tool.

Once you have the password you should utilize the PGPASSWORD environment variable to get it passed to psql.  It doesn’t matter in the least how you obtained that password in the first place.

David J.

pgsql-general by date:

Previous
From: Brad White
Date:
Subject: Re: How to fork pg_dump or psql w/o leaking secrets?
Next
From: Brad White
Date:
Subject: Start service