From: Chris Wright <chrisw@osdl.org>
To: Luca Falavigna <dktrkranz@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] A different implementation of LSM?
Date: Mon, 3 Jan 2005 15:43:23 -0800 [thread overview]
Message-ID: <20050103154323.B469@build.pdx.osdl.net> (raw)
In-Reply-To: <41D9D45F.7030506@gmail.com>; from dktrkranz@gmail.com on Tue, Jan 04, 2005 at 12:25:19AM +0100
* Luca Falavigna (dktrkranz@gmail.com) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> One of the biggest limitations of LSM is we can't implement more than
> one handler for each security hook at the same time.
> Is it advisable to revise the actual implementation, introducing a
> doubly linked list based mechanism (such as Netfilter implementation),
> or this is the best solution in order to limit overhead?
This is an intentional limitation. Arbitrary security models do not
compose well. And LSM framework allows modules to store state or label
information in kernel objects. So, the callout isn't the only spot that
would need chaining. Take a look at the lsm archive, this is being
worked on presently.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2005-01-03 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 23:25 [RFC] A different implementation of LSM? Luca Falavigna
2005-01-03 23:43 ` Chris Wright [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=20050103154323.B469@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=dktrkranz@gmail.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