From: Chris Wright <chrisw@osdl.org>
To: Michael Halcrow <mahalcro@us.ibm.com>
Cc: chrisw@osdl.org, linux-kernel@vger.kernel.org, mike@halcrow.us
Subject: Re: [PATCH] BSD Secure Levels LSM (1/3)
Date: Mon, 30 Aug 2004 09:08:54 -0700 [thread overview]
Message-ID: <20040830090853.A1924@build.pdx.osdl.net> (raw)
In-Reply-To: <20040830143547.GA9980@halcrow.us>; from mike@halcrow.us on Mon, Aug 30, 2004 at 09:35:47AM -0500
* Michael Halcrow (mike@halcrow.us) wrote:
> +config SECURITY_STACKER
> + tristate "Stacker"
> + depends on SECURITY
> + help
> + Implements LSM stacker.
> +
> source security/selinux/Kconfig
>
> endmenu
> --- linux-2.6.8-rc3/security/Makefile 2004-06-16 00:19:43.000000000 -0500
> +++ linux-2.6.8-rc3_seclvl/security/Makefile 2004-08-30 08:35:02.000000000 -0500
> @@ -15,3 +15,5 @@
> obj-$(CONFIG_SECURITY_SELINUX) += selinux/built-in.o
> obj-$(CONFIG_SECURITY_CAPABILITIES) += commoncap.o capability.o
> obj-$(CONFIG_SECURITY_ROOTPLUG) += commoncap.o root_plug.o
> +obj-$(CONFIG_SECURITY_SECLVL) += seclvl.o
> +obj-$(CONFIG_SECURITY_STACKER) += stacker.o
Looks like some extra stacker bits snuck in. Unused, correct?
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-08-30 16:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 14:35 Michael Halcrow
2004-08-30 14:38 ` [PATCH] BSD Secure Levels LSM (2/3) Michael Halcrow
2004-08-30 14:40 ` [PATCH] BSD Secure Levels LSM (3/3) Michael Halcrow
2004-08-30 16:08 ` Chris Wright [this message]
2004-08-30 15:15 ` [PATCH] BSD Secure Levels LSM (1/3) Michael Halcrow
2004-08-30 16:10 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 15:14 Michael Halcrow
2004-08-10 17:17 ` Lee Revell
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=20040830090853.A1924@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahalcro@us.ibm.com \
--cc=mike@halcrow.us \
/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
Powered by JetHome