From: Andy Spencer <andy753421@gmail.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Privilege dropping security module
Date: Wed, 23 Sep 2009 22:31:10 +0000 [thread overview]
Message-ID: <20090923223110.GA1449@c.hsd1.tn.comcast.net> (raw)
In-Reply-To: <4ABA892A.9090804@schaufler-ca.com>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
> Hi Andy. Git is a wonderful tool, but if you want people to review
> your work you need to post patches.
Thanks for letting me know, I've posted a separate message with patch.
> And what do you propose as an interesting use case for dpriv?
I think the two most important things about dpriv is that it can be used
by ordinary users and that is can create policies programmatically.
Being able to use dpriv as a non root user is pretty strait forward. For
example, a user of a multi-user system may want to try some untrusted
code without risking access to the rest of the system:
$ cd ~/my_project
$ echo rxRX / > /sys/kernel/security/dpriv/stage
$ echo X $HOME > /sys/kernel/security/dpriv/stage
$ echo rwxRWX $HOME/my_project > /sys/kernel/security/dpriv/stage
$ echo commit > /sys/kernel/security/dpriv/control
$ patch < untrusted.patch
$ make && ./src/some_exe
The above example also demonstrates how dpriv can be used
programmatically. That is, a policy for allowing read-write-exec access
to build and test tools in ~/my_project didn't have to exist ahead of
time.
A more realistic example might be for a virtual hosting web server where
you want apache to only have access to the files for the current virtual
host.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-09-23 22:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 0:56 Andy Spencer
2009-09-23 20:46 ` Casey Schaufler
2009-09-23 22:31 ` Andy Spencer [this message]
2009-09-23 23:03 ` Tetsuo Handa
2009-09-24 16:37 ` David Wagner
2009-09-25 7:22 ` Andy Spencer
2009-09-25 20:48 ` David Wagner
2009-09-26 21:09 ` Andy Spencer
2009-09-27 0:28 ` David Wagner
2009-10-01 7:38 ` Pavel Machek
2009-10-01 9:15 ` Andy Spencer
2009-10-01 10:42 ` Pavel Machek
2009-09-23 21:31 ` [RFC][PATCH] " Andy Spencer
2009-09-24 16:25 ` Casey Schaufler
2009-09-25 10:06 ` Andy Spencer
2009-09-25 16:23 ` Casey Schaufler
2009-09-26 21:35 ` Andy Spencer
2009-09-28 5:38 ` Rob Meijer
2009-09-25 21:00 ` David Wagner
2009-09-29 7:36 ` Andy Spencer
2009-09-29 7:10 ` [RFC][PATCH] Permission masking security module (was dpriv) Andy Spencer
2009-09-29 17:44 ` Greg KH
2009-09-30 0:18 ` Andy Spencer
2009-10-01 2:33 ` 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=20090923223110.GA1449@c.hsd1.tn.comcast.net \
--to=andy753421@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®