From: "Nerazzurri.YANG" <spng.yang@gmail.com>
To: selinux@tycho.nsa.gov
Subject: please guide me a way to study selinux in Kernel
Date: Wed, 20 Dec 2006 15:00:39 +0800 [thread overview]
Message-ID: <4588DF97.3060703@gmail.com> (raw)
In-Reply-To: <200612150142.kBF1gsHi002790@faith.austin.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030; format=flowed, Size: 702 bytes --]
hi all,
i am studying SELinux, mainly about kernel part.
but i can not find more informations about that, except
the docs in NSA website.
most of docs and websites are about user space and policy,
which is not i want now.
please guide me a way to find more informations about selinux
in linux kernel, especially in implementations
by the way, where can i get the book
<<SELinux by Example: Using Security Enhanced Linux>>
wrote by Tresys, i am in china.
thanks very much
--
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:[~2006-12-20 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 1:42 [PATCH 7/7] labeled ipsec policy changes Joy Latten
2006-12-20 7:00 ` Nerazzurri.YANG [this message]
2006-12-20 14:51 ` please guide me a way to study selinux in Kernel James Morris
2006-12-20 15:02 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2006-12-21 2:51 Nerazzurri.YANG
[not found] ` <1166702840.30579.164.camel@moss-spartans.epoch.ncsc.mil>
[not found] ` <458B3E1B.20107@gmail.com>
[not found] ` <1166792252.13969.7.camel@moss-spartans.epoch.ncsc.mil>
2006-12-25 1:35 ` Nerazzurri.YANG
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=4588DF97.3060703@gmail.com \
--to=spng.yang@gmail.com \
--cc=selinux@tycho.nsa.gov \
/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.