From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Eric Paris" <eparis@redhat.com>
Cc: malware-list@lists.printk.net, linux-kernel@vger.kernel.org
Subject: Re: request for comment: generic kernel interface for malware vendors
Date: Wed, 23 Jul 2008 09:09:40 -0700 [thread overview]
Message-ID: <2c0942db0807230909l1e38ed97x9f5ce510dc0dcdd7@mail.gmail.com> (raw)
In-Reply-To: <1216613887.2960.18.camel@localhost.localdomain>
On Sun, Jul 20, 2008 at 9:18 PM, Eric Paris <eparis@redhat.com> wrote:
> 1 - ****hooks, basics, infrastructure
> 2 - configuration generic stuff for the other patches
> 3 - ****results caching
> 4 - exclusions based on the operation or filetype
> 5 - per process exclusions
> 6 - filesystem type exclusions
> 7 - patch exclusions, don't scan when accessed through certain path
> 8 - patch inclusions, only scanning selected things
> 9 - ****userspace vetting, the big stuff
> 10 - operating when userspace is broken
If, along the way, you can also address the needs provided by the
fschange patches (system-wide inotify, in essence, without having to
register individual watches), that'd be gravy. I haven't looked at
either the patches above or the fsnotify ones, so I can't speak to
whatever overlap they may have, except that it certainly seems like
the anti-malware stuff would be a superset.
http://stefan.buettcher.org/cs/fschange/index.html
~r.
next prev parent reply other threads:[~2008-07-23 16:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 4:18 Eric Paris
2008-07-21 11:17 ` James Morris
2008-07-24 9:58 ` Christoph Hellwig
2008-07-21 17:43 ` Rafael C. de Almeida
2008-07-21 18:14 ` Christian Borntraeger
2008-07-22 0:23 ` Eric Paris
2008-07-23 16:09 ` Ray Lee [this message]
2008-07-29 3:39 ` Greg KH
2008-07-29 4:50 ` [malware-list] " Jon Masters
2008-07-30 11:13 ` tvrtko.ursulin
2008-08-04 19:37 ` Greg KH
[not found] <aRVce-Em-3@gated-at.bofh.it>
[not found] ` <aS7Go-7AK-3@gated-at.bofh.it>
2008-07-23 12:43 ` Bodo Eggert
2008-07-23 15:14 ` Arjan van de Ven
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=2c0942db0807230909l1e38ed97x9f5ce510dc0dcdd7@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
/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
Powered by JetHome