[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080817162603.065c756f@infradead.org>
Date: Sun, 17 Aug 2008 16:26:03 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Eric Paris <eparis@...hat.com>
Cc: Jan Harkes <jaharkes@...cmu.edu>, Rik van Riel <riel@...hat.com>,
"Press, Jonathan" <Jonathan.Press@...com>,
Alan Cox <alan@...rguk.ukuu.org.uk>, peterz@...radead.org,
linux-kernel@...r.kernel.org, malware-list@...ts.printk.net,
hch@...radead.org, andi@...stfloor.org, viro@...IV.linux.org.uk
Subject: Re: [malware-list] TALPA - a threat model? well sorta.
On Sun, 17 Aug 2008 19:19:37 -0400
Eric Paris <eparis@...hat.com> wrote:
> On Fri, 2008-08-15 at 15:05 -0700, Arjan van de Ven wrote:
> > On Fri, 15 Aug 2008 16:16:22 -0400
> > Jan Harkes <jaharkes@...cmu.edu> wrote:
> >
> > > > I believe we really do need the block-on-open.
> >
> > I believe more that we need block-on-read ;-)
> > (on open we can start an async scan to cut latency)
> >
> > read() (or mmap etc) is where the actual use/transfer of
> > contaminated data happens, not in the open.
>
> I could probably buy that, but I don't know how an HSM would work.
> Would we have everything we need at open for them to fire off?
>
> /me is HSM clueless and trying to include their needs is proving a
> challenge.
I bet it's the same; until you read/mmap... no need to get the data.
you wouldn't want an "ls -l" or "find" to restore your entire system
from tape after all :)
--
If you want to reach me at my work email, use arjan@...ux.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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists