Subject: Re: [RFC 0/5] [TALPA] Intro to a linux interface for on access
	scanning
From: John Moser <nigelenki@comcast.net>
To: Eric Paris <eparis@redhat.com>
Cc: malware-list@lists.printk.net, linux-kernel@vger.kernel.org
In-Reply-To: <1217883616.27684.19.camel@localhost.localdomain>
References: <1217883616.27684.19.camel@localhost.localdomain>
Content-Type: text/plain
Date: Mon, 18 Aug 2008 10:06:50 -0400
Message-Id: <1219068410.6361.151.camel@icebox>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 23

On Mon, 2008-08-04 at 17:00 -0400, Eric Paris wrote:
> Background
> ++++++++++
> There is a consensus in the security industry that protecting against
> malicious files (viruses, root kits, spyware, ad-ware, ...) by the way
> of so-called on-access scanning is usable and reasonable approach.
> Currently the Linux kernel does not offer a completely suitable
> interface to implement such security solutions.  Present solutions

A long time ago the FUSE developers said something about implementing
write-through stacking for FUSE (i.e. 'sudo fusermount -o allow_other
encfs / /' would allow mounting on /, and encfs could read/write under
its own mount point).

Wouldn't that make more sense?  You could i.e. edit /etc/avfs.conf to
say "scanner=clamscan" "clamscan=/usr/bin/clamscan" and mount avfs
on /...?

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