From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 03:31:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D96A16A401 for ; Mon, 3 Apr 2006 03:31:12 +0000 (UTC) (envelope-from scrappy@postgresql.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id C395B43D5D for ; Mon, 3 Apr 2006 03:31:02 +0000 (GMT) (envelope-from scrappy@postgresql.org) Received: from localhost (av.hub.org [200.46.204.144]) by hub.org (Postfix) with ESMTP id D1F27824479; Mon, 3 Apr 2006 00:31:01 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 11271-06; Mon, 3 Apr 2006 00:31:00 -0300 (ADT) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id A74C3823E22; Mon, 3 Apr 2006 00:30:59 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id 59EE23B0FA; Mon, 3 Apr 2006 00:30:58 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 529763B051; Mon, 3 Apr 2006 00:30:58 -0300 (ADT) Date: Mon, 3 Apr 2006 00:30:58 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Kris Kennaway In-Reply-To: <20060403032130.GA58053@xor.obsecurity.org> Message-ID: <20060403002830.W947@ganymede.hub.org> References: <26796.1144028094@sss.pgh.pa.us> <20060402225204.U947@ganymede.hub.org> <26985.1144029657@sss.pgh.pa.us> <20060402231232.C947@ganymede.hub.org> <27148.1144030940@sss.pgh.pa.us> <20060402232832.M947@ganymede.hub.org> <20060402234459.Y947@ganymede.hub.org> <27417.1144033691@sss.pgh.pa.us> <20060403031157.GA57914@xor.obsecurity.org> <27515.1144034269@sss.pgh.pa.us> <20060403032130.GA58053@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Cc: Tom Lane , "Marc G. Fournier" , freebsd-stable@freebsd.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] semaphore usage "port based"? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 03:31:12 -0000 On Sun, 2 Apr 2006, Kris Kennaway wrote: > On Sun, Apr 02, 2006 at 11:17:49PM -0400, Tom Lane wrote: >> Kris Kennaway writes: >>> On Sun, Apr 02, 2006 at 11:08:11PM -0400, Tom Lane wrote: >>>> If this is the story, then FBSD have broken their system and must revert >>>> their change. They do not have kernel behavior that totally hides the >>>> existence of the other process, and therefore having some calls that >>>> pretend it's not there is simply inconsistent. >> >>> I'm guessing it's a deliberate change to prevent the information >>> leakage between jails. >> >> I have no objection to doing that, so long as you are actually doing it >> correctly. This example shows that each jail must have its own SysV >> semaphore key space, else information leaks anyway. > > By default SysV shared memory is disallowed in jails. 'k, but how do I fix kill so that it has the proper behaviour if SysV is enabled? Maybe a mount option for procfs that allows for pre-5.x behaviour? I'm not the first one to point out that this is a problem, just the first to follow it through to the cause ;( And I believe there is more then just PostgreSQL that is affected by shared memory (ie. apache2 needs SysV IPC enabled, so anyone doing that in a jail has it enabled also) ... Basically, I don't care if 'default' is ultra-secure ... but some means to bring it down a notch would be nice ... :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664