From: Russell Coker <russell@coker.com.au>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Stephen D. Smalley" <sds@epoch.ncsc.mil>,
linux-kernel@vger.kernel.org, linux-security-module@wirex.com
Subject: Re: [RFC][PATCH] Add LSM sysctl hook to 2.5.59
Date: Mon, 20 Jan 2003 02:05:41 +0100 [thread overview]
Message-ID: <200301200205.41049.russell@coker.com.au> (raw)
In-Reply-To: <20030120004320.A10659@infradead.org>
On Mon, 20 Jan 2003 01:43, Christoph Hellwig wrote:
> On Mon, Jan 20, 2003 at 01:39:39AM +0100, Russell Coker wrote:
> > > What's the reason you can't just live with DAC for sysctls?
> >
> > What exactly do you mean by "live with DAC" in this context? If you mean
> > "allow UID==0 processes to do whatever they like" then it's not going to
> > work for any sort of chroot setup.
>
> This means check the unix file permissions / ACLs only overriden by
> CAP_FOWNER processes.
I don't think that would do for my chroot environments. I want to have root
owned processes running in a chroot with no ability to escape or to affect
the outside environment (and proc is mounted in the chroot).
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
next prev parent reply other threads:[~2003-01-20 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 21:54 Stephen D. Smalley
2003-01-20 0:08 ` Christoph Hellwig
2003-01-20 0:39 ` Russell Coker
2003-01-20 0:43 ` Christoph Hellwig
2003-01-20 1:05 ` Russell Coker [this message]
2003-01-21 14:51 Stephen D. Smalley
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=200301200205.41049.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
/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®