From: Greg KH <greg@kroah.com>
To: tvrtko.ursulin@sophos.com
Cc: Jon Masters <jonathan@jonmasters.org>,
linux-kernel@vger.kernel.org, malware-list@lists.printk.net
Subject: Re: [malware-list] request for comment: generic kernel interface for malware vendors
Date: Mon, 4 Aug 2008 12:37:37 -0700 [thread overview]
Message-ID: <20080804193737.GB21883@kroah.com> (raw)
In-Reply-To: <20080730111341.BA49F2FE875@pmx1.sophos.com>
On Wed, Jul 30, 2008 at 12:13:36PM +0100, tvrtko.ursulin@sophos.com wrote:
> malware-list-bounces@dmesg.printk.net wrote on 29/07/2008 05:50:58:
>
> > On Mon, 2008-07-28 at 20:39 -0700, Greg KH wrote:
> > > On Mon, Jul 21, 2008 at 12:18:07AM -0400, Eric Paris wrote:
> > > >
> > > > This is a request for comment. This is a first stab and I'm here to
> > > > address all of the concerns that people have. Please don't hold
> back,
> > > > I've got thick skin. BUT, I don't want to hear 'this is how we have
> > > > been doing it, do it that way.' I want to hear how this won't work
> for
> > > > your needs (and WHY) or how we can do it better.
> > > >
> > > > you can find the patches at:
> > > > http://people.redhat.com/~eparis/talpa
> >
> > Ouch. Adds a bunch of hooks outside of LSM - what's the plan here wrt.
> > LSM, because LKML folks are going to ask :)
>
> What is the plan with LSM is also a question? Is it gonna stay or be
> removed?
LSM is staying, no need to remove it.
> Stacking looks like it will never happen and so it really doesn't cut
> it for this kind of use.
Agreed, stacking is probably never going to happen.
thanks,
greg k-h
prev parent reply other threads:[~2008-08-04 19:41 UTC|newest]
Thread overview: 11+ 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
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 [this message]
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=20080804193737.GB21883@kroah.com \
--to=greg@kroah.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malware-list@lists.printk.net \
--cc=tvrtko.ursulin@sophos.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
Powered by JetHome