mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Toshiharu Harada" <haradats@gmail.com>
To: "Rik van Riel" <riel@redhat.com>
Cc: "Stephen Smalley" <sds@tycho.nsa.gov>,
	"Toshiharu Harada" <haradats@nttdata.co.jp>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [RFC] TOMOYO Linux
Date: Thu, 14 Jun 2007 07:25:21 +0900	[thread overview]
Message-ID: <9d732d950706131525n667587e6t59e94c5cee951c6d@mail.gmail.com> (raw)
In-Reply-To: <467064B9.1080005@redhat.com>

2007/6/14, Rik van Riel <riel@redhat.com>:
> Toshiharu Harada wrote:
> > 2007/6/14, Rik van Riel <riel@redhat.com>:
> > SELinux has a well designed robust and flexible functions.
> > So it should be used for everywhere.  I understand it.
> > As you mentioned one can analyze the system (process)
> > behaviors from AVC logs. But the maintenance cost is not trivial.
> >
> > If logging with process context is the only purpose,
> > current TOMOYO Linux can do it with no hustle at all.
>
> Yes, but so does standard SELinux.
>
> You are making me curious: what does TOMOYO do that is
> not done by regular SELinux?
>
> Logging with process name, path name and contexts is
> already done.  I must have missed some other TOMOYO
> feature in your initial email...

I see SELinux can log with process name, path name and
contexts, but "contexts" must be defined beforehand.
TOMOYO Linux kernel does that with pathname, so no
label definitions needed.
You can confirm the process (domain) transitions any time
and access occurred are clarified per domain basis automatically.
Security context in TOMOYO Linux is represented and stored
as a call chain and very intuitive.

TOMOYO Linux has a mode called "learning"
in addition to "permissive" and "enforce". You can easily
get the TOMOYO Linux policy with learning mode that
SELinux does not have. In addition, access control mode of
TOMOYO Linux can be managed for every difference domain.

-- 
Toshiharu Harada
haradats@gmail.com

  reply	other threads:[~2007-06-13 22:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13  8:13 Toshiharu Harada
2007-06-13 14:07 ` Stephen Smalley
2007-06-13 14:22   ` Toshiharu Harada
2007-06-13 19:37     ` Stephen Smalley
2007-06-15  6:37       ` Toshiharu Harada
2007-06-13 20:02     ` Rik van Riel
2007-06-13 21:35       ` Toshiharu Harada
2007-06-13 21:42         ` Rik van Riel
2007-06-13 22:25           ` Toshiharu Harada [this message]
2007-06-13 22:54             ` James Morris
2007-06-13 23:18               ` Toshiharu Harada
2007-06-15  1:39               ` Tetsuo Handa
2007-06-13 23:32             ` william(at)elan.net
2007-06-14 10:53               ` Stephen Smalley
2007-06-15  6:10   ` Toshiharu Harada
2007-06-15  8:37     ` 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:
  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=9d732d950706131525n667587e6t59e94c5cee951c6d@mail.gmail.com \
    --to=haradats@gmail.com \
    --cc=haradats@nttdata.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=sds@tycho.nsa.gov \
    /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

all inboxes | Powered by JetHome®