Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752763AbXFVA3N (ORCPT ); Thu, 21 Jun 2007 20:29:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751270AbXFVA24 (ORCPT ); Thu, 21 Jun 2007 20:28:56 -0400 Received: from dsl081-033-126.lax1.dsl.speakeasy.net ([64.81.33.126]:40973 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750717AbXFVA2z (ORCPT ); Thu, 21 Jun 2007 20:28:55 -0400 Date: Thu, 21 Jun 2007 17:28:57 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Joshua Brindle cc: Lars Marowsky-Bree , Stephen Smalley , 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 Subject: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching In-Reply-To: <467B14D9.8050000@manicmethod.com> Message-ID: 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> <20070621211743.GN20105@marowsky-bree.de> <467B14D9.8050000@manicmethod.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1563 Lines: 38 On Thu, 21 Jun 2007, Joshua Brindle wrote: > Lars Marowsky-Bree wrote: >> On 2007-06-21T16:59:54, Stephen Smalley wrote: >> >> >> >> > Um, no. It might not be able to directly open files via that path, but >> > showing that it can never read or write your mail is a rather different >> > matter. >> > >> >> Yes. Your use case is different than mine. >> > > So.. your use case is what? If an AA user asked you to protect his mail from > his browser I'm sure you'd truthfully answer "no, we can't do that but we can > protect the path to your mail from your browser".. I think not. One need only > look at the wonderful marketing literature for AA to see what you are telling > people it can do, and your above statement isn't consistent with that, sorry. remember, the policies define a white-list so if a hacker wants to have mozilla access the mail files he needs to get some other process on the sysstem to create a link or move a file to a path that mozilla does have access to. until that is done there is no way for mozilla to access the mail through the filesystem. other programs could be run that would give mozilla access to the mail contents, but it would be through some other path that the policy permitted mozilla accessing in the first place. David Lang - 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/