From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: selinux@tycho.nsa.gov
Cc: sakaia@jp.fujitsu.com
Subject: README in libselinux
Date: Thu, 30 Oct 2008 13:16:27 +0900 [thread overview]
Message-ID: <4909351B.5090805@ak.jp.nec.com> (raw)
Hi,
I got a question on the secure os users mailing-list in Japan.
He said that he is interested in sVirt patches but not good at the way
to apply the security policy of SELinux on userspace object manager, so
it makes him hesitate to comment for the patches.
We know great manpages are provided yet, but a structured documentation
to implement SELinux aware userspace object managers is not well known.
It is not unclear whether it should be included within README, or not.
However, an official guidance for developers should be considered.
Any comment?
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
--
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 reply other threads:[~2008-10-30 4:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 4:16 KaiGai Kohei [this message]
2008-10-30 14:33 ` README in libselinux Stephen Smalley
2008-10-30 18:46 ` Eamon Walsh
2008-10-30 19:04 ` Eamon Walsh
2008-10-31 9:17 ` KaiGai Kohei
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=4909351B.5090805@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=sakaia@jp.fujitsu.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.