From: Florian Weimer <fweimer@redhat.com>
To: oss-security@lists.openwall.com
Cc: Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [oss-security] Summary of security bugs (now fixed) in user namespaces
Date: Tue, 16 Apr 2013 14:19:17 +0200 [thread overview]
Message-ID: <516D41C5.9080009@redhat.com> (raw)
In-Reply-To: <CALCETrX6Rcv1uMfPdG=K6THusgx-CAjHRkUpMwruBNaZGDvb8Q@mail.gmail.com>
On 04/13/2013 07:16 PM, Andy Lutomirski wrote:
> I previously reported these bugs privatley. I'm summarizing them for
> the historical record. These bugs were never exploitable on a
> default-configured released kernel, but some 3.8 versions are
> vulnerable depending on configuration.
Looking at this list, is there some way to restrict this new
functionality to, say, membership in a certain group? At present, most
system users (daemons) do not need this functionality, so it would make
sense to restrict access to it.
Or is the expectation that we disable CONFIG_USER_NS until things
stabilize further?
--
Florian Weimer / Red Hat Product Security Team
prev parent reply other threads:[~2013-04-16 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 17:16 Summary of security bugs (now fixed) in user namespaces Andy Lutomirski
2013-04-16 12:19 ` Florian Weimer [this message]
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=516D41C5.9080009@redhat.com \
--to=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oss-security@lists.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