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
Subject: [TOMOYO #15 0/8] TOMOYO Linux
Date: Thu, 05 Feb 2009 17:18:10 +0900 [thread overview]
Message-ID: <20090205081810.331987920@nttdata.co.jp> (raw)
TOMOYO Linux is a name-based MAC extension (LSM module) for the Linux kernel.
Changes since previous posting.
1. Removed d_realpath(). For now, TOMOYO uses __d_path().
2. Removed singly linked list. For now, TOMOYO uses standard doubly linked list
with "struct rw_semaphore".
3. Fixed bitmap initialization error in tomoyo_update_single_path_acl().
4. Updated patch description.
How to try:
1. Apply patches and compile kernel with CONFIG_SECURITY_TOMOYO=y.
2. Download userspace tools (ccs-tools) available at
http://sourceforge.jp/projects/tomoyo/releases/30298/ and
extract and run 'make -C ccstools/ install' as root user.
3. Run /usr/lib/ccs/tomoyo_init_policy.sh as root user.
4. Run following commands to set learning-mode as default.
(This step is optional but recommended on your first try.)
# echo '<kernel>' > /etc/tomoyo/domain_policy.conf
# echo 'use_profile 1' >> /etc/tomoyo/domain_policy.conf
5. Reboot.
(If you compiled kernel with CONFIG_SECURITY_{SELINUX,SMACK}=y,
add 'security=tomoyo' to kernel's command line.)
6. Run /usr/sbin/ccs-editpolicy to browse and edit policy.
LiveCD-based tutorials are available at
http://tomoyo.sourceforge.jp/en/1.6.x/1st-step/ubuntu8.04-live/
http://tomoyo.sourceforge.jp/en/1.6.x/1st-step/centos5-live/ .
Though these tutorials use non-LSM version of TOMOYO,
they are useful for you to know what TOMOYO is.
These patches are refreshed for
security-testing-2.6.git-27421e211a39784694b597dbf35848b88363c248.tar.gz ,
but should be applicable for 2.6.29-rc3 and later.
Regards.
--
next reply other threads:[~2009-02-05 9:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 8:18 Kentaro Takeda [this message]
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 ` [TOMOYO #15 7/8] Kconfig and Makefile Kentaro Takeda
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=20090205081810.331987920@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 \
/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