From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263326AbVGOQal (ORCPT ); Fri, 15 Jul 2005 12:30:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263323AbVGOQah (ORCPT ); Fri, 15 Jul 2005 12:30:37 -0400 Received: from smtp.osdl.org ([65.172.181.4]:48082 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S263322AbVGOQae (ORCPT ); Fri, 15 Jul 2005 12:30:34 -0400 Date: Fri, 15 Jul 2005 09:30:12 -0700 From: Chris Wright To: Jan Engelhardt Cc: Christoph Hellwig , Chris Wright , Linux Kernel Mailing List Subject: Re: Add security_task_post_setgid Message-ID: <20050715163012.GN9153@shell0.pdx.osdl.net> References: <20050714223807.GA25671@infradead.org> <20050715143238.GA5759@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Jan Engelhardt (jengelh@linux01.gwdg.de) wrote: > And when is this becoming business? What made post_setUid go into the kernel? That went as part of supporting capabilities as they were, to do fixups on set{r,e,s}uid.