All of lore.kernel.org
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: Paul Moore <paul@paul-moore.com>
Cc: LSM <linux-security-module@vger.kernel.org>,
	SELinux <Selinux@tycho.nsa.gov>
Subject: Re: Functions prefixed with security_ in SELinux
Date: Sat, 25 Oct 2014 17:26:26 -0700	[thread overview]
Message-ID: <544C3FB2.2010308@schaufler-ca.com> (raw)
In-Reply-To: <CAHC9VhQ37HsMqyxGSgtPN07QUn6J2mJXBQy6RQZD1FnbzunV9Q@mail.gmail.com>

On 10/25/2014 9:45 AM, Paul Moore wrote:
> On Fri, Oct 24, 2014 at 5:33 PM, Casey Schaufler <casey@schaufler-ca.com> wrote:
>> Would you consider patches that address this as part of the Multiple
>> LSM work? I wouldn't be doing the security server integration as that
>> would be outside the scope of the effort, but I consider the namespace
>> issue to be in scope. I won't bother if you aren't open to it.
> No, sadly I think a rename patch would need to be part of a larger
> cleanup/integration effort; otherwise it just looks like a lot of
> churn for minimal benefit.  I understand that is probably looks
> significant within the work you are doing to stack LSMs, but
> considering how rare/unique that work is, I don't think this is
> problem many people are likely to run into on a regular basis.

OK, I shan't worry about it. I suspect that I'm the only person
on the planet likely to be bothered especially much by it, and I
do have enough other kittens to fry.

      reply	other threads:[~2014-10-26  0:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 17:55 Functions prefixed with security_ in SELinux Casey Schaufler
2014-10-24 19:49 ` Paul Moore
2014-10-24 21:33   ` Casey Schaufler
2014-10-25 16:45     ` Paul Moore
2014-10-26  0:26       ` Casey Schaufler [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=544C3FB2.2010308@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=Selinux@tycho.nsa.gov \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    /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.