Re: [malware-list] scanner interface proposal was: [TALPA] Intro to a linux interface for on access scanning

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Alan Cox <alan@...>
Cc: <tvrtko.ursulin@...>, Theodore Tso <tytso@...>, Arjan van de Ven <arjan@...>, Adrian Bunk <bunk@...>, <capibara@...>, Casey Schaufler <casey@...>, <david@...>, linux-kernel <linux-kernel@...>, <linux-security-module@...>, <malware-list@...>, <malware-list-bounces@...>, Mihai Don??u <mdontu@...>, Peter Dolding <oiaohm@...>, Pavel Machek <pavel@...>, <rmeijer@...>
Date: Monday, August 18, 2008 - 9:42 am

tvrtko.ursulin wrote:

Alan Cox wrote: 

  I suspect we're saying "on close" when what's really meant is
"opened for write". In the latter case, the notification would tell
the user-space program to watch for changes, possibly by something as
simple as doing a stat now and another when it gets around to 
deciding if it should scan the file. I see lots of room for
user-space alternatives for change detection, depending on how much
state it keeps. Rsync-like, perhaps?

--dave
-- 
David Collier-Brown            | Always do right. This will gratify
Sun Microsystems, Toronto      | some people and astonish the rest
davecb@sun.com                 |                      -- Mark Twain
cell: (647) 833-9377, bridge: (877) 385-4099 code: 506 9191#
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [malware-list] scanner interface proposal was: [TALPA] I..., David Collier-Brown, (Mon Aug 18, 9:42 am)