From: James Morris <jmorris@namei.org>
To: Toshiharu Harada <haradats@gmail.com>
Cc: Rik van Riel <riel@redhat.com>,
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 18:54:48 -0400 (EDT) [thread overview]
Message-ID: <Line.LNX.4.64.0706131835040.13360@localhost.localdomain> (raw)
In-Reply-To: <9d732d950706131525n667587e6t59e94c5cee951c6d@mail.gmail.com>
On Thu, 14 Jun 2007, Toshiharu Harada wrote:
> 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.
Blindly generating security policy through observation of the system is
potentially dangerous for many reasons.
See
<http://securityblog.org/brindle/2006/03/25/security-anti-pattern-status-quo-encapsulation/>
Note that while SELinux does also have a similar capability with the
audit2allow tool, it should be considered an expert tool, the output of
which needs to be understood before use (as noted in its man page).
> In addition, access control mode of
> TOMOYO Linux can be managed for every difference domain.
We have considered per-domain enforcing mode a couple of times in the
past, but figured that it could be implemented via policy alone (e.g. run
the task in a domain where all accesses are allowed and logged); and it
would also be of limited usefulness because of the aforementioned problems
with learning mode security policy.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2007-06-13 22:55 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
2007-06-13 22:54 ` James Morris [this message]
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=Line.LNX.4.64.0706131835040.13360@localhost.localdomain \
--to=jmorris@namei.org \
--cc=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
Powered by JetHome