From: Arnd Bergmann <arnd@arndb.de>
To: Vasiliy Kulikov <segoon@openwall.com>
Cc: linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
Andrew Morton <akpm@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC 0/5 v4] procfs: introduce hidepid=, hidenet=, gid= mount options
Date: Thu, 16 Jun 2011 10:50:27 +0200 [thread overview]
Message-ID: <201106161050.27716.arnd@arndb.de> (raw)
In-Reply-To: <1308163895-5963-1-git-send-email-segoon@openwall.com>
On Wednesday 15 June 2011, Vasiliy Kulikov wrote:
>
> This patch series adds support of procfs mount options and adds
> mount options to restrict /proc/<pid>/ directories to owners and
> /proc/<pid>/net/* to root. Additional group may be defined via
> gid=, and this group will be privileged to study others /proc/<pid>/
> and networking information.
>
> Similar features are implemented for old kernels in -ow patches (for
> Linux 2.2 and 2.4) and for Linux 2.6 in -grsecurity, but both of them
> are implemented as configure options, not cofigurable in runtime, with
> changes of gid of /proc/<pid>/, and without backward-compatible
> /proc/<pid>/net/* handling.
The patches all look good to me implementation-wise.
I have no opinion on whether it's a good idea to include the feature or not.
Arnd
next prev parent reply other threads:[~2011-06-16 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 18:51 [RFC 0/5 v4] procfs: introduce hidepid=, hidenet=, gid= mount options Vasiliy Kulikov
2011-06-16 8:50 ` Arnd Bergmann [this message]
2011-06-16 8:58 ` Vasiliy Kulikov
2011-06-16 11:40 ` Arnd Bergmann
2011-06-16 13:33 ` Vasiliy Kulikov
2011-10-30 17:09 ` richard -rw- weinberger
2011-06-21 22:31 ` Andrew Morton
2011-06-22 6:45 ` Vasiliy Kulikov
2011-06-22 10:17 ` Vasiliy Kulikov
2011-06-29 19:16 ` Vasiliy Kulikov
2011-07-06 11:25 ` Alexey Dobriyan
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=201106161050.27716.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=segoon@openwall.com \
/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