From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] SELinux Policy development guide
Date: Sat, 23 Apr 2011 13:37:29 +0200 [thread overview]
Message-ID: <20110423113729.GA31345@siphos.be> (raw)
Hi all,
One of the requests from this weeks' meeting was a document covering the
SELinux development (tips and tricks, guidelines, whatever) so that
interested developers or advanced users can help us out further with the
development.
I've made a first attempt at writing such a document. It is available in
hardened-doc.git, the preview can be seen online at http://goo.gl/weI8p (if
you still notice TODOs, add "&1" or so to the URL as your browser is still
caching the document).
Comments and feedback is always appreciated.
Also, selinux-faq.xml has been updated yesterday as well, adding two more
FAQs. One is about rlpkg complaining about conflicting types, the other one
is about portage complaining about libsandbox.so not being loaded.
FAQ preview at http://goo.gl/uaaf4
Wkr,
Sven Vermeulen
next reply other threads:[~2011-04-23 12:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 11:37 Sven Vermeulen [this message]
2011-04-24 16:10 ` [gentoo-hardened] SELinux Policy development guide Chris Richards
2011-04-25 10:42 ` Anthony G. Basile
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=20110423113729.GA31345@siphos.be \
--to=sven.vermeulen@siphos.be \
--cc=gentoo-hardened@lists.gentoo.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox