Linux-Security-Module Archive on
 help / color / Atom feed
From: (Peter Moody)
Subject: out of tree lsm's
Date: Mon, 20 Mar 2017 12:45:34 -0700
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Mar 20, 2017 at 12:30 PM, Paul Moore <> wrote:
> On Mon, Mar 20, 2017 at 2:54 PM, Peter Moody <> wrote:
>> with the success of stackable lsm's, it occurs to me that
>> site-specific, out-of-tree modules could be extremely worthwhile.
> Keep in mind we don't have a general purpose solution ... yet.  Casey
> continues to work on it, and I'm sure he'll have something at some
> point, but right now you are limited to a single "big" LSMs (e.g.
> SELinux) and some combination of "small" LSMs (e.g. Yama).

right. sorry for the imprecise language; by site-specific I meant a "small" lsm.

I would love to have the ability write a small lsm that I can build as
a module and load at boot eg. via initrd.

AIUI, adding even a new "small" lsm requires kconfig patches, building
a new kernel, etc. I know there are objections to dynamically loadable
lsms and I was trying to find a compromise that made them easier to
work with.


>> I realize that it doesn't make a lot of sense to have something that I
>> can insmod/rmmod well post-boot, but being able to at least stuff an
>> lsm in an initrd that's loaded during boot could be very helpful.
>> Without having any code to pick apart just now, is the idea of this
>> functionality amenable to folks?
> I think the usual comments about out-of-tree modules apply here;
> you're free to do what you like, but upstream is only going to offer
> limited help/support if/until the code starts its way upstream.
> --
> paul moore
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at
More majordomo info at

  reply index

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 18:54 Peter Moody
2017-03-20 19:30 ` Paul Moore
2017-03-20 19:45   ` Peter Moody [this message]
2017-03-20 20:17     ` Casey Schaufler
2017-03-20 22:18       ` Tetsuo Handa
2017-03-21 10:41         ` Tetsuo Handa
2017-03-21 15:36           ` Casey Schaufler
2017-03-21 16:06             ` Peter Moody
2017-03-21 16:21               ` Casey Schaufler
2017-03-21 21:53                 ` Tetsuo Handa
2017-03-21 22:10                   ` Casey Schaufler
2017-03-22 12:13                     ` Tetsuo Handa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Security-Module Archive on

Archives are clonable:
	git clone --mirror linux-security-module/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-security-module linux-security-module/ \
	public-inbox-index linux-security-module

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone