mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>, Kees Cook <keescook@chromium.org>
Cc: Paul Moore <paul@paul-moore.com>,
	LSM <linux-security-module@vger.kernel.org>,
	John Johansen <john.johansen@canonical.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	LKLM <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] LSM: Add /sys/kernel/security/lsm
Date: Wed, 18 Jan 2017 15:25:23 -0800	[thread overview]
Message-ID: <b0b3b1d8-ad9f-29ae-dd9b-611c2fb5ab7b@schaufler-ca.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1701190959450.23247@namei.org>

On 1/18/2017 3:00 PM, James Morris wrote:
> On Wed, 18 Jan 2017, Kees Cook wrote:
>
>> On Wed, Jan 18, 2017 at 11:22 AM, Paul Moore <paul@paul-moore.com> wrote:
>>> On Wed, Jan 18, 2017 at 7:43 AM, James Morris <jmorris@namei.org> wrote:
>>>> On Tue, 17 Jan 2017, Casey Schaufler wrote:
>>>>
>>>>> Subject: [PATCH] LSM: Add /sys/kernel/security/lsm
>>>>>
>>>>> I am still tired of having to find indirect ways to determine
>>>>> what security modules are active on a system. I have added
>>>>> /sys/kernel/security/lsm, which contains a comma separated
>>>>> list of the active secuirty modules. No more groping around
>>>>> in /proc/filesystems or other clever hacks.
>>>>>
>>>>> Unchanged from previous versions except for being updated
>>>>> to the latest security next branch.
>>>>>
>>>> Any objections to merging this?
>>>>
>>> I'm fairly certain I ack'd a prior version of this at one point ...
>>>
>>> Acked-by: Paul Moore <paul@paul-moore.com>
>> Yeah, me too.
>>
>> Acked-by: Kees Cook <keescook@chromium.org>
>>
> Casey: next time, please remember to include previous acks.

Sorry. You had said you where taking it after 4.8, but didn't.
I assumed that I was starting over. My mistake.

  reply	other threads:[~2017-01-18 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 23:42 Casey Schaufler
2017-01-18  0:25 ` John Johansen
2017-01-18 12:43 ` James Morris
2017-01-18 14:30   ` Tetsuo Handa
2017-01-18 19:22   ` Paul Moore
2017-01-18 21:01     ` Kees Cook
2017-01-18 23:00       ` James Morris
2017-01-18 23:25         ` Casey Schaufler [this message]
2017-01-18 23:29 ` James Morris
2017-01-18 23:52   ` 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=b0b3b1d8-ad9f-29ae-dd9b-611c2fb5ab7b@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=sds@tycho.nsa.gov \
    /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

all inboxes | Powered by JetHome®