From: Casey Schaufler <casey@schaufler-ca.com>
To: SELinux <Selinux@tycho.nsa.gov>,
LSM <linux-security-module@vger.kernel.org>
Subject: Functions prefixed with security_ in SELinux
Date: Thu, 09 Oct 2014 10:55:32 -0700 [thread overview]
Message-ID: <5436CC14.2040906@schaufler-ca.com> (raw)
As I've been working on the multiple concurrent modules project I have
frequently encountered the use of the function prefix security_ in
SELinux specific code. I understand and appreciate that this code has
been there since the dawn of time. The LSM infrastructure also uses this
prefix, and that's where I have my concern. When I'm grubbing about for
uses of the LSM infrastructure in the SELinux code it's really quite
annoying. Would the SELinux community be open to considering the
possibility of thinking about cleaning up this bit of namespace
pollution? It surely isn't a critical issue, but it would certainly look
better.
security_context_to_sid -> selinux_context_to_sid
Just a thought.
next reply other threads:[~2014-10-09 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 17:55 Casey Schaufler [this message]
2014-10-24 19:49 ` Functions prefixed with security_ in SELinux Paul Moore
2014-10-24 21:33 ` Casey Schaufler
2014-10-25 16:45 ` Paul Moore
2014-10-26 0:26 ` Casey Schaufler
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=5436CC14.2040906@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=Selinux@tycho.nsa.gov \
--cc=linux-security-module@vger.kernel.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 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.