From: Arnd Bergmann <arnd@arndb.de>
To: Richard Weinberger <richard@nod.at>
Cc: Kees Cook <kees.cook@canonical.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
serge@hallyn.com, eparis@redhat.com, jmorris@namei.org,
eugeneteo@kernel.org, drosenberg@vsecurity.com,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] [RFC] Make it easier to harden /proc/
Date: Wed, 16 Mar 2011 22:03:59 +0100 [thread overview]
Message-ID: <201103162204.00031.arnd@arndb.de> (raw)
In-Reply-To: <201103162152.49615.richard@nod.at>
On Wednesday 16 March 2011 21:52:49 Richard Weinberger wrote:
> Am Mittwoch 16 März 2011, 21:45:45 schrieb Arnd Bergmann:
> > How does this interact with the per-namespace sysctls that Eric
> > Biederman added a few years ago?
>
> Do you mean CONFIG_{UTS, UPC, USER, NET,}_NS?
I mean specifically e51b6ba07 "sysctl: Infrastructure for per namespace sysctls"
and related patches. I've looked a bit closer there and it seems that
this is only used for network namespaces at the moment.
> > I had expected that any dangerous sysctl would not be visible in
> > an unpriviledge container anyway.
>
> No way.
> That's why it's currently a very good idea to mount /proc/ read-only into a container.
Ok, I see.
Arnd
next prev parent reply other threads:[~2011-03-16 21:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 19:31 [PATCH] [RFC] Make it easier to harden /proc/ Richard Weinberger
2011-03-16 19:55 ` Kees Cook
2011-03-16 20:08 ` Richard Weinberger
2011-03-16 20:45 ` Arnd Bergmann
2011-03-16 20:52 ` Richard Weinberger
2011-03-16 21:03 ` Arnd Bergmann [this message]
2011-03-16 21:04 ` Alexey Dobriyan
2011-03-16 21:07 ` Richard Weinberger
2011-03-16 21:15 ` Alexey Dobriyan
2011-03-17 10:14 ` Miquel van Smoorenburg
2011-03-17 10:57 ` Richard Weinberger
2011-03-16 21:17 ` Eric W. Biederman
2011-03-16 21:23 ` Richard Weinberger
2011-03-16 21:27 ` Eric W. Biederman
2011-03-17 6:41 ` Kees Cook
2011-03-17 7:30 ` Richard Weinberger
2011-03-16 21:19 ` Alexey Dobriyan
2011-03-17 16:51 ` Eric W. Biederman
2011-03-19 10:43 ` Richard Weinberger
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=201103162204.00031.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=drosenberg@vsecurity.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=eugeneteo@kernel.org \
--cc=jmorris@namei.org \
--cc=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=serge@hallyn.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