All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaspreet Singh <jsingh@ensim.com>
To: Andreas Hasenack <andreas@conectiva.com.br>
Cc: nsa <SELinux@tycho.nsa.gov>
Subject: Re: Selinux book: based on 2.4 or 2.6?
Date: Fri, 26 Nov 2004 10:30:42 +0530	[thread overview]
Message-ID: <1101445242.21913.6.camel@jsingh> (raw)
In-Reply-To: <20041125122713.GJ15141@conectiva.com.br>

Hi, 


> So, a book for administrators (which is good).
> 

actually more than that .. after reading the book you can not only
understand the policies but write your custom stuff ... and also
understand how kernel intercepts these security calls (but this info is
not enough for those who want to understand flask implementation)


Thanx
Jaspreet




--
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:[~2004-11-26  5:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:03 Selinux book: based on 2.4 or 2.6? Andreas
2004-11-23 20:47 ` Eric Andreychek
2004-11-25  6:54 ` Jaspreet Singh
2004-11-25 12:27   ` Andreas Hasenack
2004-11-26  5:00     ` Jaspreet Singh [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=1101445242.21913.6.camel@jsingh \
    --to=jsingh@ensim.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=andreas@conectiva.com.br \
    /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.