Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Oct 2002 20:55:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Oct 2002 20:55:52 -0400 Received: from vladimir.pegasys.ws ([64.220.160.58]:35089 "HELO vladimir.pegasys.ws") by vger.kernel.org with SMTP id ; Mon, 21 Oct 2002 20:55:51 -0400 Date: Mon, 21 Oct 2002 18:01:48 -0700 From: jw schultz To: Linux Kernel Mailing List Subject: Re: System call wrapping Message-ID: <20021022010148.GA31385@pegasys.ws> Mail-Followup-To: jw schultz , Linux Kernel Mailing List References: <1035222121.1063.20.camel@pc177> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1389 Lines: 35 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/