From: Casey Schaufler <casey@schaufler-ca.com>
To: "d.capitella@tin.it" <d.capitella@tin.it>,
linux-kernel@vger.kernel.org,
LSM List <linux-security-module@vger.kernel.org>
Subject: Re: Implementing a Linux Security Module
Date: Sun, 13 Apr 2008 09:23:44 -0700 (PDT) [thread overview]
Message-ID: <947311.34222.qm@web36606.mail.mud.yahoo.com> (raw)
In-Reply-To: <11947e44e7e.d.capitella@tin.it>
--- "d.capitella@tin.it" <d.capitella@tin.it> wrote:
> Hi there! I'm studying the Linux Security Module Framework, and I'm
> experiencing some issues while trying to register the modules I create.
>
> I created a basic test module that just registers itself as a lsm. I
> tried to load it on many distros, Ubuntu, Fedora, RedHat but it is not
> allowed to register.
>
> May this be due to other LSMs that doesn't
> support stacking and that are
> already loaded on those distros? If
> that's the problem, can't we just
> create a security module that does
> nothing but managing the stacking of
> other security modules?
Yes, that is an option.
There was work on a stacking module early on, but the
lack of available modules and some of the stickier interaction
issues lead to it being set aside.
It certainly makes sense to stack a time-clock access
module and a physical location module. It would not
make sense to stack SELinux and ... well, anything.
What you need to do in the current environment is build your
own kernel, not just the module. It takes more time, disk,
and cpu, but that's about it.
Casey Schaufler
casey@schaufler-ca.com
prev parent reply other threads:[~2008-04-13 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 13:05 Implementing a Linux Security Module d.capitella
2008-04-13 16:23 ` Casey Schaufler [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=947311.34222.qm@web36606.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=d.capitella@tin.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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