From: Enrico Weigelt <weigelt@metux.de>
To: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: scanner interface proposal was: [TALPA] Intro to a linux interface for on access scanning (fwd)
Date: Mon, 1 Dec 2008 01:51:42 +0100 [thread overview]
Message-ID: <20081201005142.GA27387@nibiru.local> (raw)
In-Reply-To: <20081123230306.48bc0274@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > Fine. Why not just putting this into a userland filesystem ?
>
> 1. Performance
Does it really hurt so bad, compared with all actual AV stuff ?
It has to go to userland anyway, in case you don't intend to
put the scanner into the kernel ;-o
> 2. Networked file systems
What's the problem ?
(btw: 9P already *IS* an network filesystem ;-P)
> 3. Ioctls
Ah, just forgot a while that this crap still exists ;-o
BUT: do the affected dirs have to contain devices ?
Is there any point for pulling /dev through the AV scanner ?
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
next prev parent reply other threads:[~2008-12-01 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 1:25 scanner interface proposal was: [TALPA] Intro to a linux interface for on access scanning (fwd) david
2008-08-18 10:30 ` [malware-list] " tvrtko.ursulin
2008-08-18 11:44 ` david
2008-08-18 12:18 ` tvrtko.ursulin
2008-08-18 12:34 ` david
2008-11-23 22:37 ` Enrico Weigelt
2008-11-23 23:03 ` Alan Cox
2008-12-01 0:51 ` Enrico Weigelt [this message]
2008-12-01 5:22 ` david
2008-12-01 10:03 ` Alan Cox
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=20081201005142.GA27387@nibiru.local \
--to=weigelt@metux.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox