All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Yao <yffbrave@163.com>
Cc: SELinux@tycho.nsa.gov
Subject: Re: about ss
Date: Fri, 18 Mar 2011 10:02:58 -0400	[thread overview]
Message-ID: <1300456978.25429.29.camel@moss-pluto> (raw)
In-Reply-To: <3030f704.11efc.12ec66a93b9.Coremail.yffbrave@163.com>

On Fri, 2011-03-18 at 08:43 +0800, Yao wrote:
> Hi, all
> I looked at linux-2.6.36/security/selinux/ss/*.c and found most source
> files include <linux/***.h>
> I know security server need to use some of kernel data structures.
> But does ss use kernel fuctions?
> Is it possible to modify security server and make it self-contained if
> ss used kernel function?

The original security server code was developed for another OS
(Fluke/Flask) and then ported to Linux.  There are a small number of
fundamental dependencies on the runtime environment, like memory
allocation, logging/auditing, locking, etc.  Over time, the security
server code in Linux has become increasingly "nativized" for Linux so
you may find further dependencies in the current code.

You'll find other forms of the security server code that may be more
portable in:
1) The SELinux userspace (http://userspace.selinuxproject.org)
In particular, a copy of the security server code lives in libsepol.
Originally there was a single code base shared between
checkpolicy/libsepol and the kernel, but this was forked when SELinux
went into mainline.

2) The OSKit (http://www.cs.utah.edu/flux/oskit/)
This was used in Fluke/Flask.  Security server is under security/, AVC
is in com/avc.c.

3) Various ports of SELinux to other systems
(http://www.nsa.gov/research/selinux/related.shtml)

-- 
Stephen Smalley
National Security Agency


--
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:[~2011-03-18 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18  0:43 about ss Yao
2011-03-18 14:02 ` Stephen Smalley [this message]
2011-03-21  3:11   ` Yao
2011-03-21  8:31     ` Kohei Kaigai
2011-03-21 12:29     ` Stephen Smalley
2011-03-23  1:10       ` Yao
2011-03-23 13:24         ` Stephen Smalley
2011-03-25  6:11           ` Yao
2011-03-25 12:43             ` Stephen Smalley
2011-03-28  0:55               ` Yao
2011-03-28 12:49                 ` Stephen Smalley

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=1300456978.25429.29.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=SELinux@tycho.nsa.gov \
    --cc=yffbrave@163.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.