mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Valdis.Kletnieks@vt.edu
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	serue@us.ibm.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: TOMOYO Linux Security Goal
Date: Sun, 30 Dec 2007 00:02:17 +0000	[thread overview]
Message-ID: <20071230000217.GA17828@ucw.cz> (raw)
In-Reply-To: <27904.1198862631@turing-police.cc.vt.edu>

On Fri 2007-12-28 12:23:51, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 28 Dec 2007 23:32:09 +0900, Tetsuo Handa said:
> 
> > You can run your system with only policy collected by learning mode.
> > Thus, you basically don't need manual intervention.
> > But since there are randomly named files (i.e. temporary files),
> > you pay a little time to modify policy.
> > 
> > The learning mode is to save time for permitting commonly accessed resources.
> > Administrator reviews policy collected by learning mode. Thus the readability
> > of policy is important so that administrator can understand what he/she is
> > going to allow or reject.
> 
> Please make a *big* notation someplace that "learning mode" is quite likely to
> *not* produce a totally correct policy.  In particular, it won't build rules for
> infrequently used code paths (such as error handling) unless you find a way to
> exercise those paths while in learning mode.
> 
> Particularly fun - when learning mode doesn't create an entry for the logfile
> for I/O errors.  Then when one actually happens, you have no idea what it was...

Yes... if you disallow access to /etc/nologin (or do something
similary stupid) you can even introduce security hole...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2007-12-29 23:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-25 12:33 Tetsuo Handa
2007-12-26 16:42 ` Serge E. Hallyn
2007-12-27 13:00   ` Tetsuo Handa
2007-12-27 14:54     ` Serge E. Hallyn
2007-12-28 14:32       ` Tetsuo Handa
2007-12-28 15:12         ` Serge E. Hallyn
2007-12-29  3:43           ` Tetsuo Handa
2007-12-31 15:17             ` Serge E. Hallyn
2007-12-31 15:25               ` Tetsuo Handa
2007-12-31 16:17                 ` Serge E. Hallyn
2007-12-28 17:23         ` Valdis.Kletnieks
2007-12-30  0:02           ` Pavel Machek [this message]
2007-12-30  5:29           ` Tetsuo Handa
2007-12-30  6:28             ` Valdis.Kletnieks
2007-12-31 15:27               ` Casey Schaufler

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=20071230000217.GA17828@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=serue@us.ibm.com \
    /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