Re: How to fork pg_dump or psql w/o leaking secrets?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Dominique Devienne <ddevienne(at)gmail(dot)com>
Cc: Luca Ferrari <fluca1978(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: How to fork pg_dump or psql w/o leaking secrets?
Date: 2023-09-22 18:27:56
Message-ID: CAKFQuwYqituJYWixouf-h1ipQa1ZGaRTDffQHOGyYZ3WwpWaQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Friday, September 22, 2023, Dominique Devienne <ddevienne(at)gmail(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Brad White 2023-09-22 18:40:34 Start service
Previous Message Brad White 2023-09-22 18:18:38 Re: How to fork pg_dump or psql w/o leaking secrets?