From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753169AbbBWQrG (ORCPT ); Mon, 23 Feb 2015 11:47:06 -0500 Received: from resqmta-ch2-09v.sys.comcast.net ([69.252.207.41]:56401 "EHLO resqmta-ch2-09v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751812AbbBWQrE (ORCPT ); Mon, 23 Feb 2015 11:47:04 -0500 Date: Mon, 23 Feb 2015 10:47:01 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Andy Lutomirski cc: Serge Hallyn , Serge Hallyn , Aaron Jones , "Ted Ts'o" , LSM List , Andrew Morton , "Andrew G. Morgan" , Mimi Zohar , Austin S Hemmelgarn , Markku Savela , Jarkko Sakkinen , "linux-kernel@vger.kernel.org" , Linux API , Michael Kerrisk , Jonathan Corbet Subject: Re: [PATCH] capabilities: Ambient capability set V1 In-Reply-To: Message-ID: References: <20150223161625.GD25477@ubuntumail> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 23 Feb 2015, Andy Lutomirski wrote: > Is there really a need to drop privilege and then regain it or is it > sufficient to keep the privilege permitted (and perhaps ambient, too) > and just to have execve not drop it for you? I assume the latter. I would think just keep the ambient set active as long as there is no prctl switching the cap off in the child processes. Do not let it be affected by the usual drop privs stuff.