From: Dominick Grift <dominick.grift@gmail.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Tony Scully <tonyjscully@gmail.com>,
Daniel J Walsh <dwalsh@redhat.com>,
Community support for Fedora users
<users@lists.fedoraproject.org>,
Fedora SELinux Users <selinux@lists.fedoraproject.org>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux Coloring book?
Date: Wed, 13 Nov 2013 18:35:10 +0100 [thread overview]
Message-ID: <1384364110.30406.53.camel@d30> (raw)
In-Reply-To: <20131113171326.GA13491@wolff.to>
On Wed, 2013-11-13 at 11:13 -0600, Bruno Wolff III wrote:
> On Wed, Nov 13, 2013 at 17:10:43 +0000,
> Tony Scully <tonyjscully@gmail.com> wrote:
> >That's excellent!
>
> The mls case might have been overly simplified. It didn't cover writing,
> where the dominance goes in the other direction. People might be incorrectly
> left with the impression the top secret can do everything that secret
> can do.
> --
I agree with you on the danger of oversimplification in generel with
regard to explaining SELinux
This is also why i find it sub-optimal to leave the two other default
security models out of the equation (RBAC/IBAC)
It is mentioned in the article that SELinux complements Linux security,
by briefly touching on IBAC one would clarify at least to some degree
how SELinux associates with Linux security
RBAC by itself is worth mentioning in my view, if only to have touched
on each security attribute in a security context tuple.
The idea of the illustrated article is nice, but the article is not
comprehensive.
Granted, there are constraints. You cannot simply publish a three page
article on a medium like this i suspect
--
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.
next prev parent reply other threads:[~2013-11-13 17:35 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 [this message]
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
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=1384364110.30406.53.camel@d30 \
--to=dominick.grift@gmail.com \
--cc=bruno@wolff.to \
--cc=dwalsh@redhat.com \
--cc=selinux@lists.fedoraproject.org \
--cc=selinux@tycho.nsa.gov \
--cc=tonyjscully@gmail.com \
--cc=users@lists.fedoraproject.org \
/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.