From: Casey Schaufler <casey@schaufler-ca.com>
To: zhou peng <ailvpeng25@gmail.com>
Cc: linux-security-module@vger.kernel.org,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: About ACL for IPC Object
Date: Wed, 20 Jan 2010 19:02:27 -0800 [thread overview]
Message-ID: <4B57C3C3.9010606@schaufler-ca.com> (raw)
In-Reply-To: <6fb445941001200120m3aa5e944j54a6f645ce82d76f@mail.gmail.com>
zhou peng wrote:
> Hi all,
>
> There are ACL in file system, but why there are no ACL implementation
> in IPC object, eg. shm, message queue, FIFO?
>
Most people haven't noticed that IPC objects are even there, much less
that they have mode bits and not ACLs. Even when we were doing security
evaluations on Unix boxes in the 1990's they were considered insufficiently
interesting to justify the additional work to do ACLs.
If you really want ACLs on IPC objects it would make a dandy little
project for a summer. I would be happy to review patches.
> Is there any fine grained granting in ipc object just like in file object?
>
As Stephen Smalley points out, you can do it with SELinux, although
that it rather like driving a thumbtack with a bulldozer.
> Thanks,
> Best
>
> --
> zhoupeng
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next prev parent reply other threads:[~2010-01-21 3:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6fb445941001200112o2934f805l4eb4f78000e9527e@mail.gmail.com>
2010-01-20 9:20 ` About ACL for IPC Object zhou peng
2010-01-20 21:50 ` Jeremy Allison
2010-01-20 22:00 ` Jeremy Allison
2010-01-21 3:02 ` Casey Schaufler [this message]
2010-01-21 9:05 ` Christoph Hellwig
2010-01-22 9:15 ` zhou peng
2010-01-22 10:02 ` Américo Wang
2010-01-25 15:21 ` zhou peng
2010-01-25 16:26 ` Américo Wang
2010-03-23 9:01 ` zhou peng
2010-03-23 11:55 ` Christoph Hellwig
2010-03-24 0:17 ` 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=4B57C3C3.9010606@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=ailvpeng25@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).