Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755014Ab0DUBiO (ORCPT ); Tue, 20 Apr 2010 21:38:14 -0400 Received: from mail-pv0-f174.google.com ([74.125.83.174]:44866 "EHLO mail-pv0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754795Ab0DUBiM convert rfc822-to-8bit (ORCPT ); Tue, 20 Apr 2010 21:38:12 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=U/h512rJxWOLm48aEsB4HXNmnJuDKQMd8pgbLfnXeGkTXmdUqK9bDXqmsI5XM5IZzv MEOIVDNn/G3kcDaZOZAbwV2gAIWE1C9txQHNATdO12O/APXGb7RY23+4teLSWjHEuWxS U5mVZ+l4xCXrg+bNKkI3R+ZIlYuCnW8OuyzwQ= MIME-Version: 1.0 In-Reply-To: <1271767039.30027.50.camel@moss-pluto.epoch.ncsc.mil> References: <20100419172639.GA15800@us.ibm.com> <20100419213952.GA28494@hallyn.com> <1271767039.30027.50.camel@moss-pluto.epoch.ncsc.mil> From: Andrew Lutomirski Date: Tue, 20 Apr 2010 21:37:52 -0400 X-Google-Sender-Auth: 543f1d97c1121e49 Message-ID: Subject: Re: [PATCH 0/3] Taming execve, setuid, and LSMs To: Stephen Smalley Cc: "Serge E. Hallyn" , "Serge E. Hallyn" , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, Eric Biederman , "Andrew G. Morgan" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1060 Lines: 26 On Tue, Apr 20, 2010 at 8:37 AM, Stephen Smalley wrote: > On Mon, 2010-04-19 at 16:39 -0500, Serge E. Hallyn wrote: >> Quoting Andrew Lutomirski (luto@mit.edu): >> > ? 1. LSM transitions already scare me enough, and if anyone relies on >> > them working in concert with setuid, then the mere act of separating >> > them might break things, even if the "privileged" (by LSM) app in >> > question is well-written. >> >> hmm... >> >> A good point. > > At least in the case of SELinux, context transitions upon execve are > already disabled in the nosuid case, and Eric's patch updated the > SELinux test accordingly. I don't see that code in current -linus, nor do I see where SELinux affects dumpability. What's supposed to happen? I'm writing a patch right now to clean this stuff up. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/