From: Christoph Hellwig <hch@infradead.org>
To: "Stephen D. Smalley" <sds@epoch.ncsc.mil>
Cc: 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 00:08:53 +0000 [thread overview]
Message-ID: <20030120000853.A9023@infradead.org> (raw)
In-Reply-To: <200301172154.QAA00757@moss-shockers.ncsc.mil>; from sds@epoch.ncsc.mil on Fri, Jan 17, 2003 at 04:54:37PM -0500
On Fri, Jan 17, 2003 at 04:54:37PM -0500, Stephen D. Smalley wrote:
>
> This patch adds a LSM sysctl hook for controlling access to
> sysctl variables to 2.5.59, split out from the lsm-2.5 BitKeeper tree.
> SELinux uses this hook to control such accesses in accordance with the
> security policy configuration.
I'm not very happy with this hook. This means every single security
module needs a list of all sensitive sysctl variables, i.e. we duplicate
information in (possible a large number of) different places.
What's the reason you can't just live with DAC for sysctls?
next prev parent reply other threads:[~2003-01-19 23:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 21:54 [RFC][PATCH] Add LSM sysctl hook to 2.5.59 Stephen D. Smalley
2003-01-20 0:08 ` Christoph Hellwig [this message]
2003-01-20 0:39 ` Russell Coker
2003-01-20 0:43 ` Christoph Hellwig
2003-01-20 1:05 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
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=20030120000853.A9023@infradead.org \
--to=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