public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kentaro Takeda <takedakn@nttdata.co.jp>
To: jmorris@namei.org
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	haradats@nttdata.co.jp, Kentaro Takeda <takedakn@nttdata.co.jp>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Subject: [TOMOYO #15 7/8] Kconfig and Makefile
Date: Thu, 05 Feb 2009 17:18:17 +0900	[thread overview]
Message-ID: <20090205082234.211966947@nttdata.co.jp> (raw)
In-Reply-To: 20090205081810.331987920@nttdata.co.jp

TOMOYO uses LSM hooks for pathname based access control and securityfs support.

Signed-off-by: Kentaro Takeda <takedakn@nttdata.co.jp>
Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
---
 security/Kconfig         |    1 +
 security/Makefile        |    2 ++
 security/tomoyo/Kconfig  |   11 +++++++++++
 security/tomoyo/Makefile |    1 +
 4 files changed, 15 insertions(+)

--- security-testing-2.6.git.orig/security/Kconfig
+++ security-testing-2.6.git/security/Kconfig
@@ -134,6 +134,7 @@ config SECURITY_DEFAULT_MMAP_MIN_ADDR
 
 source security/selinux/Kconfig
 source security/smack/Kconfig
+source security/tomoyo/Kconfig
 
 endmenu
 
--- security-testing-2.6.git.orig/security/Makefile
+++ security-testing-2.6.git/security/Makefile
@@ -5,6 +5,7 @@
 obj-$(CONFIG_KEYS)			+= keys/
 subdir-$(CONFIG_SECURITY_SELINUX)	+= selinux
 subdir-$(CONFIG_SECURITY_SMACK)		+= smack
+subdir-$(CONFIG_SECURITY_TOMOYO)        += tomoyo
 
 # always enable default capabilities
 obj-y		+= commoncap.o
@@ -17,3 +18,4 @@ obj-$(CONFIG_SECURITY_SELINUX)		+= selin
 obj-$(CONFIG_SECURITY_SMACK)		+= smack/built-in.o
 obj-$(CONFIG_SECURITY_ROOTPLUG)		+= root_plug.o
 obj-$(CONFIG_CGROUP_DEVICE)		+= device_cgroup.o
+obj-$(CONFIG_SECURITY_TOMOYO)		+= tomoyo/built-in.o
--- /dev/null
+++ security-testing-2.6.git/security/tomoyo/Kconfig
@@ -0,0 +1,11 @@
+config SECURITY_TOMOYO
+	bool "TOMOYO Linux Support"
+	depends on SECURITY
+	select SECURITYFS
+	select SECURITY_PATH
+	default n
+	help
+	  This selects TOMOYO Linux, pathname-based access control.
+	  Required userspace tools and further information may be
+	  found at <http://tomoyo.sourceforge.jp/>.
+	  If you are unsure how to answer this question, answer N.
--- /dev/null
+++ security-testing-2.6.git/security/tomoyo/Makefile
@@ -0,0 +1 @@
+obj-y = common.o realpath.o tomoyo.o domain.o file.o

--


  parent reply	other threads:[~2009-02-05  9:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05  8:18 [TOMOYO #15 0/8] TOMOYO Linux Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 1/8] Add in_execve flag into task_struct Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 2/8] Memory and pathname management functions Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 3/8] Common functions for TOMOYO Linux Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 4/8] File operation restriction part Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 5/8] Domain transition handler Kentaro Takeda
2009-02-05  8:18 ` [TOMOYO #15 6/8] LSM adapter functions Kentaro Takeda
2009-02-05 17:10   ` Alexey Dobriyan
2009-02-06  1:41     ` Tetsuo Handa
2009-02-05  8:18 ` Kentaro Takeda [this message]
2009-02-05  8:18 ` [TOMOYO #15 8/8] MAINTAINERS info Kentaro Takeda
2009-02-12  5:34 ` [TOMOYO #15 0/8] TOMOYO Linux James Morris
2009-02-12  6:53   ` Tetsuo Handa
2009-02-12  9:25     ` James Morris
2009-02-13  7:00       ` Tetsuo Handa
2009-02-14  1:33         ` James Morris
2009-02-22 14:23   ` Pavel Machek
2009-02-22 14:27     ` Tetsuo Handa
2009-02-22 14:48       ` Pavel Machek
2009-02-23  7:37         ` Toshiharu Harada
2009-02-25 19:46           ` Pavel Machek
2009-02-27  1:27             ` KOSAKI Motohiro
2009-03-01 22:45               ` Pavel Machek

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=20090205082234.211966947@nttdata.co.jp \
    --to=takedakn@nttdata.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=haradats@nttdata.co.jp \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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