From: Ryan Anderson <ryan@michonline.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: is it possible to have a kernel module with a BSD license?!
Date: Sun, 28 Dec 2003 10:27:11 -0500 [thread overview]
Message-ID: <20031228152711.GE17870@michonline.com> (raw)
In-Reply-To: <20031227145102.GA14464@hh.idb.hist.no>
[snipping a bit to keep this succint]
On Sat, Dec 27, 2003 at 03:51:02PM +0100, Helge Hafting wrote:
> > About:
> > This project provides a kernel module which provides 3rd-party
> > applications with an interface for file access control. It was
> > originally developed for on-access virus scanning. Other uses include a
>
> "On access" seems to be exactly the wrong moment for a virus check -
> that way you are getting the check delay at the worst moment, when
> the user actually want to use the file.
>
> Consider doing virus checking on write only, viruses spread
> only at that time.
So, when I stick my nicely virus infected floppy/cdrom/etc into your
machine, and your write-only virus scan gets disabled by my module
patching virus...
So, when I stick my nicely virus infected floppy/cdrom/etc into your
machine, and your write-only virus scan gets disabled by the module
the virus loads...
--
Ryan Anderson
sometimes Pug Majere
prev parent reply other threads:[~2003-12-28 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 15:17 is it possible to have a kernel module with a BSD license?! Bruce Ferrell
2003-12-24 16:10 ` Arjan van de Ven
2003-12-24 22:11 ` Mike Fedyk
2003-12-24 23:12 ` Samuel Flory
2003-12-25 8:33 ` Arjan van de Ven
2003-12-24 22:01 ` Stan Bubrouski
2003-12-24 22:10 ` Mike Fedyk
2003-12-24 23:34 ` David Lang
2003-12-26 20:14 ` Samuel Flory
2003-12-27 14:51 ` Helge Hafting
2003-12-28 15:27 ` Ryan Anderson [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=20031228152711.GE17870@michonline.com \
--to=ryan@michonline.com \
--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