On Fri 2007-12-28 12:23:51, Valdis.Kletnieks@vt.edu wrote:
quoted text
> 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
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/