From: James Morris <jmorris@namei.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: Mon, 21 Jul 2008 21:17:45 +1000 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0807212054001.17349@us.intercode.com.au> (raw)
In-Reply-To: <1216613887.2960.18.camel@localhost.localdomain>
On Mon, 21 Jul 2008, Eric Paris wrote:
[ITYM anti-malware vendors...]
> First I'd like to thank Sophos who stepped up and originally wrote a lot
> of this code. They might not recognize it since I've gotten my hands on
> it, but they were nice enough to get the ball rolling by giving me some
> GPL code which addressed near every request people on the malware list
> had.
We need a document explaining what the problem being solved actually is.
What is the rationale for adding malware scanning to the Linux kernel?
How does it benefit people? Why does it need to be in the kernel? What
are the general requirements, and how does this interface meet those ?
Does this interface represent an approach suitable to a range of
anti-malware vendors ?
(I'm assuming the fundamental question of whether malware scanning is a
good idea or not is not up for discussion, because there'll never be
consensus).
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2008-07-21 11:18 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 [this message]
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
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=Xine.LNX.4.64.0807212054001.17349@us.intercode.com.au \
--to=jmorris@namei.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