From: Arjan van de Ven <arjan@infradead.org>
To: CaT <cat@zip.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
yang.y.yi@gmail.com, linux-kernel@vger.kernel.org,
johnpol@2ka.mipt.ru, matthltc@us.ibm.com
Subject: Re: [2.6.16 PATCH] Connector: Filesystem Events Connector v3
Date: Fri, 24 Mar 2006 08:55:31 +0100 [thread overview]
Message-ID: <1143186931.2882.16.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060324075245.GY2057@zip.com.au>
On Fri, 2006-03-24 at 18:52 +1100, CaT wrote:
> On Thu, Mar 23, 2006 at 11:42:00PM -0800, Andrew Morton wrote:
> > You explained why it was better than grafting audit onto this application.
> >
> > But do you see some special value in the actual services which this patch
> > provides - monitoring filesystem events?
>
> Is there something around atm that would, for example, allow a virus
> scanner to scan files when they are created, etc? Or to add files to
> an index for quick searches?
audit, inotify
> There are probably other potential uses but I'm too tired and those two
> come to mind right now.
but this mechanism doesn't actually cover the virus scanner need at
least; audit is a bit more complex in code because it's a security tool
and needs to be accurate for security-related events. Now guess what...
a virus scanner needs this same level of scrutiny... (well unless you
don't care about that it's easy to bypass your scanner and that you
support linux only for marketing reasons ;)
next prev parent reply other threads:[~2006-03-24 7:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 3:27 Yi Yang
2006-03-24 6:59 ` Arjan van de Ven
2006-03-24 7:06 ` David S. Miller
2006-03-24 7:23 ` Andrew Morton
2006-03-24 7:29 ` David S. Miller
2006-03-24 7:42 ` Andrew Morton
2006-03-24 7:52 ` CaT
2006-03-24 7:55 ` Arjan van de Ven [this message]
2006-03-24 8:08 ` Evgeniy Polyakov
2006-03-24 8:14 ` Arjan van de Ven
2006-03-24 8:16 ` Evgeniy Polyakov
2006-03-24 14:20 ` yang.y.yi
2006-03-24 14:14 ` yang.y.yi
2006-03-24 14:25 ` Arjan van de Ven
2006-03-25 5:37 ` Yi Yang
2006-03-25 23:16 ` Greg Stark
2006-03-26 7:14 ` Benoit Boissinot
2006-03-24 14:24 ` yang.y.yi
2006-03-24 14:28 ` Arjan van de Ven
2006-03-24 15:44 ` James Morris
2006-03-24 21:13 ` Evgeniy Polyakov
2006-03-24 8:05 ` [2.6.16 PATCH] " Evgeniy Polyakov
2006-03-24 8:20 ` David S. Miller
2006-03-24 8:25 ` Evgeniy Polyakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143186931.2882.16.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=cat@zip.com.au \
--cc=davem@davemloft.net \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.com \
--cc=yang.y.yi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®