From: "Anthony G. Basile" <basile@opensource.dyc.edu>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] SELinux Policy development guide
Date: Mon, 25 Apr 2011 06:42:55 -0400 [thread overview]
Message-ID: <4DB5502F.7040206@opensource.dyc.edu> (raw)
In-Reply-To: <4DB44B64.5050808@giz-works.com>
On 04/24/2011 12:10 PM, Chris Richards wrote:
> On 04/23/2011 06:37 AM, Sven Vermeulen wrote:
>> 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.
> Looks like a good start to me. Off hand, I can't see anything to add.
>> 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
>>
>>
>
An impressive amount of work! Thanks.
--
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197
prev parent reply other threads:[~2011-04-25 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 11:37 [gentoo-hardened] SELinux Policy development guide Sven Vermeulen
2011-04-24 16:10 ` Chris Richards
2011-04-25 10:42 ` Anthony G. Basile [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=4DB5502F.7040206@opensource.dyc.edu \
--to=basile@opensource.dyc.edu \
--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