From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.5 module development mailing list needed? [Fwd: Linux Security Module Interface]
Date: Tue, 10 Apr 2001 19:30:36 -0700 [thread overview]
Message-ID: <3AD3C1CC.D6167000@megapathdsl.net> (raw)
Hi,
Since the 2.5 kernel development will require continued module
architecture changes to accomodate power management, pluggable
security and PCMCIA in the kernel tree, it would seem to make
sense that the various groups that are doing module related
architecture changes collaborate and be aware of what each
other are doing, so that changes can be coordinated.
Groups that contain individuals who might be interested
might include:
acpi@phobos.fs.tum.de
linux-hotplug-devel@lists.sourceforge.net
linux-power@phobos.fs.tum.de
linux-security-module@wirex.com
LKML
Comments?
Miles
Crispin Cowan wrote:
>
> One of the byproducts of the Linux 2.5 Kernel Summit
> http://lwn.net/2001/features/KernelSummit/ was the notion of an
> enhancement of the loadable kernel module interface to facilitate
> security-oriented kernel modules. The purpose is to ease the tension
> between folks (such as Immunix and SELinux) who want to add substantial
> security capabilities to the kernel, and other folks who want to
> minimize kernel bloat & have no use for such security extensions.
>
> Modules that can be loaded, or not, are the obvious solution, but the
> current LKM does not export sufficient hooks to support many security
> mechanisms. Thus many current security enhancements end up existing as
> kernel patches, which marginalizes their utility by making distribution
> problematic. The proposed solution is to enhance the LKM with a variety
> of new kernel elements exported to the module interface, so as to
> support a reasonable variety of security enhancements.
>
> We have started a new mailing list called linux-security-module. The
> charter is to design, implement, and maintain suitable enhancements to
> the LKM to support a reasonable set of security enhancement packages.
> The prototypical module to be produced would be to port the POSIX Privs
> code out of the kernel and make it a module. An essential part of this
> project will be that the resulting work is acceptable for the mainline
> Linux kernel.
>
> The list is open to all. You can subscribe here
> http://mail.wirex.com/mailman/listinfo/linux-security-module or by
> sending e-mail to linux-security-module-request@wirex.com with a subject
> of "subscribe".
next reply other threads:[~2001-04-11 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 2:30 Miles Lane [this message]
2001-04-11 9:20 ` 2.5 module development mailing list needed? [Fwd: Linux Security Module Interface] Matti Aarnio
2001-04-11 17:07 ` Miles Lane
2001-04-11 20:06 ` Rik van Riel
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=3AD3C1CC.D6167000@megapathdsl.net \
--to=miles@megapathdsl.net \
--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