Date: Mon, 4 Aug 2008 20:26:19 -0400
From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Eric Paris <eparis@redhat.com>, malware-list@lists.printk.net,
       linux-kernel@vger.kernel.org
Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a linux interface
	for on access scanning
Message-ID: <20080805002618.GA18215@infradead.org>
References: <1217883616.27684.19.camel@localhost.localdomain> <20080804223249.GA10517@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080804223249.GA10517@kroah.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1050
Lines: 29

On Mon, Aug 04, 2008 at 03:32:49PM -0700, Greg KH wrote:
> >   1. Intercept file opens (exec also) for vetting (block until
> >   decision is made) and allow some userspace black magic to make
> >   decisions.

NACK, this kind of policy should be done in kernelspace.

> >   2. Intercept file closes for scanning post access

Not  even possible for mmap, and dumb otherwise, NACK.

> >   6. Scan files directly not relying on path.  Avoid races and problems with namespaces, chroot, containers, etc.

Explain? 

> >   9. Mark a processes as exempt from on access scanning

Nack, this completely defeats the purpose.

> >  11. Exclude sub-trees from scanning based on filesystem path
> >  12. Include only certain sub-trees from scanning based on filesystem path

Nack, please no pathname based idiocies.

--
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/