From: Casey Schaufler <casey@schaufler-ca.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: eparis@redhat.com, jmorris@namei.org,
linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov,
john.johansen@canonical.com, keescook@chromium.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [PATCH v10] LSM: Multiple concurrent LSMs
Date: Thu, 13 Dec 2012 08:38:45 -0800 [thread overview]
Message-ID: <50CA0495.2060706@schaufler-ca.com> (raw)
In-Reply-To: <201212132106.AFI82338.QMFHFLSJOtOOFV@I-love.SAKURA.ne.jp>
On 12/13/2012 4:06 AM, Tetsuo Handa wrote:
> Casey Schaufler wrote:
>> You're suggesting that we don't change the kernel until the
>> applications are fixed. No one is going to change the applications
>> until the kernel is fixed.
> People *can* change the applications before the kernel is changed if clear
> specification is provided. That's why my approach has migration period.
Of course they *can*, they just *won't*. The whole discussion
is based on the fact that people resist change so strenuously.
>> I have also added LSM identified files in /proc/.../attr:
>>
>> /proc/.../attr/current
>> /proc/.../attr/selinux.current
>> /proc/.../attr/apparmor.current
>> /proc/.../attr/keycreate
>> /proc/.../attr/selinux.keycreate
>>
>> SELinux applications and libraries can use simple logic to determine
>> what to do:
>>
>> if /sys/kernel/security/lsm does not contain "selinux"
>> Stop! No SELinux here!
>> if /sys/kernel/security/present does not contain "selinux"
>> Use selinux.current
>> else
>> Use current if you like.
>>
> Can we use prctl() interface instead of /proc/$pid/attr/$lsmname.$type ?
> I simply don't want to see flood of entries when "find /proc/" runs. ;-)
That cat is so long out of the bag that it's been adopted and spayed.
>
> prctl() can tell the caller whether specified LSM is enabled/presented or not
> via its return value.
>
> I think we can provide a simple utility that maps
>
> echo something > /proc/pid/attr/selinux.current
>
> to
>
> prctl(PR_SET_SECURITY, pid, "selinux", "current", "something")
>
> and
>
> cat /proc/pid/attr/selinux.current
>
> to
>
> prctl(PR_GET_SECURITY, pid, "selinux", "current", buffer)
>
> for calling prctl() from script programs.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2012-12-13 16:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50C65DE2.5090909@schaufler-ca.com>
[not found] ` <201212112128.ADI26010.OQJVLOFSOFtHMF@I-love.SAKURA.ne.jp>
2012-12-11 15:31 ` [PATCH v10] LSM: Multiple concurrent LSMs Casey Schaufler
[not found] ` <201212122159.CEC09839.HMOFtQFLJSVFOO@I-love.SAKURA.ne.jp>
2012-12-12 15:48 ` Casey Schaufler
2012-12-12 15:55 ` Eric Paris
2012-12-12 16:24 ` Casey Schaufler
2012-12-12 16:33 ` Eric Paris
2012-12-12 17:04 ` Casey Schaufler
2012-12-12 17:11 ` Eric Paris
[not found] ` <CAGXu5jLf+apZK5poD6GKzLkC+p6+mAqKhU3neoOZjr2JumvmpA@mail.gmail.com>
2012-12-12 17:22 ` Eric Paris
2012-12-12 17:31 ` Casey Schaufler
2012-12-12 17:47 ` Eric Paris
2012-12-12 18:25 ` Casey Schaufler
2012-12-12 18:47 ` Eric Paris
2012-12-12 20:46 ` Casey Schaufler
2012-12-12 20:51 ` Eric Paris
2012-12-12 22:01 ` Casey Schaufler
[not found] ` <201212132106.AFI82338.QMFHFLSJOtOOFV@I-love.SAKURA.ne.jp>
2012-12-13 16:12 ` Eric Paris
2012-12-13 16:31 ` Casey Schaufler
[not found] ` <CAGXu5jJf4NEvs6TjVCBxgd9e8cGwag_-viEntgTBUq85fULr8w@mail.gmail.com>
2012-12-16 3:06 ` Casey Schaufler
[not found] ` <201212142326.DDG90674.SFHFMOOVLFJtQO@I-love.SAKURA.ne.jp>
2012-12-14 15:07 ` Eric Paris
2012-12-13 16:38 ` 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=50CA0495.2060706@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=selinux@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 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.