From: Eric Paris <eparis@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.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 20:23:39 -0400 [thread overview]
Message-ID: <1216686219.3594.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200807212014.17296.borntraeger@de.ibm.com>
On Mon, 2008-07-21 at 20:14 +0200, Christian Borntraeger wrote:
> Am Montag, 21. Juli 2008 schrieb Eric Paris:
> > 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.
>
> I have not looked at the code, but if I remember correctly there was another
> GPLed code for file access scanning. It was called dazuko. Google gave me
> http://en.wikipedia.org/wiki/Dazuko
>
> Maybe you can get some ideas from there as well?
Maybe ideas, but it works by disabling mandatory access controls. No
SELinux, no AppArmor, no SMACK, no TOMOYO, and therefore a non-starter.
I certainly don't think its a good idea to take a box that I am using to
try to increase organization wide security and have to lower its
individual security properties.
-Eric
next prev parent reply other threads:[~2008-07-22 0:25 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 [this message]
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=1216686219.3594.6.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=borntraeger@de.ibm.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