mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: 7eggert@gmx.de
Cc: "Rafael C. de Almeida" <almeidaraf@gmail.com>,
	Eric Paris <eparis@redhat.com>,
	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 08:14:03 -0700	[thread overview]
Message-ID: <20080723081403.4c615bcb@infradead.org> (raw)
In-Reply-To: <E1KLdgU-0001a9-7F@be1.7eggert.dyndns.org>

On Wed, 23 Jul 2008 14:43:09 +0200
Bodo Eggert <7eggert@gmx.de> wrote:

> Rafael C. de Almeida <almeidaraf@gmail.com> wrote:
> > Eric Paris wrote:
> 
> >> [Kernel support for malware scanners]
> 
> > I'm a newbie here, so don't take me too serious. But I don't see why
> > that needs a kernel interface, at least from the example on the
> > Documentation directory (patch 9). Seems to me you could just use
> > file permission to deny or allow the access for a certain file. The
> > only thing that would be a little trickier from user-space is to
> > know when a given file is read. So, talpa should do only that or
> > you could take advantage of preload like trickle does for bandwidth
> > shapping.
> 
> How do you ensure that the LD_PRELOAD variable stays intact and will
> be honored by all applications - including that commercial one
> supplying it's own libc, by suid-binaries and by programs written in
> a non-libc-language?

neither approach is fool proof for that matter
it's just a matter of how high you want to put the bar.

that's why it's really important to see the design ideas for this
code... to figure out what it is supposed to do ;)

-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-23 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

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=20080723081403.4c615bcb@infradead.org \
    --to=arjan@infradead.org \
    --cc=7eggert@gmx.de \
    --cc=almeidaraf@gmail.com \
    --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