Re: SELinux Coloring book?

[Dominick Grift <dominick.grift@gmail.com>]

On Wed, 2013-11-13 at 20:01 +0100, Dominick Grift wrote:
> On Wed, 2013-11-13 at 18:37 +0000, Radzykewycz, T (Radzy) wrote:
> > General question:
> > 
> > Does the "coloring book" really need to cover all aspects of security, and cover them in depth?  If this is a kindergarten grade level introduction, then explaining all the nuances of priority may be too much to ask.  If it is for more experienced audiences, then why does it need to be a coloring book?
> > 
> > See Spot.  See Spot run.  See Spot manage the pack's dominance hierarchy through vociferous displays of aggressive behavior.  Run, Spot, run!
> > 
> 
> Yes, good point
> 
> But why favor one aspect over another?
> 
> Also in SELinux everything is associated one way or another. If you
> leave out pieces, then you end up with loose ends. Loose end can be
> confusing
> 
> If you're comprehensive, then pieces tend to fall into place
> 
> That helps getting the overall big picture
> 

What i am suggesting here is that sometimes, what seems like a longer
route initially, may end up being the shortest route after all in my
view

I sincerely think that it is better to be comprehensive, than to cherry
pick some aspects if your aim is to provide the audience with the big
picture

Plus, i think dominance hierarchy, and "no read up/no write down" can
also be explained through simple illustrations





--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.