All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Toshiharu Harada <haradats@gmail.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: Wed, 13 Jun 2007 17:42:17 -0400	[thread overview]
Message-ID: <467064B9.1080005@redhat.com> (raw)
In-Reply-To: <9d732d950706131435s636b852di98026aed1d9a6ac6@mail.gmail.com>

Toshiharu Harada wrote:
> 2007/6/14, Rik van Riel <riel@redhat.com>:
>> > So I think pathname based call chains are advantages for
>> > at least auditing and profiling.
>>
>> SELinux audit logs (well, whatever is in /var/log/audit on
>> my system) does show the path names of objects that fail to
>> be accessed as well as the name and context of the processes
>> trying to access them.
>>
>> This is with standard Fedora and RHEL installations.
> 
> Thank you for your comment.
> 
> 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...

-- 
All Rights Reversed

  reply	other threads:[~2007-06-13 21:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13  8:13 [RFC] TOMOYO Linux 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 [this message]
2007-06-13 22:25           ` Toshiharu Harada
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=467064B9.1080005@redhat.com \
    --to=riel@redhat.com \
    --cc=haradats@gmail.com \
    --cc=haradats@nttdata.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.