From: Bruce Ferrell <bferrell@baywinds.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: is it possible to have a kernel module with a BSD license?!
Date: Wed, 24 Dec 2003 07:17:02 -0800 [thread overview]
Message-ID: <3FE9ADEE.1080103@baywinds.org> (raw)
from the project announcement on freshmeat:
Dazuko 2.0.0-pre5 (Default)
by John Ogness - Tuesday, November 11th 2003 06:56 PST
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
file-access monitor/logger or external security implementations. It
operates by intercepting file-access calls and passing the file
information to a 3rd-party application. The 3rd-party application then
has the opportunity to tell the kernel module to allow or deny the
file-access. The 3rd-party application also receives information about
the file, such as type of access, process ID, user ID, etc.
Release focus: Minor bugfixes
Changes:
Some "in use" problems with spontaneous context-switches when unloading
under FreeBSD were fixed. Macros for hooking/unhooking system calls were
added. Filename length restrictions were removed. Code for generating
protocol13 was abstracted and moved into XP layer. Support for filenames
with non-printable characters was added. The ability to compile the
interface library without 1.x compatibility was added. An "off by one"
bug which occurred when calculating include/exclude path lengths was
fixed. Support for Linux 2.6 kernels was added (not yet complete, but
very functional).
Last release License
Default 2.0.0-pre5 24-Dec-2003 BSD License (revised)
next reply other threads:[~2003-12-24 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 15:17 Bruce Ferrell [this message]
2003-12-24 16:10 ` is it possible to have a kernel module with a BSD license?! 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
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=3FE9ADEE.1080103@baywinds.org \
--to=bferrell@baywinds.org \
--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