Re: Should libpq set close-on-exec flag on its socket? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Should libpq set close-on-exec flag on its socket?
Date
Msg-id 23213.1098388399@sss.pgh.pa.us
Whole thread Raw
In response to Re: Should libpq set close-on-exec flag on its socket?  (Dennis Bjorklund <db@zigo.dhs.org>)
Responses Re: Should libpq set close-on-exec flag on its socket?
List pgsql-hackers
Dennis Bjorklund <db@zigo.dhs.org> writes:
> On Thu, 21 Oct 2004, Tom Lane wrote:
>> It was suggested to me off-list that libpq should do
>> "fcntl(fd, F_SETFD, FD_CLOEXEC)" on the socket connecting to the server.
>> This would prevent any child program from accidentally or maliciously
>> interfering with the connection.

> Either way that the lib sets it, the client can alter the setting itself
> by issuing a new SETFD command.

That's a fair point, and certainly passing it down to the child
intentionally wouldn't be a common case.  I'll put the change in.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dennis Bjorklund
Date:
Subject: Re: Should libpq set close-on-exec flag on its socket?
Next
From: "Jim C. Nasby"
Date:
Subject: Re: plans for bitmap indexes?