All of lore.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: System call wrapping
Date: Mon, 21 Oct 2002 18:01:48 -0700	[thread overview]
Message-ID: <20021022010148.GA31385@pegasys.ws> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210211812240.22993-100000@imladris.surriel.com>

On Mon, Oct 21, 2002 at 06:14:48PM -0200, Rik van Riel wrote:
> Maybe you could use the Linux Security Module hooks for
> open() and exec() to pass a request to your virus scan
> software ?
> 
> Note that this kernel module needs to be GPL, due to the
> fact that it's a derived work of the kernel itself. This
> only applies to the kernel module that asks the virus
> scanner to check the files for virusses, not necessarily
> the virus scanner itself.

Even _if_ Rik is overstating this (I'm inclined to agree
with him).  You will have an issue with kernel tainting.

If you don't make your module GPL compatible then your users
will have to look to you for kernel support.  And you can
argue with nvidia about which of you supports the shared
customers.  Or you can tell your customers you don't support
them if they use any other modules that are on the same
license terms as your own.

I enjoy the idea that installing a virus scanner will TAINT
the kernel.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

      parent reply	other threads:[~2002-10-22  0:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 17:42 System call wrapping Henrý Þór Baldursson
2002-10-21 18:12 ` Alan Cox
2002-10-21 18:16 ` Miquel van Smoorenburg
2002-10-21 18:33   ` Karim Yaghmour
2002-10-22 14:02   ` Rogier Wolff
2002-10-21 20:14 ` Rik van Riel
2002-10-21 20:33   ` Lucio Maciel
2002-10-22  5:19     ` Greg KH
2002-10-22  1:01   ` jw schultz [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=20021022010148.GA31385@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.