Re: Should libpq set close-on-exec flag on its socket?

From: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Should libpq set close-on-exec flag on its socket?
Date: 2004-10-21 19:07:44
Message-ID: Pine.LNX.4.44.0410212044160.2015-100000@zigo.dhs.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-10-21 19:53:19 Re: Should libpq set close-on-exec flag on its socket?
Previous Message Tom Lane 2004-10-21 18:10:48 Should libpq set close-on-exec flag on its socket?