Date: Sun, 2 Dec 2007 12:02:14 -0800
From: Arjan van de Ven <arjan@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: Pavel Machek <pavel@ucw.cz>, tvrtko.ursulin@sophos.com,
       Andi Kleen <andi@firstfloor.org>, ak@suse.de,
       linux-kernel@vger.kernel.org
Subject: Re: Out of tree module using LSM
Message-ID: <20071202120214.68cf1700@laptopd505.fenrus.org>
In-Reply-To: <17957.1196624688@turing-police.cc.vt.edu>
References: <p738x4i9nyd.fsf@crumb.suse.de>
	<OFFB86F10D.D565B603-ON802573A2.005A558C-802573A2.005B85B0@sophos.com>
	<20071201084332.GB4446@ucw.cz>
	<17957.1196624688@turing-police.cc.vt.edu>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1065
Lines: 29

On Sun, 02 Dec 2007 14:44:48 -0500
Valdis.Kletnieks@vt.edu wrote:

> On Sat, 01 Dec 2007 08:43:32 GMT, Pavel Machek said:
> 
> > So what you are trying to do is 'application may never read bad
> > sequence of bits from disk', right?
> 
> No, in many of the use cases, we're trying to do "if application
> reads certain specified sequences of bits from disk we know about
> it", which is subtly different.  Often, *absolute* prevention isn't
> required, as long as we can generate audit trails and/or alerts...

.. which breaks down if/when glibc uses mmap() to implement the
fopen/fread etc interface
(note: it already does, just not quite yet by default)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/