All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Shaz <shazalive@gmail.com>
Cc: "Sutton, Harry (MSE)" <harry.sutton@hp.com>,
	Joshua Kramer <josh@globalherald.net>,
	"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: O'Rielly SELinux Book (2005)
Date: Wed, 28 Jan 2009 00:44:19 -0800	[thread overview]
Message-ID: <49801AE3.4070605@gmail.com> (raw)
In-Reply-To: <7b740b700901272331qed57282i5955e6ac09bf3d90@mail.gmail.com>

Shaz wrote:
> And to stay up to date with the commands and infrastructure than you 
> would like to go for Fedora SELinux guide. It might as well give you 
> partial details on the design of SELinux, although SELinux by Example 
> has a very clear description of the design in its first section. 
> Policy models are discussed in section 2.
>
> On Wed, Jan 28, 2009 at 12:44 AM, Sutton, Harry (MSE) 
> <harry.sutton@hp.com <mailto:harry.sutton@hp.com>> wrote:
>
>     Hi Josh,
>
>     I found that to be one of the (few) O'Reilly books that didn't really
>     cut it for me on its stated subject matter; my preference is
>     Prentice-Hall's "SELinux by Example, Using Security Enhanced
>     Linux", by
>     Frank Mayer, Karl MacMillan and David Caplan (ISBN 0-13-196369-4).
>     It's
>     a much clearer (and more comprehensive) treatment of the theory in
>     depth
>     you're asking for.
>
>     Best regards,
>
>        /Harry Sutton, RHCA / RHCSS
>         Hewlett-Packard Company
>
>     Joshua Kramer wrote:
>     > Howdy Folks,
>     >
>     > I have a copy of the O'Rielly SELinux book from 2005.
>     >
>     > Many things have changed as far as the implementation and practice.
>     > However, is this still a good book to read if I just want to
>     learn the
>     > theory in-depth?  Or have basic elements of SELinux changed
>     since then?
>     >
>     > Thanks!
>     > -Josh
>     >
>     >
>
>
>
>
> -- 
> Shaz
>
In any case(from my point of view) seeing any  info
about SELinux is nice to see.
hopefully more people adopt the policy.
eventually(hopefully) this will be a something that
every system adopts;

regards;

Justin P. Mattock,



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

      reply	other threads:[~2009-01-28  8:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 17:31 O'Rielly SELinux Book (2005) Joshua Kramer
2009-01-27 19:44 ` Sutton, Harry (MSE)
2009-01-27 20:40   ` Enabling the "noatime" option on filesystems Hasan Rezaul-CHR010
2009-01-27 21:54     ` James Morris
2009-01-28  7:31   ` O'Rielly SELinux Book (2005) Shaz
2009-01-28  8:44     ` Justin P. Mattock [this message]

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=49801AE3.4070605@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=harry.sutton@hp.com \
    --cc=josh@globalherald.net \
    --cc=selinux@tycho.nsa.gov \
    --cc=shazalive@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.