All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <dominick.grift@gmail.com>
To: "Radzykewycz, T (Radzy)" <radzy@windriver.com>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Bruno Wolff III <bruno@wolff.to>,
	Tony Scully <tonyjscully@gmail.com>,
	SELinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux Coloring book?
Date: Thu, 14 Nov 2013 12:55:13 +0100	[thread overview]
Message-ID: <1384430113.6663.35.camel@d30> (raw)
In-Reply-To: <33006C99F5A5194A9B7A7715DFA3E383B53C2366@ALA-MBB.corp.ad.wrs.com>

On Wed, 2013-11-13 at 20:58 +0000, Radzykewycz, T (Radzy) wrote:
> Yes, I don't disagree with anything you've said.
> 
> My point is that this is supposed to be simple and easy-to-understand.  It's intended (I think) to address the complaint that many people have, that SE Linux is too complex, which I'm sure you've all heard.
> 
> If it gets too complex, then people will stop reading, and just continue with their current pre-conception that it's "too hard."  If that happens, then the effort to put it together is wasted.  I don't want that.  I would prefer if this allows people to get past their "too hard" ideas.  And all complexity that is added makes that more probable.  Even the goal of addressing the big picture, at all, makes it more complex.
> 
> If a kid is learning "see spot" then the idea of a pack dominance hierarchy is advanced material, as is mention of displays of aggressive behavior.  To say nothing of the mere word "vociferous."  The pack dominance hierarchy and descriptions of behavior are necessary for the big picture, but they aren't basic introductory material.
> 
> I don't think there isn't room for improvement.  I just hope that trying for the big picture confuses more people than it needs to, especially since too many people already think it's too complex.
> 
> I also think that it's pretty good, as it is right now, for what it is trying to do.  So: kudos to the authors!  :)
> 

Sure i like the article as well, and i also think there is room for
improvement.

The articles title is one of those areas. It was the main reason for my
reply. I do not believe that the title reflects the contents accurately.

If the title would be something like ...

"Your visual teaser for SELinux policy enforcement"

... Then in my mind there would be no doubt that the article achieved
its goal.


--
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.

  parent reply	other threads:[~2013-11-14 11:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 15:10 SELinux Coloring book? Daniel J Walsh
2013-11-13 16:00 ` Paul Howarth
2013-11-13 16:11   ` Daniel J Walsh
     [not found] ` <CAKuJGC9FTi__fc6+4O9nViDiCnT-+xrsFvR+E4FXAfML8x+QSQ@mail.gmail.com>
2013-11-13 17:13   ` leo kirotawa
     [not found] ` <1bddae0010527398cc85d89bb8f1aad9.squirrel@host290.hostmonster.com>
     [not found]   ` <CAMk6u_TUztYjqUTFCd5ukcHWOYt=cJaJv2ARvw-RafcVAAVUQw@mail.gmail.com>
     [not found]     ` <20131113171326.GA13491@wolff.to>
2013-11-13 17:35       ` Dominick Grift
2013-11-13 18:10         ` Daniel J Walsh
2013-11-13 18:37           ` Radzykewycz, T (Radzy)
2013-11-13 19:01             ` Dominick Grift
2013-11-13 19:25               ` Dominick Grift
2013-11-13 20:58                 ` Radzykewycz, T (Radzy)
2013-11-14  1:48                   ` Casey Schaufler
2013-11-14 11:55                   ` Dominick Grift [this message]
2013-11-13 18:07       ` Daniel J Walsh

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=1384430113.6663.35.camel@d30 \
    --to=dominick.grift@gmail.com \
    --cc=bruno@wolff.to \
    --cc=dwalsh@redhat.com \
    --cc=radzy@windriver.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=tonyjscully@gmail.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 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.