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

From Francisco Olarte
Subject Re: How to fork pg_dump or psql w/o leaking secrets?
Date
Msg-id CA+bJJbzQ=YjKytmeHwR94O8f5cZhc+5suJnw613NiGrYD86rqg@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>)
List pgsql-general
On Fri, 22 Sept 2023 at 15:25, Dominique Devienne <ddevienne@gmail.com> wrote:
> On Fri, Sep 22, 2023 at 12:45 PM Luca Ferrari <fluca1978@gmail.com> wrote:
...
>> I think that forking a beast like psql will make you incurring into a
>> lot of security problems that are worst your "password leak".
> I'm sorry, but this doesn't make sense to me.
> I'm talking of replacing using my tool then psql, with using my tool that forks psql.
> In both cases these are clients apps that connect to a particular DB, for a given user.

It appears you use fork to mean "fork & exec", the classic way to
start a slave ( controlled? helper ? I do not know the modern PC word
for that ) process on *ix, while Luca is thinking on a source fork,
the thing which is normally done in git and friends to have a similar
but derived software built.

Francisco Olarte.



pgsql-general by date:

Previous
From: Dominique Devienne
Date:
Subject: Re: How to fork pg_dump or psql w/o leaking secrets?
Next
From: Luca Ferrari
Date:
Subject: Re: debugger from superuser only.... why?