From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Marowsky-Bree Subject: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching Date: Thu, 21 Jun 2007 23:17:43 +0200 Message-ID: <20070621211743.GN20105@marowsky-bree.de> References: <20070615200623.GA2616@elf.ucw.cz> <20070615211157.GB7337@kroah.com> <46732124.80509@novell.com> <20070616000251.GG2616@elf.ucw.cz> <20070621160840.GA20105@marowsky-bree.de> <20070621183311.GC18990@elf.ucw.cz> <20070621192407.GF20105@marowsky-bree.de> <20070621195400.GK20105@marowsky-bree.de> <1182459594.20464.16.camel@moss-spartans.epoch.ncsc.mil> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: James Morris , Pavel Machek , Crispin Cowan , Greg KH , Andreas Gruenbacher , jjohansen@suse.de, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Stephen Smalley Return-path: Received: from gate.in-addr.de ([212.8.193.158]:48731 "EHLO mx.in-addr.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1755082AbXFUVSU (ORCPT ); Thu, 21 Jun 2007 17:18:20 -0400 Content-Disposition: inline In-Reply-To: <1182459594.20464.16.camel@moss-spartans.epoch.ncsc.mil> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On 2007-06-21T16:59:54, Stephen Smalley wrote: > Or can access the data under a different path to which their profile > does give them access, whether in its final destination or in some > temporary file processed along the way. Well, yes. That is intentional. Your point is? > The emphasis on never modifying applications for security in AA likew= ise > has an adverse impact here, as you will ultimately have to deal with > application mediation of access to their own objects and operations n= ot > directly visible to the kernel (as we have already done in SELinux fo= r > D-BUS and others and are doing for X). Otherwise, your "protection" = of > desktop applications is easily subverted. That is an interesting argument, but not what we're discussing here. We're arguing filesystem access mediation. > Um, no. It might not be able to directly open files via that path, b= ut > showing that it can never read or write your mail is a rather differe= nt > matter. Yes. Your use case is different than mine. Regards, Lars --=20 Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wil= de - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html