From: "S. Lockwood-Childs" <sjl@dent.vctlabs.com>
To: gentoo-hardened@lists.gentoo.org
Subject: [gentoo-hardened] Feedback on article recommending Gentoo for SELinux
Date: Sun, 12 Jul 2015 16:46:03 -0700 [thread overview]
Message-ID: <20150712234603.GQ2951@dent.vctlabs.com> (raw)
I'd appreciate feedback on a blog-style article[1] talking about
how CIL is going to improve SELinux policy maintenance, and in
particular, the last section where I try to point out how good Gentoo
is for experimenting with SELinux technologies. The article is
maintained as an rst file in github[2], so corrections/additions
could be submitted as a pull request if desired (though plain old
mailing list replies are equally welcome).
[1] http://vctlabs.com/posts/2015/Jul/12/selinux_cil/
[2] https://github.com/VCTLabs/vct-web/blob/master/content/articles/selinux_cil.rst
next reply other threads:[~2015-07-12 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 23:46 S. Lockwood-Childs [this message]
2015-07-13 11:31 ` [gentoo-hardened] Feedback on article recommending Gentoo for SELinux Jason Zaman
2015-07-13 13:02 ` Sven Vermeulen
2015-07-13 13:51 ` Jason Zaman
2015-07-13 16:50 ` Sven Vermeulen
2015-07-13 17:02 ` Sven Vermeulen
2015-07-15 5:35 ` S. Lockwood-Childs
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=20150712234603.GQ2951@dent.vctlabs.com \
--to=sjl@dent.vctlabs.com \
--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