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

From Dennis Bjorklund
Subject Re: Should libpq set close-on-exec flag on its socket?
Date
Msg-id Pine.LNX.4.44.0410212044160.2015-100000@zigo.dhs.org
Whole thread Raw
In response to Should libpq set close-on-exec flag on its socket?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Should libpq set close-on-exec flag on its socket?
List pgsql-hackers
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. I would not have expected it to be set 
but it is probably a good idea for most clients (and for most file 
descriptors).

-- 
/Dennis Björklund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Should libpq set close-on-exec flag on its socket?
Next
From: Tom Lane
Date:
Subject: Re: Should libpq set close-on-exec flag on its socket?