Linux Container Development
 help / color / mirror / Atom feed
From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman)
To: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
Cc: Seth Forshee
	<seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
	Linux Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	Andy Lutomirski <luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org>
Subject: Re: User namespace feature freeze lifted
Date: Tue, 15 Sep 2015 13:05:38 -0500	[thread overview]
Message-ID: <874mivd0ct.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20150915173633.GD4699@ubuntumail> (Serge Hallyn's message of "Tue, 15 Sep 2015 17:36:33 +0000")

Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org> writes:

> Quoting Eric W. Biederman (ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org):
>> 
>> As of v4.3-rc1 all of the security issues I am aware of with the user
>> namespace have been addressed.  If someone knows of something I have
>> overlooked please let me know.
>> 
>> As much as humanly possible I want to avoid security bugs in the future
>> so I will endeavour to ensure any future user namespace patches receive
>> a close review.
>> 
>> As for merging features I expect I will likley start with Seth's code
>> for associating superblock with user namespaces, and then move on to
>> Lukasz's code for figuring out how to add namespace for smack.
>
> Should there be a User Namespace maintainer?

Do you mean documented in maintainers?  Last I cheked I am wearing
the user namespace maintainer hat.

Eric

  reply	other threads:[~2015-09-15 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 17:27 User namespace feature freeze lifted Eric W. Biederman
     [not found] ` <87io7bd23x.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-09-15 17:36   ` Serge Hallyn
2015-09-15 18:05     ` Eric W. Biederman [this message]
     [not found]       ` <874mivd0ct.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-09-15 18:44         ` Serge E. Hallyn
2015-09-15 18:23   ` Seth Forshee

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=874mivd0ct.fsf@x220.int.ebiederm.org \
    --to=ebiederm-as9lmozglivwk0htik3j/w@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=luto-kltTT9wpgjJwATOyAt5JVQ@public.gmane.org \
    --cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
    --cc=seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
    /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