Received: from tech.com.au (IDENT:root@techpt.lnk.telstra.net [139.130.75.122]) by hub.org (8.10.1/8.10.1) with ESMTP id e68F8YW34095 for ; Sat, 8 Jul 2000 11:08:35 -0400 (EDT) Received: from bitmead.com (IDENT:chris@tardis [203.41.180.243]) by tech.com.au (8.9.3/8.9.3) with ESMTP id BAA12110 for ; Sun, 9 Jul 2000 01:08:31 +1000 Message-ID: <396743EB.62592694@bitmead.com> Date: Sun, 09 Jul 2000 01:08:27 +1000 From: Chris Bitmead X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: PostgreSQL HACKERS Subject: Re: fcntl(SETLK) [was Re: 2nd update on TOAST] References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200007/510 > There's a possible DoS attack when someone else comes first and creates a > file /tmp/.s.PGSQL.5432. But detecting whether there's another program > running on that socket (if it's a socket) isn't going to help because you > most likely won't be able to delete it anyway. The solution to this is to > make the path of the socket file configurable more easily so that the > administrator has the choice of putting it a safer place that he prepared > appropriately. If you are worried about DoS, I think the only solution is to figure out a way to be using one of the reserved <1000 ports. I don't think there's any way around that is there? Also presumably not using a reserved port is a security risk. Not that I'm worried.